Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 731 of 796  Not logged in ELOG logo
ID Date Icon Author Author Emailup Category OS ELOG Version Subject
  1940   Mon Sep 18 22:09:23 2006 Reply Steve Jonessteve.jones@freescale.comBug reportOther2.6.2-1714Re: SVN1714 will not run in 'daemon" mode on Solaris8

Steve Jones wrote:
On Solaris, SVN1714 will not go into daemon mode. Running the compiled version under TRUSS (which provides a dump of every system call) and shows precisely where elog is failing. I have attached two TRUSS outputs: one where it errors out and the other where it runs but "interactively". Both runs are as root, simply one with and one without the "-D"



Quote:

As a followon, when I do run SVN1714 as a detached process but started as ROOT I get the following console messages:

Cannot restore original GID/UID.
Cannot restore original GID/UID.
Cannot restore original GID/UID.
Cannot restore original GID/UID.
Cannot restore original GID/UID.
Cannot restore original GID/UID.
Cannot restore original GID/UID.

I do not get these when I run the app as me - which is a non-UID 0 account. Perhaps this is an artifact of the "-x" option?

  1942   Tue Sep 19 19:22:31 2006 Reply Steve Jonessteve.jones@freescale.comQuestionAll2.6.2-1714Re: Re: Why are Preset fields blanked out?

Stefan Ritt wrote:

Steve Jones wrote:

I think I found it. Try this:
Locked Attributes = ApprovedDate, CompletedDate
##################################################
# Define CRState
#
Options CRState = PENDING{a}, APPROVED{b}, HOLD{a}, REJECTED{a}, COMPLETED{c}
{a}
{b} Preset ApprovedDate = $date
{c} Preset CompletedDate = $date

In my config when I remove the two attributes from "LOCKED ATTRIBUTES" the fields do not get blanked out.


No, even with that it does not get blanked out. Attached is the complete elogd.cfg with which it works fine in my case (R1714). Can you try that?



Quote:

Stefan, when I try that config in a demo logbook in my installation *but with all other items in [global] I get the same field-blanking behavior. I am going to try going back to a completely pristine .cfg, but I suspect this will work fine. I will need to add back in configuration items until I run into the culprit.

Ok, I found it. Try this config:
[global]
port = 8080


[demo]
Comment = Test
Attributes = Author, CRState, ApprovedDate, CompletedDate
Locked Attributes = ApprovedDate, CompletedDate
Type CompletedDate = date
Type ApprovedDate = date

Format CompletedDate = 1
Options CRState = PENDING{a}, APPROVED{b}, HOLD{a}, REJECTED{a}, COMPLETED{c}
{a}
{b} Preset ApprovedDate = $date
{c} Preset CompletedDate = $date

Setting the "Type" to "date" causes the blanking to occur.
  1944   Tue Sep 19 20:37:59 2006 Warning Steve Jonessteve.jones@freescale.comBug reportOther2.6.2-1714Shell execution generating error
When started as root *but not running as a daemon* shell execution results in the following errors that are sent to Standard Error:
Cannot restore original GID/UID.
Cannot remove pidfile "/var/run/cr-elogd.pid"
; Permission denied
Cannot restore original GID/UID.
Cannot remove pidfile "/var/run/cr-elogd.pid"
; Permission denied
  1945   Tue Sep 19 20:38:49 2006 Reply Steve Jonessteve.jones@freescale.comQuestionAll2.6.2-1714Re: Re: Why are Preset fields blanked out?

Stefan Ritt wrote:

Steve Jones wrote:

Setting the "Type" to "date" causes the blanking to occur.


Ok, then don't set the "Type" to "date" Wink




Quote:

Yuk! Thanks!

Big grin
  1953   Fri Sep 22 19:31:15 2006 Reply Steve Jonessteve.jones@freescale.comBug reportOther2.6.2-1714Re: Shell execution generating error

Stefan Ritt wrote:

Steve Jones wrote:
When started as root *but not running as a daemon* shell execution results in the following errors that are sent to Standard Error:
Cannot restore original GID/UID.
Cannot remove pidfile "/var/run/cr-elogd.pid"
; Permission denied
Cannot restore original GID/UID.
Cannot remove pidfile "/var/run/cr-elogd.pid"
; Permission denied


The "/var/run/elogd.pid" file is created from elogd to indicate under which PID it is running. If you run elogd once under root, this file then belongs to root. If you afterwards run it under a user account, it cannot delete or change the file belonging to root. In that case, just delete that file manually.




Quote:

When a process starts via the normal startup process it is started as root then the process changes to run as nobody -- so the pid file will always be owned by root. Yes? Then, shell commands wil not be able to deal with the pid file, right? Why would the shell exec want to deal with the PID file anyway?

Just curious. As long as this does not pose a problem then I will nto worry about it.
  1954   Fri Sep 22 19:32:45 2006 Reply Steve Jonessteve.jones@freescale.comBug reportOther2.6.2-1714Re: SVN1714 will not run in 'daemon" mode on Solaris8

Stefan Ritt wrote:

Steve Jones wrote:
On Solaris, SVN1714 will not go into daemon mode. Running the compiled version under TRUSS (which provides a dump of every system call) and shows precisely where elog is failing. I have attached two TRUSS outputs: one where it errors out and the other where it runs but "interactively". Both runs are as root, simply one with and one without the "-D"


The "one where it errors out" does not look like an error. It does the "fork()" at the end and the main thread ends, that's how it's supposed to be.



Quote:


Ok, what this tells me is I need to get TRUSS to follow the fork - which I think I can do. The behavior, however, is that elog never goes into daemon mode after that fork.

More info to follow.
  1955   Fri Sep 22 19:42:21 2006 Reply Steve Jonessteve.jones@freescale.comQuestionAll2.6.2-1714Re: "Supress Email Notification" checkbox

Stefan Ritt wrote:

Steve Jones wrote:

Steve Jones wrote:
Is there a way to allow email notification but have the "Suppress Email Notification" checked by default? We had complaints about the enormous amount of email so I turned off email notification for edits/replys, but there are times that I would like to allow email to be sent out -- this would imply allowing email by unchecking the "Suppress" box.


What I think would be needed is:
Suppress Email on edit = 0|1|2
                             ^
Where a '2' denotes that the "Suppress Email Notification" shows up but *checked*


Just to a
Suppress default = 1




Quote:

Not quite what I am looking for. What I need is:

"New" Logs
- Always send an email -- do not provide an option to check the box.
-- use
Suppress Default = 2

"Edits and Replys"
- Provide the option to send an email, but by default the "suppress" box is checked
-- need
Suppress Email on edit = 2 

  1956   Fri Sep 22 22:12:18 2006 Reply Steve Jonessteve.jones@freescale.comBug reportOther2.6.2-1714Re: SVN1714 will not run in 'daemon" mode on Solaris8

Stefan Ritt wrote:

Steve Jones wrote:
On Solaris, SVN1714 will not go into daemon mode. Running the compiled version under TRUSS (which provides a dump of every system call) and shows precisely where elog is failing. I have attached two TRUSS outputs: one where it errors out and the other where it runs but "interactively". Both runs are as root, simply one with and one without the "-D"


The "one where it errors out" does not look like an error. It does the "fork()" at the end and the main thread ends, that's how it's supposed to be.




Quote:
Ok, I got it. I've attached the TRUSS output where we follow the fork. It appears that elogd cannot open any of the specified files then gives up. What was throwing me is no error output, even to STDERR. When I run the same but without the -D flag the files are opened fine.

There are also strange system calls that differ, and I thought it might be due to the setuid(60001) -nobody- but the the non-daemn mode also sets to nobody and works fine.
ELOG V3.1.5-2eba886