mirror of
https://github.com/GameServerManagers/LinuxGSM.git
synced 2026-04-25 14:15:59 +03:00
[GH-ISSUE #2005] Updated LGSM. Now seeing "numfmt: invalid number: 'K'". #1574
Labels
No labels
Atomic
Epic
cannot reproduce
command: backup
command: console
command: debug
command: details
command: fast-dl
command: install
command: mods
command: monitor
command: post-details
command: restart
command: send
command: start
command: stop
command: update
command: update-lgsm
command: validate
command: wipe
distro: AlmaLinux
distro: Arch Linux
distro: CentOS
distro: Debian
distro: Fedora
distro: RedHat
distro: Rocky Linux
distro: Ubuntu
distro: openSUSE
engine: goldsrc
engine: source
game: 7 Days to Die
game: ARMA 3
game: Ark: Survival Evolved
game: Assetto Corsa
game: Avorion
game: BATTALION: Legacy
game: Barotrauma
game: Battalion 1944
game: Battlefield 1942
game: Black Mesa: Deathmatch
game: Blade Symphony
game: Call of Duty 2
game: Call of Duty 4
game: Call of Duty: United Offensive
game: Counter-Strike 1.6
game: Counter-Strike 2
game: Counter-Strike: Global Offensive
game: Counter-Strike: Source
game: Day of Infamy
game: Dayz
game: Death Match Classic
game: Don't Starve Together
game: ET: Legacy
game: Eco
game: Factorio
game: Factorio
game: Garry's Mod
game: Half-Life
game: Hurtword
game: Insurgecy
game: Insurgecy
game: Insurgency: Sandstorm
game: Just Cause 3
game: Killing Floor
game: Killing Floor 2
game: Left 4 Dead 2
game: Minecraft
game: Minecraft Bedrock
game: Mordhau
game: Multi Theft Auto
game: Mumble
game: Natural Selection 2
game: No More Room in Hell
game: Pavlov VR
game: Post Scriptum
game: Project Zomboid
game: Quake 3
game: QuakeWorld
game: Red Orchestra: Ostfront 41-45
game: Return to Castle Wolfenstein
game: Rising World
game: Rust
game: San Andreas Multiplayer
game: Satisfactory
game: Soldat
game: Soldier of Fortune 2
game: Squad
game: Squad 44
game: Starbound
game: Stationeers
game: Sven Co-op
game: Team Fortress 2
game: Teamspeak 3
game: Teeworlds
game: Terraria
game: The Front
game: Unreal Tournament 2004
game: Unreal Tournament 3
game: Unreal Tournament 99
game: Unturned
game: Valheim
game: Wurm Unlimited
game: Zombie Master Reborn
game: label missing
good first issue
help wanted
info: alerts
info: dependency
info: docker
info: docs
info: email
info: query
info: steamcmd
info: systemd
info: tmux
info: website
info: website
needs more info
outcome: duplicate
outcome: issue resolved
outcome: issue resolved
outcome: issue unresolved
outcome: pr accepted
outcome: pr rejected
outcome: unconfirmed
outcome: wontfix
outcome: wrong forum
potential-duplicate
priority
pull-request
type: bug
type: feature
type: feature
type: feature request
type: game server request
type: refactor
waiting response
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/LinuxGSM#1574
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jrmain on GitHub (Sep 9, 2018).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2005
Originally assigned to: @dgibbs64 on GitHub.
Describe the bug
Since updating LGSM on September 8 (using update-lgsm), some LGSM commands are showing
numfmt: invalid number: 'K'. Servers seem to be running fine otherwise. LGSM version shows as 170305. Tried installing UT99server from scratch and that's also showing the same error. Updated my other server (UT2K4) using update-lgsm and it's showing the same error.To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
No error messages.
** Minimum Information **
The game server I am running: UT99 (also UT2K4, also affected).
The link from
./gameserver postdetailscommand: postdetails did not work. Manual attempt to use hastebin also failed. Server details pasted below (first is before LGSM updates, second is after clean re-install of LGSM and UT99 server).Additional context
Excerpt of command output showing error in context:
Original server details (ANSI removed):
After clean re-install:
@jrmain commented on GitHub (Sep 9, 2018):
It's kind of a long shot, but I think the problem may be related to the new 'ansi' option. I've disabled ansi in my ut99 server config, and it had no effect: ANSI colours are still appearing everywhere. And some of the ANSI codes include 'K'.
@dgibbs64 commented on GitHub (Sep 9, 2018):
I think I know where the issue is but I'm on my phone so can't bring it up currently
@jrmain commented on GitHub (Sep 9, 2018):
I just reinstalled my UT2004 server from scratch and it's doing the same thing.
@dgibbs64 commented on GitHub (Sep 10, 2018):
I think its related to this https://github.com/GameServerManagers/LinuxGSM/pull/1971
@xxngle commented on GitHub (Sep 19, 2018):
Same for CS:GO server.
@Venopsis commented on GitHub (Sep 30, 2018):
Hi,

Having same issue since update LGSM for Project Zomboid Server to last version (180908).
@Troopie commented on GitHub (Sep 30, 2018):
I have same issue at insurgency and KF2 server
@dgibbs64 commented on GitHub (Sep 30, 2018):
I am aware of this issue. Should be fixed in next release. It doesnt break anything important :)
@dgibbs64 commented on GitHub (Oct 4, 2018):
connects to #1971
@dgibbs64 commented on GitHub (Oct 14, 2018):
I am not getting this issue. I think its related older distros like Ubuntu 14.04
@Venopsis commented on GitHub (Oct 14, 2018):
Hello Daniel,
Here is the details of my server:
Let me know if you need more details to troubleshoot.
@dgibbs64 commented on GitHub (Oct 14, 2018):
Odd I just tested the issue on CentOS 7 and the issue didn't occur
@dgibbs64 commented on GitHub (Oct 14, 2018):
Here are my details
Looks like you are only running kernel 2.6 which is really old
@Venopsis commented on GitHub (Oct 14, 2018):
If I try the same command than your previous message, I don't have error:

