Recent content by ScottW

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...

Ok, so it seems the concern is that this isn't guaranteed to solve the problem in aggregate -- and we might end up "back where we started." That is a valid concern. Since we don't know the root cause, nobody can be sure either way without actually trying (testing) it. What is the ECD for...

You seem to be saying we "know for a fact" that the missing jobs are being caused by multiple scripts trying to use cru at/near the same time, and some failure of the lock file logic. Has that been proven? (I know there are some other threads on this, but I haven't been following them all so...

True - The checking first is not absolutely required, if repeatedly re-writing the crontab file without need is acceptable, and if logging of the anomaly (jobs missing when they should be present) is not desired.

I don't think post-mount will help here. Like services-start, it (usually) only happens once, at boot, and doesn't get re-fired when the WAN goes down/up. But firewall-start gets called at boot, wan up/down, and several other cases. It is a little later than services-start, but getting the cron...

Long before backupmon.... I had issues with cron jobs disappearing. I would inject them via services-start, then later (days or weeks) notice they were missing. I added various logging, but never determined a root cause. I did find that *sometimes* after the WAN had gone down, then come...

Well... My linux knowledge is really limited, so I could be off base here but... I *think* the "white" line in your 'htop' snapshot is the main process -- and the "green" line(s) are worker threads. So, you have only (1) main process, and (1) worker thread. If you run "ps | grep "syslog-ng"...

Update... I did a backup of the USB drive and set it up again with amtm. Before, it was two partitions: partition-1 was 80gb ext4, and partition-2 was unformatted. This time I set it up as one ext 4 partition using the entire drive. Used amtm to create the 4gb swap file, as before, then...

About 3 months ago, I rebooted my AX86U and noticed afterwards that syslog-ng was not logging correctly. The files were simply not being updated. Scribe status showed everything as working. Rather than investigate, I just did a scribe restart and the logging began working fine again. The...

Fantastic! Thank you very much!

I had the same problem, which is why I ended up manually removing the file from the tarball (on Windows, using 7zip). Though maybe I was doing something wrong, but I guess busybox tar just doesn't support it. I tried several variations like you did but couldn't get "exclude from restore" to...

I was surprised that, after the tar failure, the script just continued and rebooted as if everything was fine. Maybe adding some return code checking after the tar completes? At least "pause" if tar returns a "fatal error", so the user can see the error message?

If you decide to add an "automatically exclude swap files from backup" feature of some kind, you can find the fully qualified path(s) with `cat /proc/swaps`.

Agreed, I should have phrased my question differently. Should the swap file be Automatically excluded by BackupMon? Or is each user expected to manually exclude it? I see the provision exists for an exclusion file, and I'm fine with manually managing that... But I was just surprised the...

My USB drive failed today (Samsung Fit Plus, 32gb). Won't mount or even be detected on any of my machines. It's dead, Jim. Switching to an SSD drive is on my todo list, but I haven't gotten there yet. :) I inserted a new USB drive (same model as old one) and followed the backmon...