Zhui
Inactive Member-
Posts
6 -
Joined
-
Last visited
-
Feedback
0%
Zhui's Achievements
-
Because those files are corrupted. It will write in errorlog this: SYSERR: Nov 9 16:21:27 :: Process: FDWATCH: peer null in event: ident 21 SYSERR: Nov 9 16:21:43 :: Process: FDWATCH: peer null in event: ident 21 SYSERR: Nov 9 16:21:44 :: Process: FDWATCH: peer null in event: ident 22 SYSERR: Nov 9 16:21:44 :: Process: FDWATCH: peer null in event: ident 23 SYSERR: Nov 9 16:22:01 :: Process: FDWATCH: peer null in event: ident 23 and your core will restart, restart, restart... making it unable to join and play. Nobody can solve this problem, because nobody knows, why this error appears - it's just corrupted. Lot of ppl have this error with these files. Don't use them. Better try other files. I'm using those files and never had this error once.
-
How do I connect to winscp? Do I need to setup something like hamachi or what?
-
What do I need to update? Wich client do you recommend using the 34k files?
-
So I updated to the 34k from the 2089M from Invoice 2013v2. Pets work fine and stuff. But there is a problem with the mounts. When I press, for example, the White Lion Seal I mount it and the Seal goes into the item slot. When I press ctrl+g to get down, I unmount but the seal is still in the item slot. Is there a fix to this? Let me know if its not clear enough. Thanks for every help.
-
So I added the Tables from the files, now its 'working'. The Channels Start up, but I get the 'connect: Connection refused' And thats the ch1 syserr: SYSERR: Nov 5 04:47:43 :: socket_connect: HOST localhost:15000, could not connect. (Many times) And the db syserr: SYSERR: Nov 5 04:45:32 :: pid_init: Start of pid: 774 SYSERR: Nov 5 04:45:32 :: Start: TABLE_POSTFIX not configured use default
-
Hey, I was trying to Upgrade from the 2089M Files to 34k. So I added a package folder, made linkings. Then I replaced the 'db' file with the new one. Now after some time fixxing some smaller things like adding the txt and stuff I get this: 'Failed localization information so exit' when I start the Server with start.sh The cores don't even start up: Thanks for any help.