BACKUPMON BACKUPMON v1.5.10 -Mar 1, 2024- Backup/Restore your Router: JFFS + NVRAM + External USB Drive! (**Thread closed due to age**)

[Ripshod]

Why the different font and colours in the new version? Also see a broken line.
Top the test from earlier, below the new test email:
Never mind. That only affects test emails. Success/failure emails are well formatted.
Good work.

 

[SomeWhereOverTheRainBow]

I actually came to the opposite conclusion -- that using service-event (or firewall-start) is the way to mitigate the problem, rather than anything causing it.

When I saw jobs missing, they were always the jobs that had been added from services-start or postmount. I had been using services-start for mine, while scribe's logrotate job is added from post-mount, and those were the jobs "missing" after certain WAN down/WAN restored events occurred. Conversely, all the jobs added by scripts hooked in service-event, like diversion and skynet, were still present.

My best guess is that some (unknown) event, or combination of events, causes the entirety of crontab to be lost. Scripts hooked via service-event or firewall-start then have another chance to check and add jobs again, whereas scripts hooked via services-start and post-mount generally get only one shot, at boot time.

I've seen jobs missing from init-start, service-start, service-event, and post mount. It has just been along time since I have ran into that particular problem. I know @Jack Yaz did alot of improvements with his scripts to solve the "cron-job" disappearance problem. Maybe if he is still around he wouldn't mind sharing some knowledge or pearls of wisdom.

 

[Viktor Jaep]

Why the different font and colours in the new version? Also see a broken line.
Top the test from earlier, below the new test email:
Never mind. That only affects test emails. Success/failure emails are well formatted.
Good work.

Yeah I noticed that too... I need to figure out why it does it differently between the two. As long as you get emails, that's what counts! Lol

 

[Martinski]

Why the different font and colours in the new version? Also see a broken line.
Top the test from earlier, below the new test email:
Never mind. That only affects test emails...

Yeah I noticed that too... I need to figure out why it does it differently between the two.

WRT the "broken line" in the email:

From the "A88U
" router.

It's very odd. It looks as if a linefeed was inserted just after the value of the "FRIENDLY_ROUTER_NAME" variable (which is the one used in that line), but I just double-checked the script and I don't see any LF at all between the var and the double quotes. Intriguing!!

 

[visortgw]

And I just received three (3) emails to verify successful completion of daily backups!

 

[Ripshod]

Yeah I noticed that too... I need to figure out why it does it differently between the two. As long as you get emails, that's what counts! Lol

I wouldn't worry too much. After all, it only affects test emails (for me).

 

[Viktor Jaep]

WRT the "broken line" in the email:

From the "A88U
" router.

It's very odd. It looks as if a linefeed was inserted just after the value of the "FRIENDLY_ROUTER_NAME" variable (which is the one used in that line), but I just double-checked the script and I don't see any LF at all between the var and the double quotes. Intriguing!!

Thanks for looking into this @Martinski ... you never know, my editor can do some weird things. I'll see if I can get around this... maybe instead of breaking lines, just make lines continuous text, and end each one with a \n will get around it.

EDIT: @Martinski... that was the problem... when you eliminate that run-on printf statement, then the formatting works fine. The messages in these emails is short enough... I don't think I need to worry about needing to printf paragraphs.

 

[aex.perez]

Here's a strage one, on one of the nose post beta I got this email

FAILURE: BACKUPMON was unable to mount the primary network drive. Please check your network environment and configuration.

/tmp/mnt/backups would not mount download 1.46 and rebuilt the config as it was, tested and it worked, the back on 1.52.b1 and all was fine, its al iff the config got wiped

"BACKUPMON is not configured. Proceding with 1st time setup!"
"**ERROR**: Page File does not exist"
" Successfully wrote a new config file"

Afterwards all is working fine. This happened on the one node that I was planning on replacing the USB drive with SSD, if it doesn't happen to anyone else chalk it up to that. There was plenty of space and I could write a file in the directory. All I changed was the password for the NAS/Network that the defaults were bing used and wouldn't update until I went back to 1.46, after a few successful tests, put 1.51b1 back on and tested successfully again, then ran the mssed backup.

The new feature of emailing on a failure is working great, it's how I noticed it failed. The other node and router are setup identically and worked fine.
Back in business!

