VMware Cloud Community
herrschlupp
Contributor
Contributor

vSAN missing file service agent and no possibility to create a vsan file service.

Hello everyone,

I have tried to configure the vsan file service.

Unfortunately without success.

The file service is created, but vsan reports problems with the deployment of the file service domain".

Which leads to the configuration not being completed successfully.

After that I started troubleshooting, but without success.

Then I noticed that the "file service agent" (see the attached picture) is missing. I have no idea why, and I could not find a solution.

I hope you can help me to find the "File Service Agent" and then I hope I can solve the problem with the File Service Domain.

Thanks a lot.

7.0.1.00100

17004997

Tags (2)
Reply
0 Kudos
2 Replies
gregzuro
Contributor
Contributor

I believe that I am having the same problem(s).

I was able to Enable File Services once without an AD.

I disabled that so I could add AD and that failed.

Ever since that failure, I cannot get FS enabled regardless of AD inclusion.

Attempts fail (timeout) on the first host's 'Create vSAN file service domain' step.

I no longer see the 'File Service Agent' page.

From the logs, I see that these appear regularly during the 10-15 minute timeout period:

```console

2020-11-03T07:54:51.219Z info [EndpointController-1] [RemoveObjects] DEBUG: Remove objects ['fscontainer/failover/192.168.128.236']

2020-11-03T07:54:52.155Z info [EndpointMonitor-4] [MonitorFSContainer] Current configFailCount is 0

2020-11-03T07:54:52.220Z info [EndpointMonitor-4] [MonitorFSContainer] DEBUG: failCounts: {}

2020-11-03T07:54:52.220Z info [EndpointMonitor-4] [MonitorFSContainer] Failed IPs: []

2020-11-03T07:54:52.309Z error [fs-sched-D-4] [WaitObjects] Failed to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237'] Traceback (most recent call last):   File "/build/mts/release/bora-16850804/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/VDFSEndpointController.py", line 2484, in WaitObjects TimeoutError: Timeout to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237']

2020-11-03T07:54:53.328Z error [fs-sched-D-4] [WaitObjects] Failed to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237'] Traceback (most recent call last):   File "/build/mts/release/bora-16850804/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/VDFSEndpointController.py", line 2484, in WaitObjects TimeoutError: Timeout to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237']

2020-11-03T07:54:54.346Z error [fs-sched-D-4] [WaitObjects] Failed to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237'] Traceback (most recent call last):   File "/build/mts/release/bora-16850804/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/VDFSEndpointController.py", line 2484, in WaitObjects TimeoutError: Timeout to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237']

2020-11-03T07:54:55.360Z error [fs-sched-D-4] [WaitObjects] Failed to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237'] Traceback (most recent call last):   File "/build/mts/release/bora-16850804/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/VDFSEndpointController.py", line 2484, in WaitObjects TimeoutError: Timeout to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237']

2020-11-03T07:54:56.380Z error [fs-sched-D-4] [WaitObjects] Failed to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237'] Traceback (most recent call last):   File "/build/mts/release/bora-16850804/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/VDFSEndpointController.py", line 2484, in WaitObjects TimeoutError: Timeout to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237']

2020-11-03T07:54:57.170Z info [EndpointMonitor-2] [MonitorFSContainer] Current configFailCount is 0

2020-11-03T07:54:57.225Z info [EndpointMonitor-2] [MonitorFSContainer] DEBUG: failCounts: {}

2020-11-03T07:54:57.225Z info [EndpointMonitor-2] [MonitorFSContainer] Failed IPs: []

2020-11-03T07:54:57.397Z error [fs-sched-D-4] [WaitObjects] Failed to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237'] Traceback (most recent call last):   File "/build/mts/release/bora-16850804/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/VDFSEndpointController.py", line 2484, in WaitObjects TimeoutError: Timeout to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237']

2020-11-03T07:54:58.415Z error [fs-sched-D-4] [WaitObjects] Failed to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237'] Traceback (most recent call last):   File "/build/mts/release/bora-16850804/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/VDFSEndpointController.py", line 2484, in WaitObjects TimeoutError: Timeout to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237']

2020-11-03T07:54:59.430Z error [fs-sched-D-4] [WaitObjects] Failed to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237'] Traceback (most recent call last):   File "/build/mts/release/bora-16850804/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/VDFSEndpointController.py", line 2484, in WaitObjects TimeoutError: Timeout to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237']

2020-11-03T07:55:00.448Z error [fs-sched-D-4] [WaitObjects] Failed to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237'] Traceback (most recent call last):   File "/build/mts/release/bora-16850804/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/VDFSEndpointController.py", line 2484, in WaitObjects TimeoutError: Timeout to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.236', 'fscontainer/192.168.128.237']

2020-11-03T07:55:01.678Z error [fs-sched-D-4] [WaitObjects] Failed to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.237'] Traceback (most recent call last):   File "/build/mts/release/bora-16850804/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/VDFSEndpointController.py", line 2484, in WaitObjects TimeoutError: Timeout to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.237']

2020-11-03T07:55:02.190Z info [EndpointMonitor-6] [MonitorFSContainer] Current configFailCount is 0

2020-11-03T07:55:02.700Z error [fs-sched-D-4] [WaitObjects] Failed to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.237'] Traceback (most recent call last):   File "/build/mts/release/bora-16850804/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/VDFSEndpointController.py", line 2484, in WaitObjects TimeoutError: Timeout to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.237']

2020-11-03T07:55:03.720Z error [fs-sched-D-4] [WaitObjects] Failed to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.237'] Traceback (most recent call last):   File "/build/mts/release/bora-16850804/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/VDFSEndpointController.py", line 2484, in WaitObjects TimeoutError: Timeout to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.237']

2020-11-03T07:55:04.739Z error [fs-sched-D-4] [WaitObjects] Failed to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.237'] Traceback (most recent call last):   File "/build/mts/release/bora-16850804/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/VDFSEndpointController.py", line 2484, in WaitObjects TimeoutError: Timeout to wait objects ['fscontainer/192.168.128.235', 'fscontainer/192.168.128.237']

           RX bytes:10007 (10.0 KB)  TX bytes:394 (394.0 B)er:00k:255.255.252.00      Link encap:Ethernet  HWaddr 02:42:c0:a8:80:ec

2020-11-03T07:55:05.367Z info [EndpointMonitor-6] [MonitorFSContainer] DEBUG: failCounts: {}

2020-11-03T07:55:05.367Z info [EndpointMonitor-6] [MonitorFSContainer] Failed IPs: []

```

