| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68645
|
Wed Jul 19 10:25:08 2017 |
 | Phil Rubin | rubinp@cern.ch | Question | Linux | 2.9.2 | Re: Email Notification (Not) Initiated by elog Client Utility | I didn't realize you required every detail of the command, since the entry is being logged, but here is an example (only the user information is blanked out):
/usr/local/bin/elog -h vmna62s1 -p 8080 -l NA62Logbook -u xxxx xxxx -a Author=Rubin -a Type=Problem\(s\) -a Category=Elog -a Subject="Client Initiated E-mail Notification" "Tests"
From elogd.cfg:
Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = Access, Beam, CHANTI, CHOD, Computer/Network, DCS/DSS, Elog,
GTK, HASC, IRC/SAC, KTAG, LAV, LKr, MUV, NewCHOD, Online Monitor, RICH, Run, Run
Control, Shift, STRAW, TDAQ
{1} Email Category Elog =
{2} Email Category Elog = Philip.Rubin@cern.ch
{3} Email Category Elog =
The TDAQ-category command that is misbehaving is essentially identical:
/usr/local/bin/elog -h vmna62s1 -p 8080 -l NA62Logbook -u xxxx xxxx -a Author="Run Control" -a Type=Problem\(s\) -a Category=TDAQ -a Subject="Board Reload" "KTAG4"
| Andreas Luedeke wrote: |
|
If that is your command then it is obvious why no email is send:
you do set "Type=Type", but only for "Type=Problem(s)" and "Category=TDAQ" you would send an email.
Instead of writing "-h host" you should as well define the actual hostname, like "-h midas.psi.ch", likewise for all other parameter.
| Phil Rubin wrote: |
|
Thank you for responding.
I thought I provided the command at the end of the note:
/usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"
This results in an entry being appropriately logged in Notebook with the correct author, type, category, subject, and text. The only problem is that, when the type is such that email notification should be sent to the list associated with category, it is not sent.
For the record, I reconfigured elogd.conf so that parentheses are no longer there, but this made no difference, so this isn't the problem.
Sorry for forgetting these details: bash shell; linus version 2.6.32-696.el6.x86_64
| Andreas Luedeke wrote: |
|
Yes, parentheses in field content might be difficult to pass from a shell command. You did not even mention which Linux shell you are using and you did not show the actual elog command. Maybe you want to add that information?
| Phil Rubin wrote: |
|
Our configuration sends out e-mail notifications based on a hierarchy of attributes, and works fine with WEB submissions, but not with client utility submissions (no notifications are sent; the log doesn't show it even trying to send any: 14-Jul-2017 18:36:01 [rubinp@nn.nn.nn.nn] {Notebook} NEW entry #0) . Since notification is the default (suppression requires -x), I presume there is something wrong with the way we're going about this. Can you see what it is? Could it be the parentheses in the type Problem(s), which have to be sent at the shell in the client command as Type=Problem\(s\)?
[global]
.
Suppress Email to users = 1
.
[Notebook]
.
Attributes = Author, Type, Category, Subject
Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = ... TDAQ ...
.
{1} Email Category TDAQ =
{2} Email Category TDAQ = user1@aa.bb, user2@cc.dd,...
{3} Email Category TDAQ =
.
Use Email Subject = Elog Notice: $subject
Command: /usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"
|
|
|
|
|
|
68646
|
Wed Jul 19 13:37:33 2017 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 3.1.3 | Re: Email Notification (Not) Initiated by elog Client Utility | Okay, I can confirm that this does not work. It is likely related to the disclaimer in the ELOG documentation (https://midas.psi.ch/elog/config.html#conditional)
Conditional attributes are usually only used for change items in the entry form.
I guess that the "Email" command never worked with conditional attributes. I use the "Email" command and conditional attributes extensively, but I've never tried before to use "Email" in a condition.
I've tested the functionality with the following minimal configuration for the latest ELOG version 3.1.3-aded4ae :
Attributes = A, B
Options A = X{1}, Y{2}
Options B = N, M
{2} Email B M = andreas.luedeke@psi.ch
The following elog command creates the desired entry, but does not send out an email. Creating the identical entry via the web form does initiate the email.
elog -u <user> <password> -h <host> -p 80 -l <logbook> -a "A=Y" -a "B=M" -n 1 "entry by elog cmd"
Thank you Phil for pointing out the problem.
Cheers, Andreas
| Phil Rubin wrote: |
|
I didn't realize you required every detail of the command, since the entry is being logged, but here is an example (only the user information is blanked out):
/usr/local/bin/elog -h vmna62s1 -p 8080 -l NA62Logbook -u xxxx xxxx -a Author=Rubin -a Type=Problem\(s\) -a Category=Elog -a Subject="Client Initiated E-mail Notification" "Tests"
From elogd.cfg:
Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = Access, Beam, CHANTI, CHOD, Computer/Network, DCS/DSS, Elog,
GTK, HASC, IRC/SAC, KTAG, LAV, LKr, MUV, NewCHOD, Online Monitor, RICH, Run, Run
Control, Shift, STRAW, TDAQ
{1} Email Category Elog =
{2} Email Category Elog = Philip.Rubin@cern.ch
{3} Email Category Elog =
The TDAQ-category command that is misbehaving is essentially identical:
/usr/local/bin/elog -h vmna62s1 -p 8080 -l NA62Logbook -u xxxx xxxx -a Author="Run Control" -a Type=Problem\(s\) -a Category=TDAQ -a Subject="Board Reload" "KTAG4"
| Andreas Luedeke wrote: |
|
If that is your command then it is obvious why no email is send:
you do set "Type=Type", but only for "Type=Problem(s)" and "Category=TDAQ" you would send an email.
Instead of writing "-h host" you should as well define the actual hostname, like "-h midas.psi.ch", likewise for all other parameter.
| Phil Rubin wrote: |
|
Thank you for responding.
I thought I provided the command at the end of the note:
/usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"
This results in an entry being appropriately logged in Notebook with the correct author, type, category, subject, and text. The only problem is that, when the type is such that email notification should be sent to the list associated with category, it is not sent.
For the record, I reconfigured elogd.conf so that parentheses are no longer there, but this made no difference, so this isn't the problem.
Sorry for forgetting these details: bash shell; linus version 2.6.32-696.el6.x86_64
| Andreas Luedeke wrote: |
|
Yes, parentheses in field content might be difficult to pass from a shell command. You did not even mention which Linux shell you are using and you did not show the actual elog command. Maybe you want to add that information?
| Phil Rubin wrote: |
|
Our configuration sends out e-mail notifications based on a hierarchy of attributes, and works fine with WEB submissions, but not with client utility submissions (no notifications are sent; the log doesn't show it even trying to send any: 14-Jul-2017 18:36:01 [rubinp@nn.nn.nn.nn] {Notebook} NEW entry #0) . Since notification is the default (suppression requires -x), I presume there is something wrong with the way we're going about this. Can you see what it is? Could it be the parentheses in the type Problem(s), which have to be sent at the shell in the client command as Type=Problem\(s\)?
[global]
.
Suppress Email to users = 1
.
[Notebook]
.
Attributes = Author, Type, Category, Subject
Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = ... TDAQ ...
.
{1} Email Category TDAQ =
{2} Email Category TDAQ = user1@aa.bb, user2@cc.dd,...
{3} Email Category TDAQ =
.
Use Email Subject = Elog Notice: $subject
Command: /usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"
|
|
|
|
|
|
|
384
|
Mon Jun 30 17:07:03 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | elog-2.3.6-1 | Re: Email Notification | > Is there a way to configure elog so users that have their email notification
> on only get notified for updates to logs they have access to? I've looked
> all through the documentation and I can't seem to find a way to do this.
I guess you have a global password file and use "login user" statements for
your logbooks. I have added some code which does per default not send any
email to people who are not in the "login user" list, in case this list is
present. New code under CVS. Please give it a try and let me know if it works
for you.
- STefan |
|
386
|
Mon Jun 30 20:29:43 2003 |
 | Robert Keeney | brassrlk@yahoo.com | Question | Linux | elog-2.3.6-1 | Re: Email Notification | You guessed right. I give it a try soon as I get a chance. Thanks.
> I guess you have a global password file and use "login user" statements for
> your logbooks. I have added some code which does per default not send any
> email to people who are not in the "login user" list, in case this list is
> present. New code under CVS. Please give it a try and let me know if it works
> for you.
>
> - STefan |
|
407
|
Wed Jul 23 12:53:25 2003 |
| Robert Keeney | brassrlk@yahoo.com | Question | Linux | elog-2.3.6-1 | Re: Email Notification | I have had this installed for about two weeks now and it seems to be working
fine. I haven't seen any problems at all and none of the other users have
reported any.
Thanks. This is very helpful.
> > Is there a way to configure elog so users that have their email notification
> > on only get notified for updates to logs they have access to? I've looked
> > all through the documentation and I can't seem to find a way to do this.
>
> I guess you have a global password file and use "login user" statements for
> your logbooks. I have added some code which does per default not send any
> email to people who are not in the "login user" list, in case this list is
> present. New code under CVS. Please give it a try and let me know if it works
> for you.
>
> - STefan |
|
68789
|
Wed Apr 18 12:30:51 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.1.1 | Re: Email Config | SMTP host = ...
as written in the documentation!
Automatic email after expiration is not possible.
| Stefan Werler wrote: |
|
Hi,
I´m new in ELOG,
Can u explain me how i config the Mailing?
in my Configuration i do have not the ability to set an Email Host/Server. or i didn´t find it....
I have to use ELOG as ticket system, is it possible to send an email automatically after expiration of a period?
|
|
|
68790
|
Wed Apr 18 13:18:07 2018 |
 | Stefan Werler | stefan.werler@ah-senden.de | Comment | Windows | 3.1.1 | Re: Email Config | many thanks
| Stefan Ritt wrote: |
|
SMTP host = ...
as written in the documentation!
Automatic email after expiration is not possible.
| Stefan Werler wrote: |
|
Hi,
I´m new in ELOG,
Can u explain me how i config the Mailing?
in my Configuration i do have not the ability to set an Email Host/Server. or i didn´t find it....
I have to use ELOG as ticket system, is it possible to send an email automatically after expiration of a period?
|
|
|
|
68791
|
Wed Apr 18 13:43:36 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 3.1.1 | Re: Email Config |
SMTP host = ...
MUST be set in the [global] section of your configuration - it will likely not work when you try to set it for a specific logbook.
I don't see how ELOG can send an automatic email after a date expired.
But you could set-up a script that checks for expired entries, and if there are any it'll send out an email. You can use any http connection to do the query using the find command (e.g. curl).
To get the right URL, just make the find from the web form and copy the URL that gives you the desired result.
Hope that helps.
Andreas
| Stefan Werler wrote: |
|
Hi,
I´m new in ELOG,
Can u explain me how i config the Mailing?
in my Configuration i do have not the ability to set an Email Host/Server. or i didn´t find it....
I have to use ELOG as ticket system, is it possible to send an email automatically after expiration of a period?
|
|
|