ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69188
|
Sun Aug 2 09:06:46 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | ELOG V3.1.4-966 | Re: Missing log files when rsync to replacement server. |
If nothing is specified elogd looks for logbooks in the current directory where it got started under ./logbooks/
No idea what happened to your 2020 logbook.
VUIIS SysAdmin wrote: |
Thank-you. That is good information to have.
What is the default if you you do not specify anything in elogd.cfg? I assume it is /usr/local/elog otherwise it would not see the existing logbooks.
With a default Linux RPM install, where else would the logbooks be? Still looking for a 2020 directory on either server.
Bruce
Stefan Ritt wrote: |
You can put your files where ever you want, just tell elogd where to find the elogd.cfg file via the "-c" flag. Then tell elogd where to find files in the elogd.cfg file via the "Logbook dir" and "Resource dir" directives.
Stefan
VUIIS SysAdmin wrote: |
On the new server in the logbook that should have several 2020 entries it stops on the last entry of 2019.
On the old server after stopping elogd i get:
/usr/sbin/elogd -v 3
Cannot open "elogd.cfg": No such file or directory
Are the files supposed to be in /usr/local/elog or /usr/share/elog? I have both on the old server. I only synced /usr/local/elog to the new server. In any case the Logbook with 2020 entries does not show a 2020 directory.
My backup system also does not show any 2020 logbook directories. It was current up to this week when I started this process.
|
|
|
|
69187
|
Sun Aug 2 02:57:59 2020 |
| VUIIS SysAdmin | vuiis-sysadmin@vumc.org | Question | Linux | ELOG V3.1.4-966 | Re: Missing log files when rsync to replacement server. |
Thank-you. That is good information to have.
What is the default if you you do not specify anything in elogd.cfg? I assume it is /usr/local/elog otherwise it would not see the existing logbooks.
With a default Linux RPM install, where else would the logbooks be? Still looking for a 2020 directory on either server.
Bruce
Stefan Ritt wrote: |
You can put your files where ever you want, just tell elogd where to find the elogd.cfg file via the "-c" flag. Then tell elogd where to find files in the elogd.cfg file via the "Logbook dir" and "Resource dir" directives.
Stefan
VUIIS SysAdmin wrote: |
On the new server in the logbook that should have several 2020 entries it stops on the last entry of 2019.
On the old server after stopping elogd i get:
/usr/sbin/elogd -v 3
Cannot open "elogd.cfg": No such file or directory
Are the files supposed to be in /usr/local/elog or /usr/share/elog? I have both on the old server. I only synced /usr/local/elog to the new server. In any case the Logbook with 2020 entries does not show a 2020 directory.
My backup system also does not show any 2020 logbook directories. It was current up to this week when I started this process.
|
|
|
69185
|
Sat Aug 1 15:13:17 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | ELOG V3.1.4-966 | Re: Missing log files when rsync to replacement server. |
You can put your files where ever you want, just tell elogd where to find the elogd.cfg file via the "-c" flag. Then tell elogd where to find files in the elogd.cfg file via the "Logbook dir" and "Resource dir" directives.
Stefan
VUIIS SysAdmin wrote: |
On the new server in the logbook that should have several 2020 entries it stops on the last entry of 2019.
On the old server after stopping elogd i get:
/usr/sbin/elogd -v 3
Cannot open "elogd.cfg": No such file or directory
Are the files supposed to be in /usr/local/elog or /usr/share/elog? I have both on the old server. I only synced /usr/local/elog to the new server. In any case the Logbook with 2020 entries does not show a 2020 directory.
My backup system also does not show any 2020 logbook directories. It was current up to this week when I started this process.
|
|
69184
|
Fri Jul 31 21:40:02 2020 |
| VUIIS SysAdmin | vuiis-sysadmin@vumc.org | Question | Linux | ELOG V3.1.4-966 | Re: Missing log files when rsync to replacement server. |
On the new server in the logbook that should have several 2020 entries it stops on the last entry of 2019.
On the old server after stopping elogd i get:
/usr/sbin/elogd -v 3
Cannot open "elogd.cfg": No such file or directory
Are the files supposed to be in /usr/local/elog or /usr/share/elog? I have both on the old server. I only synced /usr/local/elog to the new server. In any case the Logbook with 2020 entries does not show a 2020 directory.
My backup system also does not show any 2020 logbook directories. It was current up to this week when I started this process.
Stefan Ritt wrote: |
Start your new server interactively with "elogd -v 3" to see all verbose output. You will then see how it indexes all logbooks. If not, you might have a wrong path in elogd.cfg
VUIIS SysAdmin wrote: |
I am moving from a Hyper-V host to a VMware host and created a new elog server. I installed the elog software and did an rsync to get the .cfg file and logbooks to the new server.
rsync -av root@old.elog.server:/usr/local/elog /usr/local/
On the new server all of the 2020 entries are missing and there does not appear to be a 2020 logbook on either server but I can still access the 2020 entries on the old server. Where might they be and how do I get them over to the new server.
Old server says version is ELOG V3.1.4-unknown and new server says version is ELOG V3.1.4-966e3dd
Bothe servers a fully updated CentOS 7.
|
|
|
69183
|
Fri Jul 31 15:42:55 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | ELOG V3.1.4-966 | Re: Missing log files when rsync to replacement server. |
Start your new server interactively with "elogd -v 3" to see all verbose output. You will then see how it indexes all logbooks. If not, you might have a wrong path in elogd.cfg
VUIIS SysAdmin wrote: |
I am moving from a Hyper-V host to a VMware host and created a new elog server. I installed the elog software and did an rsync to get the .cfg file and logbooks to the new server.
rsync -av root@old.elog.server:/usr/local/elog /usr/local/
On the new server all of the 2020 entries are missing and there does not appear to be a 2020 logbook on either server but I can still access the 2020 entries on the old server. Where might they be and how do I get them over to the new server.
Old server says version is ELOG V3.1.4-unknown and new server says version is ELOG V3.1.4-966e3dd
Bothe servers a fully updated CentOS 7.
|
|
69182
|
Fri Jul 31 08:34:35 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.4 | Re: testing the client: unclear it worked |
The <hostname> you have to actually replace with your real host name. Same for logbook, username and password.
On my local test system I get (actual password hidden here with "...")
~$ elog -h localhost -p 8080 -l demo -u stefan ... -a Authort=SR -a Subject=test test
Message successfully transmitted, ID=5
~$
Jose Caballero wrote: |
Hello,
I just gave it a quick try to the command line client, to see if I can use it to access our institution service.
[root@host ~]# cd /tmp/
[root@host ~]# mkdir elog
[root@host ~]# cd elog
[root@host ~]# wget https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-2.el7.x86_64.rpm
[root@host ~]# rpm2cpio elog-3.1.4-2.el7.x86_64.rpm | cpio -idmv
[root@host ~]# cd usr/local/bin/
[root@host ~]# ./elog --help
[root@host ~]# ./elog -h <hostname> -l <logbook> -u <myusername> <mypassword> -w last
"Message successfully transmitted, ID=-1"
Is that the expected output? I was expecting to see info about the latest message in the server.
Cheers,
Jose
|
|
69181
|
Thu Jul 30 17:11:05 2020 |
| VUIIS SysAdmin | vuiis-sysadmin@vumc.org | Question | Linux | ELOG V3.1.4-966 | Missing log files when rsync to replacement server. |
I am moving from a Hyper-V host to a VMware host and created a new elog server. I installed the elog software and did an rsync to get the .cfg file and logbooks to the new server.
rsync -av root@old.elog.server:/usr/local/elog /usr/local/
On the new server all of the 2020 entries are missing and there does not appear to be a 2020 logbook on either server but I can still access the 2020 entries on the old server. Where might they be and how do I get them over to the new server.
Old server says version is ELOG V3.1.4-unknown and new server says version is ELOG V3.1.4-966e3dd
Bothe servers a fully updated CentOS 7. |
69180
|
Thu Jul 30 17:03:12 2020 |
| Jose Caballero | jcaballero.hep@gmail.com | Question | Linux | 3.1.4 | testing the client: unclear it worked |
Hello,
I just gave it a quick try to the command line client, to see if I can use it to access our institution service.
[root@host ~]# cd /tmp/
[root@host ~]# mkdir elog
[root@host ~]# cd elog
[root@host ~]# wget https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-2.el7.x86_64.rpm
[root@host ~]# rpm2cpio elog-3.1.4-2.el7.x86_64.rpm | cpio -idmv
[root@host ~]# cd usr/local/bin/
[root@host ~]# ./elog --help
[root@host ~]# ./elog -h <hostname> -l <logbook> -u <myusername> <mypassword> -w last
"Message successfully transmitted, ID=-1"
Is that the expected output? I was expecting to see info about the latest message in the server.
Cheers,
Jose |