starred/LinuxGSM

Fork 0

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

[GH-ISSUE #1674] Discord alerts failing for ut99server #1301

New issue

Closed

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

kerem commented

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

Owner

Originally created by @jrmain on GitHub (Oct 28, 2017).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1674

Originally assigned to: @dgibbs64 on GitHub.

When I use test-alert to check Discord alert functionality, I get this: [ FAIL ] Alert ut99-server: Sending Discord alert: {"code": 50006, "message": "Cannot send an empty message"}

I followed the instructions at https://github.com/GameServerManagers/LinuxGSM/wiki/Discord to create the Webhook and updated the server script to enable Discord alerts, but it's not working as expected.

Any ideas?

Originally created by @jrmain on GitHub (Oct 28, 2017). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1674 Originally assigned to: @dgibbs64 on GitHub. When I use test-alert to check Discord alert functionality, I get this: ```[ FAIL ] Alert ut99-server: Sending Discord alert: {"code": 50006, "message": "Cannot send an empty message"}``` I followed the instructions at https://github.com/GameServerManagers/LinuxGSM/wiki/Discord to create the Webhook and updated the server script to enable Discord alerts, but it's not working as expected. Any ideas?

kerem

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

closed this issue
added the
type: bug

outcome: issue resolved

game: Unreal Tournament 99
labels

kerem commented

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

Author

Owner

@gamersalpha commented on GitHub (Nov 6, 2017):

Hello yes
try this :

edit this files :

nano lgsm/config-lgsm/arkserver/common.cfg

adding this line :

servername="ark-server-ubuntu"

like this :
https://gist.github.com/gamersalpha/f27370566023c21af16bf6cebfad434a

and now the that"s works :)

[ OK ] Alert arkserver: Sending Discord alert

i have the same error and i fix it like this
https://github.com/GameServerManagers/LinuxGSM/issues/1680

@gamersalpha commented on GitHub (Nov 6, 2017): Hello yes try this : edit this files : `nano lgsm/config-lgsm/arkserver/common.cfg` adding this line : `servername="ark-server-ubuntu"` like this : https://gist.github.com/gamersalpha/f27370566023c21af16bf6cebfad434a and now the that"s works :) `[ OK ] Alert arkserver: Sending Discord alert` i have the same error and i fix it like this https://github.com/GameServerManagers/LinuxGSM/issues/1680

kerem commented

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

Author

Owner

@jrmain commented on GitHub (Nov 6, 2017):

@gamersalpha I tried something similar for the UT99 server, but it didn't seem to help. For your server, where did the value for servername come from?

@jrmain commented on GitHub (Nov 6, 2017): @gamersalpha I tried something similar for the UT99 server, but it didn't seem to help. For your server, where did the value for servername come from?

kerem commented

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

Author

Owner

@abortizjr commented on GitHub (Nov 22, 2017):

I'm getting the same message. I put the servername in the common.cfg and it still didn't work.

@abortizjr commented on GitHub (Nov 22, 2017): I'm getting the same message. I put the servername in the common.cfg and it still didn't work.

kerem commented

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

Author

Owner

@abortizjr commented on GitHub (Nov 22, 2017):

For the record, I have a UT2k4 server running on the same box and it sends Discord alerts just fine.

I also have a KF2 server on a separate box that sends Discord alerts just fine.

So there seems to be something different with the UT99 implementation.

@abortizjr commented on GitHub (Nov 22, 2017): For the record, I have a UT2k4 server running on the same box and it sends Discord alerts just fine. I also have a KF2 server on a separate box that sends Discord alerts just fine. So there seems to be something different with the UT99 implementation.

kerem commented

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

Author

Owner

@jrmain commented on GitHub (Nov 22, 2017):

Confirmed that Discord alerts work fine with my UT2K4 server on the same box. Still not working for the UT99 server.

@jrmain commented on GitHub (Nov 22, 2017): Confirmed that Discord alerts work fine with my UT2K4 server on the same box. Still not working for the UT99 server.

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Nov 22, 2017):

Please, follow the minimum requirements to report an issue.
https://github.com/GameServerManagers/LinuxGSM/wiki/Support

