Now I see message "Internal server error has occurred" in System -> Events -> System Events.
How I can to see reasons of this message? NSX-V 188.8.131.5219921
Log in into your manager and check the status of the services, and resources for the appliance.
If possible, restart the services and see if that fixes your issue.
Services is working fine
Is there ways to find out reasons of this message?
NicolasAlauzet I rebooted whole NSX-manager... Result - thу trouble is not solved...
Connect ssh to your manager and:
show filesystems (to see if there is any partition full)
then check for any error or wargnings in the next (if you can attach a fragment)
show log manager reverse (the reverse is to change the chronological orde)
show log system reverse
I also would suggest you to open a gss so you get official support while you try to find the issue
Also: Is this the only place that you get error for that NSX Manager? If you go to host preparation for example, is the information populated or the same error?
Also check inside the Manager the registration against SSO and vCenter (Maybe something is not ok there)
Filesystems is ok:
Filesystem Size Used Avail Use% Mounted on
/dev/root 5.6G 1.4G 3.9G 27% /
devtmpfs 7.9G 0 7.9G 0% /dev
tmpfs 7.9G 444K 7.9G 1% /run
/dev/sda6 44G 3.0G 39G 8% /common
/dev/loop0 16G 45M 15G 1% /common/vdisk_mnt
In log messages a lot of "INFO"...
and some "WARN":
2020-08-31 09:01:30.889 MSK WARN VLSI-client-connection-monitor-549 HttpConfigurationCompilerBase$ConnectionMonitorThreadBase:84 - Interrupted, no more connection pool cleanups will be performed.
2020-08-31 09:01:30.888 MSK WARN http-nio-127.0.0.1-7441-exec-19 HttpConfigurationCompilerBase$ConnectionMonitorThreadBase:92 - Shutting down the connection monitor.
2020-08-31 09:01:30.849 MSK WARN http-nio-127.0.0.1-7441-exec-19 SiteAffinityServerEndpointProvider:95 - CDC not configured java.lang.NoClassDefFoundError: com/vmware/identity/cdc/CdcFactory
In host preparation everythings fine
Manager registration is also OK.
As everything looks fine, I would suggest you to move it forward with GSS.
Maybe something is broken inside the NSX DB, I'm doing some research but not able to find something that can help =(
We had this issue after upgrading nsx-v manager from 6.4.5 to 6.4.8 in a process plan to migrate to nsx-t later
- vendor found that in our previous upgrade from nsxv 6.3.2 to 6.4.5 the upgrade coordinator failed with internal server already
- we entered the esxi agent manager (eam) http://vcenter (DNS name) or (IP_address of vcenter)/eam/mob
- inside EAM ,they found some cluster has no entry as its agent value was (unset ), so we destroyed the agency of that cluster as it was not in use in production
-After that we logged in to vcenter and deleted that cluster with all its logical switches and there was Transport zone created with cluster name so we deleted it too ( we were not using that cluster and we forgot to delete all its dependencies )
-after that the issue was resolved successfully