This shows the first appearance of these messages. NB that the ...236 address appears initially, then disappears at 07:55:02.

The end of these messages is followed by (these are from different attempt from the above, the remaining IPs are different here):

```console

2020-11-03T08:33:15.069Z info vsand[2131280] [opID=13092810-sq1:j4-3db5-W14130 VsanFileServiceSystemImpl::_waitForContainersUp] failed container: ['192.168.128.236', '192.168.128.237'] err msgs are: {'192.168.128.237': 'Unknown container start up failure', '192.168.128.236': 'Unknown container start up failure'}

2020-11-03T08:33:15.082Z info vsand[2131280] [opID=13092810-sq1:j4-3db5-W14130 VsanFileServiceSystemImpl::_waitForContainersUp] IP failed to come up: 192.168.128.237, failureKeyMsg: ('com.vmware.vsan.fileservice.fault.containercreationfailures.unknownerror', 'File server creation failed due to unkown reason. Contact Vmware Support for more information')

2020-11-03T08:33:15.094Z info vsand[2131280] [opID=13092810-sq1:j4-3db5-W14130 VsanFileServiceSystemImpl::_waitForContainersUp] IP failed to come up: 192.168.128.236, failureKeyMsg: ('com.vmware.vsan.fileservice.fault.containercreationfailures.unknownerror', 'File server creation failed due to unkown reason. Contact Vmware Support for more information')

```

I am able to ping all three of these addresses (.235-237) during the entire time these 'wait objects' messages are appearing.  Toward the end of the process, two of the addresses stop responding to pings, then the last one stops when the task times out.

Hope this is helpful.

Is there some other log info that would be helpful?

7.0 Update 1 - 16850804

Reply
0 Kudos
RajeshVasadi
Contributor
Contributor

Hi

Thanks for  the post. I too facing same issue my vc running with 7.0u3j and tried to enable vSAN file service. Any solution? Please share us.

Thank you

Rajesh Vasadi

Reply
0 Kudos