[Fedora-directory-users] role of uxwdog?

[speedy zinc]

What is the role of this watch dog? It would seem more
useful if the watch dog can watch over the slapd
process (and restart it if it dies), but it does not.

So what is it doing? Seems like it's watching over the
ns-httpd instead.

rgds

sz


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

[Rich Megginson]

speedy zinc wrote:

> What is the role of this watch dog? It would seem more
> useful if the watch dog can watch over the slapd
> process (and restart it if it dies), but it does not.
>   
>  
We will be addressing that in an upcoming release with sysV init scripts.

> So what is it doing? Seems like it's watching over the
> ns-httpd instead.
>   
>  
That's right.

> rgds
>
> sz
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>   
>

[Rob Crittenden]

speedy zinc wrote:
>  What is the role of this watch dog? It would seem more
>  useful if the watch dog can watch over the slapd
>  process (and restart it if it dies), but it does not.
>  
>  So what is it doing? Seems like it's watching over the
>  ns-httpd instead. 
The admin server included with the current Red Hat DS is a stripped-down 
copy of the Netscape Enterprise Server, a standalone web server. The web 
server includes its own watchdog daemon, uxwdog. So yes, uxwdog watches 
ns-httpd and not ns-slapd.

I don't know about a watchdog for ns-slapd, I'll leave that up to the 
more learned LDAP gurus.

rob

[David Boreham]

>  I don't know about a watchdog for ns-slapd, I'll leave that up to the 
>  more learned LDAP gurus. 
Simple : The LDAP server never crashes.

;)

[speedy zinc]

--- David Boreham <david_list(a)boreham.org&gt; wrote:

>  
>  >
>  >
>  > I don't know about a watchdog for ns-slapd, I'll
>  leave that up to the 
>  > more learned LDAP gurus.
>  
>  Simple : The LDAP server never crashes.
>  
>  ;)
>   
Sure, I was playing with replication, and I kill one
of them
intentionally, just to see what that watch dog is
doing :)

sz



		
__________________________________ 
Start your day with Yahoo! - Make it your home page! 
http://www.yahoo.com/r/hs

[Mike Jackson]

David Boreham wrote:
>  
> >
> >
> > I don't know about a watchdog for ns-slapd, I'll leave that up to the 
> > more learned LDAP gurus.
>  
>  
>  Simple : The LDAP server never crashes.
>  
>  ;) 
I have setup an LDAP server watchdog before with OpenLDAP and 
Daemontools. It works like a charm.

To work with daemontools, a daemon should be able to start without 
forking itself into the background, e.g. with -f switch or similar, and 
log all of it's output to stdout (access, errors, etc). OpenLDAP can do 
this, but I don't believe that FDS can (although it would certainly be a 
great feature to add because daemontools really kick ass).

--
mike

Mike Jackson wrote:

>  David Boreham wrote:
>
> >
> >>
> >>
> >> I don't know about a watchdog for ns-slapd, I'll leave that up to 
> >> the more learned LDAP gurus.
> >
> >
> >
> > Simple : The LDAP server never crashes.
> >
> > ;)
>
>
>  I have setup an LDAP server watchdog before with OpenLDAP and 
>  Daemontools. It works like a charm.
>
>  To work with daemontools, a daemon should be able to start without 
>  forking itself into the background, e.g. with -f switch or similar, 
>  and log all of it's output to stdout (access, errors, etc). OpenLDAP 
>  can do this, but I don't believe that FDS can (although it would 
>  certainly be a great feature to add because daemontools really kick ass). 
The Daemontools look very handy!  I run qmail under them but hadn't paid 
enough attention.

If ns-slapd is started with -d<error level> it will not fork-and-exit 
and it logs errors to stdout.  That's how to launch ns-slapd in debugger 
and avoid having to follow children.  You can use the regular 
start-slapd script to pass arguments, like "start-slapd -d0" for normal 
log level.

[Mike Jackson]

uffe(a)loop.to wrote:

>  
>  If ns-slapd is started with -d<error level> it will not fork-and-exit 
>  and it logs errors to stdout.  That's how to launch ns-slapd in debugger 
>  and avoid having to follow children.  You can use the regular 
>  start-slapd script to pass arguments, like "start-slapd -d0" for normal 
>  log level. 
Hi,
  While that does work, you don't get any of the normal accesslog 
information, only errors. That is not really acceptable for everyone, at 
least not for me.

  So, I would say that if you don't care about access logging at all, 
and want to run slapd under daemontools, then you could start it like this:



#!/bin/sh
#
# daemontools run script for ns-slapd service
#
exec 2>&1
echo "Starting ns-slapd..."
exec \
     cd /opt/fedora-ds/bin/slapd/server; \
     ./ns-slapd \
     -D /opt/fedora-ds/slapd-foo \
     -d 0


--
mike

[Mike Jackson]

Mike Jackson wrote:

>  
>  Hi,
>   While that does work, you don't get any of the normal accesslog 
>  information, only errors. That is not really acceptable for everyone, at 
>  least not for me.
>   

Actually, I just discovered how to make it work, at least on linux:


nsslapd-accesslog: /dev/stdout


I will create a page on the wiki about running FDS under daemontools.

--
mike

[Mike Jackson]

speedy zinc wrote:
>  What is the role of this watch dog? It would seem more
>  useful if the watch dog can watch over the slapd
>  process (and restart it if it dies), but it does not. 

Hi,
  You can use daemontools as a watchdog for slapd, which will restart it 
if it dies.

  I just wrote a howto on the wiki:

	http://directory.fedora.redhat.com/wiki/Howto:Daemontools


  Please test it and mail any mistakes to the list.

BR,
--
mike