@UltimateByte commented on GitHub (Nov 22, 2017): Please, follow the minimum requirements to report an issue. https://github.com/GameServerManagers/LinuxGSM/wiki/Support

kerem commented

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

Author

Owner

@jrmain commented on GitHub (Nov 22, 2017):

Game server: UT99

Postdetails produces this:

touch: cannot touch ‘’: No such file or directory
[ FAIL ] Postdetails ut99-server: Unable to create temporary file .
command_postdetails.sh exiting with code: 0

Context: trying to get Discord alerts working. Followed the instructions at https://github.com/GameServerManagers/LinuxGSM/wiki/Discord, which worked fine for UT2K4. Running the test-alert command produces this:

[ FAIL ] Alert ut99-server: Sending Discord alert: {"code": 50006, "message": "Cannot send an empty message"}
[  OK  ] Alert ut99-server: Sending Email alert: operator@jrc-core.com
[ WARN ] Alert ut99-server: IFTTT alerts not enabled
[ WARN ] Alert ut99-server: Mailgun alerts not enabled
[ WARN ] Alert ut99-server: Pushbullet alerts not enabled
[ WARN ] Alert ut99-server: Pushover alerts not enabled
[ WARN ] Alert ut99-server: Telegram Messages not enabled
command_test_alert.sh exiting with code: 3

Linux distro/version: Ubuntu Linux 14.04.5

Kernel info: Linux foghorn 3.13.0-135-generic #184-Ubuntu SMP Wed Oct 18 11:55:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Glibc version: ldd (Ubuntu EGLIBC 2.19-0ubuntu6.13) 2.19

TMux version: tmux 2.0

Log excerpts: none that seem relevant

Screenshot: n/a

Server hardware:
CPU: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 8 cores
RAM: 8 GB
Storage: 450 GB
Bandwidth: 25 Mbps down; 5 Mbps up

Tests tried: I tried the fix suggested by gamersalpha above, but it didn't help.

@jrmain commented on GitHub (Nov 22, 2017): **Game server:** UT99 **Postdetails** produces this: ```fetching command_postdetails.sh...OK touch: cannot touch ‘’: No such file or directory [ FAIL ] Postdetails ut99-server: Unable to create temporary file . command_postdetails.sh exiting with code: 0 ``` **Context:** trying to get Discord alerts working. Followed the instructions at https://github.com/GameServerManagers/LinuxGSM/wiki/Discord, which worked fine for UT2K4. Running the test-alert command produces this: ```[ WARN ] Alert ut99-server: More Info not enabled [ FAIL ] Alert ut99-server: Sending Discord alert: {"code": 50006, "message": "Cannot send an empty message"} [ OK ] Alert ut99-server: Sending Email alert: operator@jrc-core.com [ WARN ] Alert ut99-server: IFTTT alerts not enabled [ WARN ] Alert ut99-server: Mailgun alerts not enabled [ WARN ] Alert ut99-server: Pushbullet alerts not enabled [ WARN ] Alert ut99-server: Pushover alerts not enabled [ WARN ] Alert ut99-server: Telegram Messages not enabled command_test_alert.sh exiting with code: 3 ``` **Linux distro/version:** Ubuntu Linux 14.04.5 **Kernel info:** Linux foghorn 3.13.0-135-generic #184-Ubuntu SMP Wed Oct 18 11:55:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux **Glibc version:** ldd (Ubuntu EGLIBC 2.19-0ubuntu6.13) 2.19 **TMux version:** tmux 2.0 **Log excerpts:** none that seem relevant **Screenshot:** n/a **Server hardware:** CPU: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 8 cores RAM: 8 GB Storage: 450 GB Bandwidth: 25 Mbps down; 5 Mbps up **Tests tried:** I tried the fix suggested by gamersalpha above, but it didn't help.

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Nov 22, 2017):

Thanks
"Unable to create temporary file" > Permission issue? Directory with spaces issues?
Can you please make sure that you eliminated these two possible sources of issues and try postdetails again?

