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

I don't know why elogd uses different logbook directories depending on the user. Maybe you start it in different directories, or one user cannot read the config file and falls back to some default. Anyhow, you can start elogd interactively wit the -v flag which tells you which logbook files are parsed. There are no cache files or similar, everything is stored in Yymmdda.log files, you just have to search for them.

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

What is the string length limit in url tag and how to increase it?

For example,

[url=http://example.com?<text_string>]click here[/url]

When I provide very long <text_string>, it was truncated and showed partial link only.

Here is the problem:

[url=http://example.com?arrays[]=v1&arrays[]=v2]click here[/url]

How can I escape [] inside url tag?

\[\] seems not working.

The URL encoding of ']' as '%5D' appears to work:

[url=http://example.com?arrays[%5D=v1&arrays[%5D=v2]click here[/url]

Cheers, Andreas

That tweak works!

Thanks

Forgive me I'm not incredibly Elog savy yet.

A little backround about this log book -  I have our log set up as individual user names.  The log book is designed for entrys to be made when a process shutdown needs to be bypassed.  The operator will create an entry and submit it.  Then a supervisor will come in after and review/approve it.  I've removed the edit function,  but left the "Reply" option available for the supervisor to go into the same entry and check off the "Reviewed" attribute.  When the reviewed attribute is checked off, even with a different logged in author the next entry ID still shows the original author that put in the entry rather then the author who clicked reviewed.  If there a way to get around this?

[Process Bypass]
Comment = (Not in use right now, currently developing)
Attributes = Author, Date/Time of Bypass, Equipment Name, Device Tag, Supervisor Sign-off,
Moptions Supervisor Sign-off = Reviewed
List Menu commands = New, Find, Logout
Menu Commands = New, Find, Reply, Logout
Required Attributes = Date/Time of ByPass, Equipment Name, Device Tag
 

Preset on reply Author = $long_name
Cheers, Andreas

Works Great. Thanks Andreas

Hi,

First of all, thanks for all the great work, we all thank you here at SESAME synchrotron 

I am trying to set a conditional attribute where selecting one option in that attribute should trigger multiple outcomes as shown below:

Options Type = Fault{1_1&1_2}, Test{2_1&2_2}, Report{2_1&2_2}

{1_1} Options Fault Status = Open{a}, Fixed{b}
{2_1} Preset Fault Status = NA
{1_2} Preset Icon = attn.png
{2_2} Preset Icon = icon1.gif

I tries adding "&" as shown but that didn't work, my goal is to have 1_1 and 1_2 triggered whenever I select "Fault" as type, how can I do that?

Thanks in advance.

Cheers,

Sofian.

Hi Sofian,

it should work like this:

Options Type = Fault{1}, Test{2}, Report{3}

{1} Options Fault Status = Open{a}, Fixed{b}
{2,3} Preset Fault Status = NA
{1} Preset Icon = attn.png
{2,3} Preset Icon = icon1.gif

It is described under "Multiple conditions" in the documentation (https://midas.psi.ch/elog/config.html#conditional).

Cheers and good luck!

Andreas

Thanks Andreas,

Works great.

I tried reading the documentation on this but I was not able to deduce this solution.

Thanks a lot again.

What about this:

Options Type = Fault{1}, Test{2}, Report{3}

{1} Options Fault Status = Open{a}, Fixed{b}
{2,3} Preset Fault Status = NA
{1} Preset Icon = attn.png
{2,3} Preset Icon = icon1.gif

-Stefan

I am modifying the elogd.cfg automatically with a script.  The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.

Everything worked fine, until we hit the critical number of 100 attributes.  I saw this is also stated in the manual.

Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior. 

Is there a reason for this limit?

Thanks

Jonathan

The limit is in the variable 

#define MAX_N_ATTR      100

in elogd.c. If you increase it and recompile, it could work, but at some time you will get a stack overflow since arrays with that size are dynamically allocated on the stack, and depending on your compiler settings the stack size is only finite.

Stefan

Thank you Stefan, I think then I will leave it at the default value.  I need a stable Systen

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 are written there?

The debian version of elog is pretty old with quite a number of bugs fixed in meantime. Unfortunatlely the debig packase has not bee updated by the maintainers. So better download the current version from bitbucket and compile elogd yourself.