Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   Email Notification (Not) Initiated by elog Client Utility, posted by Phil Rubin on Fri Jul 14 19:26:06 2017 
    icon2.gif   Re: Email Notification (Not) Initiated by elog Client Utility, posted by Andreas Luedeke on Wed Jul 19 08:50:16 2017 
       icon2.gif   Re: Email Notification (Not) Initiated by elog Client Utility, posted by Phil Rubin on Wed Jul 19 08:59:52 2017 
          icon2.gif   Re: Email Notification (Not) Initiated by elog Client Utility, posted by Andreas Luedeke on Wed Jul 19 10:14:44 2017 
             icon2.gif   Re: Email Notification (Not) Initiated by elog Client Utility, posted by Phil Rubin on Wed Jul 19 10:25:08 2017 
                icon2.gif   Re: Email Notification (Not) Initiated by elog Client Utility, posted by Andreas Luedeke on Wed Jul 19 13:37:33 2017 
Message ID: 68643     Entry time: Wed Jul 19 08:59:52 2017     In reply to: 68641     Reply to this: 68644
Icon: Reply  Author: Phil Rubin  Author Email: rubinp@cern.ch 
Category: Question  OS: Linux  ELOG Version: 2.9.2 
Subject: Re: Email Notification (Not) Initiated by elog Client Utility 

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"

 

 

ELOG V3.1.5-3fb85fa6