mainstoreBackup - Support: sr #108505, storeBackupMount and logfile

 
 

sr #108505: storeBackupMount and logfile

Submitter:  Achim <esj>
Submitted:  Thu 13 Feb 2014 09:48:22 AM UTC
   
 
Category:  None Priority:  5 - Normal
Severity:  3 - Normal Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open Operating System:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Fri 14 Feb 2014 01:10:16 PM UTC, comment #3: 

Internally, the logging is done via some perl objects I've written. What you see in storeBackup.pl is mostly the interface of that module. In storeBackupMount.pl, this interface is not brought to the outside world, so you are not able to set the same options as in storeBackup.pl.

I just added those options to the storeBackupMount.pl command line and configuration file options. It seems to work for me in some basic tests.

It would be nice if you can send me a direct email, so I can send you the "beta" (or whatever) of the new version for testing.

bzw. The new version seems to work, but lacks of documentation. If you speed German, please tell me so I can copy some very basic comments about the new version in my response.

Regards, Heinz-Josef

Heinz-Josef Claes <hjclaes>
Group administrator
Thu 13 Feb 2014 03:13:47 PM UTC, comment #2: 

Hi Heinz-Josef,

> do you use the actual version 3.4.3 or an old one?


I'm using the current 3.4.3. In the beginning I used the version shipped with Ubuntu - but unfortunately they deliver only 3.2.1 in Ubuntu 12.04, 13.10 and 14.04 (beta). So I switched early to the current tgz.

> the options of storeBackupMount.pl are different


Yes, both config files I've created with -g and then do the following:

1. backup.sh cronjob:
/usr/local/bin/storeBackupMount.pl -f /opt/storeBackup/storeBackupMount.conf
(in one single line)

2. /opt/storeBackup/storeBackupMount.conf:
logFile=/var/log/storeBackup/storeBackupMount.log
debug=yes
storeBackup = -f /opt/storeBackup/storeBackup.conf

3. /opt/storeBackup/storeBackup.conf:
verbose=yes
debug=1
maxFilelen=0
logFile = /var/log/storeBackup/storeBackup.log
# Additionally
logInBackupDir=yes


I don't know why storeBackupMount.log is being deleted and replaced by a new and empty logfile as soon as 1M is reached. Is there any hidden configuration option or limit?

Thanks & regards, Achim

Achim <esj>
Thu 13 Feb 2014 11:41:14 AM UTC, comment #1: 

Hi,

do you use the actual version 3.4.3 or an old one?

StoreBackupMount.pl was written newly in version 3.3.1.

Please double check your issue with the new version - and remember, the options of storeBackupMount.pl are different.

Regards, Heinz-Josef

PS: If you have to install the new version independent to your packet manager, follow the instructions:
http://www.nongnu.org/storebackup/en/node5.html
http://www.nongnu.org/storebackup/de/node5.html

There will be no conflict with the version installed by the packet manager. But you have to set your PATH environmental variable to the new version or use absolute paths.

Heinz-Josef Claes <hjclaes>
Group administrator
Thu 13 Feb 2014 09:48:22 AM UTC, original submission:  

Hi all,

I use storeBackupMount to mount my sources and trigger after that storeBackup. All done by config files.

storeBackup has a config file entry "logfile".
storeBackupMount has also a config file entry "logfile".

The diff of the logs shows me that storeBackupMount.log = [ping test and mount info]  + storeBackup.log + [unmount info]

As far as good.

I discovered that storeBackupMount.log is every times beeing deleted after a size > 1M and again grows from zero, but there are no options like "maxFilelen" or "noOfOldFiles" in the storeBackupMount.conf.
If the same logFile is used in storeBackupMount and storeBackup, then the whole head of the logfile is lost.

How can I avoid the rotation/deletion of storeBackupMount.log?

Thanks, Achim

Achim <esj>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by hjclaes (Posted a comment)
  • -email is unavailable- added by esj (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    No changes have been made to this item

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code