Linux agent backup successful but "unshare snap" command error

[Pierpa]

Hi,
I'm trying to backup a Ubuntu vm based on Proxmox. The vm version is VERSION="22.04.5 LTS (Jammy Jellyfish)" and it is a test system.

The backup job is successful, but if I check the /var/log/syslog I see:

Code: Select all

Mar 10 10:35:10 ubu22cl systemd-udevd[10055]: veeamimage2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/veeamimage2' failed with exit code 1.
Mar 10 10:35:10 ubu22cl systemd-udevd[10052]: veeamimage0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/veeamimage0' failed with exit code 1.
Mar 10 10:35:10 ubu22cl systemd-udevd[10053]: veeamimage1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/veeamimage1' failed with exit code 1.
Mar 10 10:35:12 ubu22cl kernel: [236555.143827] EXT4-fs (veeamimage1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
Mar 10 10:35:12 ubu22cl systemd[1]: tmp-veeam-\x7bc2567189\x2d50ae\x2d44d3\x2d9bbf\x2d4f1f243ddb93\x7d.mount: Deactivated successfully.
Mar 10 10:35:13 ubu22cl kernel: [236555.392677] EXT4-fs (veeamimage2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
Mar 10 10:35:13 ubu22cl systemd[1]: tmp-veeam-\x7b4ffce2cb\x2d6a5e\x2d42f6\x2d93a7\x2d2cb096309e45\x7d.mount: Deactivated successfully.

If I run the unshare command via shell I see:

Code: Select all

root@ubu22cl:/var/log# /usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/veeamimage0
auto-import is disabled on classic

May I consider my backup sucessful? Have I to take care about "auto-import is disabled on classic" error?

Thanks in advance for your support
Pierpa

[PTide]

Hi,

Do you use Snap packages on your system? To me it seems that snap is messing around with block devices created by Veeam agent.

Thanks!

[Pierpa]

Hi,
sorry, but I'm totally unaware and novice about snap packages.
I've just installed veeam agent on ubuntu to practice and test the installation procedure ( well documented in the pdf doc ). Normally I don't use ubuntu so anything for me is a surprise.
How can I "disable" snap ? I've seen that there is a snapd service, I've stopped it and disabled but nothing changes.
Even if here is not the right place to ask how can I avoid snapd packages usage in order to let veem run peacefully?

Thanks for your patience
Pierpa

[Pierpa]

Hi,
apparently, really easy ...
I deinstalled snap with "apt remove snapd" and now messages disappeared. Everything is clean.

Mar 19 16:24:43 ubu22cl kernel: [ 832.866564] EXT4-fs (veeamimage1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
Mar 19 16:24:43 ubu22cl systemd[1]: tmp-veeam-\x7b78535796\x2d01f5\x2d4036\x2d976f\x2dcd346aa350fb\x7d.mount: Deactivated successfully.
Mar 19 16:24:44 ubu22cl kernel: [ 833.303341] EXT4-fs (veeamimage2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
Mar 19 16:24:44 ubu22cl systemd[1]: tmp-veeam-\x7b54ed964d\x2d3d9d\x2d4793\x2dbdaf\x2d67e511ba81f0\x7d.mount: Deactivated successfully.
Mar 19 16:25:57 ubu22cl systemd[1]: Starting Cleanup of Temporary Directories...
Mar 19 16:25:57 ubu22cl systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Mar 19 16:25:57 ubu22cl systemd[1]: Finished Cleanup of Temporary Directories.

Great!! New lesson learned !!

Thanks
Pierpa