ChronosWS

We still see crashes on a semi-regular basis - well hangs really, as the server can't be bothered to take itself down. 16:31:12 Avorion server Beta 0.29.2 r18532 ea4d9c756593 running on Amazon Linux 2 starting up in "/data/avorion/galaxies/Galaxy" 16:31:12 CPU: Intel(R) Xeon(R) Platinum 8275CL CPU @ 3.00GHz 2 Cores 16:31:12 RAM: 3GB

The answer is to use the same app id (565060) and add "-beta beta" as an additional argument.

I thought it was 445220 but this does not install what I thought it would. Need the Steam app ID I can use with steamcmd to update a dedicated server to the Beta branch. 565060 for stable works fine. Thanks!

I've added a feature request for write-through logging.

I am going to move my server to the beta branch and see if my players stop seeing this as well. Thanks.

I would like server logs to be available live, rather than (apparently) buffered and written upon either exit or the filling of the buffer. My log distribution utility (AWS CloudWatch) will nicely grab logs but as the server only writes them when its buffer gets full, I don't even see logs from a server which just started until that threshold has been reached, and when diagnosing certain issues in realtime, being able to review the logs in realtime without cycling the server would be nice. An option to enable writethrough for the logs would be much appreciated! Additionally I would like to be able to relocate where the logs live - rather than being in my galaxy directory, I'd prefer to move them to something like /var/log with the rest of the log files on my servers so I can centralize my log handling. An option to change the directory where logs are stored would be nice. Additional log configuration (like log file naming) would also be appreciated (i'd like to get rid of the spaces and change the date format.) Much appreciated!

I have a similar issue. Server had a single player on it, not sure exactly what they were doing at the time. I have also observed this behavior from time to time. Once the "crash" has occurred, the server will keep sending crash reports, approximately every 75 minutes (in bursts of a couple dozen.) Sample logs from below (I can try turning on tracing to help track down the issue?) 02:55:47 Avorion server Beta 0.28.1 r18395 5f179a296d34 running on Amazon Linux 2 starting up in "/data/avorion/galaxies/Galaxy" 02:55:47 CPU: Intel(R) Xeon(R) Platinum 8275CL CPU @ 3.00GHz 2 Cores 02:55:47 RAM: 3GB 06:20:16 saving sector (-110:-210) 06:20:16 sector (-110:-210) saved to "/data/avorion/galaxies/Galaxy/sectors/-110_-210" 07:30:24 scheduled save for sector (-117:-206), 0x7f22b5d94530, entities: 0 07:30:24 saving sector (-117:-206) 07:30:24 sector (-117:-206) saved to "/data/avorion/galaxies/Galaxy/sectors/-117_-206" 07:30:24 scheduled save for sector (-152:-178), 0x7f22c59a5ae0, entities: 520 07:30:24 saving sector (-152:-178) 07:30:24 sector (-152:-178) saved to "/data/avorion/galaxies/Galaxy/sectors/-152_-178" 07:30:24 scheduled save for sector (-142:-189), 0x7f22ce7109f0, entities: 0 07:30:24 saving sector (-142:-189) 07:30:24 sector (-142:-189) saved to "/data/avorion/galaxies/Galaxy/sectors/-142_-189" 07:30:24 scheduled save for sector (-130:-198), 0x7f22bc725b80, entities: 0 07:30:24 saving sector (-130:-198) 07:30:24 sector (-130:-198) saved to "/data/avorion/galaxies/Galaxy/sectors/-130_-198" 07:30:24 scheduled save for sector (-117:-206), 0x7f22b5d94530, entities: 0 07:30:24 saving sector (-117:-206) 07:30:24 sector (-117:-206) saved to "/data/avorion/galaxies/Galaxy/sectors/-117_-206" 07:30:24 Triggered saving of all server data. 07:30:24 scheduled save for sector (-110:-210), 0x7f22bc3f22a0, entities: 2035 07:30:24 saving sector (-110:-210) 07:30:24 sector (-110:-210) saved to "/data/avorion/galaxies/Galaxy/sectors/-110_-210" 07:30:24 Hang of at least 30 seconds detected, sending stack traceSending crash report ... 07:30:24 Crash report sent successfully! 07:30:24 Hang of at least 30 seconds detected, sending stack traceSending crash report ... 07:30:24 Crash report sent successfully! 07:30:24 Hang of at least 30 seconds detected, sending stack traceSending crash report ... 07:30:24 Crash report sent successfully!

I've set up a multiplayer server running in the cloud (AWS in this instance) and am wondering if anyone has run into (and solved) an issue I am seeing with logging - namely that the server does not automatically flush logs out when they occur, rather it seems to wait until they've reached some internal buffer and then write. I am using AWS CloudWatch to grab the log file as it's written, but unfortunately when the server starts, we just get the 0-byte file of an open but unflushed buffer. I found no server options that would seem to affect this. If the server shuts down, the file is flushed as expected. Thoughts?