[GH-ISSUE #4428] [Bug]: info_distro.sh [: : integer expression expected #2770

New issue

Closed

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

kerem commented

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

Owner

Originally created by @Scott-GMI on GitHub (Dec 27, 2023).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4428

User story

After updating Survive the Nights to Version v 23.7.1 we started to see this error >> [: : integer expression expected <<. Command(s) run - just prints this error to the terminal. Have about 10 other servers running an older version (23.6.2) and I do not see this error.

Game

Survive the Nights on Rocky Linux 9.2

Linux distro

Other

Command

command: start, command: details

Further information

[stnserver@mcgs-002 ~]$ ./stnserver stop
[ OK ] Stopping stnserver: Graceful: CTRL+c: 9: OK
[stnserver@mcgs-002 ~]$ ./stnserver start
[ .... ] Starting stnserver: /home/stnserver/lgsm/modules/info_distro.sh: line 100: [: : integer expression expected
[ OK ] Starting stnserver: MCGC - STN Server

[stnserver@mcgs-002 ~]$ ./stnserver dt
/home/stnserver/lgsm/modules/info_distro.sh: line 100: [: : integer expression expected

Distro Details

Date: Tue Dec 26 08:09:22 PM EST 2023
Distro: Rocky Linux 9.2 (Blue Onyx)
Arch: x86_64
Kernel: 5.14.0-284.30.1.el9_2.x86_64
Hostname: mcgs-002
Environment: xen
Uptime: 58d, 3h, 11m
tmux: 3.2a
glibc: 2.34

Relevant log output

No response

Steps to reproduce

No response

Originally created by @Scott-GMI on GitHub (Dec 27, 2023). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4428 ### User story After updating Survive the Nights to Version v 23.7.1 we started to see this error >> [: : integer expression expected <<. Command(s) run - just prints this error to the terminal. Have about 10 other servers running an older version (23.6.2) and I do not see this error. ### Game Survive the Nights on Rocky Linux 9.2 ### Linux distro Other ### Command command: start, command: details ### Further information [stnserver@mcgs-002 ~]$ ./stnserver stop [ OK ] Stopping stnserver: Graceful: CTRL+c: 9: OK [stnserver@mcgs-002 ~]$ ./stnserver start [ .... ] Starting stnserver: /home/stnserver/lgsm/modules/info_distro.sh: line 100: [: : integer expression expected [ OK ] Starting stnserver: MCGC - STN Server [stnserver@mcgs-002 ~]$ ./stnserver dt /home/stnserver/lgsm/modules/info_distro.sh: line 100: [: : integer expression expected Distro Details =================================================================================== Date: Tue Dec 26 08:09:22 PM EST 2023 Distro: Rocky Linux 9.2 (Blue Onyx) Arch: x86_64 Kernel: 5.14.0-284.30.1.el9_2.x86_64 Hostname: mcgs-002 Environment: xen Uptime: 58d, 3h, 11m tmux: 3.2a glibc: 2.34 ### Relevant log output _No response_ ### Steps to reproduce _No response_

kerem

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

closed this issue
added the
type: bug

command: console

command: details

command: start

info: tmux

distro: Rocky Linux
labels

kerem commented

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

Author

Owner

@Scott-GMI commented on GitHub (Jan 6, 2024):

Line 98 in info_distro.sh

elif [[ "${distroidlike}" == "rhel" ]] || [ "${distroid}" == "rhel" ]; then

Changed to

elif [ "${distroidlike}" == "rhel" ] || [ "${distroid}" == "rhel" ]; then

This fixed the error -> line 100: [: : integer expression expected

Changing the to [ ] @ line 98 looks to be the fix.

@Scott-GMI commented on GitHub (Jan 6, 2024): Line 98 in info_distro.sh elif [[ "${distroidlike}" == *"rhel"* ]] || [ "${distroid}" == "rhel" ]; then Changed to elif [ "${distroidlike}" == *"rhel"* ] || [ "${distroid}" == "rhel" ]; then This fixed the error -> line 100: [: : integer expression expected Changing the [[ ]] to [ ] @ line 98 looks to be the fix.

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Mar 3, 2025):

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 (Mar 3, 2025): 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.