View Issue Details

IDProjectCategoryView StatusLast Update
0003224unrealircdpublic2010-07-14 17:47
ReporterJasonTik Assigned To 
PrioritynormalSeverityminorReproducibilityrandom
Status closedResolutionduplicate 
Product Version3.2.6 
Summary0003224: A rehash is already in progress.... Forever.
DescriptionI recently received the message "A rehash is already in progress". The rehash appeared hung forever. I am not certain, bug I suspect it has to do with a network or server error in retrieving the remote includes.

This needs better error handling, it seems. It would be much better to fail than to hang forever.
3rd party modules

Activities

djGrrr

2007-02-02 14:22

reporter   ~0013160

Last edited: 2007-02-02 14:28

Remote includes need a timeout value...like 5 seconds maybe
Is this possible with curl ?

edit: actually, it seems there is already a 45 second timeout in remote includes...

Bricker

2007-02-02 20:36

reporter   ~0013165

hmm, i believe i found an issue like this during testing and believed it to be fixed, i'll see if i cant find anything of it, but as it shows, it must not be fixed *shrugs*

JasonTik

2007-02-04 13:32

reporter   ~0013187

Usually when there is a timeout or something, it goes ERROR, and all is well.

There is, however, though I cannot say what, an unhandled error somewhere.

Stealth

2007-02-04 16:40

reporter   ~0013190

Last edited: 2007-02-04 16:40

Maybe something like:

set::remote-includes::timeout
set::remote-includes::retries
set::remote-includes::bind-ip

Those 3 settings will be great for remote includes, and solve multiple issues :)

EDIT: Typo

djGrrr

2007-02-04 17:55

reporter   ~0013191

Last edited: 2007-02-04 18:00

set::remote-includes::bind-ip would prove to be useless as it can't possibly work, because of the way the conf file is parsed.

Look at report 0003185 for a possible solution to that problem

edit: actually, for that matter, all those settings are useless because of the way config files are parsed.

Bricker

2007-02-04 19:06

reporter   ~0013192

There was supposed to be an error, and i think it had smth to do with its check wait time, but i havnt been able to locate it. give syzop or aqua a poke on #u-s and DEMAND they look at it

syzop

2010-07-14 17:46

administrator   ~0016177

Since we never heard of this again for the past 3 years, and the clear timeout of 45s, I think this can be closed..
See als Bricker's comments

Issue History

Date Modified Username Field Change
2007-02-02 13:44 JasonTik New Issue
2007-02-02 14:22 djGrrr Note Added: 0013160
2007-02-02 14:28 djGrrr Note Edited: 0013160
2007-02-02 20:36 Bricker Note Added: 0013165
2007-02-04 13:32 JasonTik Note Added: 0013187
2007-02-04 16:40 Stealth Note Added: 0013190
2007-02-04 16:40 Stealth Note Edited: 0013190
2007-02-04 17:55 djGrrr Note Added: 0013191
2007-02-04 17:56 djGrrr Note Edited: 0013191
2007-02-04 18:00 djGrrr Note Edited: 0013191
2007-02-04 19:06 Bricker Note Added: 0013192
2007-04-27 03:14 stskeeps Status new => acknowledged
2010-07-14 17:46 syzop QA => Not touched yet by developer
2010-07-14 17:46 syzop U4: Need for upstream patch => No need for upstream InspIRCd patch
2010-07-14 17:46 syzop Note Added: 0016177
2010-07-14 17:46 syzop Status acknowledged => closed
2010-07-14 17:47 syzop Resolution open => duplicate