Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon4.gif   SVN1714 will not run in 'daemon" mode on Solaris8, posted by Steve Jones on Mon Sep 18 20:35:44 2006 truss-error.outtruss-good.out
    icon2.gif   Re: SVN1714 will not run in 'daemon" mode on Solaris8, posted by Steve Jones on Mon Sep 18 22:09:23 2006 
    icon2.gif   Re: SVN1714 will not run in 'daemon" mode on Solaris8, posted by Stefan Ritt on Fri Sep 22 07:47:58 2006 
       icon2.gif   Re: SVN1714 will not run in 'daemon" mode on Solaris8, posted by Steve Jones on Fri Sep 22 19:32:45 2006 
       icon2.gif   Re: SVN1714 will not run in 'daemon" mode on Solaris8, posted by Steve Jones on Fri Sep 22 22:12:18 2006 truss-daemon-1714.txt
          icon2.gif   Re: SVN1723 (was SVN1714) will not run in 'daemon" mode on Solaris8, posted by Steve Jones on Tue Oct 10 23:29:53 2006 
             icon2.gif   Re: SVN1723 (was SVN1714) will not run in 'daemon" mode on Solaris8, posted by Steve Jones on Wed Oct 11 00:19:05 2006 
                icon2.gif   Re: SVN1723 (was SVN1714) will not run in 'daemon" mode on Solaris8, posted by Stefan Ritt on Wed Oct 11 08:18:14 2006 
                   icon2.gif   SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8), posted by Steve Jones on Thu Oct 26 21:54:40 2006 
                      icon2.gif   SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8), posted by Stefan Ritt on Wed Nov 8 08:20:34 2006 
                         icon2.gif   SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8), posted by Steve Jones on Wed Nov 8 12:55:58 2006 
                            icon2.gif   SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode, posted by Stefan Ritt on Wed Nov 8 13:07:31 2006 
Message ID: 2051     Entry time: Wed Nov 8 12:55:58 2006     In reply to: 2050     Reply to this: 2052
Icon: Reply  Author: Steve Jones  Author Email: steve.jones@freescale.com 
Category: Bug report  OS: Other  ELOG Version: 2.6.2-1714 
Subject: SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8) 

Stefan Ritt wrote:

Steve Jones wrote:
BUG: In the initial comment section of elogd_fancy.cfg the line
# This [global] section contains settings common to all logbooks
is not parsed correctly as a comment and the embedded [global] is picked up and confuses elogd, eg., elogd will not pickup the port=8080 option. Taking "[global]" out of the comment restores fucntionality. I recommend checking to make sure that the config file checking routine ignores *entire* lines starting with a comment char;


Acknowledged. The problem was that the section between the line
# This [global] section contains settings common to all logbooks
and the real
 [global] 
section was interpreted as the global section, and thus the "real" one was omitted. I changed the code now such that all lines starting with a '#' or ';' are completely skipped, that fixes the problem. The fix is contained in revision 1745.


Steve Jones wrote:
ISSUE: The option
Logbook dir = 
causes an enormous amount of problems, and this may be limited to elog installs that exist in NFS space (as opposed to local disk). If the default is left alone elogd appears to work fine; Try and override and the fun begins. The previous attached traces show that once going into daemon mode none of the logbook dirs can be found nor indexed. The workaround is to use the default "logbooks" dir. Perhaps the routine that creates the default (if not found) should be the same as the one that creates the override (?).


That's weird. Have you tried to specify a full path for the logbook, like /nfs/some/directory ? The only difference of the daemon mode compared to the normal mode is that elogd does a cd to the root ('/'). If you specify logbook dir relative to the starting directory, like 'some/subdir', elogd will the try to access it under '/some/subdir', where it might not have read/write privileges.



Quote:
Very weird. No, I did not try an absolute path - but I did notice the attempt to "cd /" in the truss output. In fact, it was immediately after that "cd /" test that things appeared to start not working - basically, elogd could not find anything.

I'm putting this on hold for the time being as I now have test systems going into production. I'll be able to test next week.

ELOG V3.1.5-fe60aaf