LinuxGSM Alert Summary ================================= Server name Lazy Rusters V - RolePlay Test Information rustserver is not running. Game server has been restarted. Game Rust Server IP 24.153.122.246:29090 Hostname rustserver Server Time Mon 05 Jan 2026 08:20:08 AM EST Distro Details ================================= Date: Mon 05 Jan 2026 08:20:08 AM EST Distro: Ubuntu 20.04.6 LTS Arch: x86_64 Kernel: 5.4.0-216-generic Hostname: rustserver Environment: none Uptime: 74d, 11h, 13m tmux: 3.0a glibc: 2.31 Server Resource ================================= CPU Model: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz Cores: 4 Frequency: 3771.194MHz Avg Load: 2.53, 4.82, 6.70 Memory Mem: total used free cached available Physical: 32GB 9.3GB 22GB 600MB 22GB Swap: 4.0GB 1.8GB 2.3GB Storage Filesystem: /dev/mapper/ubuntu--vg-ubuntu--lv Total: 98G Used: 78G Available: 16G Network Interface: eno1 Link Speed: 1000Mb/s IP: 192.168.1.66 Internet IP: 24.153.122.246 Rust Resource Usage ================================= CPU Used: 0% Mem Used: 0% 0MB Storage Total: 9.6G Serverfiles: 8.5G Rust Server Details ================================= Server name: Lazy Rusters V - RolePlay Test App ID: 258550 Server IP: 192.168.1.66:29090 Internet IP: 24.153.122.246:29090 RCON password: ******** RCON web: 1 Maxplayers: 100 Game mode: vanilla Tick rate: 30 Save interval: 300s Seed: 666 Salt: 0 World size: 4500m Status: STOPPED rustserver Logs ================================= Script log =================== /home/lr1/log/script/rustserver-script.log Jan 05 08:00:09.693 rustserver: MONITOR: PASS: Checking session: OK Jan 05 08:00:11.208 rustserver: MONITOR: INFO: Querying port: gamedig: 192.168.1.66:29015 : 1 : QUERYING Jan 05 08:00:12.928 rustserver: MONITOR: PASS: Querying port: gamedig: 192.168.1.66:29015 : 1 : OK Jan 05 08:00:12.936 rustserver: MONITOR: INFO: Server name: Lazy Rusters V - RolePlay Test Jan 05 08:00:12.941 rustserver: MONITOR: INFO: Players: 0/100 Jan 05 08:00:12.943 rustserver: MONITOR: INFO: Map: Procedural Map Jan 05 08:00:12.971 rustserver: MONITOR: INFO: LinuxGSM version: v24.3.2 Jan 05 08:00:12.974 rustserver: MONITOR: PASS: core_exit.sh exiting with code: 0 Jan 05 08:10:03.257 rustserver: MONITOR: PASS: Using cached IP as public IP address Jan 05 08:11:12.486 rustserver: MONITOR: PASS: Using cached IP as public IP address Jan 05 08:11:14.251 rustserver: MONITOR: INFO: Checking session: CHECKING Jan 05 08:11:14.526 rustserver: MONITOR: PASS: Checking session: OK Jan 05 08:11:16.051 rustserver: MONITOR: INFO: Querying port: gamedig: 192.168.1.66:29015 : 1 : QUERYING Jan 05 08:11:17.699 rustserver: MONITOR: PASS: Querying port: gamedig: 192.168.1.66:29015 : 1 : OK Jan 05 08:11:17.704 rustserver: MONITOR: INFO: Server name: Lazy Rusters V - RolePlay Test Jan 05 08:11:17.707 rustserver: MONITOR: INFO: Players: 0/100 Jan 05 08:11:17.708 rustserver: MONITOR: INFO: Map: Procedural Map Jan 05 08:11:17.721 rustserver: MONITOR: INFO: LinuxGSM version: v24.3.2 Jan 05 08:11:17.723 rustserver: MONITOR: PASS: core_exit.sh exiting with code: 0 Jan 05 08:20:02.764 rustserver: MONITOR: PASS: Using cached IP as public IP address Jan 05 08:20:05.407 rustserver: MONITOR: PASS: Using cached IP as public IP address Jan 05 08:20:07.021 rustserver: MONITOR: INFO: Checking session: CHECKING Jan 05 08:20:07.258 rustserver: MONITOR: FATAL: Checking session: FAIL Jan 05 08:20:07.266 rustserver: MONITOR: INFO: Sending alert: rustserver is not running. Game server has been restarted Jan 05 08:20:08.020 rustserver: MONITOR: PASS: Using cached IP as public IP address Console log ==================== /home/lr1/log/console/rustserver-console.log (LOG FILE IS EMPTY) Server log =================== /home/lr1/log/server src/steamnetworkingsockets/clientlib/steamnetworkingsockets_lowlevel.cpp (1872) : Assertion Failed: SteamnetworkingSockets service thread waited 70ms for lock! This directly adds to network latency! It could be a bug, but it's usually caused by general performance problem such as thread starvation or a debug output handler taking too long. src/steamnetworkingsockets/clientlib/steamnetworkingsockets_lowlevel.cpp (1872) : Assertion Failed: SteamnetworkingSockets service thread waited 70ms for lock! This directly adds to network latency! It could be a bug, but it's usually caused by general performance problem such as thread starvation or a debug output handler taking too long. src/steamnetworkingsockets/clientlib/steamnetworkingsockets_lowlevel.cpp (1872) : Assertion Failed: SteamnetworkingSockets service thread waited 78ms for lock! This directly adds to network latency! It could be a bug, but it's usually caused by general performance problem such as thread starvation or a debug output handler taking too long. src/steamnetworkingsockets/clientlib/steamnetworkingsockets_lowlevel.cpp (1872) : Assertion Failed: SteamnetworkingSockets service thread waited 78ms for lock! This directly adds to network latency! It could be a bug, but it's usually caused by general performance problem such as thread starvation or a debug output handler taking too long. src/steamnetworkingsockets/clientlib/steamnetworkingsockets_lowlevel.cpp (1872) : Assertion Failed: SteamnetworkingSockets service thread waited 199ms for lock! This directly adds to network latency! It could be a bug, but it's usually caused by general performance problem such as thread starvation or a debug output handler taking too long. src/steamnetworkingsockets/clientlib/steamnetworkingsockets_lowlevel.cpp (1872) : Assertion Failed: SteamnetworkingSockets service thread waited 199ms for lock! This directly adds to network latency! It could be a bug, but it's usually caused by general performance problem such as thread starvation or a debug output handler taking too long. src/steamnetworkingsockets/clientlib/steamnetworkingsockets_lowlevel.cpp (1872) : Assertion Failed: SteamnetworkingSockets service thread waited 96ms for lock! This directly adds to network latency! It could be a bug, but it's usually caused by general performance problem such as thread starvation or a debug output handler taking too long. src/steamnetworkingsockets/clientlib/steamnetworkingsockets_lowlevel.cpp (1872) : Assertion Failed: SteamnetworkingSockets service thread waited 96ms for lock! This directly adds to network latency! It could be a bug, but it's usually caused by general performance problem such as thread starvation or a debug output handler taking too long. src/steamnetworkingsockets/clientlib/steamnetworkingsockets_lowlevel.cpp (1872) : Assertion Failed: SteamnetworkingSockets service thread waited 50ms for lock! This directly adds to network latency! It could be a bug, but it's usually caused by general performance problem such as thread starvation or a debug output handler taking too long. src/steamnetworkingsockets/clientlib/steamnetworkingsockets_lowlevel.cpp (1872) : Assertion Failed: SteamnetworkingSockets service thread waited 50ms for lock! This directly adds to network latency! It could be a bug, but it's usually caused by general performance problem such as thread starvation or a debug output handler taking too long.