But when using start command, I got error:

Suppose not related but no more able to run my server on CentOS since last update as Glibcxx 3.4.21 not found. Post open on Official game forum to check as nothing fix this.
@Venopsis commented on GitHub (Oct 14, 2018):
I have two servers as mentioned (prod and testing). The testing one use recent Kernel (more recent than yours).
Prod is openVZ server based.
Just tried on testing and not having the issue at all.
Could be Kernel related? Not an expert.
@dgibbs64 commented on GitHub (Oct 14, 2018):
Whats the kernel version of your testing server?
@dgibbs64 commented on GitHub (Oct 14, 2018):
It is my guess that kernel 2.6 does not have numfmt or a very old version of it
@dgibbs64 commented on GitHub (Oct 14, 2018):
what is the output of
numfmt --versionof the server that has the issue?the oldest version I have available is
@jrmain commented on GitHub (Oct 15, 2018):
Not sure if you were asking me, but anyway: numfmt (GNU coreutils) 8.21.
@dgibbs64 commented on GitHub (Oct 15, 2018):
@jrmain odd I can't replicate the issue myself. I am unsure of what is causing the issue but it seems limited to old distros
@Venopsis commented on GitHub (Oct 15, 2018):
Hi!
Kernel:
The production server is OpenVZ "VM" while testing is hosted on VMware Workstation pro.
numfmt (GNU coreutils)
@jrmain commented on GitHub (Oct 15, 2018):
I can look at the code. Can you provide any hints as to what I'm looking for?
@dgibbs64 commented on GitHub (Oct 15, 2018):
info_distro.shhttps://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/info_distro.sh#L96
@jrmain commented on GitHub (Oct 15, 2018):
There's no MemAvailable in /proc/meminfo. If I change 'MemAvailable' in that command (run from the CLI) to 'nonsense' the same thing happens.
@jrmain commented on GitHub (Oct 16, 2018):
Looks like MemAvailable was added to the Linux kernel relatively recently, in 3.14. I'm running 3.13.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34e431b0ae398fc54ea69ff85ec700722c9da773
Also http://manpages.ubuntu.com/manpages/bionic/man1/free.1.html
@OxECI commented on GitHub (Oct 20, 2018):
Same here.
My distro:
If additional information is needed, let me know.
@marvinlehmann commented on GitHub (Oct 22, 2018):
Same with Debian 9.5 on Windows (WSL):
Kernel: 4.4.0-17134-Microsoft
numfmt version: 8.26
@TuXEKRO commented on GitHub (Oct 24, 2018):
Same with:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
NAME="Ubuntu"
VERSION="18.04.1 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.1 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
@dgibbs64 commented on GitHub (Oct 24, 2018):
I can't see a pattern to this issue currently
@jrmain commented on GitHub (Oct 24, 2018):
Maybe just stop using MemAvailable?
@dgibbs64 commented on GitHub (Oct 24, 2018):
Yes that may be the only choice
@Venopsis commented on GitHub (Oct 24, 2018):
Replace with output from vmstat -s command?
@Bourne-ID commented on GitHub (Oct 24, 2018):
Could always do a check - if it exists then use it, otherwise we can estimate it. The full calculation is documented here but do we need to be exact, or can we say 'if the linux kernel doesn't include MemoryAvailable then we estimate with the next best thing on the list?'
@Bourne-ID commented on GitHub (Oct 24, 2018):
To add, elastic does a check for MemAvailable - and if it exists uses it, otherwise calculates it from Free, Buffers and Cache (link)
@Bourne-ID commented on GitHub (Oct 27, 2018):
Currently merged to dev, tested on all current OS and Ubuntu kernel 3.12. feel free to help test and report back :)
@dgibbs64 commented on GitHub (Oct 27, 2018):
https://github.com/GameServerManagers/LinuxGSM/pull/2058
@jrmain commented on GitHub (Oct 28, 2018):
Confirmed fixed with version 181027.
@lock[bot] commented on GitHub (Oct 28, 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.