If

1. Elog is configured to use webserver authentication, and
2. the user reported by the webserver does not exist in the password file, and
3. the "Guest Menu commands" configuration is set in "elogd.cfg", and
4. a logbook is accessed,

then Elog returns with a redirect (302) to the logbook itself, causing the loop.

The fix here is to remove the "Guest Menu commands" configuration from "elogd.cfg".

Source code location: https://bitbucket.org/ritt/elog/src/30ada1df634529c8011c27275c52a05b01b7b3d6/src/elogd.cxx#lines-27599

Attributes = Author, Category, Notification list
Email all = $Notification list

Theme = default
Comment = Logs des modification de scripts des 3 domaines
Attributes = Acteur, Action, Type, Nom du Scripts, Language, Domaine, Categorie, Commentaires,Notification
Options Action = Ajout, Modification, Suppression, Réseau, Autre, Hotfix
Options Type = Ouverture de session,Autre, deploiement
Options Language = VBS, AU3, Kix, Batch, Ksh, Perl
Options Domaine = VaubanHumanis, Humanis, Vauban
Extendable Options = Catégorie, Type, Action
Required Attributes = Acteur, Type, Lieu
Page Title = Modification Scripts - $subject
Reverse sort = 1
Quick filter = Date, Type
Suppress Email to users = 1
# Email all = someadminsuser@maildomain.com
Email all = $Notification
Options Status = 1-To Do{1}, 2-Open{2}, 3-Closed{3}, 4-Suspended{4}

Dear ELOG experts,

the ELOG server on our lab crashes  continuosly, when we add a new entry or even if we click the arrows to navigate between entries. Following the FAQ on the website, I have used gdb and found the following error:

xmalloc: not enough memory

[Inferior 1 (process 23271) exited with code 01]

It should be then some allocation issue when we try to access to the entries, but I could not figure the nature of the issue. I was, however, able to reproduce it with a fresh ELOG installation and the same configuration file (ELOG cloned from git and installed today)

Could you please give me any suggestion? I attach here the configuration file we use.

Best regards,

Antonio Iuliano

Dear all, I have a problem with my window elog installation (2.9.2) and I would like to ask your help for solving it.

I'm using elog on my lab computer for a single user installation, so something very simple. It was running smoothly for many months using the automatic window service (i.e. elogd was started automatically at boot). I need to add that the service is started as the local administrator, while my user has no administrative rights. ELOG is installed in the standard location C:\Program Files (x86)\ELOG\ with the logbook folder inside and this is actually accessible only for admins.

On 8/04/2016, elogd crashed while I was saving an edited message. Then instead of restarting the service or rebooting the PC, I was just starting elogd manually (as me not as admin). It worked for many weeks. And now comes the problem: at the next reboot the elogd service came up automatically but all the new records I added in the logbook since I re-started manually are not there. Indeed in the C:\Program Files (x86)\ELOG\logbooks the latest entry is 160408a.txt. But if I stop the service and restart elogd manually (as me not as admin), then I can see in the logbook all the new entries.

My questions is where the ascii files corresponding to the new entries? They must be saved somewhere, maybe in some temporary folder. I want to copy them back and keep them in the backup to avoid unpleasant surprise.

Thanks in advance for your help,

Antonio

So I found the my log files, but this issue should probably be documented.

When running as admin my logbook files are where they should (C:\Program Files (x86)\ELOG\logbooks)

When running as local user (with no admin rights), elogd has no writing access to the logbooks directory. So it falls back to use C:\Users\[MyUserName]\AppData\Local\VirtualStore\Program Files (x86)\ELOG\logbooks

In both cases elogd -v is not helping because it says:

elogd 2.9.2 built Feb 20 2013, 09:19:10 revision 2475
Config file  : c:\Program Files (x86)\ELOG\elogd.cfg
Resource dir : c:\Program Files (x86)\ELOG
Logbook dir  : c:\Program Files (x86)\ELOG\logbooks\
FCKedit detected
Indexing logbook "sample" in "logbooks\sample\" ... 

that is not true for the local user.

Thanks again for your help,

Antonio