Hi,

I have two logbooks based on the same data directory through "Subdir" option and when I add new entry in one logbook, then that entry is not visible in other logbook.

I suppose it is a bug in el_submit function, where I think the new message should be added to message index of every logbook based on the same data directory as the one, where the message was physically created. 

There is a piece of code, which I think should do this automatically

/* if other logbook has same index, update pointers */

but it seems the other logbooks does not have the same index. 

I'm new to elog and the sources are also new to me, so my guess to the ground of the problem may be wrong.

Let me know is this bug possible to fix in near future.

Best regards,

Jacek

Well, having two logbooks in the same subdirectory was initially a planned feature but really never worked. I re-visited this issue and made it working in the current SVN version. So the next release will contain the fix. 

If I create an entry via the web-interface, the defined encoding of the browser is used.
If I create an entry via "elog", it is always stored in UTF-8 encoding.
For the text I can overcome that with HTML encoding, but for attribute values the encoding does not show properly.
The only solution I found was to convert the whole logbook to UTF-8 encoding:

 define "charset=UTF-8" in elogd.cfg
 iconv --from-code=ISO-8859-1 --to-code=UTF-8 elogd.cfg >tmp;mv tmp elogd.cfg
 iconv --from-code=ISO-8859-1 --to-code=UTF-8 resources/eloglang.german >tmp;mv tmp resources/eloglang.german

Has anyone any idea why ISO8859-1 does not work for me?

Or can anyone advice me of an editor similar to NEdit that is capable to display UTF-8? :-)

> If I create an entry via the web-interface, the defined encoding of the browser is used.
> If I create an entry via "elog", it is always stored in UTF-8 encoding.
> For the text I can overcome that with HTML encoding, but for attribute values the encoding does not show properly.
> The only solution I found was to convert the whole logbook to UTF-8 encoding:
> 
>  define "charset=UTF-8" in elogd.cfg
>  iconv --from-code=ISO-8859-1 --to-code=UTF-8 elogd.cfg >tmp;mv tmp elogd.cfg
>  iconv --from-code=ISO-8859-1 --to-code=UTF-8 resources/eloglang.german >tmp;mv tmp resources/eloglang.german
> 
> Has anyone any idea why ISO8859-1 does not work for me?
> 
> Or can anyone advice me of an editor similar to NEdit that is capable to display UTF-8? :-)

I just tried it submitting to the Demo logbook:

https://midas.psi.ch/elogs/Linux+Demo/15

using some German Umlauts, and saw that it works fine. "elog" does not do any conversion, just submits the text as is. 
If your text is ISO-8859-1 encoded, it will be submitted as such, and your browser will correctly display it. Have you 
tried removing the "charset=UTF-8" from your elogd.cfg?

Hello,

i have a logbook with the following parameters for the Attribute "Typ":

[TEST1]
Options Typ = SDB{2}, Qualifizierung B.12.S227{4}, Qualifizierung PRO/REP{3}, Dokument zur Qualifizierung{2}, Prüf- und Wartungsvorschrift{2}, SOP ohne Change Request{2}, SOP mit Change Request{1}, Validierung PRO/REP{3}, Dokument zur Verifizierung{2}, Überprüfung und Verlängerung{2}, Spec.Sheet{2}, CoA (sofern nicht LIMS){2}, Änderungen Tg4.B07{5}, OOS (Plan/Bericht){3}, Transfer PRO/REP{3}, Studie PRO/REP{3}, Studie ohne Plan{2}, Anderes{2}
Quick filter = Date, Typ

If i choose an Entry from the "Typ" Quick Filter it shows me that there are no entries in the logbook but I'm shure that there are entries. 

Can you please help? I cannot see what's wrong.

Best Regards

Michael

I tried your configuration and it worked fine:

So can you try version 2.8.1 if that makes any difference. If not, can you send me your complete elogd.cfg, so that I can reproduce your problem.

- Stefan

 I installed 2.81 (Elog-latest) but this Version did not work. I got Error 193: %1 is not a valid Win32 Application as I tried to start the service. So i will sent you the complete elogd.cfg via Mail.

