Posts by dildano

I uninstalled the original flashmemory plugin, rebooted, and installed the latest test version. Output looks the same:

ii  folder2ram                           0.4.0                               all          script-based utility to manage tmpfs folders
ii  openmediavault                       7.5.0-1                             all          openmediavault - The open network attached storage solution
ii  openmediavault-cputemp               7.0.2                               all          cpu temperature plugin for openmediavault
ii  openmediavault-fail2ban              7.0.1                               all          OpenMediaVault Fail2ban plugin
ii  openmediavault-flashmemory           7.1                                 all          zram-config plugin for openmediavault
ii  openmediavault-keyring               1.0.2-2                             all          GnuPG archive keys of the openmediavault archive
ii  openmediavault-mergerfs              7.0.5                               all          mergerfs plugin for openmediavault.
ii  openmediavault-omvextrasorg          7.0                                 all          OMV-Extras.org Package Repositories for OpenMediaVault

Everything seems to be working fine.

Quote from ryecoaaron

You didn't want to post all the output?

My bad! Here you go...

ii  folder2ram                           0.4.0                               all          script-based utility to manage tmpfs folders
ii  openmediavault                       7.5.0-1                             all          openmediavault - The open network attached storage solution
ii  openmediavault-cputemp               7.0.2                               all          cpu temperature plugin for openmediavault
ii  openmediavault-fail2ban              7.0.1                               all          OpenMediaVault Fail2ban plugin
ii  openmediavault-flashmemory           7.1                                 all          zram-config plugin for openmediavault
ii  openmediavault-keyring               1.0.2-2                             all          GnuPG archive keys of the openmediavault archive
ii  openmediavault-mergerfs              7.0.5                               all          mergerfs plugin for openmediavault.
ii  openmediavault-omvextrasorg          7.0                                 all          OMV-Extras.org Package Repositories for OpenMediaVault

Should have also included this:

ii  openmediavault-flashmemory           7.1                                 all          zram-config plugin for openmediavault

Quote from ryecoaaron

What is the output of: dpkg -l | grep -E "openme|folder2ram"

ii  folder2ram                           0.4.0                               all          script-based utility to manage tmpfs folders

I applied the latest version to one of my RPI's, and it seems to be working so far. After rebooting, I triggered a couple of test notifications, and they came through immediately. I applied the new version on top of the old one (v7.0.1), and it appeared to properly uninstall the previous version before installing. Having said that, the old version still appears to be installed in Plugins. I'll keep testing, and if notifications stop working, I'll perform a proper uninstall of the old version and reinstall of the new version.

Interestingly, my other RPi seems to be working OK without the new version. The only real difference between the two is that one has 4GB RAM while the other has 8GB. Otherwise, they are both RPi 4's running completely up-to-date OMV instances.

Thanks ryecoaaron for the instructions and continued assistance.

How does one install the test version? I no longer see a test repo option. I'm happy to test.

Yes, I may have to go back to using NVMe drives in USB enclosures.

ryecoaaron Thanks for the info. Yeah, log2ram only redirects /var/log to RAM, but I suppose that's better than nothing.

After reading through this thread, I realized that I'm having the same issue on my two RPi OMV installs. gderf Did you create thread about the issue with the flashmemory plugin by any chance? I suppose that an alternative is to use log2ram rather than the flashmemory plugin. That's what I use on my RPi Pi-holes.

Thanks for the confirmation. I'll switch over to my Gmail account for notifications.

I've been using Hotmail/Outlook for my e-mail notifications in OMV for years, and they recently stopped working on my NAS. I'm fairly certain that it's because Microsoft has disabled basic authentication which means that even "app passwords" no longer work (yes, I tried a new app password). The log entry looks like this:

