Hi there, I just compiled and installed elog on a machine running the newest Ubuntu server. Everything went fine - no problems. Running elog on it's own (no apache).  I moved over a bunch of logbooks from an older elog, which seemed to work. Now, elog seems to crash when people are uploading files. Here is a snip from my syslog, and you can see each time it crashes with "error 4."

Jul 16 14:02:45 GrattaLab3old elogd[4526]: elogd 2.7.4 built Jul 15 2008, 18:44:44
Jul 16 14:02:45 GrattaLab3old elogd[4526]: revision 2111
Jul 16 14:02:45 GrattaLab3old elogd[4526]: FCKedit detected
Jul 16 14:02:45 GrattaLab3old elogd[4526]: ImageMagick detected
Jul 16 14:02:45 GrattaLab3old elogd[4526]: Server listening on port 8080 ...
Jul 16 16:02:42 GrattaLab3old kernel: [10631.276626] elogd[4526]: segfault at b4466000 eip 080adf19 esp bfa281d0 error 4
Jul 16 16:05:24 GrattaLab3old elogd[5509]: elogd 2.7.4 built Jul 15 2008, 18:44:44
Jul 16 16:05:24 GrattaLab3old elogd[5509]: revision 2111
Jul 16 16:05:24 GrattaLab3old elogd[5509]: FCKedit detected
Jul 16 16:05:24 GrattaLab3old elogd[5509]: ImageMagick detected
Jul 16 16:05:35 GrattaLab3old elogd[5509]: Server listening on port 8080 ...
Jul 16 16:06:06 GrattaLab3old kernel: [10834.637427] elogd[5509]: segfault at 091d7000 eip 080adf19 esp bfc313f0 error 4
Jul 16 16:07:10 GrattaLab3old elogd[5517]: elogd 2.7.4 built Jul 15 2008, 18:44:44
Jul 16 16:07:10 GrattaLab3old elogd[5517]: revision 2111
Jul 16 16:07:10 GrattaLab3old elogd[5517]: FCKedit detected
Jul 16 16:07:10 GrattaLab3old elogd[5517]: ImageMagick detected
Jul 16 16:07:10 GrattaLab3old elogd[5517]: Server listening on port 8080 ...
Jul 16 16:07:49 GrattaLab3old kernel: [10937.923301] elogd[5517]: segfault at b7c0d000 eip 080adf19 esp bffc1780 error 4

I run elog as:

Usr = elog

Grp = elog

/usr/local/sbin/elog -p 8080 -c /usr/local/elog/elogd_exo.cfg -D

where elogd_exo is my config file. Nothing special in my config file.

 Another funny problem. When I'm uploading a file, the syslog says this:

Jul 17 23:12:52 exo-elog elogd[4745]: Falling back to default group "elog"
Jul 17 23:12:52 exo-elog elogd[4745]: Falling back to default user "elog"
Jul 17 23:12:52 exo-elog elogd[4745]: Cannot restore original GID/UID.
Jul 17 23:12:52 exo-elog elogd[4745]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 17 23:12:52 exo-elog elogd[4749]: Falling back to default group "elog"
Jul 17 23:12:52 exo-elog elogd[4749]: Falling back to default user "elog"
Jul 17 23:12:52 exo-elog elogd[4749]: Cannot restore original GID/UID.
Jul 17 23:12:52 exo-elog elogd[4749]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 17 23:12:56 exo-elog elogd[4753]: Falling back to default group "elog"
Jul 17 23:12:56 exo-elog elogd[4753]: Falling back to default user "elog"
Jul 17 23:12:56 exo-elog elogd[4753]: Cannot restore original GID/UID.
Jul 17 23:12:56 exo-elog elogd[4753]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 17 23:12:56 exo-elog elogd[4757]: Falling back to default group "elog"
Jul 17 23:12:56 exo-elog elogd[4757]: Falling back to default user "elog"
Jul 17 23:12:56 exo-elog elogd[4757]: Cannot restore original GID/UID.
Jul 17 23:12:56 exo-elog elogd[4757]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 17 23:12:56 exo-elog elogd[4761]: Falling back to default group "elog"
Jul 17 23:12:56 exo-elog elogd[4761]: Falling back to default user "elog"
Jul 17 23:12:56 exo-elog elogd[4761]: Cannot restore original GID/UID.
Jul 17 23:12:56 exo-elog elogd[4761]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 17 23:12:56 exo-elog elogd[4765]: Falling back to default group "elog"
Jul 17 23:12:56 exo-elog elogd[4765]: Falling back to default user "elog"
Jul 17 23:12:56 exo-elog elogd[4765]: Cannot restore original GID/UID.
Jul 17 23:12:56 exo-elog elogd[4765]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 17 23:13:00 exo-elog elogd[4769]: Falling back to default group "elog"
Jul 17 23:13:00 exo-elog elogd[4769]: Falling back to default user "elog"
Jul 17 23:13:00 exo-elog elogd[4769]: Cannot restore original GID/UID.
Jul 17 23:13:00 exo-elog elogd[4769]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 17 23:13:00 exo-elog elogd[4773]: Falling back to default group "elog"
Jul 17 23:13:00 exo-elog elogd[4773]: Falling back to default user "elog"
Jul 17 23:13:00 exo-elog elogd[4773]: Cannot restore original GID/UID.
Jul 17 23:13:00 exo-elog elogd[4773]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Jul 17 23:13:39 exo-elog kernel: [  127.737506] elogd[4510]: segfault at b7b43000 eip 080adf19 esp bfdeeb00 error 4

