I have updated both lgsm and cs:go today and now I can't start server.
Every time I get this "server@vds111:~$ ./csgoserver start[ .... ]
Starting csgoserver: jq: error (at
Issue-Label Bot is automatically applying the label type: bug to this issue, with a confidence of 0.89. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
This issue will be resolved in the next release
Have this bug been fixed?
Distro: Ubuntu 18.04.4 LTS
Game: csgo
LinuxGSM version: v19.12.5
lanu@csgo:~$ ./csgo27010 start
jq: error (at <stdin>:0): Cannot iterate over null (null)
jq: error (at <stdin>:0): Cannot iterate over null (null)
[ INFO ] Starting csgo27010: Check IP: 10.50.0.10
jq: error (at <stdin>:0): Cannot iterate over null (null)
[ OK ] Starting csgo27010: Server 1
I also got the problem today with Ubuntu 18.04.4 LTS
Game: ark
LinuxGSM version: v19.12.5
I also got the problem today with Ubuntu 18.04.4 LTS
Game: ark
LinuxGSM version: v19.12.5
Did you check the permissions of the Engine/Binaries/Linux?
Try sudo chown -R arkserver:arkserver /home/arkserver/serverfiles and chmod 775 -R /home/arkserver/serverfiles/Engine/Binaries/Linux/.
For me it fixed the error.
Did you check the permissions of the Engine/Binaries/Linux?
Try
sudo chown -R arkserver:arkserver /home/arkserver/serverfilesandchmod 775 -R /home/arkserver/serverfiles/Engine/Binaries/Linux/.For me it fixed the error.
This helped me to discover that I'm actually missing /home/arkserver/serverfiles/Engine/Binaries/Linux/. This problem appeared immediately after I performed an automated force-update this morning at 10am EST. Curious to know if this is actually an ARK problem, not LGSM's.
I also got this problem.
@calvinsands Just go on https://survivetheark.com/index.php?/forums/topic/507564-genesis-dedicated-server-error/
Just download the file(from Google Drive from sirvulcan) and load it in the right directory.
It is missing since the last patch.
ARK - Official Community ForumsGenesis dedicated server error Hello, Getting an error when launching the dedicated server on Linux: .../ShooterGame/Binaries/Linux/ShooterGameServer: error while loading shared libraries: libsteam_api.so: cannot open shared object file: No such file or directory Anyone else getting this?
I believe this is now resolved. Please re-open if the issues returns
@dgibbs64
This is happening to me on a fresh install of LGSM & 7days2die.
Any thoughts on what could be causing it?
sdtd@jinnix:~$ ./sdtdserver details
jq: error (at <stdin>:0): Cannot iterate over null (null)
jq: error (at <stdin>:0): Cannot iterate over null (null)
Distro Details
=================================
Distro: Ubuntu 20.04.1 LTS
Arch: x86_64
Kernel: 5.4.0-42-generic
Hostname: jinnix
Uptime: 1d, 19h, 28m
tmux: tmux 3.0a
glibc: 2.31
Same on 7Days to die. I believe it comes from the gathering of the config file.
Looking into it but cannot find the reason for now.
I am getting the same thing when running the details command.
sdtdserver@sdtdserver:~$ ./sdtdserver details
[ INFO ] Viewing details sdtdserver: Check IP: x.x.x.x
jq: error (at <stdin>:0): Cannot iterate over null (null)
jq: error (at <stdin>:0): Cannot iterate over null (null)
I also noticed the port in the details is not accurate. I tried changing the port number from default in the server /home/sdtdserver/serverfiles/sdtdserver.xml and has no effect. still shows
Server IP: x.x.x.x:2690026900269052701527020
Internet IP: 96.78.12.26:2690026900269052701527020
DESCRIPTION DIRECTION PORT PROTOCOL
> Game/RCON INBOUND 2690026900269052701527020 udp
> Query INBOUND 2690026900269052701527020 udp
Distro Details
=================================
Distro: Ubuntu 18.04.5 LTS
Arch: x86_64
Kernel: 4.15.0-115-generic
Hostname: sdtdserver
Uptime: 0d, 0h, 17m
tmux: tmux 2.6
glibc: 2.27
Hey, this has been discussed and fixed here.
Hey, this has been discussed and fixed here.
Nice, thanks. that worked. I thought a fix was pushed already.
If you are reading this -
Edit: /home/sdtdserver/serverfiles/sdtdserver.xml
line 13 -
Delete: " Keep it in the ranges 26900 to 26905 or 27015 to 27020 if you want PCs on the same LAN to find it as a LAN server. "
Save.
Then run the details command again.
Closing as this is a differnt issue and the issue is discussed here: #3006
Most helpful comment
Issue-Label Bot is automatically applying the label
type: bugto this issue, with a confidence of 0.89. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!Links: app homepage, dashboard and code for this bot.