starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #655] lgsm not working with cronjob #523

New issue

Closed

opened 2026-02-27 02:02:05 +03:00 by kerem · 27 comments

kerem commented

2026-02-27 02:02:05 +03:00

Owner

Originally created by @PhilPhonic on GitHub (Jan 28, 2016).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/655

Hi,
I'm having some issues with lgsm when using cronjobs.
This is what I'm trying:

0 5 * * * ~/insserver update

This is what it returns:

/home/inssserver/insserver: line 144: `core_functions.sh': not a valid identifier

If I run this task directly on my shell, it works just fine.

Any ideas?

Originally created by @PhilPhonic on GitHub (Jan 28, 2016). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/655 Hi, I'm having some issues with lgsm when using cronjobs. This is what I'm trying: > 0 5 \* \* \* ~/insserver update This is what it returns: > /home/inssserver/insserver: line 144: `core_functions.sh': not a valid identifier If I run this task directly on my shell, it works just fine. Any ideas?

kerem

2026-02-27 02:02:05 +03:00

closed this issue
added the
type: bug
label

kerem commented

2026-02-27 02:02:06 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 29, 2016):

Hi,

Did you try ./insserver update-functions ?

@UltimateByte commented on GitHub (Jan 29, 2016): Hi, Did you try ./insserver update-functions ?

kerem commented

2026-02-27 02:02:06 +03:00

Author

Owner

@PhilPhonic commented on GitHub (Jan 29, 2016):

Yep. Doesnt solve the problem

@PhilPhonic commented on GitHub (Jan 29, 2016): Yep. Doesnt solve the problem

kerem commented

2026-02-27 02:02:06 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 29, 2016):

What distro ?

PS : Your command should look like this
0 5 * * * /home/user/insserver update > /dev/null 2>&1

@UltimateByte commented on GitHub (Jan 29, 2016): What distro ? PS : Your command should look like this `0 5 * * * /home/user/insserver update > /dev/null 2>&1`

kerem commented

2026-02-27 02:02:06 +03:00

Author

Owner

@PhilPhonic commented on GitHub (Jan 29, 2016):

Debian Jessie.
I just saw, command works with another user on the Same server.

@PhilPhonic commented on GitHub (Jan 29, 2016): Debian Jessie. I just saw, command works with another user on the Same server.

kerem commented

2026-02-27 02:02:06 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 30, 2016):

So did you get it working ?

@UltimateByte commented on GitHub (Jan 30, 2016): So did you get it working ?

kerem commented

2026-02-27 02:02:06 +03:00

Author

Owner

@PhilPhonic commented on GitHub (Jan 30, 2016):

No. The problem still exists.
I just saw that it works on another insurgency server on the same host

@PhilPhonic commented on GitHub (Jan 30, 2016): No. The problem still exists. I just saw that it works on another insurgency server on the same host

kerem commented

2026-02-27 02:02:06 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 30, 2016):

With the command i gave you ? Only 1 server per user right ? With the right address with no mistake with user spelling ?

Maybe try a root cronjob ?

@UltimateByte commented on GitHub (Jan 30, 2016): With the command i gave you ? Only 1 server per user right ? With the right address with no mistake with user spelling ? Maybe try a root cronjob ?

kerem commented

2026-02-27 02:02:06 +03:00

Author

Owner

@PhilPhonic commented on GitHub (Jan 30, 2016):

user1:
name: insserver
crontab -e

0 5 * * * ~/insserver update > /dev/null 2>&1

does not work

crontab -e

0 5 * * * /home/insserver/insserver update > /dev/null 2>&1

also does not work

user2:
name: insserver2
crontab -e

0 5 * * * ~/insserver update > /dev/null 2>&1

works

root cronjob:
crontab -e

su insserver -c '~/insserver update > /dev/null 2&1'

works

@PhilPhonic commented on GitHub (Jan 30, 2016): user1: name: insserver crontab -e > 0 5 \* \* \* ~/insserver update > /dev/null 2>&1 does not work crontab -e > 0 5 \* \* \* /home/insserver/insserver update > /dev/null 2>&1 also does not work user2: name: insserver2 crontab -e > 0 5 \* \* \* ~/insserver update > /dev/null 2>&1 works root cronjob: crontab -e > su insserver -c '~/insserver update > /dev/null 2&1' works

kerem commented

2026-02-27 02:02:06 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 30, 2016):

Did you copy the exact same command from each crontab ?
In the original syntax, there is 2 spaces after the last " * ", but i don't think it's relevant.
Couldn't this be an issue with the cronjob mode you choosed the first time you runned crontab -e in your first user ?

Try to run a root crontjob which will look like this :
0 5 * * * su - insserver -c '/home/insserver/insserver update' > /dev/null 2>&1

@UltimateByte commented on GitHub (Jan 30, 2016): Did you copy the exact same command from each crontab ? In the original syntax, there is 2 spaces after the last " \* ", but i don't think it's relevant. Couldn't this be an issue with the cronjob mode you choosed the first time you runned crontab -e in your first user ? Try to run a root crontjob which will look like this : 0 5 \* \* \* su - insserver -c '/home/insserver/insserver update' > /dev/null 2>&1

kerem commented

2026-02-27 02:02:06 +03:00

Author

Owner

@PhilPhonic commented on GitHub (Jan 30, 2016):

The root cronjob works.
I also tried deleting all cronjobs for this user (insserver) and re-create them. Didn't help.

@PhilPhonic commented on GitHub (Jan 30, 2016): The root cronjob works. I also tried deleting all cronjobs for this user (insserver) and re-create them. Didn't help.

kerem commented