and then crashes!

I am working on a logbook for a lab.  I have two questions...
First - Some of the logbook entries should not be viewed by certain users.  
What would be the easiest way to restrict viewing some entries?  

Second - I have a welcome page for the ELOG that lists some info about the 
ELOG.  When I start the ELOG, the user sees the login page.  After the user 
logs in, the welcome page appears listing the restrictions.  Right now, I 
have a hyperlink that takes the user to new, find, etc.  But I would like 
to take the user right to the logbook and not have to come back to the 
welcome page everytime.  How can I do this?

I have attached the code I have so far.  They are in .txt format for easier 
viewing.

Thanks!

The mxml source code should be moved into the elog-*/src directory. This requires changing the Makefile to:

MXMLDIR = src/mxml

Reason for change: if you want to build several versions of elog and you unpack the distributions in the same top-level directory, the most recently unpackaged version will overwrite the mxml directory contents, possibly introducing bugs.

I installed elog 2.7.2 rev 2041 into /data/elog on Redhat ES 4 Update 4. This is my initial elogd.cfg file:

[global]
port = 80
Resource dir = /data/elog/elog
Logbook dir = /data/elog/elog/logbooks
Logfile = /data/elog/elog/logs/access_log
Logging level = 2
Resolve host names = 0
Usr = nobody
Grp = nobody

[demo]
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

and start elogd - all is right with the world, everything is working properly. I shut down elog and try to add more logbooks using this template:
[A-B]
Subdir = cr_a-b
Comment = Change requests for Customers A-B
Menu commands = New, Reply, Download, Find, Last day
List Menu commands = New, Find
Display mode = summary

I create 14 of them, one for every 2 letters of the English alphabet and 0-9. The logbook name and Subdir change appropriately. When I start elog, it stays up for about 30 seconds, then crashes. No messages are recorded in syslog nor in the logfile. The only thing that looks suspicious are a couple lines in syslog:
Feb 15 17:11:05 iadopsutil04p elogd[23761]: elogd 2.7.2 built Feb 14 2008, 20:55:38 
Feb 15 17:11:05 iadopsutil04p elogd[23761]: revision 2041
Feb 15 17:11:05 iadopsutil04p elogd[23761]: FCKedit detected
Feb 15 17:11:05 iadopsutil04p elogd[23763]: Cannot restore original GID/UID.
Feb 15 17:11:05 iadopsutil04p elogd[23763]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Feb 15 17:11:05 iadopsutil04p elogd[23761]: Server listening on port 80 ...

This is obviously the child process responsible for the highlighted lines and it's coming from the cleanup function. Why it's getting called is beyond me.
Ideas?

Looking at some of the questions here this seems too newbie to even ask.

I want to set up a log book for my mechanics. I want them to each have a password to log in and enter what they do each day.

When I try to set up a password file it takes all the info, then when I hit save it says "server has been reset" and it will not log in. I have to remove the password = and restart the server.

[global]
port = 8080


[TFB]
Password file = <tfbpass>


Theme = default
Comment = TFB ENGINEERING
Attributes = Mechanic, Type of entry, Status, Subject
Attributes = Author, Status
Options Status = Completed, Incomplete, Notification only
Cell Style Status Completed  = background-color:green
Cell Style Status Incomplete  = background-color:red
Cell Style Status Notification only  = background-color:yellow



Options Mechanic= Jeff K, Arnaldo M, Bob L, Nathan P
Options Type of entry = Break Down, PM Repair, Building, FYI, Other
Options Status = Completed, Incomplete, Notification only, Other
Extendable Options = Category, Status,
Required Attributes = Mechanic, Type of entry, Category, Status,
Page Title = TFB Engineering - $subject
Reverse sort = 1
Quick filter = Date, Mechanic

 

 never mind. I figured it out I left the <  > in the password = line

Yes I do feel stupid.