Feb 10 2024 05:30:19 BACKUPMON[3958] - INFO: Finished copying restoration instructions.txt file to /tmp/mnt/backups/master
Feb 10 2024 05:30:29 BACKUPMON[3958] - INFO: External network drive ( \\192.168.1.156\Network ) unmounted successfully. - worked the day before
Feb 10 2024 05:30:29 BACKUPMON[3958] - INFO: Updating the shared library script file to support email notifications...
Feb 11 2024 05:30:31 BACKUPMON[8499] - **ERROR**: Unable to mount to external network drive. Please check your configuration! - failed
Feb 11 2024 05:30:31 BACKUPMON[8499] - INFO: Updating the shared library script file to support email notifications...
Feb 11 2024 05:30:34 BACKUPMON[8499] - INFO: Email notification was sent successfully [FAILURE: Unable to mount network drive].
Feb 11 2024 07:16:01 BACKUPMON[13657] - **ERROR**: Unable to mount to external network drive. Please check your configuration!
Feb 11 2024 07:16:04 BACKUPMON[13657] - INFO: Email notification was sent successfully [FAILURE: Unable to mount network drive].
Feb 11 2024 15:20:49 BACKUPMON[21076] - INFO: Successfully wrote a new config file - redid the config file - appeared not to take
Feb 11 2024 15:40:27 BACKUPMON[32758] - INFO: Successfully downloaded and installed BACKUPMON v1.46 - reverted back
Feb 11 2024 15:45:06 BACKUPMON[1972] - INFO: Successfully wrote a new config file - config took
Feb 11 2024 15:45:13 BACKUPMON[1972] - INFO: External network drive ( \\192.168.1.156\Network ) mounted successfully under: /tmp/mnt/backups - working
Feb 11 2024 15:45:13 BACKUPMON[1972] - INFO: Daily Backup Directory successfully created. - went back to 1.52b2 after this

 

[Viktor Jaep]

Here's a strage one, on one of the nose post beta I got this email

FAILURE: BACKUPMON was unable to mount the primary network drive. Please check your network environment and configuration.

/tmp/mnt/backups would not mount download 1.46 and rebuilt the config as it was, tested and it worked, the back on 1.52.b1 and all was fine, its al iff the config got wiped

"BACKUPMON is not configured. Proceding with 1st time setup!"
"**ERROR**: Page File does not exist"
" Successfully wrote a new config file"

Afterwards all is working fine. This happened on the one node that I was planning on replacing the USB drive with SSD, if it doesn't happen to anyone else chalk it up to that. There was plenty of space and I could write a file in the directory. All I changed was the password for the NAS/Network that the defaults were bing used and wouldn't update until I went back to 1.46, after a few successful tests, put 1.51b1 back on and tested successfully again, then ran the mssed backup.

The new feature of emailing on a failure is working great, it's how I noticed it failed. The other node and router are setup identically and worked fine.
Back in business!

It does sound like it had trouble finding the config file when it ran... that's what it would say on a brand new install if no config file exists. And it looks like BACKUPMON wasn't able to detect the name of your swap file, and threw that error about the swap file not existing. This is the command it runs to detect your swap/page file name:

cat /proc/swaps | awk 'NR==2 {print $1}' | sed 's|.*/||'

Hopefully just a temporary quirk, or maybe something going bad with your USB drive? Glad it ran fine again after some tries on 1.5.2b1, and that it was able to alert you via email! Whooo!

 

[aex.perez]

It does sound like it had trouble finding the config file when it ran... that's what it would say on a brand new install if no config file exists. And it looks like BACKUPMON wasn't able to detect the name of your swap file, and threw that error about the swap file not existing. This is the command it runs to detect your swap/page file name:

cat /proc/swaps | awk 'NR==2 {print $1}' | sed 's|.*/||'

Hopefully just a temporary quirk, or maybe something going bad with your USB drive? Glad it ran fine again after some tries on 1.5.2b1, and that it was able to alert you via email! Whooo!

That's my thoughts exactly, it's the oldest USB and needs replacing anyway, thankfully it's on the node so replacing the USB willl be easy. But al east we know the failure email works well, so that's something....

 

[Martinski]

... I'll see if I can get around this... maybe instead of breaking lines, just make lines continuous text, and end each one with a \n will get around it.

EDIT: @Martinski... that was the problem... when you eliminate that run-on printf statement, then the formatting works fine...

