file changed as we read it

[tbmay]

When running the backup script, I occasionally get the message in the subject line. Are there any ramifications or is that simply informational?

Thanks a million.

[slansing]

Can you provide an example of what you are talking about? Which subject line, and what does the message say?

[tbmay]

Sure. Just ran it again and here's the output. It doesn't always do this. In fact, I have been running it until I didn't get it then sacking that tarball away. Appreciate it.

[root@nagios scripts]# ./backup_xi.sh
Backing up Core Config Manager (NagiosQL)...
tar: Removing leading `/' from member names
tar: Removing leading `/' from member names
Backing up Nagios Core...
tar: Removing leading `/' from member names
tar: /usr/local/nagios/share/perfdata/Procurve-WE-Office-5406: file changed as we read it
tar: /usr/local/nagios/share/perfdata/Procurve-DH-A-Building-MacLab: file changed as we read it
tar: /usr/local/nagios/share/perfdata/Procurve-DO-Building-C: file changed as we read it
tar: /usr/local/nagios/var/ndo.sock: socket ignored
Backing up Nagios XI...
tar: Removing leading `/' from member names
Backing up MRTG...
tar: Removing leading `/' from member names
Backing up MySQL databases...
Backing up PostgresQL databases...
Backing up logrotate config files...
Backing up Apache config files...
Compressing backup...

===============
BACKUP COMPLETE
===============
Backup stored in /store/backups/nagiosxi/1394817029.tar.gz
[root@nagios scripts]#

[abrist]

It should not cause any issues, but you may lose a few checks in the backup if the rrds are updated during the backup. Nothing to worry about. You could always stop npcd, run teh backup, and then restart npcd, but I don't think it is necessary.