search

PocketMine / PocketMine-MP

Legacy PocketMine-MP repository. Head to https://github.com/pmmp for up to date software.
https://www.pocketmine.net/
GNU Lesser General Public License v3.0
1.26k stars 661 forks source link

[ERROR] A level 2 error happened: "unpack(): Type N: not enough input, need 4, have 3" #1173

Closed dimitrifrom31 closed 10 years ago

dimitrifrom31 commented 10 years ago

Hi,

I am getting the following error when runing the server on windows server 2008 but I do not have it when running on local pc (windows 7):

[ERROR] A level 2 error happened: "unpack(): Type N: not enough input, need 4, have 3" in "E:\minecraftPE\src\utils\Utils.php" at line 463

Regards

dimitrifrom31 commented 10 years ago

Quick note: tried on another machine with similar setup/OS and theres no error. Most likely a conflict with another game server running ? Any way to get rid of the error message ?

iksaku commented 10 years ago

@dimitrifrom31 Are you using the Alpha 1.3.11 or the dev. 1.3.12?

dimitrifrom31 commented 10 years ago

Im using alpha. Cant find dev installer, only source...

ghost commented 10 years ago

drag the dev. source code to pocket mine-mp add all the files but you may need to get YAML and pthreads 1.0.0

iksaku commented 10 years ago

@dimitrifrom31 What OS are you using? Linux, Mac or Windows? (if you are using DroidPocketMine... we can't help you here)

iksaku commented 10 years ago

@dimitrifrom31 OH! and for dev installer, if you host your server on Linux or Mac, please enter to Terminal, 'cd' to your PocketMine server directory and execute this: curl -sL http://cdn.pocketmine.net/installer.sh | bash -s - -v master That will work ;)

dimitrifrom31 commented 10 years ago

Thx for the help, Im running them on windows server 2008, the strange thing being that on my 2 boxes running 2008 I get the error on 1 box only why I suspect some kind of conflict with another app running even if that does not make much sense as they should be able to run in parallel. Ive read about using dev as a suggestion for that kind of issue but for what I could see it never fixed them, I see that similar errors were reported months ago already. Guess I will have to live with it until the cause is found and fixed. My only concern is that it is filling log quite fast making it grow huge (log was 150Mb when I last checked).