Posts by sam_scade

issue fixed in rsnapshot plugin 4.2 upgrade !

Thanks !

Hello,

This is reproducible on several OMV4.1.11 servers. Does somebody would have a idea to fix it ?

Thanks

Hello

Each time I restart a server on OMV4, lost the com with UPS :
"Communications with the UPS ond01@localhost cannot beestablished "

to get it again I had to stop an start UPS plugin

on Linux 4.17.0-0.bpo.3-amd64 / OMV 4.1.10 (Arrakis) my snmp driver configuration is

"driver = snmp-ups
mibs=apcc
port = 192.168.1.15
community = domain_users
snmp_version = v1
pollfreq = 15"

It's was not the case with the same config on OMV1,2 and 3
This issue is repetable on 5 servers upgraded on OMV4

an idea ?

Quote from ness1602

Usually you don't give more than 16GB to swap,because it loses it's purpose.

Well but I did not chose any size of swap, or I left something somewhere by default ?

it seems that debian ajust "automaticaly" or "dynamically" swap space size in function of ram size without any choice for user

where can you adjust swap space during or before OMV installation ?

Quote from ness1602

Hi,how much RAM do you have,maybe it's trying to use to much space for swap?

Yep ! ness1602 you was right !
Debian requested 34.4GB for swap
I reconfigured my Raid to let 40GB to OMV, and OMV installator accepted it !

Thanks for your help !

Quote from votdev

Hmmm, there are no exact rules, the partitioning is done dynamically depending on the size of the device. If the OMV installer fails, simply install Debian 9 and then OMV manually. See https://openmediavault.readthe…stallation/on_debian.html.

It refuses 21GB partition but approve 3TB one... some reason to this B-gluttony ?

Quote from ness1602

Hi,how much RAM do you have,maybe it's trying to use to much space for swap?

4GB, I'm going to increase that to test...oups 32GB ram and if I choose 3TB partition it is ok and it install OMV (seem too much for linux but ...;-)

it prefer HD's B not ram's B ;-))

Hello,

On a fresh server and fresh raid, OMV4.1.3 installator seems to request more than 21GB for system installation (see screenshots)

what would be the minimum required ?

Hello,

When we change a RemoteMount config the request "The changes won't take effect until you've restarted the system or manually remounted the mount"

In File Systems plugin, for the considered mount the button "Mount" and "Unmount" are not accible.

So "manually" means "use console" ?

I got it too, job seems be well done...

Can you confirm it is just omv gui issue ?

Hello

just an observation if it could help :

1/ no conflict when I mount server with smb to two clients (one in OMV4 and the other in OMV2)

Ok, fresh install of OMV only or fresh install of OMV + Linux (=format my server) ?

In first case how to uninstall OMV ? like this https://forum.openmediavault.o…-OMV-from-a-Debian-Linux/ ?

Ok, thanks
just to inform you about that : all of my 5 servers omv <=3.x use upper case letters for UPS identifier. This is the first time I see this pattern limitation with 4.x

is it possible to upgrade from 1.x or 2.x directly to 4.x ?

Or i have to reach each version to last one ?

just because when I upgrade my servers this make a error because i named my UPS with capital letters in OMV1,2,3

Hello

Why OMV4 prohibits capital letters for UPS identifer pattern ?

Thanks in advance

Hello

1/ I confirm the conflict

if I share the same folder of a one OMV1 server to two clients (one in OMV4 and the other in OMV2) none of clients can mount (with Remote Mount Plugin for OMV4 and by Remote Share Plugin for OMV2) the NFS shared folder.

if I share the folder to only one of the 2 clients (OM4 or OMV2) it works perfectly wich ever the OMV version.

2/ On my olf bkup02 (OMV4) "grep nfs /proc/mounts" return for SRVDATA (OMV1)

root@SRVBKUP02:~# grep nfs /proc/mounts
192.168.1.31:/Data2 /srv/d696ac7e-49c8-49ef-b3d6-5dbd98a60a25 nfs4 rw,relatime,vers=4.2,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,timeo=14,retrans=2,sec=sys,clientaddr=192.168.1.26,local_lock=none,addr=192.168.1.31 0 0
192.168.1.30:/_RacineDATA /srv/4141ea0b-24fc-4995-aca0-53307337ce33 nfs4 rw,relatime,vers=4.0,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,timeo=14,retrans=2,sec=sys,clientaddr=192.168.1.26,local_lock=none,addr=192.168.1.30 0 0
192.168.1.30:/_RacineDATA /sharedfolders/imRM_SRVDATA nfs4 rw,relatime,vers=4.0,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,timeo=14,retrans=2,sec=sys,clientaddr=192.168.1.26,local_lock=none,addr=192.168.1.30 0 0

Some more informations :

History :
I have srvbkup01 on OMV2 wich work since long time to mount 2 or 3 servers to backup tehm.

In parallel to gradualy upgrade to omv4, I installed a new one srvbkup02 on omv4 we are talking about.

In fact un mount same servers from bkup01 AND bkup02, so I declared on NFS of each server the bkup servers.

1/ It seems that create a conflict. To allow bkup01 to mount again the servers I have to delete bkup02 declaration in NFS of servers

2/ On my olf bkup01"grep nfs /proc/mounts" return nfs4 too ??? what this version of nfs4 do there ? why it is not nfs or nfs2 or 3 ?????

"root@srvbkup01:~# grep nfs /proc/mounts
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
192.168.1.30:/_RacineDATA /media/cdb10136-d108-42cd-973c-35578ea154b7/im_racineSRVDATA nfs4 rw,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto =tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.25,minorversion=0,local_lock=none,addr=192.168.1.30 0 0
192.168.1.33:/DIRRACINE /media/cdb10136-d108-42cd-973c-35578ea154b7/im_DIRRACINE nfs4 rw,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,p ort=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.25,minorversion=0,local_lock=none,addr=192.168.1.33 0 0"

3/ when I touch to Remote Share and Remote Mount config of bkup01 and 02 , I lost their NUT SNMP connexion to my UPS ????? I have to restart the NUT service reconnected them

yes, i tried with nfs4 option, nfsvers=3 option and nfsvers=2 option

with remote server on OMV3 : yes "grep nfs /proc/mounts" give the same "nfs4" but the share works (with or without "nfsvers=3" option)

root@SRVBKUP02:~# grep nfs /proc/mounts
192.168.1.31:/Data2 /srv/7f0757af-0b3e-4a45-8109-8af7cfacfc0e nfs4 rw,relatime,vers=4.2,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,timeo=14,retrans=2,sec=sys,clientaddr=192.168.1.26,local_lock=none,addr=192.168.1.31 0 0
192.168.1.31:/Data2 /sharedfolders/RM_im_SRVDATA2 nfs4 rw,relatime,vers=4.2,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,timeo=14,retrans=2,sec=sys,clientaddr=192.168.1.26,local_lock=none,addr=192.168.1.31 0 0
root@SRVBKUP02:~#

i can't reproduce this success with remote server on OMV1 and 2 :
Error #0:OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mount '/srv/7ac743fe-2a09-4e73-824d-c9917a44e13c' 2>&1' with exit code '32': mount.nfs: requested NFS version or transport protocol is not supported in /usr/share/php/openmediavault/system/process.inc:175