Sorry, I don't quite understand what you're trying to say. The section of the email with the line "From the ... router" is generated in a different/separate function from where the body of the email with the TEST message is set, so I'm not seeing how the latter could affect the former WRT breaking the line in two. But no worries, I'll take a look at the related code changes when you publish them in your GitHub repository to see what you meant exactly. I'm just curious & would like to understand what the cause is/was.

 

[Viktor Jaep]

Sorry, I don't quite understand what you're trying to say. The section of the email with the line "From the ... router" is generated in a different/separate function from where the body of the email with the TEST message is set, so I'm not seeing how the latter could affect the former WRT breaking the line in two. But no worries, I'll take a look at the related code changes when you publish them in your GitHub repository to see what you meant exactly. I'm just curious & would like to understand what the cause is/was.

Well, I tried reverting back to see if I can show what the difference was, but for some reason I cannot make it act like it did before. Hum. At this point, it's up in the air as to what the reasoning is.

 

[CaptainSTX]

Well, I tried reverting back to see if I can show what the difference was, but for some reason I cannot make it act like it did before. Hum. At this point, it's up in the air as to what the reasoning is.

I ran a test backup and while it worked and I received the email notification the message was overly verbose. The original test email was normal and other emails I get from the router have never included this cryptic message.

Don't know if it is something specific to this script or the amtm email setup or the email accounts themselves. gmx send to receive on Gmail.

Date/Time: Feb 11 2024 12:23:36
Asus Router Model: RT-AX86S
Firmware/Build Number: 3004.388.6_0
EXT USB Drive Label Name: ScriptSSD_3
Message-ID: <1N8GQs-1qvsTq1qoC-014F0U@mail.gmx.net>
X-Provags-ID: V03:K1:JKGk1fA+U0WaV3osLGxjJikWEoq6uDjWTqOCJSGX6dd/p37Me/6
wYt+vbg344Itkc7z2PE1wtZs4q59QG5RW6jC54Bo6tJeIjDLi7a24kLJw8pviVQWUTNWxjn
5tNn1mmYa6CeiEaSeee3kG5Sp7b3MESDfKYM2Hseu4M8ZZ6M6K0aBHy0Rj5Lcb96DZWrlFu
9f1PODFP9azrtRq0pNBnQ==
X-Spam-Flag: NO
UI-OutboundReport: notjunk:1;M010:WTbno9sEGn4=;HGwscXXczAQAX7/To5z+9VEEaSX
rUznk9koaNhI7W88ypSEtBCmOMhxH1BgXkGdMB0N0tRXtsC3XvJ1ClmNTONDL40ebWw4RGu+J
sVEkkmP9N1aFIcJP3VcNaX009U+skgf/RDSBdGMCMk9jr5SzUaBAZvkOVOAL+qhllgXDPnymR
IooEPQDA6ot4dVndesD8STyy24rIxBYAaF8zBdHUOHhPz1hj/Efay/Z0NtBqTR5clWldiVJ89
EmHfT//BtStWFMNeroYMA8S9btwrc9J1weIvlSPEhyUvrGKABlNC8Uc//xeBlpXX+PhyxpzvB
f9f9/6ORx6wCxQbe0Aw7fUQxDeEhZv7u3QsluLhdd4JnvsHbyEr/HsoPV/GNtfun9ttKZSy37
pW2Ab3ORwyKFaojRrjzmNKn9NsLD24AsjLkOpcNDmzoxjP0H+98O4lRX7XZtrzs5rieyPVf0Z
ES23ywiY3P2SHsu080fhh3A/sPqGnRdilgXj8Xdbl2TpdYS+zBTbjUkQbZwJ/mGUhvM2sOa0x
Sm36MwSmbuPJABDjzE48Mif9sKA5JwWa158Jf/vtSLoa8kb7hID0iYUOIfAKe5vwO10B9wzuk
46tcQTDoy6PljwDpSOd9YiJL7P2YtQV5DsPg17X5+MC7+UGLa2FbcR/VnaFYElYfrxP1nYF19
6d8323nn8NlwwENaYJrX7VDDZXcoixONVl4fCCJeP7MVeM/nrdr26tpXx82r69OeWrl9Ss1QS
YJEFqPgcnvEFz/LuhpKJzcRPguwD9PCBrW6UU/aNWUhLdmlzKyjUypIZgLPhKUxxYwQANqIzo
L0V21zth0zp7gqxxhfovF6BaaP6xlmTeU55Q0vwfMwcaVR400742pfyOik2htjG1e3G6DBPd8
a8wDJcQytdBj7ROEM3hMrbTK/OOyKzl4kUvvmcGdunpzgUIaGkmzb1G6/LZ599NBGqiqa7Qjb
/b+vQQ==

