Beiträge von Offal

I started receiving weekly email error from my OMV (5.6.26-1 Usul) about a weekly cron job to update smart drivedb, "openmediavault-update-smart-drivedb".

• I don't get the same error when I try to run it a shell (obviously since there's a terminal attached).
• Review the script, I don't see it calling "tput".

It's not a fatal error, as I can see in the log that the script did successfully ran.

Just hoping to fix, so the error email doesn't get sent. Any pointers would be helpful?

Thanks

----------------------------------------------------------------------------------------

Subject: Anacron job 'cron.weekly' on OMV

/etc/cron.weekly/openmediavault-update-smart-drivedb:

tput: No value for $TERM and no -T specified

Zitat von ryecoaaron

The update should have removed the security repo from /etc/apt/sources.list and put it in /etc/apt/sources.list.d/openmediavault-os-security.list.

Does: sudo omv-salt deploy run apt fix it?

Thanks ryecoaaron ! sudo omv-salt deploy run apt Fixed it for me!

Try this.....Force folder2ram to sync to filesystem on shutdown or reboot

Add "ExecStartPre=/sbin/folder2ram -syncall" to /lib/systemd/system/folder2ram_shutdown.service:

[Unit]

Description=folder2ram systemd service

Before=shutdown.target reboot.target halt.target

DefaultDependencies=no

[Service]

Type=oneshot

RemainAfterExit=yes

ExecStartPre=/sbin/folder2ram -syncall

ExecStart=/sbin/folder2ram -umountall

[Install]

WantedBy=shutdown.target reboot.target halt.target

Zitat von grokov

How can you tell it's not syncing?

With OMV 5.5.5-1 and openmediavault-flashmemory 5.0.7 (folder2ram plugin), it has been ok-ish for me. In some cases data is lost on reboot, but most times it persists. I haven't found a pattern.

Huge gaps in RRDGRaph.

As BigBro suggested, I added the ExecStartPre=/sbin/folder2ram -syncall to the folder2ram shutdown config, and I see data being persisted in the performance graphs.

Zitat von grokov

The performance data has persisted over the past several reboots over the past month or so. I don't know why, whether it's something I did or a bug was fixed in updates, but at least it seems ok for now.

When I reboot, folder2ram is still not syncing ram to the filesystem. I would have thought that -umountall will sync before it umounted.

Running 5.5.5-1 (Usul) with folder2ram.

Zitat von gderf

For me this has been broken for so long that I gave up on it.

Ohh...It was working when I was on OMV3. Has it never worked in OMV5?

I have the same issue; I'm not getting any email notification for OMV updates even though I'm able to receive the test email.

Any help on where or how to debug?

Thanks!

I ran into the same error after upgrading to OMV4.

To fix it, change the ownership for files in /var/log/clamav/ to clamav, and you will get fresh clams.

$ cd /var/log/
$ chown -R clamav clamav

Thanks @ryecoaaron !

Thanks for the info and submitting the tracker ryecoaaron.

I'm currently running 3.0.64 (Eramus) with Linux omv 4.9.0-0.bpo.1-amd64 #1 SMP Debian 4.9.2-2~bpo8+1 (2017-01-26) x86_64 GNU/Linux as a VM in ESXi. How do I upgrade the btrfs tools (currently 3.17) to the more current version 4.9?

If I try to install btrfs-progs, it will try to uninstall openmediavault!

I noticed that that package is now called btrfs-progs instead of btrfs-tools.

# apt list | grep -i btrfs

btrfs-progs/jessie-backports 4.7.3-1~bpo8+1 amd64
btrfs-progs-dbg/jessie-backports 4.7.3-1~bpo8+1 amd64
btrfs-tools/stable,now 3.17-1.1 amd64 [installed,automatic]
btrfs-tools-dbg/stable 3.17-1.1 amd64

Thanks for the tip thermodust!

I also open an issue on the developer's github page. Hopefully, @jhmiller or other dev will noticed and fix it soon. Great Plugin.

Also, I don't know how the UI says that there's an update.