starred/LinuxGSM

Fork 0

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

[GH-ISSUE #290] Email feature seems to be broken on Slackware #249

New issue

Closed

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

kerem commented

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

Owner

Originally created by @Xylemon on GitHub (Feb 8, 2015).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/290

So for the longest time the mail feature has been broken, and now I even get a bunch of nonsense when trying it out:

[ .... ] Email ts3-server: Sending notification to [email here]tail: cannot open '3' for reading: No such file or directory
[path to]/functions/fn_details_distro: line 32: [: : integer expression expected
tail: cannot open '3' for reading: No such file or directory
[path to]/functions/fn_details_distro: line 32: [: : integer expression expected
[ OK ] Email ts3-server: Sending notification to [email here]

I do have Postfix and Mailutils installed.

Originally created by @Xylemon on GitHub (Feb 8, 2015). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/290 So for the longest time the mail feature has been broken, and now I even get a bunch of nonsense when trying it out: [ .... ] Email ts3-server: Sending notification to [email here]tail: cannot open '3' for reading: No such file or directory [path to]/functions/fn_details_distro: line 32: [: : integer expression expected tail: cannot open '3' for reading: No such file or directory [path to]/functions/fn_details_distro: line 32: [: : integer expression expected [ OK ] Email ts3-server: Sending notification to [email here] I do have Postfix and Mailutils installed.

kerem

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

closed this issue
added the
type: bug
label

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Feb 8, 2015):

I definitely need access to an install of slackware so I can develop and test on slackware.

@dgibbs64 commented on GitHub (Feb 8, 2015): I definitely need access to an install of slackware so I can develop and test on slackware.

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Feb 8, 2015):

Just tested on Ubuntu had not issues. can confirm Slackware issue.

@dgibbs64 commented on GitHub (Feb 8, 2015): Just tested on Ubuntu had not issues. can confirm Slackware issue.

kerem commented

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

Author

Owner

@Xylemon commented on GitHub (Feb 9, 2015):

Interesting, must be a dependency missing?

@Xylemon commented on GitHub (Feb 9, 2015): Interesting, must be a dependency missing?

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Feb 14, 2015):

Fixed the issue. Please delete the functions dir and test.
github.com/dgibbs64/linuxgameservers@29d80e88ce

@dgibbs64 commented on GitHub (Feb 14, 2015): Fixed the issue. Please delete the functions dir and test. https://github.com/dgibbs64/linuxgameservers/commit/29d80e88ce8d8b44dbece05cb33c9ab64e9067fd

kerem commented

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

Author

Owner

@Xylemon commented on GitHub (Feb 14, 2015):

Did not fix, I'm still getting this error #218 and I don't know if that's causing the email not to be sent (although it says it's being sent which is odd).

@Xylemon commented on GitHub (Feb 14, 2015): Did not fix, I'm still getting this error #218 and I don't know if that's causing the email not to be sent (although it says it's being sent which is odd).

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Feb 16, 2015):

When I add code about tmux 1.8 the email error should!d disappear. I will also be using touch to make sure the log file is created even if the log is empty.

@dgibbs64 commented on GitHub (Feb 16, 2015): When I add code about tmux 1.8 the email error should!d disappear. I will also be using touch to make sure the log file is created even if the log is empty.

kerem commented

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

Author

Owner

@Xylemon commented on GitHub (Feb 16, 2015):

I'm not quite sure why email isn't getting sent, but sine updating Tmux #218 is fixed for me so that's one step closer to fixing this issue I hope.

@Xylemon commented on GitHub (Feb 16, 2015): I'm not quite sure why email isn't getting sent, but sine updating Tmux #218 is fixed for me so that's one step closer to fixing this issue I hope.

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Feb 17, 2015):

Is this now OK after the previous commit or are you still having issues?

@dgibbs64 commented on GitHub (Feb 17, 2015): Is this now OK after the previous commit or are you still having issues?

kerem commented

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

Author

Owner

@Xylemon commented on GitHub (Feb 18, 2015):

It's still not working. I want to say it's related to dependencies here, not the script, but I'm not sure.

@Xylemon commented on GitHub (Feb 18, 2015): It's still not working. I want to say it's related to dependencies here, not the script, but I'm not sure.

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Mar 22, 2015):

Any update on this?

@dgibbs64 commented on GitHub (Mar 22, 2015): Any update on this?

kerem commented

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

Author

Owner

@Xylemon commented on GitHub (Mar 23, 2015):

Haven't investigated it lately, will probably later today. Can you list all the deps I need for the mail feature?

@Xylemon commented on GitHub (Mar 23, 2015): Haven't investigated it lately, will probably later today. Can you list all the deps I need for the mail feature?

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Dec 20, 2015):

email feature to be re-written in #566

@dgibbs64 commented on GitHub (Dec 20, 2015): email feature to be re-written in #566

kerem commented

2026-02-27 02:00:24 +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.