starred/LinuxGSM

Fork 0

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

[GH-ISSUE #2799] command Monitor and crontab dont work #2015

New issue

Closed

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

kerem commented

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

Owner

Originally created by @kestouf on GitHub (Apr 2, 2020).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2799

User Story

As a [user description], I want [desired action] so that [desired outcome].

Basic info

Distro: [Ubuntu 18.04]
Game: [Minecraft]
Command: [Monitor]
LinuxGSM version: [v12.34.56]

Further Information

Hello
I'm looking to do a crontab to launch the monitor on a Minecraft server.
On a Linux machine, I have 3 users: Server1, Server2, Server3
Each user runs a different Minecraft server with different ports.
I made for each user a different crontab
*/3 * * * * /home/ Server1/minecraft/mcserver monitor > /dev/null 2>&1
*/3 * * * * /home/ Server2/minecraft/mcserver monitor > /dev/null 2>&1
*/3 * * * * /home/ Server3/minecraft/mcserver monitor > /dev/null 2>&1

I don't know why but none of them work. So I did a test by adding crontab
*/3 * * * * /home/ Server1/minecraft/mcserver monitor > /home/ Server1/minecraft/log.txt

and in the log.txt files:

^[[K[ .... ] Monitor mcserver: Checking lockfile: ^[[36mCHECKING^[[0m
^[[K[^[[31mERROR ^[[0m] Monitor mcserver: Checking lockfile: No lockfile found:$

Start mcserver to run monitor.

Can you help me please ?

Thx
Best regard

Originally created by @kestouf on GitHub (Apr 2, 2020). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2799 ## User Story As a [user description], I want [desired action] so that [desired outcome]. ## Basic info * **Distro:** [Ubuntu 18.04] * **Game:** [Minecraft] * **Command:** [Monitor] * **LinuxGSM version:** [v12.34.56] ## Further Information Hello I'm looking to do a crontab to launch the monitor on a Minecraft server. On a Linux machine, I have 3 users: Server1, Server2, Server3 Each user runs a different Minecraft server with different ports. I made for each user a different crontab */3 * * * * /home/ Server1/minecraft/mcserver monitor > /dev/null 2>&1 */3 * * * * /home/ Server2/minecraft/mcserver monitor > /dev/null 2>&1 */3 * * * * /home/ Server3/minecraft/mcserver monitor > /dev/null 2>&1 I don't know why but none of them work. So I did a test by adding crontab */3 * * * * /home/ Server1/minecraft/mcserver monitor > /home/ Server1/minecraft/log.txt and in the log.txt files: ^[[K[ .... ] Monitor mcserver: Checking lockfile: ^[[36mCHECKING^[[0m ^[[K[^[[31mERROR ^[[0m] Monitor mcserver: Checking lockfile: No lockfile found:$ * Start mcserver to run monitor. Can you help me please ? Thx Best regard

kerem

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

closed this issue
added the
command: monitor
label

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Apr 4, 2020):

./mcserver start

@dgibbs64 commented on GitHub (Apr 4, 2020): `./mcserver start`

kerem commented

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

Author

Owner

@kestouf commented on GitHub (Apr 8, 2020):

Hello
I'm sorry, but I don't understand your answer.
The command you write in your response is just to start the server.

@kestouf commented on GitHub (Apr 8, 2020): Hello I'm sorry, but I don't understand your answer. The command you write in your response is just to start the server.

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Apr 8, 2020):

correct you only get the error if you don't start the server first.

The error tells you what you need to do.

Start mcserver to run monitor.

@dgibbs64 commented on GitHub (Apr 8, 2020): correct you only get the error if you don't start the server first. The error tells you what you need to do. ``` Start mcserver to run monitor. ```

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Apr 9, 2021):

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

@github-actions[bot] commented on GitHub (Apr 9, 2021): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-27 04:54:04 +03:00

[PR #3891] Feature/jk3server #4157