Hi,

I am experiencing repeated crashing of the elog daemon.

If I go into select mode while in threaded view, I can select an entire thread by selecting the top entry.

When I do so then press the Edit button, the server crashes.

I have to manually restart it. Syslog shows no error.

This does not happen under Summary or Full view.

Running Ubuntu 12.04, ELOG 2.9.2-2455

I can provide my elog.cfg if necessary.

Cheers!

Louis

P.S. i just crashed the forums ELOG following those same steps!! Sorry!! At least it was restarted in no time.

The Debian init script contributed here has been working quite well for me for the last few Ubuntu versions. Unless you edit it, it sets the elog base directory to /etc  so that's where you have to put your themes dir, resources, .conf file, scripts, logbooks, etc. I use symlinks to actually store my logbooks elsewhere.

I would also vote for a sane deb package. Right now, when I upgrade ELOG, I don't even run make install, I just copy the compiled binaries to their respective directories (/usr/bin or /usr/sbin). The rest stays the same.

 Hello,

Can anyone please send me, or publicly provide, working Ubuntu 10.10 binaries (64-bit) for ELOG?

I have compiled and installed the program. While the core functionalities are OK, I have run into irritating bugs in filtering and config editing that are not present in the online demo (but are in my local demo and logbook).

Hence I suspect compilation to be the cause.

For the curious:

• Saving the config within ELOG scrambles the elog.conf file

Hmm actually that last bug is also present in the demo. Any hope of fixing that?

True, some posts may not match the filters, leaving replies "orphan". I suggest that any orphan reply be either attached to the nearest upper level, or if not possible, be styled as a post instead of a reply (no arrow or indent) so as not to mistake it for a reply to the message above.

The benefit would be to be able to follow threads matching certain categories.

I noticed a behavior that might be irritating. 

After attaching/uploading files to an entry and before submitting it, one might press 'Back' or close the browser window.

This in effect cancels the entry and sends into oblivion. HOWEVER the attachments and their thumbnail files remain on the server forever.

Would there be a way to either delete attachments after some time if they don't show up in an entry? Or some other magic trick with the browser? My logbook directories are already full of orphan files that I need to seek and destroy.

Also, any thoughts on automatically cleaning up a logbook directory when the damage is done?

Louis

How about this:

Whenever a new file is uploaded, it would first be stored in a temporary directory. When the entry gets submitted, the files would be moved to the logbook directory and the entry edited accordingly.

Any wrongfully stored file would remain in that temp dir. Starting/restarting the daemon would cleanup that directory. Seems like a simpler approach and does not involve scripting the browser.

Since you used the -a switch for ls, the current directory '.' i.e. work/ is included in the list. I have the same kind of output. No worries.

Are you experiencing problems with ELOG?

Hi,

First, thanks to ELOG tool !

I'm trying to swicth a ELOG 3.1.2 server with local passwd DB to GIT version builded with SSL/PAM/LDAP options. I reuse the buildrpm script which generates correctly RPM files.

After installing on EL6 x86_64 server, i update the elogd.conf file according to GIT version doc :

• Authentication = PAM
• Password file = /usr/local/elog/elog_users.pam   (new file as i want to keep the old local DB)
• Self register = 3

I add a link for pam module :

$ ll /etc/pam.d/elogd
lrwxrwxrwx 1 root root 11 Jan 24 16:23 /etc/pam.d/elogd -> system-auth

elogd starts well

elogd 3.1.4 built Jan 24 2020, 07:34:02 revision 283534d
Config file  : /usr/local/elog/elogd.cfg
Resource dir : /usr/local/elog/
Logbook dir  : /usr/local/elog/logbooks/
Falling back to default group "elog"
Falling back to default user "elog"
CKeditor detected
Falling back to default group "elog"
Falling back to default user "elog"
Going to execute: /bin/sh -c "convert -version" > /tmp/elog_okY7qv 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
Going to execute: /bin/sh -c "/usr/bin/convert -version" > /tmp/elog_xBge3f 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
Going to execute: /bin/sh -c "/usr/local/bin/convert -version" > /tmp/elog_GfKWF0 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
Going to execute: /bin/sh -c "/opt/local/bin/convert -version" > /tmp/elog_uZtajL 2>&1
ImageMagick NOT detected. Image scaling will not work.
Indexing logbook "logbook1" in "/usr/local/elog/logbooks/logbook1/" ... ok
Indexing logbook "logbook2" in "/usr/local/elog/logbooks/logbook2/" ... ok
Server listening on port 8080 ...

When i try to connect, ELOG login window shows "Invalid user name or password!" .

The logfile (level 9) shows :

24-Jan-2020 16:36:28 [IP] POST /logbook1/ HTTP/1.1
24-Jan-2020 16:36:28 [IP] {MCO} LOGIN user "toto" (attempt)
24-Jan-2020 16:36:28 [IP] {MCO} [PAM] Starting authentication for user toto
24-Jan-2020 16:36:29 [IP] {MCO} [PAM] Authentication not successful for user toto

The problem appears for all Linux users as well.

Does i miss something ?

Thanks for help.

Laurent