systemd service error

[cezarsky]

Hey, I'm working on unturned server on ubuntu 18.04 and I wanted to make my server starting automatically after reboot but I have a problem. When I tried make service's script I get error and I have no idea how to fix it. I have idea, maybe directory is the problem but I don't know. Here my logs.

 

 

 

 

PS. When I tried run /home/steam/Steam/unturned/ServerHelper.sh -ThreadedConsole +InternetServer/sandyrp - it says "
cp: cannot stat 'linux64/steamclient.so': No such file or directory
/home/steam/Steam/unturned/ServerHelper.sh: line 34: ./Unturned_Headless.x86_64: No such file or directory
" but i know there it is

 

 

[Master Disaster]

Looking at it I would guess you made a typo and missed a . from the steam directory. On Linux the steam folder is normally ~/.steam (~ just means from the current users home dir).

 

What happens if you do ...

 

cd /home/steam/Steam/unturned/

 

... Does it sucessfully switch directory?

 

Edit: Actually does the system have a user called steam?

[Eigenvektor]

Systemd is simply telling you that the service exited with an error. So that screenshot isn't really helpful. You need to look at the logs or output of the script you're trying to start.

 

The other message

cp: cannot stat 'linux64/steamclient.so': No such file or directory

seems to be the real issue here. This is a relative directory, so whichever directory you're in right now, it expects the "linux64/steamclient.so" file to be located relative to that, which it probably isn't.

[Master Disaster]

1 minute ago, Eigenvektor said:

Systemd is simply telling you that the service exited with an error. So that screenshot isn't really helpful. You need to look at the logs or output of the script you're trying to start.

 

The other message

cp: cannot stat 'linux64/steamclient.so': No such file or directory

seems to be the real issue here. This is a relative directory, so whichever directory you're in right now, it expects the "linux64/steamclient.so" file to be located relative to that, which it probably isn't.

I guess whatever unturned is, its expecting a copy of the client binary to be in its folder at run time.

[Master Disaster]

So Unturned is just a game dedicated server. In that case you're WAAAAAY overcomplicating this.

 

There are 3 easier ways to do it, fist write a really simple shell script with the launch arguments then either

 

1) Create a crontab entry to either run the script at boot or run it every minute

2) Place the script in the /etc folder and it will run at every boot

3) Edit the rc file (note I don't recommend this method)

 

You can automate everything with Pufferpanel or Pterodactyl Panel, they're open source server control panels you can host yourself with a nice web based GUI to install, update & control game servers. Both are available to manually host (using LAMP or LEMP) or both have (unofficial) docker images.

[Guest]

Your Script is trying to access a path relative to the current working directory. Update your shell script to include the full path or change your unit files current directory.

 

WorkingDirectory=/home/steam/Steam/unturned

 

[cezarsky]

1 hour ago, Master Disaster said:

So Unturned is just a game dedicated server. In that case you're WAAAAAY overcomplicating this.

 

There are 3 easier ways to do it, fist write a really simple shell script with the launch arguments then either

 

1) Create a crontab entry to either run the script at boot or run it every minute

2) Place the script in the /etc folder and it will run at every boot

3) Edit the rc file (note I don't recommend this method)

 

You can automate everything with Pufferpanel or Pterodactyl Panel, they're open source server control panels you can host yourself with a nice web based GUI to install, update & control game servers. Both are available to manually host (using LAMP or LEMP) or both have (unofficial) docker images.

so I can modify crontab to run my script, but path isn't still relative?

[Guest]

1 hour ago, cezarsky said:

so I can modify crontab to run my script, but path isn't still relative?

The path will be relative to the current working Directory regardless of how you call it. The script needs to either have the full path or you need to set the Current Working Directory in the script or whatever is launching it.