Beiträge von bishoptf

  • OMV 6 How long will it be continued to be supported

    Zitat von votdev

    Maintenance of OMV6 ends when Debian 11 is EOL; this means mid 2024.

    Ah, thanks for the quick reply, debian security updates through 2026 right? Am I reading this LTS page correctly - https://wiki.debian.org/LTS


    I think this one makes more sense - https://wiki.debian.org/DebianReleases


    Based on that OMV 6 updates will stop mid 2024 but will continue to get security updates until mid 2026. So YMMV if staying past that date, I am ok with just getting security updates, will let 7.x mature and upgrade at some point, thanks.

  • OMV 6 How long will it be continued to be supported

    I know OMV 7 is out but my question is in regards to OMV 6. I know it's based on I believe bullseye and that will continue to get security updates through June of 2026. I am a long time user and if happy with current features and performance is there any reason that I cannot continue to use OMV 6 until closer to EOL. I assume that I will continue to receive linux security updates but wasn't sure about the OMV bits and thought I would ask, thanks. :)

  • Uodates failed and now getting a 500 failed to execute error when trying to apply updates

    Looks like its an issue with nfs-server.service, failed to start with a dependency error...never have seen this before anyone have any suggestions?


    sudo systemctl status nfs-server.service

    ● nfs-server.service - NFS server and services

    Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled)

    Active: inactive (dead) since Wed 2023-10-11 09:03:12 CDT; 22min ago

    Process: 676336 ExecStop=/usr/sbin/rpc.nfsd 0 (code=exited, status=0/SUCCESS)

    Process: 676340 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS)

    Process: 676341 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS)

    Main PID: 1576 (code=exited, status=0/SUCCESS)

    CPU: 18ms


    Oct 11 09:03:12 dpcbackup systemd[1]: Dependency failed for NFS server and services.

    Oct 11 09:03:12 dpcbackup systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'.

    Oct 11 09:05:07 dpcbackup systemd[1]: Dependency failed for NFS server and services.

    Oct 11 09:05:07 dpcbackup systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'.

    Oct 11 09:08:31 dpcbackup systemd[1]: Dependency failed for NFS server and services.

    Oct 11 09:08:31 dpcbackup systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'.

    Oct 11 09:22:41 dpcbackup systemd[1]: Dependency failed for NFS server and services.

    Oct 11 09:22:41 dpcbackup systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'.

    Oct 11 09:25:53 dpcbackup systemd[1]: Dependency failed for NFS server and services.

    Oct 11 09:25:53 dpcbackup systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'.

    itsupport@dpcbackup:~$

  • Uodates failed and now getting a 500 failed to execute error when trying to apply updates

    Did an update and received an error, looks like when I cloned the drive a while back that something was not quite right. When trying to update kernel it had an error. I dropped to the command line and did the apt update and it was asking for grub location which I identified but I am still getting the error message in OMV when trying to apply the updates.


    Here is the message:

    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=; omv-salt deploy run --no-color nfs 2>&1' with exit code '1': dpcbackup.dpc.lan:

    ----------

    ID: configure_default_nfs-common

    Function: file.managed

    Name: /etc/default/nfs-common

    Result: True

    Comment: File /etc/default/nfs-common is in the correct state

    Started: 09:05:03.208024

    Duration: 371.724 ms

    Changes:

    ----------

    ID: configure_default_nfs-kernel-server

    Function: file.managed

    Name: /etc/default/nfs-kernel-server

    Result: True

    Comment: File /etc/default/nfs-kernel-server is in the correct state

    Started: 09:05:03.580151

    Duration: 367.73 ms

    Changes:

    ----------

    ID: configure_nfsd_exports

    Function: file.managed

    Name: /etc/exports

    Result: True

    Comment: File /etc/exports is in the correct state

    Started: 09:05:03.948279

    Duration: 356.435 ms

    Changes:

    ----------

    ID: start_rpc_statd_service

    Function: service.running

    Name: rpc-statd

    Result: True

    Comment: The service rpc-statd is already running

    Started: 09:05:07.254862

    Duration: 127.635 ms

    Changes:

    ----------

    ID: start_nfs_server_service

    Function: service.running

    Name: nfs-server

    Result: False

    Comment: A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.

    Started: 09:05:07.385794

    Duration: 219.404 ms

    Changes:


    Summary for dpcbackup.dpc.lan

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

    Succeeded: 4

    Failed: 1

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

    Total states run: 5

    Total run time: 1.443 s

    [ERROR ] Command '/bin/systemd-run' failed with return code: 1

    [ERROR ] stderr: Running scope as unit: run-rf5f2b9fab564413b99925345b8f24f0b.scope

    A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.

    [ERROR ] retcode: 1

    [ERROR ] A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.


    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=; omv-salt deploy run --no-color nfs 2>&1' with exit code '1': dpcbackup.dpc.lan:

    ----------

    ID: configure_default_nfs-common

    Function: file.managed

    Name: /etc/default/nfs-common

    Result: True

    Comment: File /etc/default/nfs-common is in the correct state

    Started: 09:05:03.208024

    Duration: 371.724 ms

    Changes:

    ----------

    ID: configure_default_nfs-kernel-server

    Function: file.managed

    Name: /etc/default/nfs-kernel-server

    Result: True

    Comment: File /etc/default/nfs-kernel-server is in the correct state

    Started: 09:05:03.580151

    Duration: 367.73 ms

    Changes:

    ----------

    ID: configure_nfsd_exports

    Function: file.managed

    Name: /etc/exports

    Result: True

    Comment: File /etc/exports is in the correct state

    Started: 09:05:03.948279

    Duration: 356.435 ms

    Changes:

    ----------

    ID: start_rpc_statd_service

    Function: service.running

    Name: rpc-statd

    Result: True

    Comment: The service rpc-statd is already running

    Started: 09:05:07.254862

    Duration: 127.635 ms

    Changes:

    ----------

    ID: start_nfs_server_service

    Function: service.running

    Name: nfs-server

    Result: False

    Comment: A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.

    Started: 09:05:07.385794

    Duration: 219.404 ms

    Changes:


    Summary for dpcbackup.dpc.lan

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

    Succeeded: 4

    Failed: 1

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

    Total states run: 5

    Total run time: 1.443 s

    [ERROR ] Command '/bin/systemd-run' failed with return code: 1

    [ERROR ] stderr: Running scope as unit: run-rf5f2b9fab564413b99925345b8f24f0b.scope

    A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.

    [ERROR ] retcode: 1

    [ERROR ] A dependency job for nfs-server.service failed. See 'journalctl -xe' for details. in /usr/share/php/openmediavault/system/process.inc:242

    Stack trace:

    #0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()

    #1 /usr/share/openmediavault/engined/rpc/config.inc(178): OMV\Engine\Module\ServiceAbstract->deploy()

    #2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)

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

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

    #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(620): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusIQ...', '/tmp/bgoutput2m...')

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

    #7 /usr/share/openmediavault/engined/rpc/config.inc(199): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)

    #8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)

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

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

    #11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)

    #12 {main}

  • OMV 6 GUI not showing updates when they are available

    Following up, looks like something went sideways so here is what I did since it appeared that the omv-mkaptidx was borked since I had 2 copies, looking at my other installation I could make out that the one from Feb was the one that I wanted so I did this:


    #mv /usr/sbin/omv-mkaptidx /usr/sbin/omv-mkaptidx.old

    # mv /usr/sbin/omv-mkaptidx.real /usr/sbin/omv-mkaptidx


    and now running omv-mkaptidx works as expected, I think I should be good now...:)


    Eh...I think I am good now...:)

  • OMV 6 GUI not showing updates when they are available

    Looks like I have something similar to that issue posted above, when I run omv-mkaptidx I get no output and looking in the directory I see this:


    root@dpcbackup:~# ls -l /usr/sbin/omv-mkapt*

    -rwxr-xr-x 1 root root 17 Oct 22 2022 /usr/sbin/omv-mkaptidx

    -rwxr-xr-x 1 root root 9418 Feb 24 05:54 /usr/sbin/omv-mkaptidx.real


    I think something went sideways maybe during one of my upgrades, just looking to figure out what to do at this point to correct the issue, thanks.

  • OMV 6 GUI not showing updates when they are available

    I am still having this issues, not a major issue but I have a couple of OMV installations and one of them will not show or notify me when I have updates waiting from the GUI. One works as it should and the other one does not, same version 6.x. I can always drop to the command line and update/upgrade that way but would be nice to get it working as intended, if anyone has any suggestions on where or what to look at that may clear the issue just let me know.


    Screenshots attached, thanks. :)


    Looks like this is the same issue but I am not sure what corrected the issue and what I need to do, if anyone has any insight please let me know, lol...


    Updates not visible in WebUI · Issue #1398 · openmediavault/openmediavault
    Please only open an issue here, when advised by a moderator in openmediavault forum. My report did not have any response so reporting here. Describe the bug…
    github.com

  • OMV 6.x not showing any updates from GUI

    Zitat von votdev

    Maybe have a look here.


    Beitrag
    OMV5 upgrade to 6 not executed
    Hello,

    I tried to upgrade from 5 -> 6 using the command omv-release-upgrade.
    Ater the command finishes it tells me the upgrade has completed successfully, however the last line of code shows:
    0 upgraded, 0 newly installed, 0 to remove and 726 not upgraded.

    Upon reboot, I'm still on version 5 and debian hasn't upgraded. I'm still able to login and all shares & docker are working.
    However, when performing the command omv-release-upgrade. it hangs after updating the repositories. Also, apt…
    wouterve

    Yeah I've upgraded and I am running 6.x, everything appears to be working fine but it's not pulling updates from the GUI from 6.x. I was up and running for 4+ months and from the GUI it said I had no updates, apt-get showed plenty including kernel updates, just not from the GUI. Wasn't sure if there was something that I could look at to see why the GUI updates was not working properly.

  • OMV 6.x not showing any updates from GUI

    I upgraded a few months back from 5.x and everything appears to be working fine but I noticed today that no updates are shown from the GUI. If I drop to the CLI it shows updates available but not from the gui, been up for 4 months, did the update from the cli but wondering how I can fix the gui to start showing the updates, thanks.

  • WOL Failed to Scan - Failed to execute....

    Zitat von ryecoaaron

    6.1.3 in the repo. It will use the default adapter in the output of ip route show.

    welp...I had fun upgrading from 5.x to 6.x, I mean I cloned my ssd to a new ssd and the dang bond interface wouldn't start, I am still scratching my head on that one. Put the old one back and the bond interfaced worked fine, not sure WTH would make it change but it was changing the interface names from ethx to the new naming format, instead of trying to fight it just updated the interfaces configuration with the new names and restarted networking and the bond interface came back online fine, smh. Upgraded to 6.x and clean up all my old kernels, I still had 3.x kernels listed, lol. Went to WOL and maybe you updated before I updated since it WORKS...lol. Doesn't ask me for an interface and scan did its thing, AWESOME.


    I tried waking up a machine and that worked also, so the only thing that I would like to do if possible, is to be able to scheduled the scans like once a hour etc. I didn't see a way to do that, would that be a pain to add, since most machines are off and on, I just need to do multiple scans to pick everything up.


    Really appreciate all the help, let me know what you think, thanks again. :)

  • WOL Failed to Scan - Failed to execute....

    Ok, well let me know if there is something I can do to help debug some more, hoping I can upgrade this to 6.0 and have it go smoothly, just going to shut the system down, clone the drive and go from there...thanks for the help.

  • WOL Failed to Scan - Failed to execute....

    Zitat von ryecoaaron

    The output around this line is what I need. Can you attach all of the output in a file?

    File is attached...What do I need to do in order to stop the debug from continuing. I am going to ride up to one of the areas I support and see about upgrading the Nas from 5.x to 6.x, so I will be out of pocket for awhile depending on how that goes, lol. Oh, one more thing, I just noticed the matrix welcome screen, that is awesome ( I know im a simpleton and it doesnt take much) but how do I keep that to the the welcome screen all the time. :)

  • WOL Failed to Scan - Failed to execute....

    Zitat von ryecoaaron

    That makes me happy : ) No windows here either.

    First off I see a lot of this, repeated over and over:

    Code
    mv-engined[418180]: RPC response (service=System, method=getInformation): {"response":{"ts":1666445016,"time":"Sat 22 Oct 2022 08:23:36 AM CDT","hostname":"omv-plex.wareagle.lan","version":"6.0.42-2 (Shaitan)","cpuModelName":"Intel Core Processor (Skylake, IBRS)","cpuUsage":1.5151515151515151,"memTotal":"2077188096","memFree":"586473472","memUsed":"355704832","memAvailable":"1543663616","memUtilization":"0.25684","kernel":"Linux 5.18.0-0.bpo.1-amd64","uptime":1296120.73,"loadAverage":{"1min":0.11,"5min":0.08,"15min":0.03},"configDirty":false,"rebootRequired":false,"pkgUpdatesAvailable":true},"error":null}
