Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 77735 - nessusd restart does not restart nessusd 2.3.0, start after stop requires some pause
Summary: nessusd restart does not restart nessusd 2.3.0, start after stop requires som...
Status: VERIFIED TEST-REQUEST
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High minor (vote)
Assignee: Netmon Herd
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-12 13:28 UTC by Melle Geers
Modified: 2005-02-05 18:14 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
A new init script for nessusd (nessusd,645 bytes, text/plain)
2005-01-25 16:51 UTC, Otavio Piske (RETIRED)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Melle Geers 2005-01-12 13:28:19 UTC
When trysing to restart nessusd (~x86 2.3.0) using the rc mechanism it stops fine, but does not restart again:

# /etc/init.d/nessusd restart
 * Stop nessusd...                                                        [ ok ]
 * Starting nessusd...                                                    [ !! ]

In /var/lib/nessus/logs/nessusd.messages:

<snip normal startup messages about loading plugins>
[Wed Jan 12 22:05:08 2005][531] Loading ssh_setsid.nasl
[Wed Jan 12 22:05:08 2005][531] Loading fedora_2004-247.nasl
[Wed Jan 12 22:05:08 2005][531] Loading debian_DSA-304.nasl
[Wed Jan 12 22:05:08 2005][531] Loading unreal_detection.nasl
[Wed Jan 12 22:05:09 2005][1243] nessusd 2.3.0. started
[Wed Jan 12 22:05:13 2005][1243] received the TERM signal

When trying to restart it using stop/start, with some pause in between, it restarts as expected:

# /etc/init.d/nessusd stop
 * Stop nessusd...                                                        [ ok 
# /etc/init.d/nessusd start
 * Starting nessusd...
All plugins loaded                                                        [ ok ]

Note that some kind of counter is displayed, showing the current amount of loaded plugins, during starting (which will eventually read the "All plgins loaded." message).

However: when I start too soon after stopping, it shows the same (broken) behaviour as like it got a restart:

# /etc/init.d/nessusd stop
 * Stop nessusd...                                                        [ ok ]
# /etc/init.d/nessusd start
 * Starting nessusd...                                                    [ !! ]

In the log:


<snip normal startup messages about loading plugins>
[Wed Jan 12 22:15:14 2005][2132] Loading debian_DSA-304.nasl
[Wed Jan 12 22:15:14 2005][2132] Loading unreal_detection.nasl
[Wed Jan 12 22:15:14 2005][2135] nessusd 2.3.0. started
[Wed Jan 12 22:15:20 2005][2135] received the TERM signal

I am not sure what the delay for success should be (willing to investigate on request).

Reproducible: Always
Steps to Reproduce:
1a. As root, give the command: /etc/init.d/nessusd restart
1b. Try to give the command: /etc/init.d/nessusd stop && /etc/init.d/nessusd start
Actual Results:  
nessusd failed to restart

Expected Results:  
stop (which it did) and than restart again

# emerge info
Portage 2.0.51-r3 (default-linux/x86/2004.3, gcc-3.3.5, glibc-2.3.4.20040808-r1,
2.4.22-gentoo-r5 i686)
=================================================================
System uname: 2.4.22-gentoo-r5 i686 Celeron (Mendocino)
Gentoo Base System version 1.4.16
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
Binutils: sys-devel/binutils-2.15.92.0.2-r1
Headers:  sys-kernel/linux-headers-2.4.19-r1,sys-kernel/linux-headers-2.4.21-r1
Libtools: sys-devel/libtool-1.5.2-r7
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-Os -march=pentium2 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /usr/share/texmf/dvipdfm/config/
/usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/
/usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/alias
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-Os -march=pentium2 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="http://gentoo.osuosl.org
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="apache2 apm berkdb bitmap-fonts cdr crypt cups directfb encode fbcon
foomaticdb gdbm gif gpm imagemagick imap imlib innodb java jpeg libg++ libwww
lirc mad maildir mikmod mmx motif mysql ncurses offensive oggvorbis pam pdflib
perl php png pop3 ppds python readline samba sasl sdl sko slang snmp spell ssl
svga tcpd tetex theora tiff truetype usb x86 xml xml2 zlib"

# cat /etc/portage/package.keywords
net-analyzer/nessus ~x86
net-analyzer/nessus-plugins ~x86
net-analyzer/nessus-core ~x86
net-analyzer/libnasl ~x86
net-analyzer/nessus-libraries ~x86
#

# nessusd --version
nessusd (Nessus) 2.3.0 for Linux
(C) 1998 - 2004 Renaud Deraison <deraison@nessus.org>
#
Comment 1 Otavio Piske (RETIRED) gentoo-dev 2005-01-25 16:51:52 UTC
Created attachment 49523 [details]
A new init script for nessusd

Hi, is there anyway you can, please, test this new init script for nessusd?
This new init script checks if nessus daemon is running before proceeds.
Comment 2 Otavio Piske (RETIRED) gentoo-dev 2005-01-26 03:08:17 UTC
It's in cvs now. Please remerge nessus 2.3.0.
Comment 3 Melle Geers 2005-01-26 10:18:49 UTC
Tested the new /etc/init.d/nessusd script, and the problem is gone:

# /etc/init.d/nessusd restart
 * Stop nessusd...
 * Waiting for the environment to be sane                                 [ ok ]
 * Starting nessusd...
All plugins loaded                                                        [ ok ]
#

Thanks!

Cheers,
Melle
Comment 4 Melle Geers 2005-02-05 17:18:12 UTC
Not that familiar with Bugzilla. Should I (the submitter) close the bug now?
Comment 5 Daniel Black (RETIRED) gentoo-dev 2005-02-05 18:14:38 UTC
It is not needed. You've confirmed that the solution works which is what we were after. Thanks for testing and getting back to us.