[Sguil-devel] Problems with the 0.8.0 port upgrade

[Paul Schmehl]

I'm working on upgrading the FreeBSD ports and I've run into a strange
problem. My startup scripts fail for the server and the sensors.

Even if I start them from the commandline they refuse to daemonize.

I'm not sure what changed. These scripts worked fine in version 0.7.0.

For example:

I get this when trying to start sguild from the rc.subr startup script that
worked with 0.7.0:

# /usr/local/etc/rc.d/sguild start
Starting sguild.
/usr/local/etc/rc.d/sguild: unknown directive '/usr/local/bin/sguild'.
Usage: /usr/local/etc/rc.d/sguild
[fast|force|one|quiet](start|stop|restart|rcvar|status|poll)
/usr/local/etc/rc.d/sguild: WARNING: failed to start sguild

If I try to start it from the commandline, it starts, but it does not
daemonize:

# /usr/local/bin/sguild -D
% ^C
[***@buttercup4 /usr/ports/security/sguil-server-update/sguil-server]# ps
-auxw | grep sguild
root 42536 0.0 0.0 9128 1452 0 S+ 10:29PM 0:00.00 grep sguild

Even the -h option fails:

# /usr/local/bin/sguild -h
%

I'm not getting any error messages, so it's hard to know where to begin.
Any suggestions would be appreciated.
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*******************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson
"There are some ideas so wrong that only a very
intelligent person could believe in them." George Orwell

[Bamm Visscher]

Does it start w/o -D from the command line?

Bamm

Post by Paul Schmehl
I'm working on upgrading the FreeBSD ports and I've run into a strange
problem. My startup scripts fail for the server and the sensors.
Even if I start them from the commandline they refuse to daemonize.
I'm not sure what changed. These scripts worked fine in version 0.7.0.
I get this when trying to start sguild from the rc.subr startup script that
# /usr/local/etc/rc.d/sguild start
Starting sguild.
/usr/local/etc/rc.d/sguild: unknown directive '/usr/local/bin/sguild'.
Usage: /usr/local/etc/rc.d/sguild
[fast|force|one|quiet](start|stop|restart|rcvar|status|poll)
/usr/local/etc/rc.d/sguild: WARNING: failed to start sguild
If I try to start it from the commandline, it starts, but it does not
# /usr/local/bin/sguild -D
% ^C
-auxw | grep sguild
root 42536 0.0 0.0 9128 1452 0 S+ 10:29PM 0:00.00 grep sguild
# /usr/local/bin/sguild -h
%
I'm not getting any error messages, so it's hard to know where to begin.
Any suggestions would be appreciated.
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*******************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson
"There are some ideas so wrong that only a very
intelligent person could believe in them." George Orwell
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Sguil-devel mailing list
https://lists.sourceforge.net/lists/listinfo/sguil-devel

[Paul Schmehl]

Nope.

--On December 6, 2012 5:47:21 PM -0500 Bamm Visscher

Does it start w/o -D from the command line?  
Bamm
I'm working on upgrading the FreeBSD ports and I've run into a strange
problem.  My startup scripts fail for the server and the sensors.
Even if I start them from the commandline they refuse to daemonize.
I'm not sure what changed.  These scripts worked fine in version 0.7.0.
I get this when trying to start sguild from the rc.subr startup script that
# /usr/local/etc/rc.d/sguild start
Starting sguild.
/usr/local/etc/rc.d/sguild: unknown directive '/usr/local/bin/sguild'.
Usage: /usr/local/etc/rc.d/sguild
[fast|force|one|quiet](start|stop|restart|rcvar|status|poll)
/usr/local/etc/rc.d/sguild: WARNING: failed to start sguild
If I try to start it from the commandline, it starts, but it does not
# /usr/local/bin/sguild -D
% ^C
-auxw | grep sguild
root    42536  0.0  0.0  9128  1452   0  S+   10:29PM   0:00.00
grep sguild
# /usr/local/bin/sguild -h
%
I'm not getting any error messages, so it's hard to know where to begin.
Any suggestions would be appreciated.
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*******************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson
"There are some ideas so wrong that only a very
intelligent person could believe in them." George Orwell
-------------------------------------------------------------------------
-----
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Sguil-devel mailing list
https://lists.sourceforge.net/lists/listinfo/sguil-devel

--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*******************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson
"There are some ideas so wrong that only a very
intelligent person could believe in them." George Orwell

