No idea what's causing this. The effects though, are increased server lag, and tons of log spam.
~$ grep PDLDLKDJLKDJLKDJLKDJLKDJDLKJD log.txt.1 |head
[2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD
[2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD
[2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD
[2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD
[2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD
[2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD
[2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD
[2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD
[2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD
[2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD
~$ grep -v PDLDLKDJLKDJLKDJLKDJLKDJDLKJD log.txt.1 |wc -l
19281
~$ grep PDLDLKDJLKDJLKDJLKDJLKDJDLKJD log.txt.1 |wc -l
33390
Only log entry that seems to intermix consistently is:
[2016-05-25 14:25:25] [SERVER][RAIL] collision time limit reached. Returning to last possible
Also just had the server crash/restart, so we had an opportunity to catch this error from the server's onset. Error begins streaming 1 minute 34 seconds after the server's first "[VERION] loading version from install dir: ./" log entry. No obvious causes. Logs have been set-aside, download URL available upon request
hash of log archive: a1e261ec630faf563c763de11646a970