[Date Prev]   [Date Next] [Thread Prev]   [Thread Next] [Date Index]   [Thread Index]

 

     Re: error: newSocket() connect failed: Bad file number

Sure did. Even with those removed, it made no change to the system.

Aaron

Erik Dugo Kargard <dugo@dugo.net> wrote:
> Have you added the entires into the /etc/services file?
> 
> noclog          5354/tcp        # noclogd with TCP
> noclog          5354/udp        # noclogd with UDP
> hostmon         5355/tcp        # hostmon uses TCP
> 
> Dugo
> 
> 
> 
> At 12:05 PM 6/24/99 -0500, aaron@oneboxcorp.com wrote:
> >
> >I'm also getting :
> >
> >> newSocket() connect failed: Bad file number
> >> (libdebug) eventlog send() error: newSocket() connect failed: Bad file
> number
> >> (libdebug) eventlog send() error: newSocket() connect failed: Bad file
> number
> >> (libdebug) eventlog send() error: 
> >>                    -keepalive_monitors
> >
> >
> >Which I cannot figure out. I saw the threads in the archives about the Socket
> >problems, but that was with much older versions of perl, and BSDI.
> >
> >Can anyone offer any suggestions, or do I need to provide more information?
> >
> >Thanks in advance,
> >Aaron Marco
>