Hello,

i have config file elogd.cfg like below:

[Tom Yaht]

Theme = default

;Comment and Tittle
Comment = LogBook
Page title = Tom LogBook
List page title = Tom LogBook

;admin and user settings
admin user = tom
login user = tom, soc
login expiration = 2

Restrict edit time = 8
Attributes = Controllers, Event Date/Time, Site, Engineers, Type, Category, Subsystems, Subject, Distribution-Mail, EMail to

Moptions Distribution-Mail = Controllers, Engineers, Consultant Team, Manager

;Email settings
Email Distribution-Mail "Controllers" = ble@xxx.com, cor@xxx.com, nor@xxx.com
Email Distribution-Mail "Engineers" = blo@xxx.com, sur@xxx.com, ars@xxx.com
Email Distribution-Mail "Consultant Team" = bli@xxx.com, zam@xxx.com
Email Distribution-Mail "Manager" = bos@xxx.com
Email all = $EMail to
Use Email Subject = Tom Logbook - $Subject
Use Email Heading = New Tom Logbook entry
Use Email Heading edit = Tom Logbook has been updated

The Subject successfully displayed as i expected , but the email heading still use default heading "A new ELOG entry has been submitted" , while i want to changeit to be "New Tom Logbook entry" as i mention in Use Email Heading  above.

Could anybody help me.

Thank you

The setting

Use Email Heading

is only used for plain text encoding of email messages. The default is HTML encoding, which has its own heading which cannot be changed. If you want the different heading, use

Email encoding = 1

and you get it.

/Stefan

Hi Stefan,

Thanks for your reply, i got it now.

Thank you

Hello,

I am trying to set up my elog to have read-only guest access and require registration/password for users to be able to post to the elog. I've tried following the instructions here: https://midas.psi.ch/elog/faq.html#6, i.e. putting the following lines under the [global] section of my elogd.cfg file:

Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Logout, Help
Guest menu commands = List, Find, Login, Help
 

When I do this, I do get guest acccess, however the menu items are

New |  Find |  Select |  Import |  Config |  Logout |  Last day |  Help 

rather than the List, Find, Login, Help I would expect. Also, if I click on Logout, it simply does nothing, which means there's now no way to log in as a registered user.

Any thoughts on what might be wrong?

Thanks,

Greg

There are two menus, one for the list display, and one for the individual entry display. To change the first, you need

List menu commands = ...
Guest list menu commands = ...

Got it. Thanks!

I have Split Elog to Two Top Group [Check the Config Below].

Problem = 

After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.

[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1

Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing

[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01

[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01

It would be new to me if elog would support independent [global] sections for each logbook.
I thought you can only have one [global] section. Whatever is defined in that section will be valid for all logbooks.

If you need to have different user files, you'll need to run different elogd services with independent config files (and Password files).

Andreas

Hi Andreas

I'm following the instruction from https://midas.psi.ch/elog/config.html#groups , please scroll to the Top Groups

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = 98, ME, NT, XP, CE
Group CE = 1.0, 2.UL

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases

[global engineering]
Password file = engineers.pwd
Admin user = stefan

[global administration]
Password file = admin.pwd
Admin user = bill

Aparently I've missed that one :-)

In order to test your problem it would be useful to have a minimal config file to reproduce the problem. Yours does not include any actual logbook, only [global *] sections.

Andreas

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = 98, ME, NT, XP, CE
Group CE = 1.0, 2.UL

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases

[global engineering]
Password file = engineers.pwd
Admin user = stefan

[global administration]
Password file = admin.pwd
Admin user = bill

Hi Andreas, 

Thanks for your help. I will try to do that and if I found how to fix this problems, I will post it at here again.

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = 98, ME, NT, XP, CE
Group CE = 1.0, 2.UL

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases

[global engineering]
Password file = engineers.pwd
Admin user = stefan

[global administration]
Password file = admin.pwd
Admin user = bill

I think with the latest Imagemagick from brew (6.9.4-7) that pdf thumnails no longer get made; the attachment is there but the message "Cannot create thumbnail, please check ImageMagick installation" apears instead of the thumbnails.  I couldn't make out from elogd -v 3 why they failed, but I couldn't make out the exact convert command that was failing.  This is on MacOS 10.11.5 and I think the updated version ofImagemagick was the last thing that changed before it failed.

Hi all,

ELOG V3.0.0-21dc563

Our elogd dies alwways when searching for full text:

elogd: src/elogd.c:465: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.
elogd: src/elogd.c:465: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.

The only change we did was adding/editing entries.

Does anyone else encounter the same issue ?

I did not find any hint in release notes that this issue would be fixed in a later version

Please don't get me wrong, I am not complaining. Elog does a great job for us since years.

Christian

I would like to share my findings about the solution of our problem:

One of my collegues used elog in a way it was not intended for, he put an endry with 8021 lines of text.

So I grabbed the corresponding 160517a.log file from logdir, renamed it to a text file and created a new entry with the large textfile as attachment.

Since then, no more crash of elogs.

May this contribution be useful to other elog users...

Christian

Dear all

I installed elog from the current stable repository on Debian 8 (jessie)

The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel with an existing webserver and then I tested. The demo logbook loads fine and I see that elog created a folder for the logbook in /var/lib/elog/logbooks, which is the directory specified by default in the /etc/init.d/elog file.

Then I modified the /etc/elog.conf file, added the following lines in the global section (custompath is a local path) 

Resource dir = /<custompath>/elog/res
Logbook dir = /<custompath>/elog/logbooks

And I created a new logbook.

After restarting the elog service the second database is correctly created but both of them are still stored in  /var/lib/elog/logbooks so it seems the global configurations in the config file are overwritten.

How can I specify the custom folder so that the new logbooks a

We have always had issues with eLOG crashing intermittently...  I upgraded from Server 2003 to Server 2008 about a year ago to try to reduce the issues...  which really didn't help.

The service now seems to crash every week...  (getting worse)...  Is anyone seeing these issues in Windows servers?  Any suggestions??

We do run ELOG on a Linux server and see about weekly crashes, too. It seems to be connected to the authentication process (Kerberos, File), but we could not nail it down yet.

But we have set up a supervision process that checks every minute if the "elogd" process is still running. If not, it simply restarts it.

If ELOG is down for two minutes a week, this is fine for our users.

The elog client binary does not work with webserver authentication.  One fix would be to support both webserver and kerberos authentication (authentication = webserver, kerberos), similar to how you currently support 
"authentication = kerberos, file".

A more general discussion of the elog client binary with webserver authentication can be found at https://midas.psi.ch/elogs/Forum/68318 .

Many thanks,
Devin