VMware 6.5 update manager import iso file fails

[j-p_Delattre]

Hello,

i want to use update manager so i try to import ESXI image

   VMware-VMvisor-Installer-6.5.0.update01-5969303.x86_64.iso in update manager

but each time the transfer start for a few seconds and it fails without messages

could you help me to solve my problem

regards

jp Delattre

[vijayrana968]

You need to generate update manager logs bundle and to dig up logs. Is it Windows based vCenter or VCSA ?

[j-p_Delattre]

hello ,

that 's a VCSA

regards

[Finikiez]

Have you tried to use another browser?

[j-p_Delattre]

yes the  three most known

[Finikiez]

All three browsers don't show error message and only exclamation mark, do they?

Do you have a proxy configured in your browser?

[PGinhoux]

Hi,

I work with JP Delattre, so that I can say that no proxy is configured on the browser we use.

So the upload failed for an unknown reason. I try to review the Events on the vSphere client web but there is nothing.

Nothing also in the log located under  /var/log/vmware/vmware-updatemgr/vum-server.

Maybe I'm looking at the wrong places.

Any thoughts.

[Finikiez]

I would recommend to check Web client logs /var/log/vmware/vsphere-client/logs/vsphere_client_virgo.log

Check it for the time when the error appeared

Did you upload ISOs successfully before?

[PGinhoux]

Hi,

This is the first time we try to upload ISO.

The vsphere_client_virgo.log shows this error :

[2017-10-16T07:24:53.093Z] [INFO ] data-service-pool-626295      com.vmware.vise.util.session.SessionUtil                          Generated hashed session id: 112314
[2017-10-16T07:24:53.093Z] [INFO ] data-service-pool-626295      com.vmware.vise.util.session.SessionUtil                          Mapping: ds/sdk: sessionid to -> 112314 with clientId: 210803
[2017-10-16T07:24:55.989Z] [ERROR] http-bio-9090-exec-648        System.err                                                        [Fatal Error] :102:3: The element type "hr" must be terminated by the matching end-tag "</hr>".
[2017-10-16T07:24:55.991Z] [ERROR] http-bio-9090-exec-648        com.vmware.vum.fileupload.impl.VumServerFileUploadClient          VumFileUpload: Exception parsing vum server http response -  org.xml.sax.SAXParseException: The element type "hr" must be terminated by the matching end-tag "</hr>".
        at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257)
        at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:339)
        at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121)
        at com.vmware.vum.fileupload.impl.VumServerFileUploadClient.parseHttpResponse(VumServerFileUploadClient.java:215)
        at com.vmware.vum.fileupload.impl.VumServerFileUploadClient.executeRequest(VumServerFileUploadClient.java:114)
        at com.vmware.vum.fileupload.impl.VumServerFileUploadClient.login(VumServerFileUploadClient.java:69)
        at com.vmware.vum.fileupload.VumFileUploadServlet.doPost(VumFileUploadServlet.java:100)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
        at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
        at com.vmware.vise.security.SessionManagementFilter.doFilterInternal(SessionManagementFilter.java:82)
        at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
        at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:683)
        at org.eclipse.virgo.web.tomcat.support.ApplicationNameTrackingValve.invoke(ApplicationNameTrackingValve.java:33)
        at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423)
        at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079)
        at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:620)
        at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
        at java.lang.Thread.run(Thread.java:745)T

does it tell you something ?

[hussainbte]

Just to narrow this down could you try and upload any other ISO.

like a patch etc or a update zip.. anything other than the ISO

[jpdelattre]

Hi hussainbte,

thank's a lot for your help.

Yes we already tried to import another ISO and an update.zip

and the result is exactly the same in the vsphere_client_virgo.log

each there is a parsing error.

regards

jp

[jpdelattre]

Hello guys,

just to warn you that we don't have the problem anymore since we rebooted the Vcenter .

that's working without real explanation but it's working .

i want to thank  you all a lot for your help .

regards

jp

[hussainbte]

:smileyshocked:

[Finikiez]

Cool )