search

TeamUlysses / utime

17 stars 18 forks source link

Control Panel related crash. #1

Open ricoben3 opened 8 years ago

ricoben3 commented 8 years ago

[XXXXXXX|XXXXXXXXX] Lua Error: controlpanel.Get() - Error creating a ControlPanel! You're calling this function too early! Call it in a hook!

I updated ULib and ULX. It appears to be only when certain people join. Not sure what to do about it server side but its happening. Not sure if it caused my server to crash, but my server did restart twice in the middle of the night.

Nayruden commented 8 years ago

Why do you think it's causing your server to crash? On Mon, Jul 11, 2016 at 13:13 ricoben3 notifications@github.com wrote:

[XXXXXXX|XXXXXXXXX] Lua Error: controlpanel.Get() - Error creating a ControlPanel! You're calling this function too early! Call it in a hook!

I updated ULib and ULX. It appears to be only when certain people join. Not sure what to do about it server side but its apparently causing my server to crash.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/TeamUlysses/utime/issues/1, or mute the thread https://github.com/notifications/unsubscribe/AABAzz9jHAqjXn-Ptclmu9ovDeuK2zpJks5qUnmzgaJpZM4JJlPk .

ricoben3 commented 8 years ago

I looked at the start bat server prompt, i saw only those errors, and i saw in the middle of the night that the server restarted twice while I was sleeping, via the sdsrc.exe(I dont know the name here, but its what the start.bat opens) command prompt.

davidepaci commented 7 years ago

Hi, is the error ever going to get fixed soon? It's quite annoying since I'm not capable of fixing it myself.

ghost commented 7 years ago

This is still a reoccurring issue. Is there a fix planned for this?

Nayruden commented 7 years ago

Since this is a client-side error, it does not affect the server. Additionally, I have not been able to replicate it, but my understanding is that the error doesn't actually affect anything client-side either.

BlackCetha commented 3 years ago

It seems that it only happens when a player joins the server for the first time. There might be other things going on that slow the initialization phase down and thus lead to unexpected state.