On 10/11/21 14:07, Rusty Bird wrote:
Steve Coleman:
> I seem to have an intermittent problem when my backup scripts are
running
> late at night.
> My qubesd is apparently being shutdown (sent a sigterm signal) by
systemd
> during my long running backup sessions which then causes an eof pipe
close
> exception and qvm-backup then receives a socket exception and
immediately
> receives a second exception while still handling the first
exception, thus
> the qvm-backup process gets forcibly terminated mid stream. Just
prior to
> the qubesd shutdown I can clearly see that systemd had also
> shutdown/restarted the qubes memory manager (qubes-qmemman) too.
> Q: What kind of background maintenance processing would actually require
> qubesd or the memory manager to be restarted?
It's crond running logrotate. Fixed in R4.1 but not yet in R4.0:
https://github.com/QubesOS/qubes-issues/issues/5004
> Q: Could this processing be put on hold during backups?
I always sandwich backup runs between 'systemctl stop crond' and
'systemctl start crond'.
Great!
I was hoping for an answer like that. In my case the system will be
shutting down after the unattended backup completes, so this is actually
twice as easy!
thanks!
Rusty
>
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/d1528316-5e0e-9052-2f43-952c91559fcb%40gmail.com.
