[Dxspider-support] Bad file descriptor ??

[Iain Philipps]

Paul,

I've seen Perl spit out errors like that simply because it's been unable to resolve the IP address of the system you're trying to connect to.

Try "nslookup dxspots.net"and see what you get back ....


Regards     -     Iain
 
  ----- Original Message ----- 
  From: Paul M Dunphy 
  To: dxspider-support at dxcluster.org 
  Sent: Saturday, September 29, 2007 6:54 AM
  Subject: [Dxspider-support] Bad file descriptor ??


      After a couple months of pretty much flawless connections, I can't connect to N5IN-2's node anymore.  Here's what I get:

  connect 16: timeout set to 60
  connect 16: timeout set to 30
  CONNECT 16 sort: telnet command: DXSPOTS.NET 23
  ***Connect 16 Failed to DXSPOTS.NET 23 Bad file descriptor
  -> D VE1DX connection to N5IN-2 started

      Any thoughts?  Seems to have been OK until yesterday.  Here's my connect script:

  timeout 30
  connect telnet DXSPOTS.NET 23
  'login' 've1dxi'


      Any thoughts?  The "bad file descriptor" makes me suspicious it may be on my end.  (I stopped my cluster, rebooted the system and restarted with the same results.)

  73, Paul VE1DX (a/k/a VE1DXI) 


------------------------------------------------------------------------------


  _______________________________________________
  Dxspider-support mailing list
  Dxspider-support at dxcluster.org
  http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20070929/589833dd/attachment.htm