Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 94 of 806  Not logged in ELOG logo
icon5.gif   How to configure eLog to send an e-mail notification when new logbook entry time is reached?, posted by Tero Suominen on Wed Mar 25 14:16:21 2009 Expiration_field.GIF

Hello!

First I would like to thank you for making such a good free software available:). Then right back into the busness. I have a question to developers. I used the following Options to get the logbook entry  which defines the licences expiration date (See the attachement). Now I would like to ask on how to configure eLog to send an e-mail notification when this date is reached?

 

Attributes = Licence Expiration date
Type Licence Expiration date = date
Date format = %A, %B %d, %Y

 

The ideal solution would be to have configurable variable which would automatically send a notification X days before the expiration date is reached. Do you think this would be possible feature request to this Forum into eLog wishlist?

BR,


Tero Suominen

    icon2.gif   Re: How to configure eLog to send an e-mail notification when new logbook entry time is reached?, posted by Tero Suominen on Wed Mar 25 14:35:23 2009 

Stefan Ritt wrote:

 

Tero Suominen wrote:

Hello!

First I would like to thank you for making such a good free software available:). Then right back into the busness. I have a question to developers. I used the following Options to get the logbook entry  which defines the licences expiration date (See the attachement). Now I would like to ask on how to configure eLog to send an e-mail notification when this date is reached? 

 

Attributes = Licence Expiration date
Type Licence Expiration date = date
Date format = %A, %B %d, %Y

 

BR,


Tero Suominen

 

That's not possible with ELOG, which is meant as an electronic logbook. You need a calendar application for that. 

 Hi! Thanks for the quick response. Do you have any suggestions on which calendar applications I should start looking for for this purpose?

Thanks,

Tero

icon5.gif   New entry cannot be written to directory "/usr/local/elog/logbooks/demo/", posted by Tapasi Ghosh on Mon Feb 8 13:52:33 2016 image.png

Dear All,

I could not submit a new enetry to my logbook whenever restarting my laptop.  I am a new user to elog.

Attached is the screenshot of the error message and also there is "nobody" while I grep elog.

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

>>

Tapasis-MacBook-Pro-2:elog-3.1.0 tapasi$  ps aux | grep elog

tapasi            560   0.4  0.0  2432772    644 s002  S+    9:50AM   0:00.01 grep elog

nobody             76   0.0  0.4  2481308  18440   ??  Ss    9:48AM   0:00.08 /usr/local/sbin/elogd -c /usr/local/elog/elogd.cfg

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

Any suggesstion will be very much appreciated.

Thanks in advance,

Tapasi

 

 

    icon2.gif   Re: New entry cannot be written to directory "/usr/local/elog/logbooks/demo/", posted by Tapasi Ghosh on Mon Feb 8 16:19:11 2016 

Thanks for your reply.

I am the user and  it also has the write access 

cd /usr/local/elog/

ls -ltr

drwxrwxrwx  6 tapasi  admin  204 Jan  7 18:26 demo

Andreas Luedeke wrote:

You should check if the directory /usr/local/elog/logbooks/demo belongs to the right user and has the right write permissions.

Since the elogd process belongs to the user "nobody", the directory should best belong to "nobody" as well (or - not recommended - allows write access for "others")

Cheers, Andreas

Tapasi Ghosh wrote:

Dear All,

I could not submit a new enetry to my logbook whenever restarting my laptop.  I am a new user to elog.

Attached is the screenshot of the error message and also there is "nobody" while I grep elog.

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

>>

Tapasis-MacBook-Pro-2:elog-3.1.0 tapasi$  ps aux | grep elog

tapasi            560   0.4  0.0  2432772    644 s002  S+    9:50AM   0:00.01 grep elog

nobody             76   0.0  0.4  2481308  18440   ??  Ss    9:48AM   0:00.08 /usr/local/sbin/elogd -c /usr/local/elog/elogd.cfg

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

Any suggesstion will be very much appreciated.

Thanks in advance,

Tapasi

 

 

 

 

    icon2.gif   Re: New entry cannot be written to directory "/usr/local/elog/logbooks/demo/", posted by Tapasi Ghosh on Mon Feb 8 17:40:27 2016 

Sorry, it was my mistake while copying  from terminal to the email .  There is no "demo" directory under /usr/local/lib.

Tapasis-MacBook-Pro:elog tapasi$ cd  /usr/local/elog/logbooks/demo

