ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68286
|
Tue Mar 15 09:26:40 2016 |
 | Neal Grafton | neal.grafton@stfc.ac.uk | Question | Windows | latest | URL |
Hi
Can I asign a URL to a Radio Button to bring up another program? |
|
68285
|
Tue Mar 15 03:48:58 2016 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.1.0 | Re: Pre-populate filed based on selection |
Use "conditional attributes" as described in the documentation: https://midas.psi.ch/elog/config.html#conditional
| Jimmy Bria wrote: |
|
Hi,
Is it possible to pre-populate a field based on the selection of another field. I like to have the Equipment Description field populated when the use makes a selection on the EQ# field.
Thank you,
Jimmy
|
|
|
68284
|
Mon Mar 14 16:00:02 2016 |
| Jimmy Bria | jimmy.bria@gmail.com | Question | Windows | 3.1.0 | Pre-populate filed based on selection |
Hi,
Is it possible to pre-populate a field based on the selection of another field. I like to have the Equipment Description field populated when the use makes a selection on the EQ# field.
Thank you,
Jimmy
|
| Attachment 1: elog_prepopulate.JPG
|
|
| Attachment 2: elog_prepopulate_1.JPG
|
|
|
68283
|
Fri Mar 11 19:24:11 2016 |
| Phil Rubin | rubinp@cern.ch | Question | Linux | 3.1.1 | Re: Installation: Failed Dependencies |
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
| Phil Rubin wrote: |
|
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
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
So, I backed these out and restored the previous executables, and access to the elog was restored, and the elogd.cfg accessed is the original one, but all logbooks are empty and requiring authentication. The logbook directories still contain all the old entries, so I'm not sure what has happened.
Thanks for your advice.
Phil
| Phil Rubin wrote: |
|
Is there anything I can do about this?
kernel: 2.6.32-279.14.1.el6.x86_64
ldd (GNU libc) 2.12
/lib64/libc.so.6
/usr/lib64/libssl.so.10
rpm -i elog-latest.i386.rpm
error: Failed dependencies:
libc.so.6 is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.0) is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.1) is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.1.3) is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.3) is needed by elog-3.1.1-1.i386
libssl.so.6 is needed by elog-3.1.1-1.i386
|
|
|
|
68282
|
Fri Mar 11 18:59:30 2016 |
| Phil Rubin | rubinp@cern.ch | Question | Linux | 3.1.1 | Re: Installation: Failed Dependencies |
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
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
So, I backed these out and restored the previous executables, and access to the elog was restored, and the elogd.cfg accessed is the original one, but all logbooks are empty and requiring authentication. The logbook directories still contain all the old entries, so I'm not sure what has happened.
Thanks for your advice.
Phil
| Phil Rubin wrote: |
|
Is there anything I can do about this?
kernel: 2.6.32-279.14.1.el6.x86_64
ldd (GNU libc) 2.12
/lib64/libc.so.6
/usr/lib64/libssl.so.10
rpm -i elog-latest.i386.rpm
error: Failed dependencies:
libc.so.6 is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.0) is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.1) is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.1.3) is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.3) is needed by elog-3.1.1-1.i386
libssl.so.6 is needed by elog-3.1.1-1.i386
|
|
|
68281
|
Fri Mar 11 17:29:47 2016 |
| Phil Rubin | rubinp@cern.ch | Question | Linux | 3.1.1 | Installation: Failed Dependencies |
Is there anything I can do about this?
kernel: 2.6.32-279.14.1.el6.x86_64
ldd (GNU libc) 2.12
/lib64/libc.so.6
/usr/lib64/libssl.so.10
rpm -i elog-latest.i386.rpm
error: Failed dependencies:
libc.so.6 is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.0) is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.1) is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.1.3) is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.3) is needed by elog-3.1.1-1.i386
libssl.so.6 is needed by elog-3.1.1-1.i386 |
|
68280
|
Fri Mar 11 17:19:02 2016 |
| Phil Rubin | rubinp@cern.ch | Question | Linux | 3.1.1 | Installation: Failed Dependencies |
Is there anything I can do about this?
kernel: 2.6.32-279.14.1.el6.x86_64
ldd (GNU libc) 2.12
/lib64/libc.so.6
/usr/lib64/libssl.so.10
rpm -i elog-latest.i386.rpm
error: Failed dependencies:
libc.so.6 is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.0) is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.1) is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.1.3) is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.3) is needed by elog-3.1.1-1.i386
libssl.so.6 is needed by elog-3.1.1-1.i386 |
|
68279
|
Thu Mar 10 00:26:03 2016 |
| Dave | david.levine@lmco.com | Question | Windows | 2.71 | elogd -m Error sending local entry: Error transmitting message |
I'm running ELOG on a seperate Windows Servers.
When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message"
If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG.
Can anyone tell me why I get this error?
==============================
Here is the command & output:
c:\Program Files (x86)\ELOG>elogd -m
Retrieving entries from "http://166.22.64.201/Equipment Log"...
All entries identical
Retrieving entries from "http://166.22.64.201/System Log"...
Error sending local entry: Error transmitting message |