View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001995 | unreal | ircd | public | 2004-07-28 20:59 | 2004-08-04 04:15 |
| Reporter | binary101 | Assigned To | |||
| Priority | normal | Severity | crash | Reproducibility | N/A |
| Status | closed | Resolution | open | ||
| Product Version | 3.2.1 | ||||
| Summary | 0001995: [08:47] -matrix.ch.il.ozirc.org- *** Notice -- [BUG] trying to add fd #19400 to 0x8128d20 (0x8128ec0/0x8128360/0x81280c0/0x8128d | ||||
| Description | I had an entry in unrealircd.conf to allow an Service be an Operator, once it opered, i got the above notice on my ircd, and it crashed. | ||||
| 3rd party modules | |||||
|
|
Uhh, can you explain this. I don't understand what you mean by "service" |
|
|
I presume someone/something used /OPER on the server locally? And not something via services or god knows what ;p. It's very odd at least, fd (or actually 'slot' would be more appropriate) can never be such an insane value (19400). And when looking at the code I don't see anything wrong. I therefore think it's something like: memory corruption (would be a bit odd), or something with compiling. 1. Is this the first time you get this? How did things go in the past? 2. Did you recently change MAXCONNECTIONS or recompile UnrealIRCd for any reason? (if so, how long ago / what did you change). 3. Any 3rd party modules? (anything besides commands and cloak) 4. Any ircd modifications? (just asking to be sure) Oh.. you said it even crashed.. Well, in that case.. also include a gdb backtrace by doing: -- gdb src/ircd name.of.core.file bt -- |
|
|
hey guys, sorry about the late response. Yes I did get a service, (OperServ) to Oper via it's own username/password in the unrealircd.conf, I get that message everytime OperServ opers, the IRCd will crash there after that when someone quits normally, connect normally, or when services disconnect from the network. MAXCONNECTIONS was changed to 100. No third party modules. I have been using Unreal since Beta-4 and I've never ever gotten this message when I allow OperServ to become an Global Operator. -bash-2.05b$ gdb src/ircd core.3975 -bash: gdb: command not found tried the command, didn't work sorry. |
|
|
Usually services clients like operserv have their own server. Do you mean a U:lined eggdrop or something similar with this nickname? |
|
|
U:Lined eggdrop... *shudder* |
|
|
aquanight :P |
|
|
A client on a remote server should NEVER send an oper command to another server. |
|
|
Well I've never gotten the message in past releases. So it must be current in this release. I only required OperServ for oper permissions so I can set G:Lines via a Service instead of Opers doing /Gline. Worked in the past. Services are connected through there own remote server via mIRC sockets, then a link is made, then I REGISTER the services via NICK, then set modes, then I get .sockwrite -tn serv : $+ $OperServ OPER $susername $spassword and thats when the notice from the ircd comes in. |
|
|
Right, that's *100%* improper use of server commands. Perhaps learn something about services/the protocol first... you clearly have no idea what you are doing. You should be glad (or not) that it didn't even crash your ircd in past releases, it very easily can since you are f*cking things up as hell :P. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-07-28 20:59 | binary101 | New Issue | |
| 2004-07-28 21:12 |
|
Note Added: 0007270 | |
| 2004-07-29 17:16 | syzop | Note Added: 0007272 | |
| 2004-08-03 12:53 | binary101 | Note Added: 0007295 | |
| 2004-08-03 15:51 | vonitsanet | Note Added: 0007296 | |
| 2004-08-03 21:41 | aquanight | Note Added: 0007298 | |
| 2004-08-03 22:17 | vonitsanet | Note Added: 0007299 | |
| 2004-08-03 23:11 |
|
Note Added: 0007300 | |
| 2004-08-04 00:40 | binary101 | Note Added: 0007301 | |
| 2004-08-04 04:15 | syzop | Status | new => closed |
| 2004-08-04 04:15 | syzop | Note Added: 0007302 |
