Installation: Failed Dependencies, posted by Phil Rubin on Fri Mar 11 17:29:47 2016
|
Is there anything I can do about this?
kernel: 2.6.32-279.14.1.el6.x86_64
ldd (GNU libc) 2.12 |
Re: Installation: Failed Dependencies, posted by Phil Rubin on Fri Mar 11 18:59:30 2016
|
I attempted instead to build from the tar ball, and, except for a "fatal" git error, make built elogd, elog, and elconv. I put
the first in /usr/local/sbin, and the latter two in /usr/local/bin, and then restarted elogd, but this didn't work:
Service Temporarily Unavailable |
|
Re: Installation: Failed Dependencies, posted by Phil Rubin on Fri Mar 11 19:24:11 2016
|
OK. I found the source of the logbook problem in an exchange from May 2015, so no need to answer this one.
But I would like to be able to upgrade to 3.x from 2.9, so any help with this will be much appreciated.
Phil |
|
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 |
|
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" |
|
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 |
|
Naming a Notebook KTAG Wipes Out Formatting. Why?, posted by Phil Rubin on Sat May 22 20:44:33 2021
|
An experiment's ELOG installation, using the default theme, names logbooks after its subsystem's acronyms. One subsystem is referred to
as KTAG, but when this name (or its lowercase version) is used for a logbook name, the logbook appears unformatted. Changing the name, even to K-TAG,
works fine. Nothing close to KTAG appears in elog.css. Does anyone know why this happens and whether it is possible or worth the while to get |
|
Re: Spurious characters in the searched string, posted by Phil Rubin on Mon Jan 3 19:11:08 2022
|
Hi,
Ten years later...this problem shows up in my installation behind Apache, affecting only drop-down menu searches. Test installations with
elog serving itself do not show the problem, so I presume it has something to do with Apache configuration, re-routing, etc. Unfortunately, this |