Posts by auanasgheps

    Sounds interesting. Care to share some details of what me might expect to see in the update? 8|

    It will include a new notification system which is much more reliable and flexible compared to the previous one. And also a couple of minor changes, plus lots of bugfixes and logic/safeguards improvements.


    Most of what I'm saying is already on Github, and the installation is super easy.

    That's why I haven't focused on the integration with the plugin, but it will happen.

    Yes, this is a common problem when mounting Borg backups with FUSE, which by default limits the access to the mount user.


    When executing the command, if done via the CLI, you can add the allow_other option.


    Otherwise you can adjust FUSE configuration (/etc/fuse.conf) and add the option there.


    And yes, it will be available via SMB!

    Postfix wasn't fully working yet with the test version.
    You have to add a specific service to the systemd file.

    I fixed the issue by adding a new line

    Code
    Before=postfix@-.service


    More info here.


    I have solved both Postfix and nginx doesn't exist/exist emails, while sending a test email to verify Postfix is alive.

    Thanks again to wenzhuo for the help. You are a master!


    I have tested it and this this fixes two issues:

    • Postfix getting stuck (worked around with a scheduled service reboot after system boot)
    • Email about nginx does not exist/exists (which I could not workaround)


    Edit the folder2ram_startup.service systemd: systemctl edit folder2ram_startup.service --full


    Add the following to the [Unit] section

    Code
    RequiresMountsFor=/var
    Wants=tmp.mount
    Before=monit.service rrdcached.service minidlna.service nginx.service nmbd.service

    It should look like this


    Code
    [Unit]
    Description=folder2ram systemd service
    After=local-fs.target
    After=blk-availability.service
    DefaultDependencies=no
    RequiresMountsFor=/var
    Wants=tmp.mount
    Before=monit.service rrdcached.service minidlna.service nginx.service nmbd.service

    Save and reboot.

    ENJOY!

    Hi,

    Yesterday I received a scrub report notification for each of my disks:


    Code
    Scrub report of the file system mounted at /srv/dev-disk-by-uuid-7e5bf71c-c945-4bea-8f96-6ebe8545198d [UUID=7e5bf71c-c945-4bea-8f96-6ebe8545198d]
    
    Scrub device /dev/sda (id 1) done
    Scrub started:    Sat Jun 14 11:46:18 2025
    Status:           finished
    Duration:         5:44:44
    Total to scrub:   4.73TiB
    Rate:             239.40MiB/s
    Error summary:    no errors found

    I've previously set the variable OMV_BTRFS_SCRUB_ENABLE to NO, but it still ran.


    Code
    omv-env get | grep OMV_BTRFS
    OMV_BTRFS_SCRUB_ENABLE=NO


    What should I do to disable it?


    I am using SnapRAID which has built-in scrub feature, that's why I don't want another one.


    Thanks!

    did anyone find a fix for this? I run two OMV7 servers on similar but slightly different hardware. One of my servers send email notifications fine, the other one hangs and does not send notifications until I run `sudo systemctl restart postfix` and then I get a flood of emails.


    The only thing that is really different (and how I started noticing it) was I run this snapraid script https://github.com/auanasgheps/snapraid-aio-script by auanasgheps but I am not sure if that is the cause of the issue.


    any help is appreciated, happy to provide further information.

    My script only uses the current OMV Postfix configuration, so it doesn't make any changes regarding email.


    I am seeing the same issue with postfix (emails not being sent) , because I'm running the flashmemory plugin. If you are too, unfortunately this is to be expected with OMV7 (don't know why, OMV6 worked flawylessly with this plugin).

    More info can be found here.

    The workaround for me is to set a cron job on restart to 60 seconds:


    Code
    sleep 60 && systemctl restart postfix



    To be honest I'm evaluating the replacement of my USB thumb drive with a USB SSD so I can discard the plugin.

    Hi, I am hijacking this thread just to make ryecoaaron aware that I've found another issue related to the flashmemoryplugin:


    It's just an alert, the service doesn't get stuck like postfix, but I wanted to make you aware.

    I meant the docker storage field on the Settings tab in the Compose plugin. If you leave it blank, the plugin won't change daemon,json. Then you can just manually edit daemon.json instead of trying to add saltstack code.

    Allright, I can go with this approach!


    The salt code itself is working, but I'm sure I'm doing something wrong since the Compose plugin isn't applying it (albeit no errors are displaied right now)

    Unless you leave the docker storage blank. Then the plugin/salt doesn't touch the daemon.json file.


    If your code posted is the code you are using, the formatting is causing the problem.

    And yes, the docker storage has been added to the Compose config, since I'm using a NVMe for Docker but the system is run from a slow thumb drive.


    The code I posted is exactly the one I'm using, with the exception of real paths to cert files.

    I've tested it locally and it works if I execute


    Code
    salt-call --local state.sls omv.deploy.compose.60docker-tls
    systemctl restart docker.service


    So what formatting should I check?

    EDIT: woops, the copy paste didn't work correctly, let me fix that. The code is now updated with the actual one I'm using.

    Hi,

    I'd like to add TLS config to the Docker daemon, because I have a Docker container that uses such API to get some data.


    The Compose plugin doesn't have this option and it overrides any configuration to /etc/docker/daemon.json as expected.


    I'm aware it's an advanced config so I'm not asking to expose it in the GUI.


    I'm trying to add it via a Salt config, but I'm doing something wrong.


    I created the file /srv/salt/omv/deploy/compose/60docker-tls.sls

    With this content:


    The file is picked up by the compose plugin during the save process, because earlier on I was using a wrong syntax and was throwing an error.
    Now it doesn't error out but it simply doesn't apply the configuration.

    Can you help on this?

    Hi,

    Few weeks ago I've done a fresh install of OMV 7 on my main system. Since then I am receiving nginx alerts at every start up.

    They are two and are always delivered together:


    So it seems that it recovers, but I'd like to fix the issue.


    This issue is very similar to this thread, but it's not the same.


    I am running the flashmemory plugin which is causing issues to postfix (apparently fixed with a delayed restart of the service)


    OMV version is: 7.7.7-1


    Here's my systemd-analyze blame output:


    Sorry for the spam, but the solution unfortunately is not reliable, I can't get postfix to work reliably.
    I've done another reboot and it's stuck: