Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   Missing log files when rsync to replacement server., posted by VUIIS SysAdmin on Thu Jul 30 17:11:05 2020 
    icon2.gif   Re: Missing log files when rsync to replacement server., posted by Stefan Ritt on Fri Jul 31 15:42:55 2020 
       icon2.gif   Re: Missing log files when rsync to replacement server., posted by VUIIS SysAdmin on Fri Jul 31 21:40:02 2020 
          icon2.gif   Re: Missing log files when rsync to replacement server., posted by Stefan Ritt on Sat Aug 1 15:13:17 2020 
             icon2.gif   Re: Missing log files when rsync to replacement server., posted by VUIIS SysAdmin on Sun Aug 2 02:57:59 2020 
                icon2.gif   Re: Missing log files when rsync to replacement server., posted by Stefan Ritt on Sun Aug 2 09:06:46 2020 
Message ID: 69187     Entry time: Sun Aug 2 02:57:59 2020     In reply to: 69185     Reply to this: 69188
Icon: Reply  Author: VUIIS SysAdmin  Author Email: vuiis-sysadmin@vumc.org 
Category: Question  OS: Linux  ELOG Version: ELOG V3.1.4-966 
Subject: 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.

 

ELOG V3.1.4-80633ba