postfix/smtp[571250]: 270E81C40798: to=<intentionallyremoved@hotmail.com>, orig_to=<root>, relay=smtp-mail.outlook.com[40.97.212.6]:587, delay=243829, delays=243818/0.1/11/0, dsn=4.7.139, status=deferred (SASL authentication failed; server smtp-mail.outlook.com[40.97.212.6] said: 535 5.7.139 Authentication unsuccessful, basic authentication is disabled.

I believe that Google has also disabled basic authentication for Gmail accounts. Is there any way to get the OMV notifications to work with OAuth? Is there some other solution other than using an e-mail provider with weak security?

Thanks.

Quote from ryecoaaron

if xrdp is running on the guest, you should be connecting to the guest's IP address UNLESS you are using NAT.

OK, I understood it correctly, and there's just something on my LAN preventing access. I'm clearly not a networking expert. Time to try out a bridge. Thanks for the help.

Quote from ryecoaaron

When you use spice, you only need to connect to the host. The spice service is connecting directly to the spice component of the VM without involving networking.

Just to be clear, for xrdp, I should be connecting to the IP of the host, correct? So let's say the host is 192.168.1.10 and the VM is 192.168.122.100. I'm connecting to 192.168.1.10:3389, right? Neither one works for me. Obviously, the host is accessible on my LAN because it's my NAS, and my Windows PC is on the same subnet (192.168.1.9). I feel like I'm just missing something really obvious.

Quote from ryecoaaron

You really should convert to a bridge. There are instructions on how to do that in the kvm guide.

Thanks. I'll try this. I don't think the KVM guide existed when I set all this up initially. Took me forever to figure it out. Spice works fine, but I just can't get xrdp working.

Quote from ryecoaaron

Can you telnet from another machine to port 3389?

No, I get "connect failed" when I try to telnet to 3389 on my host. And other than your bridge interface, I don't see any significant differences in our configs. I don't have any firewall rules on my host, so I don't know what would be blocking 3389.

Edit: Definitely something weird going on. I can't ping my Windows PC from the Debian VM either. It's like NAT isn't working at all.

Quote from ryecoaaron

Yep. I have an Ubuntu 22.04 VM that I use xrdp on every day. I also have a Windows 10 Pro VM that I use every once in a while. I'm using a bridge on them but pretty sure I used to use NAT and was able to connect from a machine other than the host.

Did you have to do anything special on the host or in the KVM setup for the VM? This is driving me crazy.

Quote from ryecoaaron

kvm does not care what you install on the VM. I run xrdp on many VMs.

Ryecoaaron, are you running xrdp on VMs using KVM? I've never been able to get it to work. I just loaded a fresh Debian 11 VM using the default network (NAT). The xrdp service is running on the default port (3389), and there's no firewall (ufw) loaded on the VM. When I try to connect from a Windows machine (to the host IP), it fails. Is there some configuration change I need to make to allow traffic through to the VM?

Thanks.

I ran into the same issue when trying to set up a mergerfs pool of eight disks. I got the "file name too long" error. After digging into the mergerfs documentation a bit, I decided to try "globbing". Try this as the path in the plugin:

/srv/dev-disk-by-uuid-*

It's working for me, and created the mount point under /srv/mergerfs/<name of pool>. Of course, this may not work for you if you have disks that you don't want to include in the pool since it uses a wildcard. I can only guess that there is an issue with the plugin with a character limitation or something since this worked fine in OMV5.

I got it to work with the --no-auth command. Here's my Docker compose section:

portainer:
    container_name: portainer
    environment:
        - PGID=1000
        - PUID=1000
    image: portainer/portainer
    networks:
        - lan # Pre-defined Docker network
    ports:
        - 9000:9000
    command:
        - "--no-analytics"
        - "--no-auth" # I needed to put it on a separate line
    restart: always
    volumes:
        - '/etc/localtime:/etc/localtime:ro'
        - '/var/run/docker.sock:/var/run/docker.sock'
        - '/config/portainer:/data'

This is nice because I can use http auth via my LetsEncrypt container, and I don't get hit with another authentication prompt.

Well, the new Portainer container is working fine, but the --no-auth command did not work at all. At least I can control the config now, and I'll do some more research. Thanks for the help.