dominikh changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.2.5
postmodern has quit [Quit: Leaving]
_djbkd has quit [Remote host closed the connection]
britneywright has joined #cinch
britneywright has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
djbkd has joined #cinch
Saloun has quit [Ping timeout: 258 seconds]
sand420 has joined #cinch
sand420 has quit [Ping timeout: 240 seconds]
sand420 has joined #cinch
djbkd has quit [Remote host closed the connection]
djbkd has joined #cinch
djbkd has quit [Remote host closed the connection]
djbkd has joined #cinch
djbkd has quit [Remote host closed the connection]
djbkd has joined #cinch
djbkd has quit [Ping timeout: 256 seconds]
postmodern has joined #cinch
sarkyniin has joined #cinch
postmodern has quit [Quit: Leaving]
apt-get_ has joined #cinch
sarkyniin has quit [Ping timeout: 240 seconds]
britneywright has joined #cinch
apt-get_ has quit [Remote host closed the connection]
head8debian has quit [Ping timeout: 240 seconds]
head8debian has joined #cinch
head8debian has quit [Read error: Connection reset by peer]
head8debian has joined #cinch
head8debian has joined #cinch
eebs has joined #cinch
head8debian has joined #cinch
britneywright has quit [Ping timeout: 265 seconds]
<eebs> How would I debug *why* my bot times out when connecting to an IRC network?
<eebs> I can connect to the network (gamesurge) just fine via Adium, and I've been able to connect the bot in the past, but now it just times out
britneywright has joined #cinch
britneywright has quit [Client Quit]
britneywright has joined #cinch
britneywright has quit [Quit: Textual IRC Client: www.textualapp.com]
djbkd has joined #cinch
<dominikh> well, what does the log say
djbkd has quit [Remote host closed the connection]
<eebs> I think it's on their end
<eebs> cause I got it to connect by using a different host
<eebs> but I was just curious if there was a way to get some additional info, or if timing out was as much info as was available
sarkyniin has joined #cinch
<dominikh> not via cinch, no. you'd probably diagnose it via tools such as dig and ping and telnet and see if all hosts behave that way, etc
<dominikh> the server is not telling us anything, not even rejecting the connection, hence a timeout
<eebs> *nod* That's the conclusion I arrived at as well, thanks for the confirmation. I ended up pinging, got no response, and eventually used dig to find a different hostname that worked. Clearly something weird on their end
<eebs> Thanks again though
<dominikh> sure thing
djbkd has joined #cinch
djbkd has quit [Read error: Connection reset by peer]
_djbkd has joined #cinch
djbkd has joined #cinch
sarkyniin has quit [Ping timeout: 272 seconds]
_djbkd has quit [Ping timeout: 276 seconds]
sarkyniin has joined #cinch
djbkd has quit [Remote host closed the connection]
djbkd has joined #cinch
djbkd has quit [Remote host closed the connection]
djbkd has joined #cinch
djbkd has quit [Remote host closed the connection]
sarkyniin has quit [Remote host closed the connection]
eebs has quit [Quit: Leaving.]
thews has quit [Ping timeout: 256 seconds]
thews has joined #cinch
Azure has quit [Ping timeout: 265 seconds]
Azure has joined #cinch