@UltimateByte commented on GitHub (Nov 22, 2017): Thanks "Unable to create temporary file" > Permission issue? Directory with spaces issues? Can you please make sure that you eliminated these two possible sources of issues and try postdetails again?

kerem commented

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

Author

Owner

@jrmain commented on GitHub (Nov 23, 2017):

No directories with spaces in them. All the files are in /home/ut99server, everything runs as ut99server, and that user appears to have full permissions over all its files.

The 'details' command works fine, but I guess you would prefer a link to the postdetails output.

The tmp directory (/tmp/user/1010) is writeable.

It seems like maybe I'm missing some functionality related to posting information on the web. Or possibly the ut99server user needs additional permissions.

@jrmain commented on GitHub (Nov 23, 2017): No directories with spaces in them. All the files are in /home/ut99server, everything runs as ut99server, and that user appears to have full permissions over all its files. The 'details' command works fine, but I guess you would prefer a link to the postdetails output. The tmp directory (/tmp/user/1010) is writeable. It seems like maybe I'm missing some functionality related to posting information on the web. Or possibly the ut99server user needs additional permissions.

kerem commented

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

Author

Owner

@jrmain commented on GitHub (Nov 23, 2017):

The postdetails.sh script seems to be expecting postdetailslog to have a value, but I don't see it being set anywhere. My UT2K4 server's postdetails command does the same thing, by the way.

@jrmain commented on GitHub (Nov 23, 2017): The postdetails.sh script seems to be expecting postdetailslog to have a value, but I don't see it being set anywhere. My UT2K4 server's postdetails command does the same thing, by the way.

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Nov 23, 2017):

Oh, maybe there is a bogus here, where a variable is missing for ut99, we need to check that out.

Awaiting for that, you can use the details command and manually post it to hastebin while masking off sensitive information, if any.

@UltimateByte commented on GitHub (Nov 23, 2017): Oh, maybe there is a bogus here, where a variable is missing for ut99, we need to check that out. Awaiting for that, you can use the details command and manually post it to hastebin while masking off sensitive information, if any.

kerem commented

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

Author

Owner

@jrmain commented on GitHub (Nov 23, 2017):

https://hastebin.com/tapaqefube.sql

@jrmain commented on GitHub (Nov 23, 2017): https://hastebin.com/tapaqefube.sql

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Nov 23, 2017):

Wondering... Is there any firewall?

@UltimateByte commented on GitHub (Nov 23, 2017): Wondering... Is there any firewall?

kerem commented

2026-02-27 02:56:24 +03:00

Author

Owner

@jrmain commented on GitHub (Nov 23, 2017):

There are various firewalls and other security measures in place on the server and elsewhere. I suppose the Linux server's firewall could be configured to block traffic going from the server to Discord's API, but doesn't that traffic just look like web traffic? In any case, the UT2K4 server on the same machine doesn't have the same problem with Discord alerts. I get the feeling that there's a setting missing or misconfigured for the UT99 server.

@jrmain commented on GitHub (Nov 23, 2017): There are various firewalls and other security measures in place on the server and elsewhere. I suppose the Linux server's firewall could be configured to block traffic going from the server to Discord's API, but doesn't that traffic just look like web traffic? In any case, the UT2K4 server on the same machine doesn't have the same problem with Discord alerts. I get the feeling that there's a setting missing or misconfigured for the UT99 server.

kerem commented

2026-02-27 02:56:24 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Jun 13, 2018):

Made some fixes to both gamedig and also this 496ace3d0e

The issue should be fixed on next release

@dgibbs64 commented on GitHub (Jun 13, 2018): Made some fixes to both gamedig and also this 496ace3d0e992814473b1847414c31ef631001a0 The issue should be fixed on next release

kerem commented

2026-02-27 02:56:24 +03:00

Author

Owner

@jrmain commented on GitHub (Jul 19, 2018):

Confirmed fixed.

@jrmain commented on GitHub (Jul 19, 2018): Confirmed fixed.

kerem commented

2026-02-27 02:56:24 +03:00

Author

Owner

@lock[bot] commented on GitHub (Nov 18, 2019):

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 (Nov 18, 2019): 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.