NSX Management Service fails to start after upgrade to 6.4.0 if timezone is set to JST
search cancel

NSX Management Service fails to start after upgrade to 6.4.0 if timezone is set to JST


Article ID: 339151


Updated On:


VMware NSX Networking



After upgrading NSX for vSphere from 6.3.5 to 6.4.0:

  • In the NSX Manager Web User Interface (UI), the NSX Management Service status is Stopped.
  • Clicking the Start button to restart the NSX Management Service returns the status back to Stopped.
  • In the NSX Manager Management Service log vsm.log file, you see entries similar to:
JST  INFO localhost-startStop-1 PostProcessorRegistrationDelegate$BeanPostProcessorChecker:325 - Bean 'com.vmware.vshield.vsm.eventing.service.impl.SystemEventPublisher' of type [com.vmware.vshield.vsm.eventing.service.impl.SystemEventPublisher] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

JST  WARN localhost-startStop-1 SqlExceptionHelper:129 - SQL Error: 0, SQLState: null

JST ERROR localhost-startStop-1 SqlExceptionHelper:131 - Cannot create PoolableConnectionFactory (FATAL: invalid value for parameter "TimeZone": "JST")


VMware NSX for vSphere 6.4.x
VMware NSX for vSphere 6.3.x


This is a known issue affecting NSX for vSphere 6.4.0.

This is resolved in NSX version 6.4.2.

To work around this issue after the upgrade:
  1. Log in to the NSX Manager virtual appliance.
  2. Under Appliance Management, click Manage Appliance Settings.
  3. Click Edit next to Time Settings.
  4. Set the timezone to "Asia/Tokyo".
  5. Click OK.
  6. Reboot the NSX Manager.
Alternatively, If this workaround does not resolve the issue, try the following:
  1. Stop the NSX Manager VM.
  2. Deploy the NSX Manager appliance with the version before the upgrade.
  3. Restore the old NSX Manager backup.
  4. Do the procedure mentioned above.
  5. Upgrade it to the new version.
  6. If no problem is seen, original NSX Manager VM can be safely removed.