Strange problem 🔗 link

kevin grady wrote:

Ok, I just did a clean install of RC2 and everything seems to be
working, accept when I attempt to access
http://myhost.mydomain/hobbit, I get a directory listing instead of
the display. I've done clean hobbit installs of RC1 without any
problems so i removed the RC2 install and tried a clean install of RC1
and I get the same results. Looking at the contents of ~/server/www it
appears to be missing files, any ideas?

 

On Thu, 17 Feb 2005 10:13:24 -0700, Charles Jones <user-e86b4aeade4e@xymon.invalid> wrote:

Humor me and try http://myhost.mydomain/hobbit/     (with tailing slash)

-Charles

kevin grady wrote:

Ok, I just did a clean install of RC2 and everything seems to be
working, accept when I attempt to access
http://myhost.mydomain/hobbit, I get a directory listing instead of
the display. I've done clean hobbit installs of RC1 without any
problems so i removed the RC2 install and tried a clean install of RC1
and I get the same results. Looking at the contents of ~/server/www it
appears to be missing files, any ideas?

kevin grady wrote:

Yeah, tried that too and same results. This is the first time I have
run across this issue after a few installs of RC1. Unfortunately I
don't have access to the installs I did that work at the moment for
reference to see what is missing from the ~/server/www/ directory. The
only things under it are folders, not one file, no index file. Within
the folders it looks like all of the necessary files are there.


On Thu, 17 Feb 2005 10:13:24 -0700, Charles Jones <user-e86b4aeade4e@xymon.invalid> wrote:
 

Humor me and try http://myhost.mydomain/hobbit/     (with tailing slash)

-Charles

kevin grady wrote:

   

Ok, I just did a clean install of RC2 and everything seems to be
working, accept when I attempt to access
http://myhost.mydomain/hobbit, I get a directory listing instead of
the display. I've done clean hobbit installs of RC1 without any
problems so i removed the RC2 install and tried a clean install of RC1
and I get the same results. Looking at the contents of ~/server/www it
appears to be missing files, any ideas?

On Thu, 17 Feb 2005 11:16:43 -0700, Charles Jones <user-e86b4aeade4e@xymon.invalid> wrote:

 The index.html file (a link to bb.html), and the other html files in that
dir are generated dynamically when hobbit runs...so if they arent there then
either hobbit is not running, or hobbit crashed, or has no write perms. 
Check the logs in /var/log/hobbit and see if anything seems amiss.
 
 -Charles

 
 kevin grady wrote: 
 Yeah, tried that too and same results. This is the first time I have run
across this issue after a few installs of RC1. Unfortunately I don't have
access to the installs I did that work at the moment for reference to see
what is missing from the ~/server/www/ directory. The only things under it
are folders, not one file, no index file. Within the folders it looks like
all of the necessary files are there. On Thu, 17 Feb 2005 10:13:24 -0700,
Charles Jones <user-e86b4aeade4e@xymon.invalid> wrote: 
 Humor me and try http://myhost.mydomain/hobbit/ (with tailing slash)
-Charles kevin grady wrote: 
 Ok, I just did a clean install of RC2 and everything seems to be working,
accept when I attempt to access http://myhost.mydomain/hobbit, I get a
directory listing instead of the display. I've done clean hobbit installs of
RC1 without any problems so i removed the RC2 install and tried a clean
install of RC1 and I get the same results. Looking at the contents of

On Thu, Feb 17, 2005 at 03:18:34PM -0500, kevin grady wrote:

Well that explains the display problem. Kick me for not checking the
logs. So this is what I have in the hobbitlaunch.log:

2005-02-17 16:16:43 Setting up network listener on 0.0.0.0:1984
2005-02-17 16:16:43 Cannot bind to listen socket (Address already in use)
2005-02-17 16:16:43 Task hobbitd terminated, status 1

I checked the ~/server/etc/hobbitserver.cfg and it has everything
listed properly. This system does not have anything listening on port
1984. Any ideas? Shouldn't the binding IP address be what is specified
in BBSERVERIP?

On Thu, 17 Feb 2005 21:41:59 +0100, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid> wrote:

On Thu, Feb 17, 2005 at 03:18:34PM -0500, kevin grady wrote:

Well that explains the display problem. Kick me for not checking the
logs. So this is what I have in the hobbitlaunch.log:

2005-02-17 16:16:43 Setting up network listener on 0.0.0.0:1984
2005-02-17 16:16:43 Cannot bind to listen socket (Address already in use)
2005-02-17 16:16:43 Task hobbitd terminated, status 1

Could be the same bug that's bitten quite a few people now: The
hostname used in hobbitserver.cfg for the BBSERVERHOSTNAME and
MACHINEDOTS settings is not listed in bb-hosts, causing hobbitd
to crash after 5 minutes.

In that case, you should have a line "hobbitd terminated with signal
6" just before those lines in the logfile.

Make sure the hostname in BBSERVERHOSTNAME is listed in bb-hosts.

I checked the ~/server/etc/hobbitserver.cfg and it has everything
listed properly. This system does not have anything listening on port
1984. Any ideas? Shouldn't the binding IP address be what is specified
in BBSERVERIP?

This error message is bogus, it happens because hobbitd attempts to
restart too quickly after it crashes.


Henrik

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

On Thu, 17 Feb 2005 23:15:21 +0100, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid> 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

On Thu, 17 Feb 2005 17:33:43 -0500, kevin grady <user-50dc3c45bc73@xymon.invalid> 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 <user-ce4a2c883f75@xymon.invalid> 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

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

kevin grady 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 <user-ce4a2c883f75@xymon.invalid> 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

   

On Thu, Feb 17, 2005 at 05:35:16PM -0500, kevin grady wrote:

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

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

On Thu, 17 Feb 2005 23:51:52 +0100, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid> wrote:

On Thu, Feb 17, 2005 at 05:35:16PM -0500, kevin grady wrote:

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

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

Just means that you started Hobbit up for the first time. The
checkpoint file is generated by hobbitd - you should see it
appear after a few minutes, and if you shut down Hobbit.

Henrik