Destrian Posted March 4, 2021 Share Posted March 4, 2021 The Linux Server version doesn't show any console output. Windows updates on real time but Linux freezes after "Setting breakpad minidump AppID = 346110" Link to comment Share on other sites More sharing options...
LHammonds Posted April 7, 2021 Share Posted April 7, 2021 I've noticed nothing shows up in the log until the server is stopped (at least during testing with nobody on the server) In GameUserSettings.ini, there is this entry: RCONServerGameLogBuffer=600 But probably only applies to how many lines get returned when viewing remotely. Might not trigger a flush to disk if this number is lowered. I tried the "getchat" command via rcon to see if it causes the buffer to dump to the log file...however, there might not be anything to flush on my test server. I find it really odd we don't have realtime access to log data so we could use a "tail -f" command to keep an eye on the log as entries are added. LHammonds Link to comment Share on other sites More sharing options...
Volunteer Moderator invincibleqc Posted April 7, 2021 Volunteer Moderator Share Posted April 7, 2021 32 minutes ago, LHammonds said: I've noticed nothing shows up in the log until the server is stopped (at least during testing with nobody on the server) In GameUserSettings.ini, there is this entry: RCONServerGameLogBuffer=600 But probably only applies to how many lines get returned when viewing remotely. Might not trigger a flush to disk if this number is lowered. I tried the "getchat" command via rcon to see if it causes the buffer to dump to the log file...however, there might not be anything to flush on my test server. I find it really odd we don't have realtime access to log data so we could use a "tail -f" command to keep an eye on the log as entries are added. LHammonds You can set the following launch option to force the asynchronous writer to flush each outputs: -forcelogflush But it can be extremely resource intensive due to how noisy logging can get and how slow filesystem calls can be. Alternatively, the following option should enable real-time logging in the server console (or an external one if set client-side): -log Or, you can set it to any symlinked name you want: log=foo.log -forcelogflush And tail that buffer. Link to comment Share on other sites More sharing options...
LHammonds Posted April 7, 2021 Share Posted April 7, 2021 Ah sweet. Shouldn't be much of a problem with a low cap server. Even if it did pose I/O issues, one could setup a small ram drive to write the logs to and sync to HD once in a while. Thanks for the reply Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.