Old topic is closed, my new topic seems removed, but server is still crashing.
https://pastebin.com/j88PZjAc
https://pastebin.com/j88PZjAc
Server still crashing
yes crashes continue,I shut down the server and I'm happy..
No problem with the vanilla server,a problem with oxide.wulf left us in class:)
(13:28:46) | Protocol: 2151.175.1
Build Date: 02/20/2019 14:27:39
Unity Version: 2018.3.3f1
Changeset: 32268
Branch: release
(13:28:48) | Protocol: 2151.175.1
Build Date: 02/20/2019 14:27:39
Unity Version: 2018.3.3f1
Changeset: 32268
Branch: release
Oxide.Rust Version: 2.0.4139
[quote]what was going on last before the crash, etc.[/quote]
Yeah, if we all would knew that :)
- Mono DLL loaded successfully at 'C:\Users\Administrator\Documents\RUST\rustds\MonoBleedingEdge\EmbedRuntime\mono-2.0-bdwgc.dll'.
- Stack Trace of Crashed Thread 1152:
- ERROR: SymGetSymFromAddr64, GetLastError: 'The specified module could not be found.' (Address: 00000070390BD110)
- ERROR: SymGetModuleInfo64, GetLastError: 'A dynamic link library (DLL) initialization routine failed.' (Address: 00000070390BD110)
- 0x00000070390BD110 ((<unknown>)) (function-name not available)
- ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFB8D2C331B)
- 0x00007FFB8D2C331B (UnityPlayer) (function-name not available)
- 0x00007FFB8DCEDC44 (UnityPlayer) UnityMain
- 0x00007FFB8DC8F5B7 (UnityPlayer) UnityMain
The most common issues that trigger “The specified module could not be found” alert are:
- missing or corrupted DLL files;
- damaged Windows registry entries;
- incorrect installation of programs;
- outdated Windows drivers;
@reel25 You need to provide more information, logs, and details about your crash. I was replying to @riderxyz who had provided a log message.
We aren't getting many reports of this, so it seems to be isolated to few people. That would indicate an issue with your particular installation.
What OS are you running on?
Have you tried re-installing Oxide?
Have you tried re-installing your server?
What OS are you running on?
Have you tried re-installing Oxide?
Have you tried re-installing your server?
In response to Calytic ():We aren't getting many reports of this, so it seems to be isolated to few people. That would indica...
server reinstalled repeatedly,
win 7, win 10, win server 2012 operating system tested,
oxide has been repeatedly reloaded,
game files reset repeatedly..
vanilla works smoothly, crashes begin when oxide is loaded.
win 7, win 10, win server 2012 operating system tested,
oxide has been repeatedly reloaded,
game files reset repeatedly..
vanilla works smoothly, crashes begin when oxide is loaded.
Same here. Even fresh installs of Rust and oxide crash once a day or so. Only thing that's the same:
Hardware
Windows 2012 on a Proxmox KVM
This reminds me of a particular issue there was with VM's and the gathering of IP addresses.
Hardware
Windows 2012 on a Proxmox KVM
This reminds me of a particular issue there was with VM's and the gathering of IP addresses.