DSGame_server error while booting

Post Reply
Khelendil
Posts: 21
Joined: Sun Nov 04, 2012 10:56 pm

DSGame_server error while booting

Post by Khelendil » Tue Jun 18, 2013 11:18 pm

Hey guys.

I ran into this problem after updating the server yesterday from 3304 to 3548. Connect n Search Server come up fine but the gameserver throws the following error:
...
[status] luautils::init:lua initilizing... - [OK]
PANIC: unprotected error in call to Lua API (attempt to index a nil value)

Am i missing a pathchange or a lua upgrade or somethin? prior the update all went well.

I added a Screen of the message and the logfile as attachment. Hope u can help me on this.
DSGame_server[r3548]_crash.png
Did the update with DSPUpdater but hat to manually build the gameserver as the updater didnt do it. No errors on that build. DSPUpdater said 5 unresolved Tables which i just dumped or better i dumped and reinstalled the entire DB.
Attachments
map-server.log
(916 Bytes) Downloaded 172 times

User avatar
kjLotus
Special Guest
Posts: 1813
Joined: Sun Jul 22, 2012 2:16 pm

Re: DSGame_server error while booting

Post by kjLotus » Wed Jun 19, 2013 12:09 am

try build -> clean

Amant
Posts: 12
Joined: Mon Sep 03, 2012 1:47 am
Location: Empyreal Paradox

Re: DSGame_server error while booting

Post by Amant » Wed Jun 19, 2013 3:11 am

Update your commands.conf in the config directory ^^

Khelendil
Posts: 21
Joined: Sun Nov 04, 2012 10:56 pm

Re: DSGame_server error while booting

Post by Khelendil » Wed Jun 19, 2013 1:36 pm

Ok i tried both tipps but still had that error so i just went ahead an got a clean checkout. Its now running again, but i got that old checkout still sitting around for analytics.

Thx for the help though

CYatta
Posts: 1
Joined: Sun Aug 26, 2012 7:23 am

Re: DSGame_server error while booting

Post by CYatta » Sun Sep 29, 2013 3:57 pm

Necro bump to share my experience with this error, in case anyone else comes across it.

Tried to build from clean source again, but still showed error. Not sure if the resolution for me was the commands.conf being updated alone, but I noticed there were some changes to the conf files since last I updated, so I updated all of them. This is when the error went away.

Post Reply