OMV 4 ready (almost) for production?

is this issue already resolved? Error: "Failed to read file '/tmp/bgstatusfs2WVj' (size=0)."

simply refresh the action you were doing. This will go fine.
Had the same error, and force it by refreshing the action. No probleme so far.

fresh install arrakis 17.1 -- extra-plugins install via openmediavault-omvextrasorg_latest_all4.deb hit button and Error: "Failed to read file '/tmp/xxxxxxxxxxxxx' (size=0)

Hi, I'm having some trouble with my OMV3 installation, so I was thinking about create a totally new installation of OMV4.
I'll use:

• plex
• deluge
• a classid RAID1
• a ZFS mirror
• autoshutdown and wake up plug-in
• sonarr

Is OMV4 already stable for this things?

I would say yes, ( between omv3 et 4 just some plugins were left over due to deprecation ... )

- seem plex works
- not sure for deluge
- classic rais 1 ok ( 0 5 6 10 available too )
- ZFS as plugin OPENMEDIAVAULT-ZFS 4.0
- cron job can do it for you
- there is some message about sonar those day ...

thanks for the answer!
- Plex is the most important plug-in for me, but in the worst case I can just install it normally and run it as root
- Same as Plex
- Great
- I asked in the ZFS thred, I thought it was better
- cron job made by myself never worked so I use autoshutdown and scheduled wakealarms
- which kind of messages?

Also I forgot about those plug-ins:
- USB Backup
- Radarr: not really important
- flashmemory: since I'll buy an SSD it should not be necessary

i read a thread with somebody having some troubles with sonar ...

USB backp OK
Radarr don't know
flashmemory of course !!

Thanks a lot I'll go for OMV4 as soon as I'll find a cheap SSD

Zitat von stratege1401

fresh install arrakis 17.1 -- extra-plugins install via openmediavault-omvextrasorg_latest_all4.deb hit button and Error: "Failed to read file '/tmp/xxxxxxxxxxxxx' (size=0)

I can report the same. Fresh install of Debian and arrakis 17.1 under VMWare ESXI. I thought it was due to the ESXI setup.
What is interesting, my direct installation of Debian and arrakis 16.1 (upgraded from OMV3 and Debian8) does not show this Error.

I had the same error within XEN and VirtualBox, each with a fresh OMV4. Have not tested much in the last two weeks.

if not fix, is there any known workaround for the issue? some people here seem to live with it happily, while for me the whole omv was unusable, as i could not apply any changes in the webui...