[GH-ISSUE #4734] [Bug]: Cronjob automatic changed, cause high load for CPU #2940

New issue

Closed

opened 2026-02-27 03:06:25 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @NNBAtes on GitHub (Jan 5, 2025).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4734

User story

Cronjob automatic changed, cause high load for CPU

Game

Palworld

Linux distro

Ubuntu 20.04

Command

command: start

Further information

Recently all palworld vps using linuxgsm - automatic change cronjob to this, and it's cause vps high load CPU.

Relevant log output

No response

Steps to reproduce

No response

Originally created by @NNBAtes on GitHub (Jan 5, 2025). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4734 ### User story Cronjob automatic changed, cause high load for CPU ### Game Palworld ### Linux distro Ubuntu 20.04 ### Command command: start ### Further information Recently all palworld vps using linuxgsm - automatic change cronjob to this, and it's cause vps high load CPU. ![image](https://github.com/user-attachments/assets/246b278c-70f4-4999-80ef-265596794c16) ![2](https://github.com/user-attachments/assets/c9452ace-560d-4ce8-8428-fe4e5dc388d3) ### Relevant log output _No response_ ### Steps to reproduce _No response_

kerem

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

closed this issue
added the
type: bug

distro: Ubuntu

command: start
labels

kerem commented

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

Author

Owner

@h3o66 commented on GitHub (Jan 5, 2025):

This does not look like it is related to lgsm at all.
This looks like someone got into your server and spawned a cpu intensive task.

@h3o66 commented on GitHub (Jan 5, 2025): This does not look like it is related to lgsm at all. This looks like someone got into your server and spawned a cpu intensive task.

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Jan 5, 2025):

yup looks like the server was hacked

@dgibbs64 commented on GitHub (Jan 5, 2025): yup looks like the server was hacked

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Jan 12, 2026):

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 (Jan 12, 2026): 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.