updatemgr service crashing with java.nio.file.NoSuchFileException: /storage/updatemgr/jetty-temp/
search cancel

updatemgr service crashing with java.nio.file.NoSuchFileException: /storage/updatemgr/jetty-temp/

book

Article ID: 408102

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • Update Manager Service crashes immediately with core dump, we see the following files at /storage/core/

    -rw-rw-r-- 1 svc.datamover support  core.updatemgr-worke.XXXX
    -rw-rw-r-- 1 svc.datamover support  core.updatemgr-worke.XXXX
    -rw-rw-r-- 1 svc.datamover support  core.updatemgr-worke.xxxx
    -rw-rw-r-- 1 svc.datamover support  core.updatemgr-worke.xxxx
    -rw-rw-r-- 1 svc.datamover support  core.updatemgr-worke.xxxx

 

  • You will see entries similar to below in /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log

YYYY-MM-DD HH:MM:SS info vmware-vum-server[913017] [Originator@6876 sub=VumVapiEndpoint] [plugin 2462] Loading Authz metadata file: /usr/lib/vmware-vapi/metadata/com.vmware.esx.health_metadata.json
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913186] [Originator@6876 sub=managedJetty] [managedJetty 431] Jetty: java.nio.file.NoSuchFileException: /storage/updatemgr/jetty-temp/start_8589051061763
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913189] [Originator@6876 sub=managedJetty] [managedJetty 431] Jetty:       at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913298] [Originator@6876 sub=managedJetty] [managedJetty 431] Jetty:       at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913298] [Originator@6876 sub=managedJetty] [managedJetty 431] Jetty:       at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913298] [Originator@6876 sub=managedJetty] [managedJetty 431] Jetty:       at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913314] [Originator@6876 sub=managedJetty] [managedJetty 431] Jetty:       at java.nio.file.Files.newByteChannel(Files.java:361)
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913314] [Originator@6876 sub=managedJetty] [managedJetty 431] Jetty:       at java.nio.file.Files.createFile(Files.java:632)
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913314] [Originator@6876 sub=managedJetty] [managedJetty 431] Jetty:       at java.nio.file.TempFileHelper.create(TempFileHelper.java:138)
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913314] [Originator@6876 sub=managedJetty] [managedJetty 431] Jetty:       at java.nio.file.TempFileHelper.createTempFile(TempFileHelper.java:161)
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913312] [Originator@6876 sub=managedJetty] [managedJetty 431] Jetty:       at java.nio.file.Files.createTempFile(Files.java:897)
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913312] [Originator@6876 sub=managedJetty] [managedJetty 431] Jetty:       at org.eclipse.jetty.start.StartArgs.getMainArgs(StartArgs.java:804)
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913312] [Originator@6876 sub=managedJetty] [managedJetty 431] Jetty:       at org.eclipse.jetty.start.Main.invokeMain(Main.java:209)
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913312] [Originator@6876 sub=managedJetty] [managedJetty 431] Jetty:       at org.eclipse.jetty.start.Main.start(Main.java:491)
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913280] [Originator@6876 sub=managedJetty] [managedJetty 431] Jetty:       at com.vmware.updatemanager.jetty.start.main(start.java:22)
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913280] [Originator@6876 sub=managedJetty] [managedJetty 431] Jetty: Usage: java -jar $JETTY_HOME/start.jar [options] [properties] [configs]
YYYY-MM-DD HH:MM:SSinfo vmware-vum-server[913280] [Originator@6876 sub=managedJetty] [managedJetty 431] Jetty:        java -jar $JETTY_HOME/start.jar --help  # for more information
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913017] [Originator@6876 sub=VumVapiEndpoint] [plugin 2462] Loading Authz metadata file: /usr/lib/vmware-vapi/metadata/com.vmware.esx.health_metadata.json
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913017] [Originator@6876 sub=VumVapiEndpoint] [plugin 2392] Loading Cli metadata file: /usr/lib/vmware-vapi/metadata/com.vmware.esx.hosts_metadata.json.
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913302] [Originator@6876 sub=managedJetty] [managedJetty 450] Jetty terminated.
YYYY-MM-DD HH:MM:SS info vmware-vum-server[913017] [Originator@6876 sub=VumVapiEndpoint] [plugin 2415] Loading Metamodel metadata file: /usr/lib/vmware-vapi/metadata/com.vmware.esx.hosts_metadata.json.
YYYY-MM-DD HH:MM:SS error vmware-vum-server[913294] [Originator@6876 sub=managedJetty] [managedJetty 485] Jetty unexpectedly stopped with status 254.  Starting new one.
YYYY-MM-DD HH:MM:SS error vmware-vum-server[913294] [Originator@6876 sub=managedJetty] [managedJetty 514] Jetty server keeps crashing!  Giving up.

Environment

VMware vCenter 8.x 

Cause

This issue occurs when the jetty-temp directory required by the Update Manager service is missing from the /storage/updatemgr/ path.

Resolution

To resolve the issue, recreate the missing directory and reset the correct ownership:

  • Log in to the vCenter Server Appliance (VCSA) using SSH.

  • Navigate to the Update Manager directory:
    • cd /storage/updatemgr/

  • If the folder jetty-temp is missing, create it:
    • mkdir jetty-temp

  • Assign the correct ownership to the updatemgr user:
    • chown updatemgr:updatemgr /storage/updatemgr/jetty-temp

  • Restart the Update Manager service:
    • service-control --stop vmware-updatemgr && service-control --start vmware-updatemgr

 

Powered by Wolken Software