vrising tail: invalid PID: '' when launching

[KingPin]

Docker Version: 24.0.2 Host OS : Ubuntu 22.04

  V-Rising:
    container_name: V-Rising
    image: ich777/steamcmd:vrising
    restart: unless-stopped
    environment:
      - GAME_ID=1829350
      - SERVER_NAME=zzzzz
      - WORLD_NAME=xxxx
      - UID=1001
      - GID=1001
      - ENABLE_BEPINEX=true
    volumes:
      - ./server:/serverdata/steamcmd
      - ./data:/serverdata/serverfiles
    ports:
      - '9876-9877:9876-9877/udp'

when launching I get the error :

vrising  | ---Checking if WINE workdirectory is present---
vrising  | ---WINE workdirectory found---
vrising  | ---Checking if WINE is properly installed---
vrising  | ---WINE properly set up---
vrising  | ---Checking for old display lock files---
vrising  | ---Server ready---
vrising  | ---Start Server---
vrising  | tail: invalid PID: ‘’

this is a clean install. I saw it on #22 but no resolution there so I'm not sure what Info to provide to help resolve this.

Thank you.

[ich777]

22 was caused because the user did use a OSX host.

I think that issue is caused because I've update all my images to Debian Bookworm which uses pretty new libraries for example it uses libssl3.0.9 instead of libssl1.1.1.

I also got a few reports on the forums where users report such issues with out of date Unraid versions but I have to say that your host system is not that out of date.

Would it possible for you to upgrade to Ubuntu 23.04? <- I know this is kind of a huge thing and I'm also fine with it if you say no. I could also build a image that is based on Debian Bullseye like it was a month ago, but please fist send the full log and see if we can solve it like that.

But first, please provide the full Docker log if possible. How does the folder structure look like. It seems to me that the dedicated server is not starting on your system.

The container is of course working because a friend of mine is running one on his server that I've set up for him.

[ich777]

Closed due to no further response.

[KingPin]

hi my apologies, I didnt see an update from github. thank you for replying.

unfortunately upgrading ubuntu wont be possible because I use ubuntu LTS releases for my machines for the 5 yr release cycle. also whats on the outside of docker shouldnt affect inside, that would nullify the whole premise of docker if my version of ubuntu changes how the libraries inside work.

I will provide a log by tomorrow at most. I will be home tomorrow so can switch to using it.

Thank you.

[KingPin]

ok I was able to test further, it only errors out if I enable bepinex. if I set bepinex to false everything works fine.

Log :

V-Rising  | usermod: no changes
V-Rising  | ---Setting umask to 000---
V-Rising  | ---Checking for optional scripts---
V-Rising  | ---No optional script found, continuing---
V-Rising  | ---Taking ownership of data...---
V-Rising  | ---Starting...---
V-Rising  | ---Update SteamCMD---
V-Rising  | Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
V-Rising  | [  0%] Checking for available updates...
V-Rising  | [----] Verifying installation...
V-Rising  | Steam Console Client (c) Valve Corporation - version 1689034828
V-Rising  | -- type 'quit' to exit --
V-Rising  | Loading Steam API...dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
V-Rising  | OK
V-Rising  |
V-Rising  | Connecting anonymously to Steam Public...
V-Rising  | OK
V-Rising  | Waiting for client config...OK
V-Rising  | Waiting for user info...
V-Rising  | OK
V-Rising  | ---Update Server---
V-Rising  | Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
V-Rising  | [  0%] Checking for available updates...
V-Rising  | [----] Verifying installation...
V-Rising  | Steam Console Client (c) Valve Corporation - version 1689034828
V-Rising  | -- type 'quit' to exit --
V-Rising  | Loading Steam API...dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
V-Rising  | OK
V-Rising  | "@sSteamCmdForcePlatformType" = "windows"
V-Rising  |
V-Rising  |
V-Rising  | Connecting anonymously to Steam Public...
V-Rising  | OK
V-Rising  | Waiting for client config...OK
V-Rising  | Waiting for user info...
V-Rising  | OK
V-Rising  | Success! App '1829350' already up to date.
V-Rising  | ---BepInEx for V Rising enabled!---
V-Rising  | ---BepInEx for V Rising Version Check---
V-Rising  |
V-Rising  | ---https://v-rising.thunderstore.io/package/BepInEx/BepInExPack_V_Rising/---
V-Rising  |
V-Rising  |
V-Rising  | ---BepInEx for V Rising not found, downloading and installing v1.668.5...---
/serverdata/serverf   0%[                    ]       0  --.-KB/s
/serverdata/serverf  32%[=====>              ]  10.00M  36.1MB/s
/serverdata/serverf 100%[===================>]  31.19M  66.4MB/s    in 0.5s
V-Rising  | ---Successfully downloaded BepInEx for V Rising v1.668.5---
V-Rising  | Archive:  /serverdata/serverfiles/BepInEx.zip
V-Rising  |    creating: /tmp/BepInEx/BepInExPack_V_Rising/
V-Rising  |  extracting: /tmp/BepInEx/BepInExPack_V_Rising/.doorstop_version
V-Rising  |
V-Rising  |
V-Rising  |    creating: /tmp/BepInEx/BepInExPack_V_Rising/BepInEx/
V-Rising  |    creating: /tmp/BepInEx/BepInExPack_V_Rising/BepInEx/config/

------------------- more inflating the bepinex zip file snipped to make log readable  -------------------

V-Rising  |
V-Rising  |   inflating: /tmp/BepInEx/manifest.json
V-Rising  |
V-Rising  |   inflating: /tmp/BepInEx/README.md
V-Rising  |
V-Rising  |
V-Rising  | ---Checking if WINE workdirectory is present---
V-Rising  | ---WINE workdirectory found---
V-Rising  | ---Checking if WINE is properly installed---
V-Rising  | ---WINE properly set up---
V-Rising  | ---Checking for old display lock files---
V-Rising  | ---Server ready---
V-Rising  | ---Start Server---
V-Rising  |
V-Rising  |
V-Rising  | tail: invalid PID: ‘’
V-Rising  | Terminated
V-Rising exited with code 0

[ich777]

ok I was able to test further, it only errors out if I enable bepinex. if I set bepinex to false everything works fine.

Then maybe the BepInEx version needs an update and it's not compatible with the new version. I remember a user on the Unraid forums also reported the same issue, however, if you find a up-to-date version, just extract the contents in the main directory replacing files and leave BepInEx enabled and everything should work as expected.

[KingPin]

sadly theres only one version of bepinex out so far, so no new version exists. it seems to be an issue with wine/docker/bepinx somewhere. either way thank you for your time.