Running Linux arma3server with long-running missions will eventually result in the server halting with repeated error message "Overflow." This does not occur with the Windows arma3server. This crashing only occurs with the Linux arma3server.
Description
Description
Details
Details
- Severity
- Crash
- Resolution
- Open
- Reproducibility
- Sometimes
- Operating System
- Linux x64
- Operating System Version
- Ubuntu
- Category
- Dedicated Server
Steps To Reproduce
Steps to reproduce:
- start an arma3server with the latest Linux server
- start a long running mission, example: Domination
- observe the server logs after 8-12 hours for "Overflow" error message, server is unresponsive and must be restarted
Repeat the test above using a Windows server, note the server does not crash.
Additional Information
This new report might be related to existing reports:
https://feedback.bistudio.com/T80902
https://feedback.bistudio.com/T83321
Event Timeline
Comment Actions
Hello.
Thank you for the report. Could you please upload your crash dumps here? Here is how to do that.
Comment Actions
It seems like something has changed since I last tested this in 2018. I'm not able to reproduce the issue on my current configuration. It could be due to newer Linux kernel, different hardware... not sure.
I changed "reproducibility" to "sometimes" while I continue a few tests. I would like to keep this ticket open a bit longer and try to collect more info.
Comment Actions
Just to clarify, I am able to see the "Overflow" error message in the server logs but the server does not crash in my current test environment. More testing at the moment.
Comment Actions
Some object is way out of terrain bounds. Probably under the ground.
Possibly. I wonder if that would cause the "Overflow" error message... That error is usually accompanied by "Server: Object not found" error. Maybe a misplaced object is the root cause.
Comment Actions
When the server is "overflowing" badly it can spam the logs with a million errors in a few hours and causes serious performance problems. Alternatively a lightly "overflowing" server sometimes self-corrects and the players don't even notice the issue.
This is what a typical log looks like when the server experiences serious performance issues:
2:26:29 Server: Object 2:1149 not found (message Type_92) 2:26:29 Server: Object 2:1150 not found (message Type_92) 2:26:29 Server: Object 2:1162 not found (message Type_92) 2:26:29 Server: Object 2:1163 not found (message Type_92) 2:26:29 Server: Object 2:1157 not found (message Type_92) 2:26:29 Server: Object 2:1158 not found (message Type_92) 2:26:29 Server: Object 2:1153 not found (message Type_92) 2:26:29 Server: Object 2:1154 not found (message Type_92) 2:26:31 Server: Object 2:5026 not found (message Type_92) 2:26:32 Server: Object 2:3755 not found (message Type_92) 2:26:36 Longtime uses modified data file 2:26:38 Server: Object 2:5893 not found (message Type_92) 2:26:38 Player Longtime connecting. 2:26:39 Player Longtime connected (id=76561197963172638). 2:26:41 Unrecognized PlayerRole target side: 7, index: 41 2:26:41 Unrecognized PlayerRole target side: 7, index: 42 2:26:41 Unrecognized PlayerRole target side: 7, index: 43 2:26:41 Unrecognized PlayerRole target side: 7, index: 44 2:26:41 Unrecognized PlayerRole target side: 7, index: 45 2:26:47 Server: Object 2:5893 not found (message Type_120) 2:26:50 Server: Object 2:3755 not found (message Type_120) Overflow Overflow Overflow 2:26:55 Server: Object 2:5026 not found (message Type_120) Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow Overflow
This comment was removed by longtime.
Comment Actions
As dedmen called it, objects out of terrain bounds with an adverse affect on the server. Fixed in the mission. I would recommend closing this issue.