View Issue Details

IDProjectCategoryView StatusLast Update
0004059unrealircdpublic2015-08-08 16:08
Reporterseraph Assigned Tosyzop  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version3.2.9 
Summary0004059: Listener-Errors at ./unreal start not shown at console
DescriptionErrors during the binding to port listeners are no longer shown at ./unreal start, please add them again.
Unreal says nothing but does not start.
Steps To ReproduceHave Unreal running and try to run a new instance from another folder using the same configuration, it will not complain but not start.
3rd party modules

Activities

Stealth

2011-11-26 20:55

reporter   ~0016800

I once made the suggestion to have Unreal list the ports in the terminal and in the log with their status on boot (like InspIRCd does). This way you know which ports have been opened and which one have not when you start the IRCd. It will also eliminate a lot of the "i can't connect to port xxx" questions.

syzop

2011-11-26 21:47

administrator   ~0016801

Seems we're talking about two issues here, the original reporter is talking about UnrealIRCd's failure to start (which is not limited to listener problems) and not reporting this back to us, and Stealth about (possibly partial) listener errors.

Anyway, with regards to the original bug report:
It does work here. If UnrealIRCd fails to start, which is detected by detected by a missing pid file 1 second after start, then it will show an error message and the last 5 lines of the log file:

=====================================================
Check above for possible errors, and this output of
ircd.log. If you cannot solve the problem, read
Unreal.nfo on where to get support
=====================================================
[Sat Nov 26 21:41:48 2011] - Error binding stream socket to IP 0.0.0.0 port 6667 - xxxxxxx.xxxx.xx[]:Address already in use

This is on Linux (Debian 5). Since you didn't fill it in, what OS/distro are you on? And what do you see, could you copy/paste?

seraph

2011-11-26 21:55

reporter   ~0016802

Debian 5 and Debian 6, both were running the original ircd prozess and then (for testing the config) I started the .9 with ./unreal start

The usual Screen output appeard but no error messages like "Address already in use" although the old running and the new starting ircd were using the same ports and addresses. Additionally unreal did not boot and is not listed at ps ux.

syzop

2011-11-27 12:38

administrator   ~0016803

Strange. Why can't I reproduce it then :)

Is it reproducible on your end, like if you try this again?
Looking at the code I can't see why it would not show an error message.
Is there anything different from your configuration than mine... do you install in a separate directory (instead of Unreal3.2)? Do you do something special with pid files?
I don't know...

seraph

2011-11-28 10:34

reporter   ~0016805

The .8.1 that was running was at /home/user/Unreal3.2 and the .9 at /home/user/Unreal3.2.9

Happened on three servers already, again Debian 6.

As I do not have more distributions to try I can only tell from debian...

syzop

2011-11-28 15:13

administrator   ~0016806

Well, like I said, I really can't reproduce it here on Debian 5.
Could I get a shell on one of the boxes to see the problem? You can mail details to [email protected] (or unrealircd.com).
I don't think I will be able to debug or fix this otherwise, as I also see no logic error in the code.

syzop

2012-01-22 17:12

administrator   ~0016893

Waiting for a reproducible case or shell.
If this is not possible, I can understand. It just means nothing can be done.

syzop

2015-08-08 16:08

administrator   ~0018597

I think this already worked fine in 3.2.x but in 3.4.x some code was changed. In any case ./unrealircd start will now show you the address in use errors if it failed to bind.

..though right now it will continue to run if it can bind to at least 1 port... I think it's better to fail completely... but that's another issue.

Issue History

Date Modified Username Field Change
2011-11-26 20:06 seraph New Issue
2011-11-26 20:55 Stealth Note Added: 0016800
2011-11-26 21:47 syzop Note Added: 0016801
2011-11-26 21:55 seraph Note Added: 0016802
2011-11-27 12:38 syzop Note Added: 0016803
2011-11-28 10:34 seraph Note Added: 0016805
2011-11-28 15:13 syzop Note Added: 0016806
2012-01-22 17:12 syzop Note Added: 0016893
2012-01-22 17:12 syzop Status new => feedback
2015-08-08 16:08 syzop Note Added: 0018597
2015-08-08 16:08 syzop Status feedback => closed
2015-08-08 16:08 syzop Assigned To => syzop
2015-08-08 16:08 syzop Resolution open => no change required