SUCCESS: BACKUPMON completed a successful primary backup to destination: USB.

Sent by the "backupmon.sh" script.
From the "AX86-Main" router.

2024-Feb-11, 12:23:36 PM EST (Sun)

 

[Viktor Jaep]

I ran a test backup and while it worked and I received the email notification the message was overly verbose. The original test email was normal and other emails I get from the router have never included this cryptic message.

Don't know if it is something specific to this script or the amtm email setup or the email accounts themselves. gmx send to receive on Gmail.

Date/Time: Feb 11 2024 12:23:36
Asus Router Model: RT-AX86S
Firmware/Build Number: 3004.388.6_0
EXT USB Drive Label Name: ScriptSSD_3
Message-ID: <1N8GQs-1qvsTq1qoC-014F0U@mail.gmx.net>
X-Provags-ID: V03:K1:JKGk1fA+U0WaV3osLGxjJikWEoq6uDjWTqOCJSGX6dd/p37Me/6
wYt+vbg344Itkc7z2PE1wtZs4q59QG5RW6jC54Bo6tJeIjDLi7a24kLJw8pviVQWUTNWxjn
5tNn1mmYa6CeiEaSeee3kG5Sp7b3MESDfKYM2Hseu4M8ZZ6M6K0aBHy0Rj5Lcb96DZWrlFu
9f1PODFP9azrtRq0pNBnQ==
X-Spam-Flag: NO
UI-OutboundReport: notjunk:1;M010:WTbno9sEGn4=;HGwscXXczAQAX7/To5z+9VEEaSX
rUznk9koaNhI7W88ypSEtBCmOMhxH1BgXkGdMB0N0tRXtsC3XvJ1ClmNTONDL40ebWw4RGu+J
sVEkkmP9N1aFIcJP3VcNaX009U+skgf/RDSBdGMCMk9jr5SzUaBAZvkOVOAL+qhllgXDPnymR
IooEPQDA6ot4dVndesD8STyy24rIxBYAaF8zBdHUOHhPz1hj/Efay/Z0NtBqTR5clWldiVJ89
EmHfT//BtStWFMNeroYMA8S9btwrc9J1weIvlSPEhyUvrGKABlNC8Uc//xeBlpXX+PhyxpzvB
f9f9/6ORx6wCxQbe0Aw7fUQxDeEhZv7u3QsluLhdd4JnvsHbyEr/HsoPV/GNtfun9ttKZSy37
pW2Ab3ORwyKFaojRrjzmNKn9NsLD24AsjLkOpcNDmzoxjP0H+98O4lRX7XZtrzs5rieyPVf0Z
ES23ywiY3P2SHsu080fhh3A/sPqGnRdilgXj8Xdbl2TpdYS+zBTbjUkQbZwJ/mGUhvM2sOa0x
Sm36MwSmbuPJABDjzE48Mif9sKA5JwWa158Jf/vtSLoa8kb7hID0iYUOIfAKe5vwO10B9wzuk
46tcQTDoy6PljwDpSOd9YiJL7P2YtQV5DsPg17X5+MC7+UGLa2FbcR/VnaFYElYfrxP1nYF19
6d8323nn8NlwwENaYJrX7VDDZXcoixONVl4fCCJeP7MVeM/nrdr26tpXx82r69OeWrl9Ss1QS
YJEFqPgcnvEFz/LuhpKJzcRPguwD9PCBrW6UU/aNWUhLdmlzKyjUypIZgLPhKUxxYwQANqIzo
L0V21zth0zp7gqxxhfovF6BaaP6xlmTeU55Q0vwfMwcaVR400742pfyOik2htjG1e3G6DBPd8
a8wDJcQytdBj7ROEM3hMrbTK/OOyKzl4kUvvmcGdunpzgUIaGkmzb1G6/LZ599NBGqiqa7Qjb
/b+vQQ==

SUCCESS: BACKUPMON completed a successful primary backup to destination: USB.

Sent by the "backupmon.sh" script.
From the "AX86-Main" router.

2024-Feb-11, 12:23:36 PM EST (Sun)

