Hello,

Recently upgraded to 2.7.3 and I'm seeing html code filling up the reply window. Before I would just see [quote] and [/quote] around the original entry. Did I miss something in the upgrade? Thanks!

 Probably you did not install the FCKeditor. Just try a reply to this message, and you will see the many formatting icons on top of the page coming from that HTML editor. Without the editor, you will only see the plain HTML. You can switch back however to the old behavior by selecting the ELCode encoding. You can make this permanent with the "Default encoding =0" option.

One of my shifters just managed to make an anonymous logbook entry even though the Author attribute is required.

It turns out that he had two tabs in his browser opened/logged into the Elog.  He logged out in one tab only.   Then he

did some other work on the desktop.  Then he returned to the browser to make a new logbook entry, finding the tab which

still showed the logged in menu, including the link for "New".  The Shifer is on day two, so he did not give any special

notice to seeing Anonymous in the Author field instead of his name.  He did point it out when I came in, and noted that

no warning was given about making an anonymous entry.

I tested the same scenario myself.  One cannot preview an anonymous entry (when Author field is a required attribute).

A warning is given.  However, one can submit the anonymous entry, and no warning is given.

Alan

 What configuration do you use? I tried to reproduce your problem with a "minimal" configuration like

[demo]
Attributes = Author, Subject
Preset Author = $long_name
Locked Attributes = Author

When I log out from the second browser tab and click on "New" on the first browser tab, I am shown the login page, not the new entry page. I guess your "menu commands" and "guest menu commands" allow non-logged in users to issue a "New" command. Try removing that.

Stefan

My Elog running on windows 2003 sp1 is crashing with this error "  Faulting application elogd.exe, version 0.0.0.0, faulting module elogd.exe, version 0.0.0.0, fault address 0x00061330."  the version of elogd.exe is  has a built date of 2/22/2008.  Will upgrading to the latest windows binary resolve this issue?    Thanks!!

 

 I would give it a try!

Hi,

When the WINDOWS binaries with the latest bug fixes will be available on the download page ?

Have a nice day

 Whenever you ask for it 

I made you an elog274-1.exe containing revision 2118.

I get the following error where thumbnails should go: Cannot create thumbnail, please check ImageMagick installation.

I restarted elog and check the log, it does in fact detect ImageMagick and it does have the most recent version. I'm running ubuntu 2.6.24-19-server.  Is there something else I should be checking?

 Try the following:

• Put logfile = elog.log into your elogd.cfg
• Upload an image to get the error
• Examine your elog.log file

You should get something like:

23-Jul-2008 15:10:38 [] Server listening on port 8080 ..
23-Jul-2008 15:10:52 [stefan@127.0.0.1] {demo} SHELL "convert "logbooks\demo\080723_151052_Capture.png" "logbooks\demo\080723_151052_Capture.png.png""

In your logfile. Now try the "convert" command manually under the same account elogd is running. Possible reasons for problems are:

• The "convert" command is not in your path or links to another program. Unfortunately ImageMagick chose a pretty standard name for this program
• The account under which elogd is running does not have write access to the logbook directory
• converts wants to call ghostscript for PDF conversion, but it is not installed
• ...

Hi, I would like to preset an attribute type useremail with $user_email but that does not work because $user_email contains mailto: like mailto:user_email@domain
Has anyone an idea how to resolve this problem?

Type Reporter = useremail
Preset Reporter = $user_email

Type Reporter = useremail
Preset Reporter = $user_email

 This was a bug. I fixed it in SVN revision 2118.

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!

We have been successfully using the TCK-##### for several months and suddenly today it has stopped incrementing. We were at ticket # 40 and this morning any new tickets come up as 12 and never increment? We have tried restarting the elog service. Any suggestions would be appreciated.

Thank You

Don

My apologies for posting this question. I have found the solution.

We had two log books each with the same variable called "Ticket" but different values. When an entry from one was Moved to the other the counter was confused. I had to manually change the value of "Ticket" to match the convention of the log book that the entry was now in.

Thanks