UCS

peterka

Member
Dec 23, 2020
42
3
13
60
On PVE 6.6 on a VM I installed UCS 4.4 / Nextcloud 20.0.10-0 (https://www.univention.de/) and configured a share (smb & nfs by samba) . In a second VM/client Linux Mint 20.1c, I can not see the nfs- or smb-shares. Server and Client can ping each other. I switched off all firewalls on all relevant network-devices in PVE. From a client LM20.1c outside of PVE (not on a VM, on a physical PC) I can see the smb-share. Any hints?
 
Last edited:
On PVE7 / UCS5 and two Linux (Mint 20.2 mate) Clients the problem still persists. Any hints?
 
hi,

can you give us some more context?

can you ping the nfs server from linux mint? do you get anything with rpcinfo -p ip.of.your.nfs (run from linux mint)

it can also help to run tcpdump on both sides to see where the packets are going missing (or blocked, etc.)
 
can you give us some more context?

can you ping the nfs server from linux mint? do you get anything with rpcinfo -p ip.of.your.nfs (run from linux mint)

it can also help to run tcpdump on both sides to see where the packets are going missing (or blocked, etc.)
===
client-firewall is off.
===
ping works.
===
showmount does not show any nfs-hosts on host UCS5.
===
rpcinfo -p
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100005 1 udp 32767 mountd
100005 1 tcp 32767 mountd
100005 2 udp 32767 mountd
100005 2 tcp 32767 mountd
100005 3 udp 32767 mountd
100005 3 tcp 32767 mountd
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100227 3 tcp 2049
100003 3 udp 2049 nfs
100227 3 udp 2049
100021 1 udp 32768 nlockmgr
100021 3 udp 32768 nlockmgr
100021 4 udp 32768 nlockmgr
100021 1 tcp 32768 nlockmgr
100021 3 tcp 32768 nlockmgr
100021 4 tcp 32768 nlockmgr
===
I can not see any problems (?).
I can do a tcpdump, if this does not help.
 
This is a tcpdump on the host (UCS5,s2) while I did a showmount from the client (192.169.10.50) onto it.
===============
20:17:37.099912 IP s2.botree.eu.ssh > 192.168.10.50.36468: Flags [P.], seq 2797746309:2797746497, ack 1003952726, win 501, options [nop,nop,TS val 3564488795 ecr 1860229806], length 188
20:17:37.100128 IP 192.168.10.50.36468 > s2.botree.eu.ssh: Flags [.], ack 188, win 4010, options [nop,nop,TS val 1860230124 ecr 3564488795], length 0
20:17:38.846809 IP 192.168.10.50.50804 > s2.botree.eu.sunrpc: Flags , seq 48392799, win 64240, options [mss 1460,sackOK,TS val 1860231870 ecr 0,nop,wscale 7], length 0
20:17:38.846860 IP s2.botree.eu.sunrpc > 192.168.10.50.50804: Flags [S.], seq 1309431153, ack 48392800, win 65160, options [mss 1460,sackOK,TS val 3564490542 ecr 1860231870,nop,wscale 7], length 0
20:17:38.847076 IP 192.168.10.50.50804 > s2.botree.eu.sunrpc: Flags [.], ack 1, win 502, options [nop,nop,TS val 1860231871 ecr 3564490542], length 0
20:17:38.847227 IP 192.168.10.50.50804 > s2.botree.eu.sunrpc: Flags [P.], seq 1:97, ack 1, win 502, options [nop,nop,TS val 1860231871 ecr 3564490542], length 96
20:17:38.847237 IP s2.botree.eu.sunrpc > 192.168.10.50.50804: Flags [.], ack 97, win 509, options [nop,nop,TS val 3564490542 ecr 1860231871], length 0
20:17:38.847388 IP s2.botree.eu.sunrpc > 192.168.10.50.50804: Flags [P.], seq 1:57, ack 97, win 509, options [nop,nop,TS val 3564490542 ecr 1860231871], length 56
20:17:38.847481 IP 192.168.10.50.50804 > s2.botree.eu.sunrpc: Flags [.], ack 57, win 502, options [nop,nop,TS val 1860231871 ecr 3564490542], length 0
20:17:38.847509 IP 192.168.10.50.50804 > s2.botree.eu.sunrpc: Flags [F.], seq 97, ack 57, win 502, options [nop,nop,TS val 1860231871 ecr 3564490542], length 0
20:17:38.847524 IP s2.botree.eu.sunrpc > 192.168.10.50.50804: Flags [F.], seq 57, ack 98, win 509, options [nop,nop,TS val 3564490542 ecr 1860231871], length 0
20:17:38.847580 IP 192.168.10.50.50804 > s2.botree.eu.sunrpc: Flags [.], ack 58, win 502, options [nop,nop,TS val 1860231871 ecr 3564490542], length 0
20:17:38.847595 IP 192.168.10.50.55486 > s2.botree.eu.32767: Flags , seq 879585070, win 64240, options [mss 1460,sackOK,TS val 1860231871 ecr 0,nop,wscale 7], length 0
20:17:38.847616 IP s2.botree.eu.32767 > 192.168.10.50.55486: Flags [S.], seq 3068447615, ack 879585071, win 65160, options [mss 1460,sackOK,TS val 3564490543 ecr 1860231871,nop,wscale 7], length 0
20:17:38.847725 IP 192.168.10.50.55486 > s2.botree.eu.32767: Flags [.], ack 1, win 502, options [nop,nop,TS val 1860231871 ecr 3564490543], length 0
20:17:38.847800 IP 192.168.10.50.55486 > s2.botree.eu.32767: Flags [P.], seq 1:77, ack 1, win 502, options [nop,nop,TS val 1860231871 ecr 3564490543], length 76
20:17:38.847808 IP s2.botree.eu.32767 > 192.168.10.50.55486: Flags [.], ack 77, win 509, options [nop,nop,TS val 3564490543 ecr 1860231871], length 0
20:17:38.847936 IP s2.botree.eu.32767 > 192.168.10.50.55486: Flags [P.], seq 1:33, ack 77, win 509, options [nop,nop,TS val 3564490543 ecr 1860231871], length 32
20:17:38.847999 IP 192.168.10.50.55486 > s2.botree.eu.32767: Flags [.], ack 33, win 502, options [nop,nop,TS val 1860231872 ecr 3564490543], length 0
20:17:38.848023 IP 192.168.10.50.55486 > s2.botree.eu.32767: Flags [F.], seq 77, ack 33, win 502, options [nop,nop,TS val 1860231872 ecr 3564490543], length 0
20:17:38.848042 IP s2.botree.eu.32767 > 192.168.10.50.55486: Flags [F.], seq 33, ack 78, win 509, options [nop,nop,TS val 3564490543 ecr 1860231872], length 0
20:17:38.848090 IP 192.168.10.50.55486 > s2.botree.eu.32767: Flags [.], ack 34, win 502, options [nop,nop,TS val 1860231872 ecr 3564490543], length 0
20:17:42.182798 ARP, Request who-has 192.168.10.51 tell s2.botree.eu, length 28
 
sorry for the delay! could you share the logs from the client and the server (most relevant would be timeframes when you're trying to mount the share) ? journalctl or syslog can show some hints. i would also check dmesg for any apparent error messages.
 
Thank You oguz for Your efforts. I believe it is an UCS5-Problem around the domain handling (Samba4 / Active Directory domain controller). I am digging into it and will report on it. I can mount shares from OMV5 and OMV6 (running on PVE7 as well) without any problem on the same client.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!