Posts by winksmith

  • software failure screen arises often when I leave myself logged in

    Thanks, but that sounds difficult without a datetime. I don't know when it happens. There is no 503 in any of the logs. I don't know what would create a 503 error as I'm not familiar with any of the code. What should I be looking for? I mean the following might be it, but how would I know?


    I'm just an ordinary Joe who randomly sees a fail screen.

    Bash
    $ zgrep -w 503 /var/log/nginx/* || echo not found
not found

    This might be in the right time? dot.10 is my desktop and "nas" is my omv host.

    Quote

    2023/11/14 17:31:38 [error] 1443#1443: *2257789 FastCGI sent in stderr: "PHP message: PHP Warning: Unknown: Headers already sent. You cannot change the session module's ini settings at this time in Unknown on line 0" while reading response header from upstream, client: 192.168.1.10, server: openmediavault-webgui, request: "POST /rpc.php HTTP/2.0", upstream: "fastcgi://unix:/run/php/php7.4-fpm-openmediavault-webgui.sock:", host: "nas", referrer: "https://nas/"

  • software failure screen arises often when I leave myself logged in

    Hi Team.


    I leave myself logged in to my OMV6 instance regularly. After a few days I get the red "Software Failure" screen while I've been redirected to the "/#/503" URI. When this happens, I just delete the "#/503" from the URI and hit enter and it continues to work normally.



    This has always happened from day one of installation, but I've just ignored it. It's just a nuisance after all. But at this point, I thought I'd ask a question about it before reporting it as a bug.


    Why does this always happen?

  • latest upgrade and SMB no longer working - no protocol supported

    I've been keeping up to date with versions. The latest update seemed to cause my SMB to stop working. Many log entries:


    Attached is my sysinfo.


    I didn't make any changes to volumes or SMB recently. I've been working SMB quite hard up until this failed yesterday. "No protocol supported" seems to be a new error. Just trying to attach to a disk causes the messages above to happen.


    Was a configuration changed, or do I have to change a configuration for my smbd to continue working with the latest version?

  • named SSL certificates

    I have self created SSL certificates (System -> Certificates -> SSL), but it's just a string of non-useful letters and numbers. If there's more than one, it gets clumsy really fast. I would find it more useful if I could add an arbitrary note to it that describes what the certificate is for in free-form commentary.


    Also, just having the certificate named is partly useful, but if I could set the filename of the certificate on disk would also be really handy. Otherwise, it's up to me to figure out that openmediavault-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.key is actually the file I want. Now imagine that there are 10 of those filenames. I'm not quite sure how I'm gonna handle that.


    And while I'm thinking about certificates, it might be handy to also be able to import "real" signed by active SA's certificates and store them within the system.

  • postfix docker instance conflicts with OMV postfix instance

    Quote from votdev

    OMV can send emails, so Postfix makes sense.


    And what about all those Linux userland apps that are using smtp to send notifications, e.g. monit, smartd, mail, ...? Postfix was choosen with reason.

    Postfix does receive mail locally on 127.1:smtp which is exactly what monit, smartd, mail, etc. will be using (see above). I'm just wondering what other purpose is Postfix serving on OMV. I can see exactly two reasons: 1) listen on 127.1:smtp as discussed; 2) logging function (during debugging) . Were there any other functions?


    If the logging function, which doesn't seem to be mail related, can go somewhere more appropriate then it will be easy to turn off Postfix and just run the one in my docker as it too will be listening on 127.1:smtp for those requests.

  • postfix docker instance conflicts with OMV postfix instance

    I see that OMV has configured postfix to generate a log message using this linkage:

    1. master.cf listens on a unix domain socket (/var/spool/postfix/private/omvnotificationfilter)
    2. runs: /usr/share/openmediavault/notification/postfix-runner.sh
    3. runs: run-parts /usr/share/openmediavault/notification/sink.d/
    4. runs: 99Syslog
    5. runs: logger

    As far as I can see it seems to be using Postfix to listen as a non-mailing function. It also receives mail locally on 127.1:smtp (which works).


    As an enhancement to OMV, if there was another way to manage listening on a Unix domain socket instead of Postfix? First off, it just seems weird to use Postfix in this way for a non-mail function. More selfishly, I could simply turn off the OMV version of Postfix and replace with my own without any loss of functionality. Of course, I could put it into my own Postfix configuration file quite easily, but then the maintainers can't update it as I will be authoritative on that file, not the maintainers.


    From a quick glance, it seems like it can be replaced with a simple socat instance (not installed by default) or even nc -U and a service file in /etc/systemd/system to run it initially.

  • postfix docker instance conflicts with OMV postfix instance

    I had been hoping to configure OMV6 Postfix like I did for OMV3, but it gets updated regularly, and rightly so I suppose. I asked around, did some digging, and it seems like docker is the right thing to do. I've configured a mailserver to run under OMV and fine tuning it before deployment. I see that there's a native Postfix running and listening on 127.1 with some OMV magic sauce running in it. That makes sense as OMV needs to be able to send emails and transfer to the local MTA.


    Now, I need an opinion: do I need both the OMV Postfix instance running and my own docker Postfix instance? MUA's run on other hosts (mainly) and my OMV instance houses my email accessed via IMAPS. Can I leave both of them running and how do I manage conflicts? (e.g. 127.1:25, 127.1:465, 127.1:587) or should my new instance take over all duties? Opinions wanted especially if you've gone through the same exercise as I have.


    Thanks.

  • updating postfix configuration reliably

    After reading up a bit, it seemed like like the best thing to do would be to create a docker instance for Postfix. I've gotten a lot of that worked out already, but I haven't sorted out the issues with conflicting resource usages for the Postfix already running on OMV6.


    Is it possible (or advisable) to run a docker Postfix and the local OMV6 Postfix simultaneously, or will my docker take over that function completely.

  • one bad disk stops SMART output

    Easily repeated:


    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; blockdev --getsize64 '/dev/sdh' 2>&1' with exit code '1': blockdev: cannot open /dev/sdh: No such device or address


    OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; blockdev --getsize64 '/dev/sdh' 2>&1' with exit code '1': blockdev: cannot open /dev/sdh: No such device or address in /usr/share/php/openmediavault/system/process.inc:220

    Stack trace:

    #0 /usr/share/php/openmediavault/system/blockdevice.inc(258): OMV\System\Process->execute(Array)

    #1 /usr/share/openmediavault/engined/rpc/smart.inc(103): OMV\System\BlockDevice->getSize()

    #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(666): Engined\Rpc\Smart->Engined\Rpc\{closure}()

    #3 /usr/share/openmediavault/engined/rpc/smart.inc(113): OMV\Rpc\ServiceAbstract->asyncProc(Object(Closure))

    #4 [internal function]: Engined\Rpc\Smart->enumerateDevices(NULL, Array)

    #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

    #6 /usr/share/openmediavault/engined/rpc/smart.inc(181): OMV\Rpc\ServiceAbstract->callMethod('enumerateDevice...', NULL, Array)

    #7 [internal function]: Engined\Rpc\Smart->getList(Array, Array)

    #8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

    #9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('getList', Array, Array)

    #10 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatuswV...', '/tmp/bgoutputWp...')

    #11 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))

    #12 /usr/share/openmediavault/engined/rpc/smart.inc(223): OMV\Rpc\ServiceAbstract->callMethodBg('getList', Array, Array)

    #13 [internal function]: Engined\Rpc\Smart->getListBg(Array, Array)

    #14 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

    #15 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getListBg', Array, Array)

    #16 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Smart', 'getListBg', Array, Array, 1)

    #17 {main}

  • one bad disk stops SMART output

    Unfortunately, one of my disks on an LVM has been hiccuping. It is made up of /dev/sdb and /dev/sdh. As you can see sdh is indeed having a problem.


    I/O error, dev sdh, sector 1297047552 op 0x1:(WRITE) flags 0x3800 phys_seg 1 prio class 2


    This is my problem to own. Unfortunately, it uncovers an OMV issue I think. Not sure how to report the error.


    My OMV instance has a number of other disks which continue to work. None of those disk are reported on this screen because of the one disk failure. I think the SMART status of the other disks should be reported. When this disk was not failing, it was indeed reporting useful SMART data associated with all of the disks.

  • disk I/O performance

    I see that there is no performance graphs for disk performance only for disk space used. For a NAS device it might be useful to know how well your disk bandwidth is being used.

  • multiple performance graphs for a better picture

    Whenever I see a performance graph that is different than baseline I want to see what else is associated with it. I was thinking this could be encapsulated together somehow. For instance, line up all the graphs either vertically or horizontally so I can see what CPU, memory usage, network, are associated with that same moment in time.

  • old unsupported unloved OMV (3.0) fails to upgrade

    Quote from chente

    That does not mean that it will always work out well to do so. You can do it like this if you want, but the recommendation remains the same: Disconnect data drives before installing. install OMV. Connect the data drives.

    Yes, thanks. Hopefully there won't be a next time. The problem was I had waited way too long and lost access to my upgrade path. I will endeavor not to be in that situation again.


    My current issue is OMV overwriting my postfix configuration changes. Any ideas as to how to avoid that?

  • updating postfix configuration reliably

    Is there any way to update postfix configuration reliably? Does it use a prototyping system and can I update the base file to my liking. I want the default to be use TLS, but updates seem to overwrite it. My last instance of OMV didn't have the characteristic of overwriting my configuration. Is there a way to make OMV6 keep my desired configuration? Thanks.

  • old unsupported unloved OMV (3.0) fails to upgrade

    I have an old version of OMV (Erasmus 3.0) which I want to upgrade. The obvious choice would be to just run the upgrade pathway, but it fails:

    Bash
    root@nas:~# omv-release-upgrade
Upgrading system to 4.0 (Arrakis) ...
ERROR: The script '/usr/share/openmediavault/mkconf/omvextrasorg' does not exist
run-parts: /tmp/tmp.6nd3atke1p/pre.d/21-update-omvextrasorg exited with return code 100

    It seemed to me that omvextrasorg should probably be omvextras so I just linked them together, but when I did that, OMV4 doesn't seem to be supported any longer. There doesn't seem to be a way to overcome that.


    Now apt-get fails as well whereas it was working previously.

    Bash
    root@nas:~# apt-get upgrade
Reading package lists... Done
E: The value 'stretch' is invalid for APT::Default-Release as such a release is not available in the sources

    I want to upgrade this system (and keep it up to date going forward), but it's unclear how to upgrade it at this point. Any ideas?