Tapasis-MacBook-Pro:demo tapasi$ ls -ltr

total 0

drwxr-xr-x   3 tapasi  admin   102 Sep 22 11:00 2001

drwxr-xr-x  55 503     admin  1870 Dec 17 13:21 2015

drwxr-xr-x   2 tapasi  admin    68 Jan  7 14:54 2016

 

So, how can I change the user from "nobody" to my name, so that elogd runs in my user name ?

Thanks

Andreas Luedeke wrote:

The process elogd runs as the user "nobody". This user obviously cannot write to /usr/local/elog/logbooks/demo.

But apparently you've created the wrong directory anyway: you've listed /usr/local/elog/demo, but ELOG looks for /usr/local/elog/logbooks/demo.

Cheers, Andreas

Tapasi Ghosh wrote:

Thanks for your reply.

I am the user and  it also has the write access 

cd /usr/local/elog/

ls -ltr

drwxrwxrwx  6 tapasi  admin  204 Jan  7 18:26 demo

Andreas Luedeke wrote:

You should check if the directory /usr/local/elog/logbooks/demo belongs to the right user and has the right write permissions.

Since the elogd process belongs to the user "nobody", the directory should best belong to "nobody" as well (or - not recommended - allows write access for "others")

Cheers, Andreas

Tapasi Ghosh wrote:

Dear All,

I could not submit a new enetry to my logbook whenever restarting my laptop.  I am a new user to elog.

Attached is the screenshot of the error message and also there is "nobody" while I grep elog.

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

>>

Tapasis-MacBook-Pro-2:elog-3.1.0 tapasi$  ps aux | grep elog

tapasi            560   0.4  0.0  2432772    644 s002  S+    9:50AM   0:00.01 grep elog

nobody             76   0.0  0.4  2481308  18440   ??  Ss    9:48AM   0:00.08 /usr/local/sbin/elogd -c /usr/local/elog/elogd.cfg

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

Any suggesstion will be very much appreciated.

Thanks in advance,

Tapasi

 

 

 

 

 

 

icon3.gif   Slackbot for ELOG, posted by Tamas Gal on Wed Jan 13 08:25:50 2016 elog-slack.png

Dear all,

I just wanted to share a small script which I wrote to integrate our ELOG in Slack. This allows us to be notified immediately if there is a new logbook entry directly within the appropriate Slack channels. We're using ELOG V2.9.2-245 but if the log-file format has "Subject, Author, Type" in the header, it should work with any other version. I'm using Pyinotify for the file watch which relies on a Linux Kernel feature (merged in kernel 2.6.13) called inotify, so the script only works on Linux.

Here is the code: https://github.com/tamasgal/elog-slack

Cheers and thanks for ELOG!

Tom

    icon2.gif   Re: Monitoring a logbook for changes, posted by Tamas Gal on Wed Jan 13 08:37:42 2016 

I recommend monitoring directly on the server. Here is an example of a very simply Python script (https://github.com/tamasgal/elog-slack) which monitors the files very efficiently and immediately pushes notifications to Slack (slack.com). Just look at the code, it's pretty straight forward and very easy to adapt it to other (web) services.

Btw. here is an ELOG entry of it https://midas.psi.ch/elogs/Forum/68224

Johan Forsberg wrote:

Hi again!

I've another need that you probably already thought of :)

I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).

Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.

Cheers,

Johan

 

    icon2.gif   Re: Monitoring a logbook for changes, posted by Tamas Gal on Wed Jan 13 17:04:34 2016 

I just noticed that there are multiple messages per file, so I have to adapt the parser. I'll update this thread when I'm done!

Johan Forsberg wrote:

Yeah, I suppose something like that would be both faster and more efficient than polling ELOG itself. Fortunately the ELOG disk format looks easily parsed.

Thanks for the pointer!

Tamas Gal wrote:

I recommend monitoring directly on the server. Here is an example of a very simply Python script (https://github.com/tamasgal/elog-slack) which monitors the files very efficiently and immediately pushes notifications to Slack (slack.com). Just look at the code, it's pretty straight forward and very easy to adapt it to other (web) services.

Btw. here is an ELOG entry of it https://midas.psi.ch/elogs/Forum/68224

Johan Forsberg wrote:

Hi again!

I've another need that you probably already thought of :)

I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).

Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.

Cheers,

Johan

 

 

 

ELOG V3.1.5-3fb85fa6