Beiträge von reynard80

    I have freshly installed OMV 4 on a fresh Debian Stretch 9.3.0. However, most of the times I install or update a package I receive an error about a Python exception at the end of the apt procedure. I'm not sure it actually creates problems for the workings of the system, but I'd like to correct this message if possible.


    Edit: I see that's it a bug in the python version. I tried the manual fix as mentioned in that thread, but it also says in the thread that it didn't help anymore for newer versions. Let's hope it works for me.


    Code
    Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f42071e46a8>
    Traceback (most recent call last):
      File "/usr/lib/python3.5/weakref.py", line 117, in remove
    TypeError: 'NoneType' object is not callable
    Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f42071e46a8>
    Traceback (most recent call last):
      File "/usr/lib/python3.5/weakref.py", line 117, in remove
    TypeError: 'NoneType' object is not callable

    Nobody?


    To be a bit more specific; after a reboot of my Windows machine, the following happens:

    • I click the shortcut the OMV server, and get the authorization popup, where I enter my credentials
    • I then get a '0x800704cf Network Error -- Network location cannot be reached'
    • I keep getting this error for a while, maybe 20-40 seconds, when I try to get to the shortcut. Sometimes I get a new authorization popup where I enter my credentials
    • Then suddenly, it seems to work, and I just get to see the samba shares

    I haven't been able to find a solution that is Windows related (and I don't have such problems with my Synology NAS and my Linux HTPC), so I'm wondering whether it has to to with the OMV installation. I'm hoping someone can provide some pointers!

    I have installed OMV3 on Debian Jessie. Now, I wanted to install some other packes from the newer Debian release, so I added stretch repositories. I did this with priority pinning, so that existing packages would be not be updated.


    However, OMV actually also shows the stretch updates for all packages in its Update Management tab. I don't want to upgrade all these packages, as these may break OMV3. Doesn't OMV look into the repository priorities? Is it possible to set a default repository for this function?

    I've installed OMV 3 on Debian Jessie, and it's working fine. There is one problem however, which is a bit strange and I can't seem to find the cause nor a solution.


    My Samba shares are working fine in essence, but when I connect to them after they haven't been used for a while, I'm getting a 'not accessible' error in Windows when I try to browse the OMV server. I then have to wait for a while (a few seconds), and try to approach the OMV server with the samba shares again; then the error is gone and the samba shares are visible.


    I can't find anything in the logs that indicates an error (not in OMV, nor in the Windows client) It almost seems like there is some power management feature going that has put the server to sleep and has to wake up or something. However, I think it's not the HDD's that are powered down, because that happens as well, and when I enter a Samba share on a spun down HDD, I have to wait while I hear the drive spinning up. So that's working without any errors.


    Some details on my system; running OMV3 on a Intel Celeron x86 machine, with an SSD as system drive and some HDD's for data. The HDD's are encrypted with the LUKS encryption plugin (could that have anything to do with it?)


    Any of you recognize what's going on and know how to fix this?


    Thanks for the great software BTW! :thumbup: