Probably something is wrong with the account under which you run elog. Normally (at least if you install elog from the RPM) you have an account "elog" and group "elog" under which you run elogd. You compile and install elogd under root (so that it can bind to port 80 for example), and then you put 

usr = elog

grp = elog

into the configuration file. So when you start elogd, it binds to the server port, then falls down to user "elog" and gives up root privileges. If the elog account for example does not exist, you get the above error message. The only problem I see there is if elog stays as root, it can do more harmful things in case it misbehaves.

Attributes = Author, Event time, ...

Preset Event time = $utcdate

Thanks Stefan, the preset UTC date works well. RTFM on my part perhaps.

I'm running version 2.7.5.2127 and am still having the issue with conditional attributes in the find area as mentioned above though.
Is it the latest SVN  **.2135 that addresses this?

Many thanks

Thanks for the response! BTW: I did get a notification - but thanks for the "personal heads-up"!

 I see. In that case, could you maybe please give a quick explanation what "List conditions" is supposed to do? In conjunction with your statement above I'm now thoroughly confused as to what it should/could be used for...

 Ah, that's an idea - I'll look into that. Thanks a mil for the suggestion!

Regards,

Thomas

 I take it you mean the "Subdir" option (the manual mentions "Data dir" as obsolete)? I tried it with that and it works like a charm - gives me now two logbooks, i.e. two tabs with the same data and two different views - which is precisely what we need. Thanks!

Regards,

Thomas

Stefan,

I have defined the "Bottom Text Login = ..." in each Logbook Configuration section. But when I use this option in the Global Section, ELOG fails to start.

Barend

 That's strange. I just tried myself following configuration file:

[global]
port = 8080
Bottom text = <center>Hello</center>
Bottom text login = <center>Login Hello</center>
Password file = passwd

[demo1]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Page Title = ELOG - $subject

[demo2]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject

and everything works fine as can be seen from the login screen:

so can you check if above file works for you?

Many people want conditional attributes on the find page, so I cannot remove it. Before adding another parameter to disable this optionally, I would like to ask you to first try the "Show attributes edit = ..." option, which is not evaluated in the "find" page. Maybe you can achieve what you want with this option.

A problem recently developed for our elog...after running without much problem the elog daemon was restarted on an ubuntu server running apache2. Now the server gives 502 Proxy Error messages:

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /elog.

Reason: Error reading from remote server

I did a force-reload of apache after making sure the modules are enabled. I also restarted elogd but to no avail. One symptom seems to be that the GET request is empty...that is before it was:

"GET /elog/sample_elog/etcetera HTTP/1.1"

but now it is just

"GET /elog HTTP/1.1"

Just started out of the blue...

Any ideas?