Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 343 of 808  Not logged in ELOG logo
    icon2.gif   Re: Full anonymous access, posted by K on Thu Apr 20 13:35:53 2017 
Does not work.

Clean install (debian 8 x64, with aptitude), only thing i've changed in the config is "URL"-parameter (global section) and
redirection with Apache. No luck. Edit or delete gives an error "Error: Command "Delete" not allowed", "New"
    icon2.gif   Re: Full anonymous access, posted by Stefan Ritt on Thu Apr 20 13:45:42 2017 
Version 2.9.2 is hopelessly outdated. Please upgrade to the current version on bitbucket. You also might have to delete any cookie in the browser sent
to the elog server.




K
    icon2.gif   Re: Full anonymous access, posted by K on Thu Apr 20 13:48:43 2017 
OK, i will try that. Thanks.




Stefan
Ritt wrote:



Version 2.9.2 is hopelessly outdated. Please upgrade to the current
icon5.gif   Email Notification (Not) Initiated by elog Client Utility, posted by Phil Rubin on Fri Jul 14 19:26:06 2017 
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
    icon2.gif   Re: Email Notification (Not) Initiated by elog Client Utility, posted by Andreas Luedeke on Wed Jul 19 08:50:16 2017 
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
    icon2.gif   Re: Email Notification (Not) Initiated by elog Client Utility, posted by Phil Rubin on Wed Jul 19 08:59:52 2017 
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"
    icon2.gif   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
    icon2.gif   Re: Email Notification (Not) Initiated by elog Client Utility, posted by Phil Rubin on Wed Jul 19 10:25:08 2017 
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
ELOG V3.1.5-3fb85fa6