regal spear
We're not entirely sure the cause, but this was all that could be figured out. it happened 3 minutes after midnight and the server crashed when the user tried to reconnect after it started acting weird - around midnight UTC.
is there maybe some timezone math going on that breaks when the date changes? the only two log lines will be posted in reply
Server Info [2024-07-09 00:03:56] World saved in 18 ms
Player {redacted steam ID} ERROR: TCP Socket Faild to RECV
everything before that is more successful save messages
karmic wagon
Do you have a crontab or something similar?
It's unlikely that this is caused by the game
regal spear
no crontabs beyond log rotate
which I can't see affecting the game server. nothing else was impacted, the server process just exited with that log message
no dmesg logs around that time either, so whatever this was, it was internal to the service. I wish I'd checked the exit code, but I was more concerned with getting the server back up
sonic bison
I was in game on the server, things started to seem a touch out of sinc so I relogged and was unable to join the server. As a side not my server list only had around 5 serveers in it until I reloaded the game at which point I could see all of them except tslaroths server.
regal spear
does your server go to sleep after midnight? 😛
nope. this is a dedicated VM for this purpose, pre-configured to stay awake, along with kernel queuing setup for userland performance
Distributor ID: Ubuntu
Description: Ubuntu 24.04 LTS
Release: 24.04
Codename: noble```my bad, there's 2 cron jobs at midnight utc; dpkg cache update and log rotate:
2024-07-09T00:00:13.334303+00:00 host systemd[1]: Starting dpkg-db-backup.service - Daily dpkg database backup service...
2024-07-09T00:00:13.340803+00:00 host systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
2024-07-09T00:00:13.370234+00:00 host systemd[1]: Starting logrotate.service - Rotate log files...
2024-07-09T00:00:13.394275+00:00 host systemd[1]: dpkg-db-backup.service: Deactivated successfully.
2024-07-09T00:00:13.394585+00:00 host systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service.
2024-07-09T00:00:13.395465+00:00 host systemd[1]: sysstat-collect.service: Deactivated successfully.
2024-07-09T00:00:13.395623+00:00 host systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
2024-07-09T00:00:13.525450+00:00 host systemd[1]: logrotate.service: Deactivated successfully.
2024-07-09T00:00:13.525662+00:00 host systemd[1]: Finished logrotate.service - Rotate log files.```sysstat runs multiple times a day, without issue before
this isn't a huge deal, this server has ran for more than a week with maybe 3 restarts, but it just struck me as super-weird that it happened right at midnight UTC
looks neat in the graphs though lol
🤔 @sonic bison did you do something about 3 hours before the crash (that spike in the CPU usage)?
or is that when you logged in?
sonic bison
I was making a lot of things (building n testing etc), that evening but dont remember any changes in performance atr all except for directly before I relogged