Cheshire Cat Computing

Steve,

disabled=yes is not in xinetd.conf. I enabled daytime and xinetd started it up so I know it is working. When I restart xinetd all that shows up in messages is:

tail /var/log/messages
Jun 22 16:03:27 alert-2 xinetd[27615]: Exiting...
Jun 22 16:03:27 alert-2 xinetd: xinetd shutdown succeeded
Jun 22 16:03:27 alert-2 xinetd: xinetd startup succeeded
Jun 22 16:03:28 alert-2 xinetd[29218]: xinetd Version 2.3.13 started with libwrap loadavg options compiled in.
Jun 22 16:03:28 alert-2 xinetd[29218]: Started working: 0 available services

'bb 1984/tcp bigbrother' is in /etc/services.

I have tried to start it manually:

[root@alert-2 bin]# ./bb2ns start -l bb2ns.log
BB2NS daemon starting...
[root@alert-2 bin]#

And the log just shows:

17:51 Opening logfile
17:51 bb2ns daemon starting

But, it never launches. I assume it should show up in the proc list and it doesn't. And an nmap scan for 1984/tcp yields this:

Starting nmap 3.70 ( http://www.insecure.org/nmap/ ) at 2006-06-22 17:57 PDT
Interesting ports on alert-2 (172.16.100.18):
PORT STATE SERVICE
1984/tcp closed bigbrother

You can see it recognizes the port.

Could there be something wrong with the compiling process:

make bb2ns
cc bb2ns.c -o bb2ns
[root@alert-2 bb2ns-v1.0]# ll bb2ns
-rwxr-xr-x 1 root root 18036 Jun 22 18:00 bb2ns

Is 18036 the right size for the executable?

try to include generic service template in services or just add the stuff thats missing to the services entry manually

try makeing the xinetd entry look like this

service bb
{
flags = REUSE
socket_type = stream
wait = no
user = nagios
group = nagios
server = /usr/sbin/bb2ns
server_args = -i -d 3 -l /var/tmp/bb2ns.log -f var/spool/nagios/nagios.cmd
disable = no
}

Looks like the problems with the services.cfg are all down to people using Nagios 2.x whereas I use Nagios 1.x. I have updated the documentation and config to take note of all this.

For the xinetd config, it seems that the sample config does not work on some systems although I dont know why yet (it works on ours). In another thread, someone claims to have fixed this problem, so I'm hoping to find out what they did.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

see my thread for nagios 2.x services and xinetd info, basicly you can't call it bb2ns.xinetd, you have to call it bb2ns

so copy/paste

mv /etc/xinetd.d/bb2ns.xinetd /etc/xinetd.d/bb2ns
service xinetd restart

and you should be set