Re: [hobbit] Strange problem

[kevin grady <kevin.grady (at) gmail.com>]

The only thing that is remaing is one yellow for hobbitd:

Cannot access checkpoint file /usr/local/hobbit/server/tmp/hobbitd.chk
for restore

Should that file exist and what creates it, because it does not exist.
hobbit has the proper access to that directory

On Thu, 17 Feb 2005 17:33:43 -0500, kevin grady <kevin.grady (at) gmail.com> wrote:
> Thanks Charles. Now that I've exposed my utter stupidity. Someone
> (that someone would be ME a few months ago) had installed big SISTER
> on this machine and yes it was running on port 1984. Bye-bye bs ,
> hello hobbit.
> 
> Thanks again. Everything is running with green smiles...
> 
> 
> On Thu, 17 Feb 2005 23:15:21 +0100, Henrik Stoerner <henrik (at) hswn.dk> wrote:
> > On Thu, Feb 17, 2005 at 04:56:18PM -0500, kevin grady wrote:
> > > I verified that the host exists in bb-hosts. This is what I get in the
> > > log when I attempt to start hobbit. I've checked permissions and
> > > anything else I could think of, but nothing looks out of place.
> > >
> > > Log entries:
> > >
> > > 2005-02-17 17:54:36 Task hobbitd started with PID 4085
> > > 2005-02-17 17:54:36 Setting up network listener on 0.0.0.0:1984
> > > 2005-02-17 17:54:36 Cannot bind to listen socket (Address already in use)
> > > 2005-02-17 17:54:36 Task hobbitd terminated, status 1
> >
> > Well, something is using port 1984 then.
> >
> > What does a "netstat -na | grep 1984" say ?
> >
> > If this is a Linux box, try running (as root) "netstat -ntlp | grep 1984"
> > That should give you the proces-ID and name of the program listening
> > on port 1984.
> >
> >
> > Henrik
> >
> > To unsubscribe from the hobbit list, send an e-mail to
> > hobbit-unsubscribe (at) hswn.dk
> >
> >
>