omv-engined[418180]: 
omv-engined[416771]: SIGCHLD received ...
omv-engined[416771]: 
omv-engined[416771]: Child (pid=418180) terminated with exit code 0
omv-engined[416771]: 
omv-engined[418191]: Child process forked (pid=418191)
omv-engined[418191]: 
omv-engined[418191]: Executing RPC (service=System, method=getInformation, params=null, context={"username":"admin","role":1}) ...


    Here is where I think I kicked off the scan:


    then I see this

    Code
    Executing RPC (service=Wol, method=doScan, params={"deviceName":"enp1s0"}, context={"username":"admin","role":1}) ...
omv-engined[418249]: 
omv-engined[418252]: Child process forked (pid=418252)
omv-engined[418252]: 
omv-engined[418252]: Executing RPC (service=System, method=getInformation, params=null, context={"username":"admin","role":1})
omv-engined[418252]: RPC response (service=System, method=getInformation): {"response":{"ts":1666445041,"time":"Sat 22 Oct 2022 08:24:01 AM CDT","hostname":"omv-plex.wareagle.lan","version":"6.0.42-2 (Shaitan)","cpuModelName":"Intel Core Processor (Skylake, IBRS)","cpuUsage":0.5,"memTotal":"2077188096","memFree":"579473408","memUsed":"362541056","memAvailable":"1536823296","memUtilization":"0.26014","kernel":"Linux 5.18.0-0.bpo.1-amd64","uptime":1296145.42,"loadAverage":{"1min":0.07,"5min":0.08,"15min":0.02},"configDirty":false,"rebootRequired":false,"pkgUpdatesAvailable":true},"error":null}
omv-engined[418252]: 
omv-engined[416771]: SIGCHLD received ...
omv-engined[416771]: 
omv-engined[416771]: Child (pid=418252) terminated with exit code 0

    But I do not see much else, I did receive a 504 on the screen..Not sure what you are looking for or if I captured it..

  • WOL Failed to Scan - Failed to execute....

    Zitat von ryecoaaron

    sudo monit stop omv-engined

    sudo omv-engined -df


    No log file. Everything is logged to screen. If you are using putty, make sure to set your line buffer higher or you can have putty log to a file.

    Eh, lol, putty....I'm one of those rare animals...I don't so windooze unless someone pays me to use it...long live linux...:) Been using it since windows xp days, even have the wife using it, lol. It will be an SSH session for sure so should not be an issue.

  • WOL Failed to Scan - Failed to execute....

    Zitat von ryecoaaron

    504 doesn't really tell me anything. If you could do that with the omv-engined in debug, that would help. And the command is running as root.

    I ahve no issue doing that but not sure I know how to run it in debug, I did a quick google search and nothing jumped out at me, have a pointer to a page that lets you know how to do that. Once running in debug is there a log file or something that I can use to provide?


    Thanks

  • WOL Failed to Scan - Failed to execute....

    Zitat von ryecoaaron

    The code should be identical between 5.x and 6.x - https://github.com/OpenMediaVa…/engined/rpc/wol.inc#L173

    Which plugin? Did you ctrl-shift-R?

    Yeah I looked at the code, I see the section but that stack trace above I only see the -m, so not sure why its not working, I know it doesnt work from the cli with just the -m option since it looks at the first interface and fails but if i give it sudo nast -m -i bond0 then it goes to work, 6.x just gives me 504 errors. Now I do know when I run it from the cli I have to run it with elevated privs, it will not run without being root.


    I figured out my other issue with the backup stuff, still need to get my head wrapped around that, so used to using clonezilla to do stuff but would be nice to back up the FS routinely.

  • WOL Failed to Scan - Failed to execute....

    Zitat von ryecoaaron

    I'm confused. The plugin is using the -m flag and -i if there is a network adapter selected. https://github.com/OpenMediaVa…/engined/rpc/wol.inc#L173

    Understand but at least on 5.5 its not working with a bond interface, the stack trace that I included in the first post I see the -m option being used but do not see the -i option, I know it works from the cli though with both the -m and -i options. But again since that is running 5.x its not going to get updated, I have not upgraded the bond interface unit to 6 yet, that is my next goal.


    Was going to try to do the fsarchiver and have a clone but having problems getting it working on my omv 6 installation, I installed the plugin and got a 504 error, it thinks its installed but I cannot find it in the menu anywhere so still trying to figure out where it places it.

  • WOL Failed to Scan - Failed to execute....

    Zitat von ryecoaaron

    Ah so you don't normally need the scan import. You just need it now because the button is not working. Cutting and pasting them into the OMV database won't work since the database is xml. I will try to get it working again but I just haven't had any time.

    Yeah no worries, understand its not used so it should be way down on the priority list. I need to work on upgrading to 6.x so I have plenty of other things to work on so if you get to it great if not no problem, appreciate all you guys have done to have a stable nas solution.

  • WOL Failed to Scan - Failed to execute....

    Zitat von ryecoaaron

    What is the use case? There is no file upload component in OMV 6.x. Are you editing the file and then want to import? I guess I don't see why that is different than clicking the button and editing the systems. I understand that it isn't as fast but I never really thought people would do it that often. This plugin isn't used by very many people.

    Yeah my use case is I support small business remotely and use WOL a lot for support purposes. right now since I cannot scan the only way to add the systems is to add them one at a time which I can do, but I have what I consider a handful, 20-30 devices at least. I am able to run the nast utility and get export to a file I just would like to import a whole list vs one at a time. The other option is if you can tell me which configuration file keeps that information then I can just go add them there by cut and paste etc, just looking for an easier way to import my list. Thats probably the better answer since its not used much not worth you spending much time on it, if you can point me to where the added ones are stored I will look into doing that.


    Thanks