[Bamm Visscher]

Any output if you 'sguild -d 2'

Nope.
--On December 6, 2012 5:47:21 PM -0500 Bamm Visscher <
Does it start w/o -D from the command line?

Post by Paul Schmehl
Bamm
I'm working on upgrading the FreeBSD ports and I've run into a strange
problem. My startup scripts fail for the server and the sensors.
Even if I start them from the commandline they refuse to daemonize.
I'm not sure what changed. These scripts worked fine in version 0.7.0.
I get this when trying to start sguild from the rc.subr startup script that
# /usr/local/etc/rc.d/sguild start
Starting sguild.
/usr/local/etc/rc.d/sguild: unknown directive '/usr/local/bin/sguild'.
Usage: /usr/local/etc/rc.d/sguild
[fast|force|one|quiet](start|**stop|restart|rcvar|status|**poll)
/usr/local/etc/rc.d/sguild: WARNING: failed to start sguild
If I try to start it from the commandline, it starts, but it does not
# /usr/local/bin/sguild -D
% ^C
ps
-auxw | grep sguild
root 42536 0.0 0.0 9128 1452 0 S+ 10:29PM 0:00.00 grep sguild
# /usr/local/bin/sguild -h
%
I'm not getting any error messages, so it's hard to know where to begin.
Any suggestions would be appreciated.
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*********************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson
"There are some ideas so wrong that only a very
intelligent person could believe in them." George Orwell
------------------------------**------------------------------**
-------------
-----
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_**12329d2d<http://p.sf.net/sfu/logmein_12329d2d>
______________________________**_________________
Sguil-devel mailing list
https://lists.sourceforge.net/**lists/listinfo/sguil-devel<https://lists.sourceforge.net/lists/listinfo/sguil-devel>

--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*********************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson
"There are some ideas so wrong that only a very
intelligent person could believe in them." George Orwell

[Paul Schmehl]

No. Very weird.

I ran this: /usr/local/bin/sguild -c
/usr/local/bin/sguil-server/sguild.conf -D &

and got this result:

# % ps -auxw | grep sguild
root 43560 0.0 0.0 9104 2804 0 T 11:04PM 0:00.01
/usr/local/bin/tclsh8.5 -c /usr/local/etc/sguil-server/sguild.conf -D
root 43562 0.0 0.0 9128 1452 0 S+ 11:04PM 0:00.00 grep sguild

[2]+ Stopped /usr/local/bin/sguild -c
/usr/local/etc/sguil-server/sguild.conf -D

So it looks like it's running and stopped at the same time.???

--On December 6, 2012 6:00:20 PM -0500 Bamm Visscher

Any output if you 'sguild -d 2' 
Nope.
--On December 6, 2012 5:47:21 PM -0500 Bamm Visscher
Does it start w/o -D from the command line?  
Bamm
I'm working on upgrading the FreeBSD ports and I've run into a strange
problem.  My startup scripts fail for the server and the sensors.
Even if I start them from the commandline they refuse to daemonize.
I'm not sure what changed.  These scripts worked fine in version 0.7.0.
I get this when trying to start sguild from the rc.subr startup script that
# /usr/local/etc/rc.d/sguild start
Starting sguild.
/usr/local/etc/rc.d/sguild: unknown directive '/usr/local/bin/sguild'.
Usage: /usr/local/etc/rc.d/sguild
[fast|force|one|quiet](start|stop|restart|rcvar|status|poll)
/usr/local/etc/rc.d/sguild: WARNING: failed to start sguild
If I try to start it from the commandline, it starts, but it does not
# /usr/local/bin/sguild -D
% ^C
-auxw | grep sguild
root    42536  0.0  0.0  9128  1452   0  S+   10:29PM   0:00.00
grep sguild
# /usr/local/bin/sguild -h
%
I'm not getting any error messages, so it's hard to know where to begin.
Any suggestions would be appreciated.
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*******************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson
"There are some ideas so wrong that only a very
intelligent person could believe in them." George Orwell
-------------------------------------------------------------------------
-----
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Sguil-devel mailing list
https://lists.sourceforge.net/lists/listinfo/sguil-devel
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*******************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson
"There are some ideas so wrong that only a very
intelligent person could believe in them." George Orwell

--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*******************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson
"There are some ideas so wrong that only a very
intelligent person could believe in them." George Orwell