View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000691 | unreal | ircd | public | 2003-01-31 15:45 | 2003-05-04 21:09 |
| Reporter | Maxsus | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | sometimes |
| Status | closed | Resolution | open | ||
| Product Version | 3.2-beta14 | ||||
| Summary | 0000691: [Win32] Rehash and die after XX hours | ||||
| Description | After a few tries on our network, we have concluded that if any amount of rehashing is done to the windows version of the ircd that it will go now within the next 24-48 hours. Looking through my event logs I found this to be true, I went 5 days without making a single change to the conf, and the server stayed up fine no problem. After that I made one little adjustment to the conf....and poof less then a day later the server went down | ||||
| Steps To Reproduce | 1) Run Server 2) Edit CONF and rehash 3) Wait less then a day | ||||
| 3rd party modules | |||||
|
|
I also have this problem. Rehashing seems to introduce some unknown instability that causes Unreal 3.2 to simply crash within the next day or so. There's no error dump of any kind, just the Microsoft error reporter |
|
|
Updated title. |
|
|
some additional info that just occured to me... I used to run a straight DreamForge wIRCd a while back, and it had a near identical problem that occured after a rehash where, given a bit of time, a user logging in would cause wIRCd to kernel dump... is it possible that this is part of the archaic DreamForge code? Hoping this might aid in hunting down the bug |
|
|
I'm not sure if that's related, your client is sending "1§" and the server replies with unknown command, that's pretty... normal ;P. Also I'm sorry but I don't trace win32 bugs because 1. I dont like windows coding, 2. I dont like ircds at win, 3. debugging/tracing at windows is more difficult / requires additional tools. Also in this particular case tracing these types of bugs is almost impossible, it's more likely someday a bug will be discovered somewhere which will cause this bug to disapear... But ofcourse I might be wrong and someone may magically find the bug! |
|
|
LoL Well thanks Syzop, any suggestions for us lame code users??? |
|
|
some more interesting notes from over the last 3 days... I changed my conf file to be several smaller files using includes and the crashes seem to have stopped. This leads me to wonder if the rehash problem isn't related to a buffer limitation or bug in implimentation or unchecked pointer in the Windows code. I'm not much of a coder though, so this is only speculation, someone who knows more about WinNT programming will probably have better ideas =^_^= |
|
|
Maybe fixed in beta16, who knows... feel free to re-report any crashes. |
