Jump to content

HP1

Members
  • Posts

    11
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

Posts posted by HP1

  1. Even if there's any disconnection issues, it's not caused by windows firewall... I never had any random disconnects. Also, kick option is ignored at client response timeout, so it may disconnect client that not sent warden response in given time (1.5 minutes).

    That explains a lot of things :) If I put timeout kicks under effect of kick config, can it result any error?

    One more short notice, logging is a bit too detailed, I should have to buy a new hdd after a week of usage :D

  2. After 2 hours of testing I got a lot of fails on these two memory tests:

    (403, 243, '', '', 4609675, 5, '5E5DC20800', NULL),

    (438, 243, '', '', 11287980, 8, '04000000903C9F00', NULL) this one is same as uac false positives on page 4

    I have no idea if the other is also a false positive or not.

    And i have a question, this implementation does not cause client freezes to mac users?

  3. I have a very similar crash, it occurs after every second server startup.

    2011-05-01 16:49:50 ERROR: Unexpected packet [255] from Wardend, trashing it

    It repeats until world thread hangs and got kicked out. Wardend was running and didnt produce any log entry that could help, only this:

    2011-05-01 16:46:50 Warden system initialized.
    2011-05-01 16:49:59 Accepting connection from '192.168.32.1'
    2011-05-01 16:49:59 World process connected.
    2011-05-01 16:50:14 Terminating connection from '192.168.32.1'

    I used Warden110406b patch and 32bit debian lenny. I runned tests using wine and windows machine for wardend, but world daemon was always on linux. Then I started tcpdumping, and got the following results:

    http://pastebin.com/tRv1bmQ9 < during startup

    http://pastebin.com/G3wTGEBB < during startup

    http://pastebin.com/rcTjeKGY < after closing wardend

    I noticed, that there are only few packets after the loop begins, so mangosd was not getting so many bad packets as the count of log messages. Maybe one false tcp packet starts this kind of loop because world daemon cant move on. I hope I could help. Should I make a few crash backtraces too?

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use