DEFAULT_LOG_OUTPUT deleted in config

[Moosbueffel]

Why was DEFAULT_LOG_OUTPUT deleted in version 0.7.1.1?

I did an upgrade and found some problems with nightly backup.

1. I didn't get any information in my Node-Red - Dashboard, because there were no .log - file any more. in /var/log/raspiBackup
2. I didn't found any .log. The last I found was in my home dir, with the upgrade
3. In my backup dir I found a tmp folder, but no .log
4. I'm trying a manual backup to see what's going on: I got error: not enought disk space.
5. It seems to me, first v0.7 make a full backup (no hardlinks). It's ok, but I didn't know/saw any hint - and no .log file
6. Now backup runs - also nightly - but I see problems with the log to analyse for my dashboard

I found description, that now .log ist stored in the backup dir and in case of an error in the home dir. This was not the fact in my case. And it is not comfortable for me to have logs an different places!

What are the suggestions to analyse of the log?

• To have a look at the backup dir is in general bad, because I want to unmount my drive after backup for security reason - or is it not a good idea or no additional security regarding destroying the backup? Should I leave it mounted?
• Than I have to look first at backup dir and if there is no log, I have to look at home dir.
• my solution idea is to copy the .log and especially the .msg to my home dir after backup in a seperate skript and a wrapper to raspiBackup.
• But it would be much easier and simplier to get back the DEFAULT_LOG_OUTPUT

Any chance of this?

[framps]

Why was DEFAULT_LOG_OUTPUT deleted in version 0.7.1.1?

Looks like you upgraded from a very old raspiBackup release ...

DEFAULT_LOG_OUPUT was never included in the config file. It only can be set with invocation option -L.

In v0.6.4.3 on April 22, 2019 the default was changed from varlog to backup. Until now nobody complained about the change of the default.

But I see the point: That's an option which also should be set in the config file. Created and issue/enhanvement to add DEFAULT_LOG_OUTPUT in the config file. Default will be still 2 (backup) but then you can update the config option to 1 (varlog) on your system and will have the same behavior as before.

I will let you know when the issue/enhancement is available in 0.7.1.

Please note: In raspiBackup there will never-ever an option be deleted. All future release are backward compatible and no option will be changed. In your case it's just the default which changed and unfortunately I missed to add DEFAULT_LOG_OUTPUT in the config file.

[Moosbueffel]

Many thanks, I'll wait for your update.

My previous version was: 0.6.9.1, 2023-11-30/21:44:19 - 36c728f

In the new config I found the hint to disabled options:

# >>>>> OPTION DELETED in config version "0.1.9" <<<<< 
# DEFAULT_LOG_OUTPUT="/var/log/raspiBackup/raspiBackup"

# >>>>> OPTION DELETED in config version "0.1.9" <<<<< 
# DEFAULT_NOTIFY_UPDATE=1

# >>>>> OPTION DELETED in config version "0.1.9" <<<<< 
# DEFAULT_YES_NO_RESTORE_DEVICE=""
 

[framps]

# >>>>> OPTION DELETED in config version "0.1.9" <<<<< 
# DEFAULT_LOG_OUTPUT="/var/log/raspiBackup/raspiBackup"

I recreated your upgrade from 36c728f and this deletion doesn't happen for me. I'm sure you manually added this option a long time ago and it was deleted by the upgrade because it was never included in the config file.

Now it's included in the config file and should be added again. It's no longer deleted when you upgrade raspiBackup in the future. Just follow the instructions in #904 and edit the config parameter accordingly.

[framps]

See #904 for the fix

[Moosbueffel]

Many thanks, it worked