eqemu_server error
I noticed today that I started getting this error on my EQ server:
https://i.ibb.co/njVkjRN/eqemu-server-error.png The server still boots up fine. I opened up eqemu_server.pl and went to line 891, which looks like this: https://i.ibb.co/5xLxfGf/line-891.png I tried removing that last elsif on line 891 but I still get the error. I also tried adding a right curly bracket but no luck either. How can I fix this error? |
Looks like your file got corrupted somehow: https://github.com/EQEmu/Server/blob...server.pl#L887
You should be able to replace the contents of your file with that in the link. EDIT: I've seen self-updates leave a blank file before..not sure why. |
Thanks Uleat.
If I replace the contents of my eqemu_server.pl file with the contents of the file from your github link, is there any chance my server will become corrupt? Right now, even with that weird error on line 891, the server runs just fine. I don't want to make this worse and my knowledge about the eqemu_server.pl is non-existent. |
No it wont do ANYTHING your server that file just is a UTILITY
|
That file from Github has 2700 lines and looks drastically different than the one I have. Mine only has 891 lines.
What exactly is the utility even doing, since I'm not noticing anything wrong with my server at all. Should I even bother updating the eqemu_server.pl or can I safely ignore it? I think I'm just not understanding at all what it's even there for =p |
Every time that you start your server, that file gets invoked to check for updates.
It's suppose to have a self-update feature that checks for file changes..but, if your file is corrupt/incomplete, it could be missing that part of it. |
Quote:
|
Thank you for the help everyone. Deleting the file completely and running my server allowed it to automatically download a new, non-corrupt version and I am no longer getting any errors.
As for the dos command, I am using Windows 7 and I typed cmd, it pulled up the cmd window and I typed: perl eqemu_server.pl ...but it didn't pull up a menu with all sorts of options. Am I using incorrect syntax? |
I'm assuming you were running that command in the same folder where the file is (server folder), but when perl was installed, it would usually put an entry in the system path variables so the perl command can be found from any folder on your computer.
|
|
Thank you Huppy. The screenshot was very helpful. It shows commands I have no desire to use, so I will not pursue this any further. Thank you!
|
Sure, no problem. But those menus have sub menus, (just one example), grabbing updated binaries for your server in the future, when they are released. Your preferences, but the option is there if you need it.
|
By the way, (this is for anyone, who may encounter this), if you see an error like this when running that script :
D:\eqemuTest>perl eqemu_server.pl [Update] No script update necessary... invalid character encountered while parsing JSON string, at character offset 182 4 (before "\x{1}BOX TEST ...") at eqemu_server.pl line 1312 That error was caused, because of "special characters" I had in the server long name in the eqemu_config.json file. EDIT: Guess I should add something. Considering that script is auto-run everytime you start your server, (checking for updates), I never saw that error in the world console window while running server. I didn't see it until I manually ran the script from cmd prompt. (script halted). So I am assuming everytime one starts their server up with special characters in the name, it's not really checking for updates, but the server still starts and runs. |
All times are GMT -4. The time now is 12:19 AM. |
Powered by vBulletin®, Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.