Re: Email Notification (Not) Initiated by elog Client Utility, posted by Andreas Luedeke on Wed Jul 19 10:14:44 2017
|
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"
|
|
|
|
|
Re: Email Notification (Not) Initiated by elog Client Utility, posted by Andreas Luedeke on Wed Jul 19 13:37:33 2017
|
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"
|
|
|
|
|
|
|
Re: Password Protect Delete, posted by Andreas Luedeke on Fri Jul 21 08:54:03 2017
|
You can allow guests to create entries, but only registered users (Admins) to delete (or edit) entries:
Menu commands = List, New, Edit, Reply, Delete, Find, Config, Logout, Help
Guest menu commands = List, New, Reply, Find, Login, Help
See https://midas.psi.ch/elog/config.html#general for details.
| Michael Cianci wrote: |
|
We don't use a password file but would like to password protect (Admin only) the DELETE function in the MENU Thank You
|
|
|
Re: Conditional attribute activation, posted by Andreas Luedeke on Mon Jul 24 14:33:51 2017
|
Yes, this is possible by using "Conditional Attributes". Have a look at the ELOG syntax help: https://midas.psi.ch/elog/config.html#conditional
To hide attributes on edit, you can use "Show Attributes Edit = ..." for the conditions; and you only list the comment reason for the case where the value of the other attribute has the value "reserved".
If you don't get it to work, then just post your logbook config with some comments on what you want to achieve.
Cheers, Andreas
| Devrim Esenturk wrote: |
|
I have a stock database running latest elog version on windows. I am reserving some products which not been sent to customer mistakenly and using value "reserved" for it. But I need another attribute for comment reason of reserving but this attribute must be activated when reserved value selected. Is this possible? I didn't see any option for this at admin guide.
Thank you
|
|
|
Re: Sharing logbooks among "Top Groups", posted by Andreas Luedeke on Sun Aug 20 14:55:18 2017
|
I don't know if that works. Why don't you just try?
| Satyajit Jena wrote: |
|
Hi,
I am currently trying to configuring elog top groups, which are supposed to separate from each other. However, I would like to have a common logbook that should be visible in each group. Is there a way to share logbooks among Top Groups for example
Top Group Electronics = Elec1, Elec_EEE, Ele2
Top Group Processing = P_AA1, PPP2, Elec_EEE
Top Group Monitoring = Mon1, Mon2, Mon3, Mon4
Top Group Data = Data1, PPP2, Data2
I would like logbook to be viewed:
- Electronics:
- Processing:
- Monitoring:
- Data:
- Data1
- PPP2
- Data2
- Mon3
- Mon4
Could you please suggest me if it is possible to set in this way (Color codes t show the common sharing).
Many thanks and regards,
satyajit
|
|
|
Re: Sharing logbooks among "Top Groups", posted by Andreas Luedeke on Mon Aug 21 08:51:09 2017
|
Hi Satyajit,
I think you've just answered your own question. There is no magic switch - as far as I know - that would change that behaviour.
Probably there are ways to achieve your desired behaviour (using mirror servers and synchronising the logbooks) but that would require a large effort and would make your installation a lot more complicated.
With kind regards, Andreas
| Satyajit Jena wrote: |
|
Hi,
I tried without success. Logbook is not sharing, it is displaying only under one "Top Group" whereever it appears first.
With regards,
satyajit
| Andreas Luedeke wrote: |
|
I don't know if that works. Why don't you just try?
| Satyajit Jena wrote: |
|
Hi,
I am currently trying to configuring elog top groups, which are supposed to separate from each other. However, I would like to have a common logbook that should be visible in each group. Is there a way to share logbooks among Top Groups for example
Top Group Electronics = Elec1, Elec_EEE, Ele2
Top Group Processing = P_AA1, PPP2, Elec_EEE
Top Group Monitoring = Mon1, Mon2, Mon3, Mon4
Top Group Data = Data1, PPP2, Data2
I would like logbook to be viewed:
- Electronics:
- Processing:
- Monitoring:
- Data:
- Data1
- PPP2
- Data2
- Mon3
- Mon4
Could you please suggest me if it is possible to set in this way (Color codes t show the common sharing).
Many thanks and regards,
satyajit
|
|
|
|
Problems with german_UTF8 language, posted by Andreas Luedeke on Mon Aug 21 11:22:09 2017 
|
Hi Stefan,
since recently (a few weeks) ELOG confuses the language translations.
Individual language strings are translated into garbage; most other strings are fine.
Currently I see the string "please select" translated into "ressed" (see attached picture), instead of what's written correctly in the language file "bitte auswählen".
But with every restart the corrupted strings vary: other strings are affected and other garbage strings are shown - some of them unreadable binary code (see Attachment 2).
I have the same version running in English: I see no problems there.
Kind regards
Andreas |
Bug with Drafts and Language German, posted by Andreas Luedeke on Mon Aug 21 11:45:06 2017
|
Hi Stefan,
when one creates a new entry, and a draft entry exists for the logbook, then a menu appears (see attachment).
If one select "Neuen Eintrag anlegen" then it should ignore the draft and create a new entry.
This feat is done by adding a "&ignore=1" to the "new" command: "<URL>/?cmd=New&ignore=1".
The problem is, that it should not be "cmd=New&..." but "cmd=Neu", since the commands are part of the translation.
Due to this, no new entry can be created as long as a draft exists; at least not in any language other than english.
This problem apparently existed since the beginning of drafts, but it only created problems at our site recently.
Kind Regards
Andreas
PS: Here's a patch that works:
diff elogd.c elogd.c-orig
9575,9576c9575,9576
< rsprintf("<input type=button value=\"%s\" onClick=\"window.location.href='?cmd=%s&ignore=1';\">\n", loc("Create new entry"),
< loc("New"));
---
> rsprintf("<input type=button value=\"%s\" onClick=\"window.location.href='%s';\">\n", loc("Create new entry"),
> "?cmd=New&ignore=1"); |
|