I had this problem a while ago, not sure how far back, but I've had this happen for the second time in as many days. Nothing seems to be throwing any errors in the logs, but out of the blue the Oxide Core will reboot/re-initialize, which then causes the server to crash and do a hard reboot.
I have two different servers, one is running on a Windows platform, and I haven't had this issue before, only seems to happen on the one running the Linux build.
The only clue I can think of is there being some memory leak, either in one of the plugins or in the server client build itself. Just this time, I noticed my server ram usage getting above 17gb, which was insane, and then it crashed. So perhaps there's a larger issue at play that's then causing Oxide to re-initializ.
I'm willing to share any log files, or do my best to try to capture the server logs before they get overridden in a crash. Or maybe capture them when I notice the RAM usage is extreme. I just want to help incase the linux build of oxide has any issues. If it's on FP, then we're just at the mercy of Helk et all lol.
Server crashing after Oxide re-initializing on Linux
Oxide is only initialized at one point on server startup. It should never reinitialize unless the Rust server is doing something odd that it shouldn't be.
Right, I just don't know what could be causing it to do that though. Here are the two log excerpts from the last crashes.
From Jan. 10, 2021
11:48 [Warning] [Tebex Donate] Successfully logged all stored connection events!
11:48 [Info] [Welcomer] nath_2233 joined the server
11:48 [Info] [Auto Purge] The purge has been started.
11:49 [Warning] [Tebex Donate] Attempting to process commands in the queue...
11:49 [Warning] [Tebex Donate] There are no online commands that need to be processed!
11:49 [Info] Loading Oxide Core v2.0.3991...
11:49 [Info] Loading extensions...
11:49 [Info] Loaded extension CSharp v2.0.4041 by Oxide Team and Contributors
11:49 [Info] Loaded extension MySql v2.0.3760 by Oxide Team and Contributors
11:49 [Info] Loaded extension Rust v2.0.4908 by Oxide Team and Contributors
11:49 [Info] Loaded extension SQLite v2.0.3762 by Oxide Team and Contributors
11:49 [Info] Loaded extension Unity v2.0.3772 by Oxide Team and Contributors
11:49 [Info] Latest compiler MD5: 8ce6d27e7718e3d164766bba8833537a
11:49 [Info] Local compiler MD5: 8ce6d27e7718e3d164766bba8833537a
11:49 [Info] Using Covalence provider for game 'Rust'
11:49 [Info] Loading plugins...From Jan. 9, 2021
22:00 [Warning] [Tebex Donate] Attempting to process commands in the queue...
22:00 [Warning] [Tebex Donate] There are no online commands that need to be processed!
22:00 [Info] [Lights On] Lights coming on. Ending at 9
22:01 [Warning] Calling 'OnServerSave' on 'FurnaceSplitter v2.3.1' took 105ms
22:01 [Info] Loading Oxide Core v2.0.3991...
22:01 [Info] Loading extensions...
22:01 [Info] Loaded extension CSharp v2.0.4041 by Oxide Team and Contributors
22:01 [Info] Loaded extension MySql v2.0.3760 by Oxide Team and Contributors
22:01 [Info] Loaded extension Rust v2.0.4908 by Oxide Team and Contributors
22:01 [Info] Loaded extension SQLite v2.0.3762 by Oxide Team and Contributors
22:01 [Info] Loaded extension Unity v2.0.3772 by Oxide Team and Contributors
22:01 [Info] Latest compiler MD5: 8ce6d27e7718e3d164766bba8833537a
22:01 [Info] Local compiler MD5: 8ce6d27e7718e3d164766bba8833537a
22:01 [Info] Using Covalence provider for game 'Rust'
22:01 [Info] Loading plugins...I'll do my best to try to save the server log next time I notice the memory usage spike.
Merged post@wulf, The server memory was sitting fine a 7gb after reboot, now it spiked up past 15gb. I can send you the server's log.txt file if you don't mind taking a look to see if anything is amiss?
That looks like a normal startup to me, not it re-initializing during runtime. The only way for it to re-initialize is if the Rust server itself re-initializes for some reason (it shouldn't). There's no indication there that your memory usage spike is related to Oxide's core either. Something on that server would have to call GameSetup.Awake(), BootStrap.Init_Tier0(), or Interface.Initialize() in order for that to happen; none of which happen naturally after the initial server boot.
Hmm, very odd then. Well thanks for the help. I'll keep digging, could just be a specific plugin causing problems. Or it could just be the rust build for linux servers.
I've not seen but maybe one or two reports of this, so it sounds like something else at play that is triggering it.