Is this repeatable for you every time you send, or receive a regular "success/failure" email? Does this same thing happen when you test it from AMTM directly? I am sending from google to google... and I'm not seeing this extra base64 "UI-OutboundReport" header info.

 

[visortgw]

I ran a test backup and while it worked and I received the email notification the message was overly verbose. The original test email was normal and other emails I get from the router have never included this cryptic message.

Don't know if it is something specific to this script or the amtm email setup or the email accounts themselves. gmx send to receive on Gmail.

Date/Time: Feb 11 2024 12:23:36
Asus Router Model: RT-AX86S
Firmware/Build Number: 3004.388.6_0
EXT USB Drive Label Name: ScriptSSD_3
Message-ID: <1N8GQs-1qvsTq1qoC-014F0U@mail.gmx.net>
X-Provags-ID: V03:K1:JKGk1fA+U0WaV3osLGxjJikWEoq6uDjWTqOCJSGX6dd/p37Me/6
wYt+vbg344Itkc7z2PE1wtZs4q59QG5RW6jC54Bo6tJeIjDLi7a24kLJw8pviVQWUTNWxjn
5tNn1mmYa6CeiEaSeee3kG5Sp7b3MESDfKYM2Hseu4M8ZZ6M6K0aBHy0Rj5Lcb96DZWrlFu
9f1PODFP9azrtRq0pNBnQ==
X-Spam-Flag: NO
UI-OutboundReport: notjunk:1;M010:WTbno9sEGn4=;HGwscXXczAQAX7/To5z+9VEEaSX
rUznk9koaNhI7W88ypSEtBCmOMhxH1BgXkGdMB0N0tRXtsC3XvJ1ClmNTONDL40ebWw4RGu+J
sVEkkmP9N1aFIcJP3VcNaX009U+skgf/RDSBdGMCMk9jr5SzUaBAZvkOVOAL+qhllgXDPnymR
IooEPQDA6ot4dVndesD8STyy24rIxBYAaF8zBdHUOHhPz1hj/Efay/Z0NtBqTR5clWldiVJ89
EmHfT//BtStWFMNeroYMA8S9btwrc9J1weIvlSPEhyUvrGKABlNC8Uc//xeBlpXX+PhyxpzvB
f9f9/6ORx6wCxQbe0Aw7fUQxDeEhZv7u3QsluLhdd4JnvsHbyEr/HsoPV/GNtfun9ttKZSy37
pW2Ab3ORwyKFaojRrjzmNKn9NsLD24AsjLkOpcNDmzoxjP0H+98O4lRX7XZtrzs5rieyPVf0Z
ES23ywiY3P2SHsu080fhh3A/sPqGnRdilgXj8Xdbl2TpdYS+zBTbjUkQbZwJ/mGUhvM2sOa0x
Sm36MwSmbuPJABDjzE48Mif9sKA5JwWa158Jf/vtSLoa8kb7hID0iYUOIfAKe5vwO10B9wzuk
46tcQTDoy6PljwDpSOd9YiJL7P2YtQV5DsPg17X5+MC7+UGLa2FbcR/VnaFYElYfrxP1nYF19
6d8323nn8NlwwENaYJrX7VDDZXcoixONVl4fCCJeP7MVeM/nrdr26tpXx82r69OeWrl9Ss1QS
YJEFqPgcnvEFz/LuhpKJzcRPguwD9PCBrW6UU/aNWUhLdmlzKyjUypIZgLPhKUxxYwQANqIzo
L0V21zth0zp7gqxxhfovF6BaaP6xlmTeU55Q0vwfMwcaVR400742pfyOik2htjG1e3G6DBPd8
a8wDJcQytdBj7ROEM3hMrbTK/OOyKzl4kUvvmcGdunpzgUIaGkmzb1G6/LZ599NBGqiqa7Qjb
/b+vQQ==

SUCCESS: BACKUPMON completed a successful primary backup to destination: USB.

Sent by the "backupmon.sh" script.
From the "AX86-Main" router.

2024-Feb-11, 12:23:36 PM EST (Sun)

Typically, headers like these are added by outbound email server, and they are only displayed if specifically configured in email client.

 

[CaptainSTX]

Is this repeatable for you every time you send, or receive a regular "success/failure" email? Does this same thing happen when you test it from AMTM directly? I am sending from google to google... and I'm not seeing this extra base64 "UI-OutboundReport" header info.

I will run some additional tests and let you know..

 

