Psybnc won't reconnect to the server

[snewp]

Hi,

I'm not really sure if this is still part of the freezebug. Once it will disconnect to the network it will not connect back. I'm just getting "No new messages". I tried doing /bquit and /bconnect still it wont reconnect. Process is still running on the box. I'm using the newest version of psybnc and a debian host.

Linux quad.iprouting.org 2.6.18-128.1.1.el5.028stab062.3 #1 SMP Sun May 10 18:54:51 MSD 2009 i686 GNU/Linux

any ideas? Thanks.

[TheAvatar]

It could be.
Why does it disconnect? What does the psybnc.log say?
Could be another user on the bouncer causing the issue?
Or - it could be the freezebug

[snewp]

Why does it disconnect? - it could be that there was a network interruption to the server/network. I had 2 users also on different network but still experiencing the same problem.

I was not able to check psybnc.log. I have deleted already the old dir. I did recompile a new one. I'll give you update once I
will be experiencing the same problem. Thanks.

[Ravine]

Hi!

I'm sure it's the same bug as reported here:
http://psybnc.at/forum/index.php?topic=74.0

I have 2 machine with debian 32bit, different mobo, different NIC, and the problem is the same: when the ISP disconnects (it's usually router maintenance), i'm not able to reconnect to the bnc (however, we are on the SAME LAN, and no router between us!). Never had this problem with the 2.4 kernel-branch.

R.

[TheAvatar]

And this happens with the unofficial -9 psyBNC version too?

[Ravine]

Yeah. When it started to bugging, i came here, and compiled the -9 one. No change.

[TheAvatar]

I see, but you can connect to the bouncer, but the bouncer can't connect to the IRC-server, right?
The thread you linked to earlier, had problems connecting back to psyBNC too (client to bnc).

I do have another version lying around here not yet suitable for release. I think it might solve the issue you experience, however, it has introduced some other bugs, I would prefer to fix before releasing it to the public, to prevent too many "complaints" about a broken software.

What does psybnc.log say when it doesn't work? It tries to connect but fails, or it doesn't even try and doesn't log anything?
Do you use async dns or blocking dns (default) (make menuconfig)?