gabe_fella Posted January 29, 2025 Report Posted January 29, 2025 Hello, To begin, I am using Arch Linux, and run it under a separate user. When I run "./server.sh start" I get the following errors: *** buffer overflow detected ***: terminated Error! username encountered problems with command execution. VintagestoryServer.dll process found ... executing command VintagestoryServer.dll status is indetermined. Error! User username could not start VintagestoryServer.dll! Please check /home/steam/vsserver_1.20.3/data/Logs. I am fully capable of joining the server despite the errors. But, I cannot run commands through the shell script. When I run "./server.sh command '/op username'" I get the following errors: VintagestoryServer.dll process found ... executing command *** buffer overflow detected ***: terminated ./server.sh: line 50: 109636 Aborted (core dumped) bash -c "${1}" Error! username encountered problems with command execution. Even more bizarre is "./server.sh stop" I get the following errors: Stopping VintagestoryServer.dll ... *** buffer overflow detected ***: terminated ./server.sh: line 50: 109815 Aborted (core dumped) bash -c "${1}" Warning! username encountered problems sending a server shutdown notification. *** buffer overflow detected ***: terminated ./server.sh: line 50: 109820 Aborted (core dumped) bash -c "${1}" Warning! username encountered problems executing the server stop command. VintagestoryServer.dll is stopped. Checking the coredump, I found this: Wed 2025-01-29 18:12:28 EST 109820 1001 1001 SIGABRT inaccessible /usr/bin/screen-5.0.0 Screen might be the culprit, but admittedly I'm not too sure.
D O Posted February 6, 2025 Report Posted February 6, 2025 Same exact problem men have u figured it out ?
AwkwardNoah Posted February 11, 2025 Report Posted February 11, 2025 Having the same problem on Mint. A workaround, for at least giving yourself admin, is to edit the "playerdata.json" file. My path for it is "/var/vintagestory/data/Playerdata". With the server stopped, edit the file change your "RoleCode" to "admin" and save.
Dilan Rona Posted February 11, 2025 Report Posted February 11, 2025 you can start with checking if you can run the screen command, and checking for any errors. you could also try updating the screen software package. might be out of date.
JakeSully Posted February 13, 2025 Report Posted February 13, 2025 make sure you got dotenet 7 not 8 or newer. When i made a server and i installed dotnet it had issues on starting too, but it was because i had dotnet 8 and newer.
gabe_fella Posted February 13, 2025 Author Report Posted February 13, 2025 Hello, thank you for the replies. @Dilan Rona Error still persists, but otherwise no new issues. I have reinstalled screen to ensure that it on the most recent version. It is currently on 5.0.0-2, which is the same version as displayed on the Arch package list. I am capable of running the screen commands on my main user and the server user. Checking the server status with "screen -ls" gives me this: There is a screen on: 56395.vss_server (Detached) 1 Socket in /home/username/.screen. @JakeSully Error still persists, but otherwise no new issues. My source for dotnet 7 is a binary package available on the AUR. I swapped to the version available in Arch's "extra" repository, installing both the runtime and the SDK. No changes. Just in case, I will mention that the version currently installed is "7.0.20.sdk120-2"
Dilan Rona Posted February 14, 2025 Report Posted February 14, 2025 well the screen command is definitely active. You can resume the screen session if you want to see inside the server using 'screen -r <name>' where <name> is you need to press TAB to autocomplete the screen name. To disconnect CTRL+A, D
JakeSully Posted February 14, 2025 Report Posted February 14, 2025 (edited) 14 hours ago, gabe_fella said: Hello, thank you for the replies. @Dilan Rona Error still persists, but otherwise no new issues. I have reinstalled screen to ensure that it on the most recent version. It is currently on 5.0.0-2, which is the same version as displayed on the Arch package list. I am capable of running the screen commands on my main user and the server user. Checking the server status with "screen -ls" gives me this: There is a screen on: 56395.vss_server (Detached) 1 Socket in /home/username/.screen. @JakeSully Error still persists, but otherwise no new issues. My source for dotnet 7 is a binary package available on the AUR. I swapped to the version available in Arch's "extra" repository, installing both the runtime and the SDK. No changes. Just in case, I will mention that the version currently installed is "7.0.20.sdk120-2" try using dotnet 7 from microsoft, that's what i did and then it worked. Download .NET 7.0 (Linux, macOS, and Windows) i used dotnet 7 from here and it worked just fine. Since some times versions on repository are modified versions and not official. Also make sure that user vintagestory has premissions to run and read required files outside from it's folder and not just have rights to execute. Edited February 14, 2025 by JakeSully
rzadkie Posted February 25, 2025 Report Posted February 25, 2025 It seems that it's an issue with screen. I commented out invocation of vs_status in server.sh and it ran without any errors. Then I ran 'bash -x ./server.sh command "/stop"' and got + as_user 'screen -p 0 -S vintagestory_server -X eval '\''stuff "//stop"\015'\''' + '[' vintagestory = vintagestory ']' + bash -c 'screen -p 0 -S vintagestory_server -X eval '\''stuff "//stop"\015'\''' *** buffer overflow detected ***: terminated then tried to run 'screen -p 0 -S vintagestory_server -X eval '\''stuff "//stop"\015'\''' standalone and got the same outcome. Quick search and I found https://gitlab.archlinux.org/archlinux/packaging/packages/screen/-/issues/2 so I guess we can rollback to older screen, patch it or wait for update. Running directly via dotnet works just fine if you don't mind having perpetually opened terminal session.
gabe_fella Posted February 27, 2025 Author Report Posted February 27, 2025 On 2/25/2025 at 10:46 PM, rzadkie said: It seems that it's an issue with screen. I commented out invocation of vs_status in server.sh and it ran without any errors. Then I ran 'bash -x ./server.sh command "/stop"' and got + as_user 'screen -p 0 -S vintagestory_server -X eval '\''stuff "//stop"\015'\''' + '[' vintagestory = vintagestory ']' + bash -c 'screen -p 0 -S vintagestory_server -X eval '\''stuff "//stop"\015'\''' *** buffer overflow detected ***: terminated then tried to run 'screen -p 0 -S vintagestory_server -X eval '\''stuff "//stop"\015'\''' standalone and got the same outcome. Quick search and I found https://gitlab.archlinux.org/archlinux/packaging/packages/screen/-/issues/2 so I guess we can rollback to older screen, patch it or wait for update. Running directly via dotnet works just fine if you don't mind having perpetually opened terminal session. Confirmed. After downgrading screen to version 4.9.1, there are no longer any issues. Marking as resolved.
Recommended Posts