[Tech9]

the message was overly verbose

This is how @Viktor Jaep normally speaks. I can read it just fine. It tells you the cat run out.

 

[Viktor Jaep]

This is how @Viktor Jaep normally speaks. I can read it just fine. It tells you the cat run out.

Bahaha!

 

[CaptainSTX]

Is this repeatable for you every time you send, or receive a regular "success/failure" email? Does this same thing happen when you test it from AMTM directly? I am sending from google to google... and I'm not seeing this extra base64 "UI-OutboundReport" header info.

Here are two examples. Test mail from amtm is just fine. Backupmon again creates a verbose email.

Greetings from amtm 4.3

This is a testmail.

Very truly yours,
Your AX86-Main router (Model type RT-AX86S)



Date/Time: Feb 12 2024 14:06:55
Asus Router Model: RT-AX86S
Firmware/Build Number: 3004.388.6_0
EXT USB Drive Label Name: ScriptSSD_3
Message-ID: <1M4axq-1ra9bj2DOI-001k80@mail.gmx.net>
X-Provags-ID: V03:K1:SSwI4+2DHHoVS0eofAt5JS3P+mKcildeXkmA02P+GAgQZA8LDE7
lu6u5IdrwzBDK1a35CbIxKNl3OyPzDv11KakWbsTJQk65LgnbXWzr173PoouyEmvhKpS7qy
Euzj2hF8bZC3LjZnZLYxeJK32hfDUU1XRB+y1RvyfElm0Q5TpPxapXqPx9kxIy6bOBhIPKe
9xImYKBXHUKCdQpl05SbA==
X-Spam-Flag: NO
UI-OutboundReport: notjunk:1;M010:+jxCk2/A6G4=;s3quHehDePA4KrioFS1E5sEdQpT
MB0k64q2i+tR7ZeQHow8BTaXUMESSndXqOqH1nDQyOQo43q5iRFDQep88M+tdhzjehj5tYsi9
4FJU3RpbpEUziQGukom0XqXxI6tDylWq9Aiu70ATN2IHJqPV1pPp397uCsPBTV9euEy3CGOW7
+nzt1fn7fCz91oiQBezg+4rqfgNDDlXZaqWlJ0uTD9Xf6y0VXP5CHXZ6lolJgR6oCcmvq2C36
i5fe+ninRB0kwSYrLEOJ0lbUwx9ZqrVfR+WANzjwWlAhdyqvJzZMvOsVo+KBOAKo9r+tCR83H
QLIFYj2SHPbUf6vipoKSdj9deD0eu8wvszNbzIEFJB64R+ylipFvchfVN5dS2h4F123PiZbcu
gYMjIPlBqZmUI23rAPRBiN8aiTI6TyekxSQePh8M3lg6G4bHl/SRPhUmPH7D7Smgz3GCf9GPr
o9H+xyuYDRA8d9sUSZY8Lc0WDZ6WKsJWakWXEmFYFaewmAhtR0hkk9meb7Eg9wlnPGw3q8xHO
u+74k6I8ijl1UQMZAXJ9RwY3KbhpaSgOxXYBlP/9oJTQHvPtbMnUlUbx8q7JhspUB3eECEDhn
6d2vXzWhmKLwl9GEcnJY3mRFyVVWPrIGma+DQMzBAS55cJWcY8caja7yLW1tGAs2d5nKbuPWI
TzGAmNRsiOjnTjcHci9xKIaesFfnzySU/iIrhfG3JCoJE+ZO5OsvVxcVCmxK18r+3CEigNthl
VtHRARm0jMeReB/Xdva1qJlN5cMA+nFEfSmlepRS0UoetAVcp4AT3/4tICWnrrgBel2y5CSm8
rMipfnmFf9ayXh4cetAbr3i7RVqq+4jemqbvnkXQsHnnicxqAtCrJxTt84qxUoaD56axQ2Ec5
93+Fp2yf+enSOh99S3jzH8NjkmtRrAphcP+CMOEqRfl6TLWfrsh6BQdmU4Nx2AU3kENprtMbO
48MaAw==

SUCCESS: BACKUPMON completed a successful primary backup to destination: USB.

Sent by the "backupmon.sh" script.
From the "AX86-Main" router.

2024-Feb-12, 02:06:55 PM EST (Mon)

 

[Viktor Jaep]

Here are two examples. Test mail from amtm is just fine. Backupmon again creates a verbose email.

