| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69769
|
Mon Mar 25 10:55:43 2024 |
 | Laurent Jean-Rigaud | lollspam@free.fr | Question | Linux | 3.1.5-1 | Re: Installation with amp on Rocky Linux | Hi,
The ELOG website provides new link to RPM packages :
Linux binaries are distributed as RPMs.
EL8/EL9 RPM are also available.
| scott wrote: |
|
Is there an RPM available for Rocky 8 or Rocky 9?
And checking over https://elog.psi.ch/elog/download/RPMS/ , only el7 is found. Is that the right place to look for EL8 or EL9 based RPM?
Thanks,
Scott
| Laurent Jean-Rigaud wrote: |
|
Normally it should work. Requirements are set in SPEC file.
$ rpm -qpi --requires elog-3.1.5-20240226.el7.x86_64.rpm
/bin/sh
/bin/sh
/bin/sh
config(elog) = 3.1.5-20240226.el7
krb5-libs
libc.so.6()(64bit)
libc.so.6(GLIBC_2.14)(64bit)
libc.so.6(GLIBC_2.15)(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libc.so.6(GLIBC_2.3)(64bit)
libc.so.6(GLIBC_2.3.4)(64bit)
libc.so.6(GLIBC_2.4)(64bit)
libc.so.6(GLIBC_2.8)(64bit)
libgcc_s.so.1()(64bit)
libgcc_s.so.1(GCC_3.0)(64bit)
libkrb5.so.3()(64bit)
libkrb5.so.3(krb5_3_MIT)(64bit)
liblber-2.4.so.2()(64bit)
libldap-2.4.so.2()(64bit)
libm.so.6()(64bit)
libpam.so.0()(64bit)
libpam.so.0(LIBPAM_1.0)(64bit)
libssl.so.10()(64bit)
libssl.so.10(libssl.so.10)(64bit)
libstdc++.so.6()(64bit)
libstdc++.so.6(CXXABI_1.3)(64bit)
libstdc++.so.6(GLIBCXX_3.4)(64bit)
openldap >= 2.4.1
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rtld(GNU_HASH)
rpmlib(PayloadIsXz) <= 5.2-1
The EL7 binary needs the following RPM :
$ ldd /usr/local/sbin/elogd | awk '{print $1}' | while read r ; do rpm -qf /lib64/$r ; done | sort -u
erreur�: fichier /lib64/linux-vdso.so.1�: Aucun fichier ou dossier de ce type
erreur�: fichier /lib64/lib64/ld-linux-x86-64.so.2�: Aucun fichier ou dossier de ce type
audit-libs-2.8.5-4.el7.x86_64
cyrus-sasl-lib-2.1.26-24.el7_9.x86_64
glibc-2.17-326.el7_9.x86_64
keyutils-libs-1.5.8-3.el7.x86_64
krb5-libs-1.15.1-55.el7_9.x86_64
libcap-ng-0.7.5-4.el7.x86_64
libcom_err-1.42.9-19.el7.x86_64
libgcc-4.8.5-44.el7.x86_64
libselinux-2.5-15.el7.x86_64
libstdc++-4.8.5-44.el7.x86_64
nspr-4.35.0-1.el7_9.x86_64
nss-3.90.0-2.el7_9.x86_64
nss-softokn-freebl-3.90.0-6.el7_9.x86_64
nss-util-3.90.0-1.el7_9.x86_64
openldap-2.4.44-25.el7_9.x86_64
openssl-libs-1.0.2k-26.el7_9.x86_64
pam-1.1.8-23.el7.x86_64
pcre-8.32-17.el7.x86_64
zlib-1.2.7-21.el7_9.x86_64
Almost all of them are installed by ELOG RPM or are already installed by default Redhat profiles.
Nina, do you use right RPM version (el7/8/9) according to Rockylinux one ? El7 rpm can not be installed on RL9...
Bye
| Stefan Ritt wrote: |
|
Is there a way to install all dependencies automatically? Like if I install a package like "emacs" I get a list of dependencies with are automatically installed:
Dependencies Resolved
====================================================================================================================================
Package Arch Version Repository Size
====================================================================================================================================
Updating:
emacs x86_64 1:24.3-23.el7_9.1 rhel7 2.9 M
Updating for dependencies:
emacs-common x86_64 1:24.3-23.el7_9.1 rhel7 20 M
Transaction Summary
====================================================================================================================================
Upgrade 1 Package (+1 Dependent package)
Total download size: 23 M
Is this ok [y/d/N]:
| Laurent Jean-Rigaud wrote: |
|
Hi Nina,
The RPM is built with Kerberos (libber*), LDAP (libldap*) and SSL (libssl*) options. These libs are missing on your system, and rpm command does not take care of dependencies.
Try to install with yum : yum install elog-latest.el7.x86_64.rpm
Normally the missing rpm files should be dlded from RL repo if your host can access to them...
.
Laurent
| Nina Bondarenko wrote: |
|
Hello all,
I am installing elog on an Rocky Linux instance. Have dependensy problem.
rpm -Uvh elog-latest.el7.x86_64.rpm
error: Failed dependencies:
liblber-2.4.so.2()(64bit) is needed by elog-3.1.5-1.el7.x86_64
libldap-2.4.so.2()(64bit) is needed by elog-3.1.5-1.el7.x86_64
libssl.so.10()(64bit) is needed by elog-3.1.5-1.el7.x86_64
libssl.so.10(libssl.so.10)(64bit) is needed by elog-3.1.5-1.el7.x86_64
Any clues from developers to resolve it and keep the software working. Thank you in advance!
Bests, Nina
|
|
|
|
|
|
|
69770
|
Mon Mar 25 16:19:02 2024 |
| scott | Thank shiva.ps@stfc.ac.uk | Question | Linux | 3.1.5-1 | Re: Installation with amp on Rocky Linux | Hi,
Thanks for the links to EL8/EL9.
Does this package support LDAP and SSL as well?
| Laurent Jean-Rigaud wrote: |
|
Hi,
The ELOG website provides new link to RPM packages :
Linux binaries are distributed as RPMs.
EL8/EL9 RPM are also available.
| scott wrote: |
|
Is there an RPM available for Rocky 8 or Rocky 9?
And checking over https://elog.psi.ch/elog/download/RPMS/ , only el7 is found. Is that the right place to look for EL8 or EL9 based RPM?
Thanks,
Scott
| Laurent Jean-Rigaud wrote: |
|
Normally it should work. Requirements are set in SPEC file.
$ rpm -qpi --requires elog-3.1.5-20240226.el7.x86_64.rpm
/bin/sh
/bin/sh
/bin/sh
config(elog) = 3.1.5-20240226.el7
krb5-libs
libc.so.6()(64bit)
libc.so.6(GLIBC_2.14)(64bit)
libc.so.6(GLIBC_2.15)(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libc.so.6(GLIBC_2.3)(64bit)
libc.so.6(GLIBC_2.3.4)(64bit)
libc.so.6(GLIBC_2.4)(64bit)
libc.so.6(GLIBC_2.8)(64bit)
libgcc_s.so.1()(64bit)
libgcc_s.so.1(GCC_3.0)(64bit)
libkrb5.so.3()(64bit)
libkrb5.so.3(krb5_3_MIT)(64bit)
liblber-2.4.so.2()(64bit)
libldap-2.4.so.2()(64bit)
libm.so.6()(64bit)
libpam.so.0()(64bit)
libpam.so.0(LIBPAM_1.0)(64bit)
libssl.so.10()(64bit)
libssl.so.10(libssl.so.10)(64bit)
libstdc++.so.6()(64bit)
libstdc++.so.6(CXXABI_1.3)(64bit)
libstdc++.so.6(GLIBCXX_3.4)(64bit)
openldap >= 2.4.1
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rtld(GNU_HASH)
rpmlib(PayloadIsXz) <= 5.2-1
The EL7 binary needs the following RPM :
$ ldd /usr/local/sbin/elogd | awk '{print $1}' | while read r ; do rpm -qf /lib64/$r ; done | sort -u
erreur�: fichier /lib64/linux-vdso.so.1�: Aucun fichier ou dossier de ce type
erreur�: fichier /lib64/lib64/ld-linux-x86-64.so.2�: Aucun fichier ou dossier de ce type
audit-libs-2.8.5-4.el7.x86_64
cyrus-sasl-lib-2.1.26-24.el7_9.x86_64
glibc-2.17-326.el7_9.x86_64
keyutils-libs-1.5.8-3.el7.x86_64
krb5-libs-1.15.1-55.el7_9.x86_64
libcap-ng-0.7.5-4.el7.x86_64
libcom_err-1.42.9-19.el7.x86_64
libgcc-4.8.5-44.el7.x86_64
libselinux-2.5-15.el7.x86_64
libstdc++-4.8.5-44.el7.x86_64
nspr-4.35.0-1.el7_9.x86_64
nss-3.90.0-2.el7_9.x86_64
nss-softokn-freebl-3.90.0-6.el7_9.x86_64
nss-util-3.90.0-1.el7_9.x86_64
openldap-2.4.44-25.el7_9.x86_64
openssl-libs-1.0.2k-26.el7_9.x86_64
pam-1.1.8-23.el7.x86_64
pcre-8.32-17.el7.x86_64
zlib-1.2.7-21.el7_9.x86_64
Almost all of them are installed by ELOG RPM or are already installed by default Redhat profiles.
Nina, do you use right RPM version (el7/8/9) according to Rockylinux one ? El7 rpm can not be installed on RL9...
Bye
| Stefan Ritt wrote: |
|
Is there a way to install all dependencies automatically? Like if I install a package like "emacs" I get a list of dependencies with are automatically installed:
Dependencies Resolved
====================================================================================================================================
Package Arch Version Repository Size
====================================================================================================================================
Updating:
emacs x86_64 1:24.3-23.el7_9.1 rhel7 2.9 M
Updating for dependencies:
emacs-common x86_64 1:24.3-23.el7_9.1 rhel7 20 M
Transaction Summary
====================================================================================================================================
Upgrade 1 Package (+1 Dependent package)
Total download size: 23 M
Is this ok [y/d/N]:
| Laurent Jean-Rigaud wrote: |
|
Hi Nina,
The RPM is built with Kerberos (libber*), LDAP (libldap*) and SSL (libssl*) options. These libs are missing on your system, and rpm command does not take care of dependencies.
Try to install with yum : yum install elog-latest.el7.x86_64.rpm
Normally the missing rpm files should be dlded from RL repo if your host can access to them...
.
Laurent
| Nina Bondarenko wrote: |
|
Hello all,
I am installing elog on an Rocky Linux instance. Have dependensy problem.
rpm -Uvh elog-latest.el7.x86_64.rpm
error: Failed dependencies:
liblber-2.4.so.2()(64bit) is needed by elog-3.1.5-1.el7.x86_64
libldap-2.4.so.2()(64bit) is needed by elog-3.1.5-1.el7.x86_64
libssl.so.10()(64bit) is needed by elog-3.1.5-1.el7.x86_64
libssl.so.10(libssl.so.10)(64bit) is needed by elog-3.1.5-1.el7.x86_64
Any clues from developers to resolve it and keep the software working. Thank you in advance!
Bests, Nina
|
|
|
|
|
|
|
|
69771
|
Mon Mar 25 16:44:03 2024 |
| Laurent Jean-Rigaud | lollspam@free.fr | Question | Linux | 3.1.5-1 | Re: Installation with amp on Rocky Linux | Yes, same build options are used.
But i can not'confirm that they are working as well as on EL7. The tests done by build script on CI/CD are quite simple and limited to rpm installation, service start and access from cmdline to elog server.
So thanks to report your personal experience with EL8/9 builds... 🤓
.
Laurent
| scott wrote: |
|
Hi,
Thanks for the links to EL8/EL9.
Does this package support LDAP and SSL as well?
| Laurent Jean-Rigaud wrote: |
|
Hi,
The ELOG website provides new link to RPM packages :
Linux binaries are distributed as RPMs.
EL8/EL9 RPM are also available.
| scott wrote: |
|
Is there an RPM available for Rocky 8 or Rocky 9?
And checking over https://elog.psi.ch/elog/download/RPMS/ , only el7 is found. Is that the right place to look for EL8 or EL9 based RPM?
Thanks,
Scott
| Laurent Jean-Rigaud wrote: |
|
Normally it should work. Requirements are set in SPEC file.
$ rpm -qpi --requires elog-3.1.5-20240226.el7.x86_64.rpm
/bin/sh
/bin/sh
/bin/sh
config(elog) = 3.1.5-20240226.el7
krb5-libs
libc.so.6()(64bit)
libc.so.6(GLIBC_2.14)(64bit)
libc.so.6(GLIBC_2.15)(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libc.so.6(GLIBC_2.3)(64bit)
libc.so.6(GLIBC_2.3.4)(64bit)
libc.so.6(GLIBC_2.4)(64bit)
libc.so.6(GLIBC_2.8)(64bit)
libgcc_s.so.1()(64bit)
libgcc_s.so.1(GCC_3.0)(64bit)
libkrb5.so.3()(64bit)
libkrb5.so.3(krb5_3_MIT)(64bit)
liblber-2.4.so.2()(64bit)
libldap-2.4.so.2()(64bit)
libm.so.6()(64bit)
libpam.so.0()(64bit)
libpam.so.0(LIBPAM_1.0)(64bit)
libssl.so.10()(64bit)
libssl.so.10(libssl.so.10)(64bit)
libstdc++.so.6()(64bit)
libstdc++.so.6(CXXABI_1.3)(64bit)
libstdc++.so.6(GLIBCXX_3.4)(64bit)
openldap >= 2.4.1
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rtld(GNU_HASH)
rpmlib(PayloadIsXz) <= 5.2-1
The EL7 binary needs the following RPM :
$ ldd /usr/local/sbin/elogd | awk '{print $1}' | while read r ; do rpm -qf /lib64/$r ; done | sort -u
erreur�: fichier /lib64/linux-vdso.so.1�: Aucun fichier ou dossier de ce type
erreur�: fichier /lib64/lib64/ld-linux-x86-64.so.2�: Aucun fichier ou dossier de ce type
audit-libs-2.8.5-4.el7.x86_64
cyrus-sasl-lib-2.1.26-24.el7_9.x86_64
glibc-2.17-326.el7_9.x86_64
keyutils-libs-1.5.8-3.el7.x86_64
krb5-libs-1.15.1-55.el7_9.x86_64
libcap-ng-0.7.5-4.el7.x86_64
libcom_err-1.42.9-19.el7.x86_64
libgcc-4.8.5-44.el7.x86_64
libselinux-2.5-15.el7.x86_64
libstdc++-4.8.5-44.el7.x86_64
nspr-4.35.0-1.el7_9.x86_64
nss-3.90.0-2.el7_9.x86_64
nss-softokn-freebl-3.90.0-6.el7_9.x86_64
nss-util-3.90.0-1.el7_9.x86_64
openldap-2.4.44-25.el7_9.x86_64
openssl-libs-1.0.2k-26.el7_9.x86_64
pam-1.1.8-23.el7.x86_64
pcre-8.32-17.el7.x86_64
zlib-1.2.7-21.el7_9.x86_64
Almost all of them are installed by ELOG RPM or are already installed by default Redhat profiles.
Nina, do you use right RPM version (el7/8/9) according to Rockylinux one ? El7 rpm can not be installed on RL9...
Bye
| Stefan Ritt wrote: |
|
Is there a way to install all dependencies automatically? Like if I install a package like "emacs" I get a list of dependencies with are automatically installed:
Dependencies Resolved
====================================================================================================================================
Package Arch Version Repository Size
====================================================================================================================================
Updating:
emacs x86_64 1:24.3-23.el7_9.1 rhel7 2.9 M
Updating for dependencies:
emacs-common x86_64 1:24.3-23.el7_9.1 rhel7 20 M
Transaction Summary
====================================================================================================================================
Upgrade 1 Package (+1 Dependent package)
Total download size: 23 M
Is this ok [y/d/N]:
| Laurent Jean-Rigaud wrote: |
|
Hi Nina,
The RPM is built with Kerberos (libber*), LDAP (libldap*) and SSL (libssl*) options. These libs are missing on your system, and rpm command does not take care of dependencies.
Try to install with yum : yum install elog-latest.el7.x86_64.rpm
Normally the missing rpm files should be dlded from RL repo if your host can access to them...
.
Laurent
| Nina Bondarenko wrote: |
|
Hello all,
I am installing elog on an Rocky Linux instance. Have dependensy problem.
rpm -Uvh elog-latest.el7.x86_64.rpm
error: Failed dependencies:
liblber-2.4.so.2()(64bit) is needed by elog-3.1.5-1.el7.x86_64
libldap-2.4.so.2()(64bit) is needed by elog-3.1.5-1.el7.x86_64
libssl.so.10()(64bit) is needed by elog-3.1.5-1.el7.x86_64
libssl.so.10(libssl.so.10)(64bit) is needed by elog-3.1.5-1.el7.x86_64
Any clues from developers to resolve it and keep the software working. Thank you in advance!
Bests, Nina
|
|
|
|
|
|
|
|
|
66020
|
Wed Oct 29 05:53:39 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.5 | Re: Installation problems | > 1) "make" fails if libssl-dev package is not installed. Documentation does not mention SSL library requirements.
I added a note to the documentation, thank you.
> 2) /etc/init.d/elogd: line 10: /etc/rc.d/init.d/functions: No such file or directory (I fixed this by commenting
> out that line).
>
> 3) Starting elogd: /etc/init.d/elogd: line 34: echo_success: command not found (Fixed by search/replace "echo_"
> to "echo ").
The elogd (or elogd.init in the distribution) is written for RedHat based systems where echo_success gives the
typical output with a green [OK] at the end of the line. For Debian, there is (was) in principle a Debian package
which has it's own startup script. Since the package maintainer is not active any more (I guess), the Debian
updates are heavily old. Once elog gets managed inside Debian again, that should get better again, but until then
one has to follow 2) and 3) from above. If I would remove it, the Scientific Linux users would complain. |
|
66033
|
Wed Nov 5 10:32:07 2008 |
| George B. | i93.borg@gmail.com | Bug report | Linux | 2.7.5 | Re: Installation problems | > The elogd (or elogd.init in the distribution) is written for RedHat based systems where echo_success gives the
> typical output with a green [OK] at the end of the line. For Debian, there is (was) in principle a Debian package
> which has it's own startup script. Since the package maintainer is not active any more (I guess), the Debian
> updates are heavily old. Once elog gets managed inside Debian again, that should get better again, but until then
> one has to follow 2) and 3) from above. If I would remove it, the Scientific Linux users would complain.
That makes sense. Might be worth adding a short Debian section to the installation instructions page?
FYI, Elog is no longer in Debian as of 2008-05-12.
Thanks,
George. |
|
66034
|
Wed Nov 5 11:52:12 2008 |
 | T. Ribbrock | emgaron+elog@ribbrock.org | Info | Linux | 2.7.5 | Re: Installation problems | > > 2) /etc/init.d/elogd: line 10: /etc/rc.d/init.d/functions: No such file or directory (I fixed this by commenting
> > out that line).
> >
> > 3) Starting elogd: /etc/init.d/elogd: line 34: echo_success: command not found (Fixed by search/replace "echo_"
> > to "echo ").
>
> The elogd (or elogd.init in the distribution) is written for RedHat based systems where echo_success gives the
> typical output with a green [OK] at the end of the line. For Debian, there is (was) in principle a Debian package
> which has it's own startup script. Since the package maintainer is not active any more (I guess), the Debian
> updates are heavily old. Once elog gets managed inside Debian again, that should get better again, but until then
> one has to follow 2) and 3) from above. If I would remove it, the Scientific Linux users would complain.
I'm actually using elog on Debian and have been rolling my own ".deb" for a while now (starting with the old Debian
one and working my way up till 2.7.5). Maybe you could add the Debian /etc/init.d/elog script to the "contrib"
directory, with a suitable note in the README or something like that? That script has not changed in a long time and
is still functional - and doing so would make it easier for people who would like to install elog on a Debian (or
Debian-based, e.g. Ubuntu) system. I'll attach the script.
Regards,
Thomas |
| Attachment 1: elog
|
#!/bin/sh
# Init script for ELOG.
# Copyright © 2003, 2005 Recai Oktaş <roktas@omu.edu.tr>
#
# Licensed under the GNU General Public License, version 2.
# See the file `http://www.gnu.org/copyleft/gpl.txt'.
PATH=/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/elogd
NAME=elogd
DESC="ELOG daemon"
test -f $DAEMON || exit 0
set -e
# Admin should be able to lock some options.
if [ -f /etc/default/elog ]; then
. /etc/default/elog
fi
# To be in the safe side, the followings should be always defined.
PIDFILE=${PIDFILE:-/var/run/$NAME.pid}
CONFFILE=${CONFFILE:-/etc/elog.conf}
# Add the options to argument list only if defined previously. Since
# some options may also be present in the conffile, we couldn't preset
# those options which would otherwise overwrite the settings in the
# conffile. Also note that, all have reasonable compiled-in defaults.
ARGS="${PIDFILE+"-f $PIDFILE"} \
${CONFFILE+"-c $CONFFILE"} \
${LOGBOOKDIR+"-d $LOGBOOKDIR"} \
${RESOURCEDIR+"-s $RESOURCEDIR"} \
${PORT+"-p $PORT"} \
${HOST+"-n $HOST"} \
${VERBOSE+"-v"}"
# Always run as a daemon.
ARGS=`echo $ARGS -D`
case "$1" in
start)
echo -n "Starting $DESC: "
start-stop-daemon --start --quiet --pidfile $PIDFILE \
--exec $DAEMON -- $ARGS 2>&1
sleep 1
if [ -f "$PIDFILE" ] && ps h `cat "$PIDFILE"` >/dev/null; then
echo "$NAME."
else
echo "$NAME failed to start; check syslog for diagnostics."
exit 1
fi
;;
stop)
echo -n "Stopping $DESC: $NAME"
start-stop-daemon --oknodo --stop --quiet --pidfile $PIDFILE \
--exec $DAEMON -- $ARGS 2>&1
echo "."
;;
reload)
# Do nothing since ELOG daemon responds to
# the changes in conffile directly.
;;
restart|force-reload)
$0 stop
sleep 1
$0 start
if [ "$?" != "0" ]; then
exit 1
fi
;;
*)
N=/etc/init.d/$NAME
echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2
exit 1
;;
esac
exit 0
# vim:ai:sts=8:sw=8:
|
|
66055
|
Mon Nov 17 11:42:46 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | 2.7.5 | Re: Installation problems | > I'm actually using elog on Debian and have been rolling my own ".deb" for a while now (starting with the old
Debian
> Maybe you could add the Debian /etc/init.d/elog script to the "contrib"
> directory, with a suitable note in the README or something like that? That script has not changed in a long
time and
> is still functional - and doing so would make it easier for people who would like to install elog on a Debian
(or
> Debian-based, e.g. Ubuntu) system. I'll attach the script.
The problem is not putting this into the "conrib" area, but supporting it. Since I don't have a Debian system,
may I suggest that you put it yourself into the elog:Contributions/ logbook. If people then get problems in the
future, they can contact you directly ;-) |
|
66088
|
Thu Nov 27 11:47:34 2008 |
| T. Ribbrock | emgaron+elog@ribbrock.org | Info | Linux | 2.7.5 | Re: Installation problems | > The problem is not putting this into the "conrib" area, but supporting it. Since I don't have a Debian system,
> may I suggest that you put it yourself into the elog:Contributions/ logbook. If people then get problems in the
> future, they can contact you directly ;-)
I finally got round to do so. I've also included the changes suggested by Yoshio Imai (reload functionality).
Hopefully, it is useful for someone... |
|