Best regards

Michael 

corrected file is attached

Hello,

Is it possible to run multiple instance of elog on the same windows box where each instance listens on a different port?

Thanks.

Behdad.

Sure. Just start with one subdirectory for each instance with a separate elogd.cfg file, where you specify a different port. Note however that there is also the concept of "top groups" (see documentation) which lets a single instance of elog look like several independent installations. 

Great. Thanks Stefan. 

I also am already using the top groups. This is just to totally separate my work and home elog.....I have to admit I am really an elog addict. 

This elog and the idea behind it is absolutely  brilliant. Very useful, easy to maintain, migrate, configure, easy to use, versatile, etc...  Good on you all.

Cheers,

Behdad.

Hello all,

I have a problem with retrieving attachments of an entry on "Execute new" command. In the syntax of elodg.cfg it is: In addition the list of all attachments can be referred to via $<attachment>. Could anyone explain it a little bit more explicit, or attach an example?

Thank you in advance.

Hello again,

I have managed with problem by using $attachments. This provides me a list o paths to attachments. If it's the correct way to use it please change elogd.cfg syntax page.

Thanks a lot.

Yes, indeed there was a typo in the documentation, $attachments is the correct one. I changed that in the syntax page.

Hello Stefan,

first of all thanks for quick response.

However I encountered another problem, but to explain it well I need to tell you more what actually I want to do with these substitutions. 

So I would like to have a python script which on add new entry will create a new entry in another logbook with the same data (Only for certain attributes' values). That's why I need attachments.

These substitutions will be used as command line arguments of the script.

Since I started using $attachments, all the substitutions used before it, are passed twice? Without using $attachments substitution, it works fine - they are passed only once.

Furthermore I tested it without script, just passing them to a text file, and it seems that it really doesn't work well. Could you check that?

-------------------

Execute new = echo $message id '$long_name' '$System' '$Equipment' '$Subject' '$text' > /tmp/zzz_elog.log             WORKS GOOD

Execute new = echo $message id '$long_name' '$System' '$Equipment' '$Subject' '$text'  $attachments> /tmp/zzz_elog.log            DOESN'T WORK GOOD

------------------

Thank you a lot in advance.

Thanks for reporting this bug. I fixed this in SVN revision  2348.

I have installed elog 2.8 in a windows pc with the installer from the distribution, it installs elog as a windows service, which is started automatically when windows starts.

It is done as:

"C:\Archivos de programa\ELOG\elogd.exe" -D -c "C:\Archivos de programa\ELOG\elogd.cfg"

Moreover Imagemagick and GhostScript are in the path:

Version: ImageMagick 6.6.4-6 2010-09-21 Q16 http://www.imagemagick.org
Copyright: Copyright (C) 1999-2010 ImageMagick Studio LLC
Features: OpenMP 

However the indexing loogbooks are only working  fine when elog is started interactively.  Is there any posiblity to start elog as a service and use thumbnails for quick preview?

Thank you in advance!

This is a know problem. I did not achieve to create the imagemagic subprocess and read its output when elogd is started as a service. Attached is the code doing that, I found it as an example from Microsoft. But even after hours of work, I could not get it running inside the service. If anybody has any idea, please let me know. 

 Hi all,

i have a question... How can i manage it that elog starts automatically on windows startup ? I  always need to type "elogd -p 85" in the console that it starts ...

Can anyone help me ? =)

Thanks

SenoX

If you install elog with the installer from the distribution, it installs elog as a windows service, which is started automatically when windows starts. 

 Hello
When the install did not work properly  ( I've never had that problem ) you can start the elog service with the SC.EXE command like this :

sc.exe create Elog binpath= "\"c:\program files\elog\elogd.exe\" -D -c \"c:\program files\elog\elogd.cfg\"" displayname= "Elogbook services" start= auto type= own

Please notice the spaces after the =  ( they are required )

You can now use :
net start elog
and
net stop elog

to start the service without a reboot.

Maybe this helps.