Greetings from amtm 4.3

This is a testmail.

Very truly yours,
Your AX86-Main router (Model type RT-AX86S)



Date/Time: Feb 12 2024 14:06:55
Asus Router Model: RT-AX86S
Firmware/Build Number: 3004.388.6_0
EXT USB Drive Label Name: ScriptSSD_3
Message-ID: <1M4axq-1ra9bj2DOI-001k80@mail.gmx.net>
X-Provags-ID: V03:K1:SSwI4+2DHHoVS0eofAt5JS3P+mKcildeXkmA02P+GAgQZA8LDE7
lu6u5IdrwzBDK1a35CbIxKNl3OyPzDv11KakWbsTJQk65LgnbXWzr173PoouyEmvhKpS7qy
Euzj2hF8bZC3LjZnZLYxeJK32hfDUU1XRB+y1RvyfElm0Q5TpPxapXqPx9kxIy6bOBhIPKe
9xImYKBXHUKCdQpl05SbA==
X-Spam-Flag: NO
UI-OutboundReport: notjunk:1;M010:+jxCk2/A6G4=;s3quHehDePA4KrioFS1E5sEdQpT
MB0k64q2i+tR7ZeQHow8BTaXUMESSndXqOqH1nDQyOQo43q5iRFDQep88M+tdhzjehj5tYsi9
4FJU3RpbpEUziQGukom0XqXxI6tDylWq9Aiu70ATN2IHJqPV1pPp397uCsPBTV9euEy3CGOW7
+nzt1fn7fCz91oiQBezg+4rqfgNDDlXZaqWlJ0uTD9Xf6y0VXP5CHXZ6lolJgR6oCcmvq2C36
i5fe+ninRB0kwSYrLEOJ0lbUwx9ZqrVfR+WANzjwWlAhdyqvJzZMvOsVo+KBOAKo9r+tCR83H
QLIFYj2SHPbUf6vipoKSdj9deD0eu8wvszNbzIEFJB64R+ylipFvchfVN5dS2h4F123PiZbcu
gYMjIPlBqZmUI23rAPRBiN8aiTI6TyekxSQePh8M3lg6G4bHl/SRPhUmPH7D7Smgz3GCf9GPr
o9H+xyuYDRA8d9sUSZY8Lc0WDZ6WKsJWakWXEmFYFaewmAhtR0hkk9meb7Eg9wlnPGw3q8xHO
u+74k6I8ijl1UQMZAXJ9RwY3KbhpaSgOxXYBlP/9oJTQHvPtbMnUlUbx8q7JhspUB3eECEDhn
6d2vXzWhmKLwl9GEcnJY3mRFyVVWPrIGma+DQMzBAS55cJWcY8caja7yLW1tGAs2d5nKbuPWI
TzGAmNRsiOjnTjcHci9xKIaesFfnzySU/iIrhfG3JCoJE+ZO5OsvVxcVCmxK18r+3CEigNthl
VtHRARm0jMeReB/Xdva1qJlN5cMA+nFEfSmlepRS0UoetAVcp4AT3/4tICWnrrgBel2y5CSm8
rMipfnmFf9ayXh4cetAbr3i7RVqq+4jemqbvnkXQsHnnicxqAtCrJxTt84qxUoaD56axQ2Ec5
93+Fp2yf+enSOh99S3jzH8NjkmtRrAphcP+CMOEqRfl6TLWfrsh6BQdmU4Nx2AU3kENprtMbO
48MaAw==

SUCCESS: BACKUPMON completed a successful primary backup to destination: USB.

Sent by the "backupmon.sh" script.
From the "AX86-Main" router.

2024-Feb-12, 02:06:55 PM EST (Mon)

The code is literally this...

    {
    printf "Date/Time: $(date +'%b %d %Y %X')\n"
    printf "Asus Router Model: ${ROUTERMODEL}\n"
    printf "Firmware/Build Number: ${FWBUILD}\n"
    printf "EXT USB Drive Label Name: ${EXTLABEL}\n"
    printf "\n"
    printf "SUCCESS: BACKUPMON completed a successful primary backup to destination: ${BACKUPMEDIA}."
    printf "\n"
    } > "$tmpEMailBodyFile"

For some reason it's inserting this block of garbage in the middle of all this. Perhaps it doesn't like blank printf "\n" lines? Let me try a different variation, and see if that sticks...