2026-02-27 02:02:06 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 30, 2016):

What shows
crontab -l
After adding a cronjob in your first user ?
Does it show your cronjob ?

@UltimateByte commented on GitHub (Jan 30, 2016): What shows `crontab -l` After adding a cronjob in your first user ? Does it show your cronjob ?

kerem commented

2026-02-27 02:02:06 +03:00

Author

Owner

@PhilPhonic commented on GitHub (Jan 30, 2016):

yes.

~$ crontab -l
0 5 * * * ~/insserver update > /dev/null 2>&1
~$

@PhilPhonic commented on GitHub (Jan 30, 2016): yes. > ~$ crontab -l > 0 5 \* \* \* ~/insserver update > /dev/null 2>&1 > ~$

kerem commented

2026-02-27 02:02:06 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 30, 2016):

What distro ?
Maybe try adding some simple quotes between the command ?
0 5 * * * '~/insserver update' > /dev/null 2>&1

@UltimateByte commented on GitHub (Jan 30, 2016): What distro ? Maybe try adding some simple quotes between the command ? `0 5 * * * '~/insserver update' > /dev/null 2>&1`

kerem commented

2026-02-27 02:02:06 +03:00

Author

Owner

@PhilPhonic commented on GitHub (Jan 30, 2016):

Debian Jessie.
Where to put the quotes?

@PhilPhonic commented on GitHub (Jan 30, 2016): Debian Jessie. Where to put the quotes?

kerem commented

2026-02-27 02:02:06 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 30, 2016):

I edited my previous message

@UltimateByte commented on GitHub (Jan 30, 2016): I edited my previous message

kerem commented

2026-02-27 02:02:06 +03:00

Author

Owner

@PhilPhonic commented on GitHub (Jan 30, 2016):

That leads to:

/bin/sh: ~/insserver update: No such file or directory

@PhilPhonic commented on GitHub (Jan 30, 2016): That leads to: > /bin/sh: ~/insserver update: No such file or directory

kerem commented

2026-02-27 02:02:06 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 30, 2016):

Replace ~ by /home/insserver

(Lol, it almost became a chatbox with auto refresh on github when we both have the page open... :p)

@UltimateByte commented on GitHub (Jan 30, 2016): Replace ~ by /home/insserver (Lol, it almost became a chatbox with auto refresh on github when we both have the page open... :p)

kerem commented

2026-02-27 02:02:07 +03:00

Author

Owner

@PhilPhonic commented on GitHub (Jan 30, 2016):

/bin/sh: /home/insserver/insserver update: No such file or directory

@PhilPhonic commented on GitHub (Jan 30, 2016): > /bin/sh: /home/insserver/insserver update: No such file or directory

kerem commented

2026-02-27 02:02:07 +03:00

Author

Owner

@PhilPhonic commented on GitHub (Jan 30, 2016):

ps: I always have to remove "> /dev/null 2>&1" to see the output..

@PhilPhonic commented on GitHub (Jan 30, 2016): ps: I always have to remove "> /dev/null 2>&1" to see the output..

kerem commented

2026-02-27 02:02:07 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 30, 2016):

Crap. Well, i tried.
I see no reason why it would run as root, and not as the user.
BTW, if you got multiple servers, i advise you to manage cronjobs as root, as it's way easier to manage all of them at once.

@UltimateByte commented on GitHub (Jan 30, 2016): Crap. Well, i tried. I see no reason why it would run as root, and not as the user. BTW, if you got multiple servers, i advise you to manage cronjobs as root, as it's way easier to manage all of them at once.

kerem commented

2026-02-27 02:02:07 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 30, 2016):

"ps: I always have to remove "> /dev/null 2>&1" to see the output.."
Yeah, because this is meant to remove the output so the command works with no issue. ^^

@UltimateByte commented on GitHub (Jan 30, 2016): "ps: I always have to remove "> /dev/null 2>&1" to see the output.." Yeah, because this is meant to remove the output so the command works with no issue. ^^

kerem commented

2026-02-27 02:02:07 +03:00

Author

Owner

@PhilPhonic commented on GitHub (Jan 30, 2016):

I know. Just wanted to make clear what I am doing ;-)

@PhilPhonic commented on GitHub (Jan 30, 2016): I know. Just wanted to make clear what I am doing ;-)

kerem commented

2026-02-27 02:02:07 +03:00

Author

Owner

@PhilPhonic commented on GitHub (Jan 30, 2016):

I think it's a user related issue, because the cronjob on the other user works fine.
I'll migrate the server to another user and try again.

@PhilPhonic commented on GitHub (Jan 30, 2016): I think it's a user related issue, because the cronjob on the other user works fine. I'll migrate the server to another user and try again.

kerem commented

2026-02-27 02:02:07 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 30, 2016):

ok :)

@UltimateByte commented on GitHub (Jan 30, 2016): ok :)

kerem commented

2026-02-27 02:02:07 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 30, 2016):

Don't forget to make a
chown -R newuser:newuser *

@UltimateByte commented on GitHub (Jan 30, 2016): Don't forget to make a `chown -R newuser:newuser *`

kerem commented

2026-02-27 02:02:07 +03:00

Author

Owner

@PhilPhonic commented on GitHub (Jan 31, 2016):

Migrating the server to another user worked. Cronjobs work fine on this new user.
I have no idea what was wrong with the other user.

@PhilPhonic commented on GitHub (Jan 31, 2016): Migrating the server to another user worked. Cronjobs work fine on this new user. I have no idea what was wrong with the other user.

kerem commented

2026-02-27 02:02:07 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jul 19, 2018):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Jul 19, 2018): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.