Hello,
I installed the latest version of oxide (Version 2.0.886) and its spamming me alot of different errors in the console. It looks like a total chaos and it feels like everything server side is going wrong because of it. I do get though that this is all early alpha, so I wondered if it was normal. I used oxide a while on my testserver to play around with some scripting, and there it was alright but that was without players on it (only myself).
I get reports that it makes the server lag a bit aswell, so i'm assuming somewhere it went wrong for me. Any thoughts? Is it running fine for you? Could I have made critical mistakes somewhere when installing it etc?
I played around with it a little bit and have no plugins installed, so they're not causing it.
Thanks in advance,
Mark
Alot of Errors in the Console, normal?
Discussion in 'Reign of Kings Discussion' started by Mark Metin, May 14, 2015.
-
Wulf Community Admin
Please upload your Reign of Kings logs and Oxide logs so we can see what's going on.
-
I'll start by uploading mine. I noticed I'm having tons of ServerLobbyModule.cs errors. I'll be honest though I haven't spent much time looking into it.
Attached Files:
-
-
Wulf Community Admin
-
Hey, sorry for the lack of response. I've removed oxide for a while until I had time again, and forgot to respond here. It seems indeed my errors are not oxide related, and the console just reveals otherwise invisible errors. Strange that I got reports about lag then, perhaps I should try again. I was just wondering if everything was supposed to be running smoothly or that it had some trouble in general running Oxide on busy servers in these early stages.
The kind of errors i'm getting in the logs are these for example:
Code:PlayerTracker: Tracker for <playername> and DamageNearby has failed to check in, but should be running and has been restarted.
Thanks alot for the work you're doing here, I post this to gather knowledge not to complain or anything!
Mark -
Wulf Community Admin
-
I noticed performance issues too, but i have reasons to believe it is caused by the announcer plugin.
Try disable that if you have it on your server, good luck!