Closed GoogleCodeExporter closed 9 years ago
Gave as much info as I could.. but it seems to be happening at 3-4am every time
and I'm rarely up to see what the problem is :/
This has been a reoccurring issue for me since 1.6 (when I started using it).
I have a Teamviewer (remove desktop) connection to the computer in question
that doesn't die when the bot does.
I'll submit more error reports as I find them.
Original comment by Tnade...@gmail.com
on 6 Feb 2013 at 8:13
So I think I found the "problem".
This is what happens at the time of the disconnect:
http://paste.ubuntu.com/1615741/
Aka, my IP runs out and I'm handed a new one by the router. I've put down a
static ip for now but I don't see why this should be necessary.
Original comment by Tnade...@gmail.com
on 6 Feb 2013 at 8:33
Sorry, I've been busy lately.
It shouldn't take 20-30 minutes for the bot to realize that its timed out. I
tested with a 30 sec socket timeout and a couple of seconds after it sent the
ping line, the input thread died with a connection reset SocketException.
Can you try adding tbot.setSocketTimeout(1000 * 30); and see if that helps your
problem?
Original comment by Lord.Qua...@gmail.com
on 18 Feb 2013 at 10:29
Haven't gotten a response, is this still an issue?
The latest dev version also fixes some problems with bot shutdown, can you give
it a try?
https://code.google.com/p/pircbotx/wiki/DevVersion
Original comment by Lord.Qua...@gmail.com
on 1 Mar 2013 at 9:27
I have yet to have a "real" disconnect but in my tests the bot seems to handle
it better. I can reopen this if I have the issue again but you can close it for
now.
Sorry for the late reply, I've been lazy with my email box.
Original comment by Tnade...@gmail.com
on 11 Mar 2013 at 10:51
That's fine. Let us know if the problem comes up again
Original comment by Lord.Qua...@gmail.com
on 11 Mar 2013 at 10:52
Original issue reported on code.google.com by
Tnade...@gmail.com
on 6 Feb 2013 at 8:08