Menu ▾ ▴

vEMan 0.9.6 esxi connection error

vEMan - Support Forum
Marco
2014-09-08
2014-09-28

  • Marco

    Marco - 2014-09-08

    Hello a have an error. The Error is that vEMan cann't connect my esxi server.
    This is the debug.

    Could you help me?

    Thanks

    ub1464@ub1464-virtual-machine:~$ /home/ub1464/Documenti/vEMan
    DEBUG: User variable file /home/ub1464/Documenti/etc/uservars_vEMan.cfg found.
    DEBUG: User variable file /home/ub1464/Documenti/etc/uservars_vEMan.cfg included successfully.
    DEBUG: System variable file /home/ub1464/Documenti/etc/sysvars_vEMan.cfg included successfully.
    DEBUG: included >F_MKCFG< successfully
    DEBUG: included >F_PARENTF< successfully
    DEBUG: included >F_HELP< successfully
    DEBUG: included >F_VERSION< successfully
    DEBUG: included >F_LICENSE< successfully
    DEBUG: included >F_INSTALLER< successfully
    DEBUG: included >F_ERR< successfully
    DEBUG: included >F_REVIEWER< successfully
    DEBUG: Requirement /home/ub1464/Documenti/vEMan met.
    DEBUG: Requirement /usr/bin/yad met.
    DEBUG: Requirement /home/ub1464/Documenti/vmapps/general/connect.pl met.
    DEBUG: Requirement /home/ub1464/Documenti/libs/getx509certificate.vEMan met.
    DEBUG: Requirement /usr/bin/ovftool met.
    DEBUG: Requirement /usr/bin/vncviewer met.
    DEBUG: Requirement /usr/bin/ovftool met.
    DEBUG: Requirement /usr/bin/vmware-cmd met.
    DEBUG: Requirement /bin/nc met.
    DEBUG: Requirement /usr/bin/esxcli met.
    DEBUG: Requirement /home/ub1464/Documenti/libs/runFUNCTION.vEMan met.
    DEBUG: Requirement /usr/bin/openssl met.
    DEBUG: Requirement /home/ub1464/Documenti/vmapps/vm/vminfo.pl met.
    DEBUG: Requirement /home/ub1464/Documenti/vmapps/vm/vmcontrol.pl met.
    DEBUG: Requirement /home/ub1464/Documenti/vmapps/vm/snapshotmanager.pl met.
    DEBUG: vEMan has been executed before. Skipping installer.
    DEBUG: starting auth popup
    DEBUG: Argument given is valid (F_GETCFG)
    DEBUG: User variable file /home/ub1464/Documenti/etc/uservars_vEMan.cfg included successfully.
    DEBUG: System variable file /home/ub1464/Documenti/etc/sysvars_vEMan.cfg included successfully.
    DEBUG: setting file included successfully
    DEBUG: selected 192.168.1.21, root, XXXXXXX (PW hidden), button id: 23
    DEBUG: making config
    DEBUG: Hashed pass is: U2FsdGVkX192BIPa+fXKCmtJ9OEa3Jzd/Nw3Qi9ISN4=
    SRV="192.168.1.21"
    Connecting to 192.168.1.21 port 443
    Generating Certificate .... done.
    DEBUG: Cert fetched successfully.
    No session file detected. Creating one..
    HASH is U2FsdGVkX192BIPa+fXKCmtJ9OEa3Jzd/Nw3Qi9ISN4=
    DEBUG: Error (0) checking authentication or creating session cookie file (F_CRTCOOKIE)
    DEBUG: Return message was: SOAP request error - possibly a protocol issue: <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soapenv:Body>
    <RetrievePropertiesResponse xmlns="urn:vim25"><returnval><obj type="ServiceInstance">ServiceInstance</obj><propSet><name>capability</name><val xsi:type="Capability"><provisioningSupported>false</provisioningSupported><multiHostSupported>false</multiHostSupported><userShellAccessSupported>true</userShellAccessSupported></val></propSet><propSet><name>content</name><val xsi:type="ServiceContent"><rootFolder type="Folder">ha-folder-root</rootFolder><propertyCollector type="PropertyCollector">ha-property-collector</propertyCollector><viewManager type="ViewManager">Vi

    Connection Successful
    DEBUG: Argument given is valid (F_ERR Target said:\n\nSOAP request error - possibly a protocol issue: <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soapenv:Body>
    <RetrievePropertiesResponse xmlns="urn:vim25"><returnval><obj type="ServiceInstance">ServiceInstance</obj><propSet><name>capability</name><val xsi:type="Capability"><provisioningSupported>false</provisioningSupported><multiHostSupported>false</multiHostSupported><userShellAccessSupported>true</userShellAccessSupported></val></propSet><propSet><name>content</name><val xsi:type="ServiceContent"><rootFolder type="Folder">ha-folder-root</rootFolder><propertyCollector type="PropertyCollector">ha-property-collector</propertyCollector><viewManager type="ViewManager">Vi

    Connection Successful\n)
    DEBUG: User variable file /home/ub1464/Documenti/etc/uservars_vEMan.cfg included successfully.
    DEBUG: System variable file /home/ub1464/Documenti/etc/sysvars_vEMan.cfg included successfully.
    DEBUG: Starting keep-alive handler...
    DEBUG: Answer was 23
    DEBUG: Manage_VM was choosen...
    DEBUG: opening action Manage_VM
    DEBUG: FIRSTACT was 0
    DEBUG: firstrun. will skip keep-alive...
    FORCECON (0), FIRSTRUN (1)
    DEBUG: Argument given is valid (F_MAINLOOP)
    DEBUG: User variable file /home/ub1464/Documenti/etc/uservars_vEMan.cfg included successfully.
    DEBUG: System variable file /home/ub1464/Documenti/etc/sysvars_vEMan.cfg included successfully.
    DEBUG: set FORCECON to 1
    DEBUG: firstrun. will skip keep-alive...
    FORCECON (1), FIRSTRUN (1)
    DEBUG: Last exit before Texas..
    DEBUG: informed keepalive handler about the exit
    DEBUG: reached exit function
    DEBUG: Cleanup end
    ub1464@ub1464-virtual-machine:~$ DEBUG: set FORCECON to 1
    DEBUG: Keep-alive handler stopped by abort detection.
    "/tmp/vEMan.exited_2959" rimosso
    DEBUG: Last function was: SAYHELLO
    DEBUG: Skipping keepalive file creation because we were executed by it
    DEBUG: reached exit function
    DEBUG: Cleanup end

    ub1464@ub1464-virtual-machine:~/Documenti$ whereis vmware-cmd
    vmware-cmd: /usr/bin/vmware-cmd /usr/bin/X11/vmware-cmd

    ub1464@ub1464-virtual-machine:~/Documenti$ vmware-cmd --version
    vSphere SDK for Perl version: 5.5.0
    Script 'vmware-cmd' version: 5.5.0

     

  • secure diversITy

    secure diversITy - 2014-09-08

    Hi Marco,

    DEBUG: Return message was: SOAP request error - possibly a protocol issue:

    means that there is an incompatibility between your esx version and/or within the SDK you're using and/or with the components the SDK is build on.
    Well mentioned that a lot but that is one of the major reasons to go away from the Vmware SDK and using the pySphere lib instead in one of the next versions..

    (Login btw seems to work fine).

    • Which ESX version including build are you trying to connect to?
    • Which Linux including version are you using?
    • Which version of libwww-perl do you have installed? -> someone reported using libwww-perl version 5.xxx (in his case it was 5.837) resolved that issue
     

  • Marco

    Marco - 2014-09-09

    Thanks for your answer.

    ESXi ver 5.5.0 build 1331820
    Linux: ubuntu 14.04 64bit
    libwww-perl: 6.08.... perl -MLWP -le "print(LWP->VERSION)"

    Sorry, but I don't know how finding version of libwww-perl.

     

  • secure diversITy

    secure diversITy - 2014-09-09

    ok found the thread I meant.

    Please take a look here:
    https://communities.vmware.com/message/2298661

    There is one who had the same problem and there is a guide how to solve that.

    Let me know if that works for you

     

  • Marco

    Marco - 2014-09-12

    Thanks. I'll try to downgrade during this week end.

     

  • Marco

    Marco - 2014-09-15

    Thanks

     

  • secure diversITy

    secure diversITy - 2014-09-17

    You're welcome.

    As you're using ESX 5.5 it may be that your FW is not configured for console access yet, please see this document for details and a howto:

    https://sourceforge.net/p/veman/git/ci/vmeditor/tree/docs/README_ESX5.1

     

  • Marco

    Marco - 2014-09-24

    Hi
    I've changed my file, but I have same error.
    The message "should display "VNC true" and vEMan console should work as expected now!" doesn't appair.
    Thanks again

     

  • secure diversITy

    secure diversITy - 2014-09-28

    Could you try to disable the Firewall completely? It seems that in newer ESX versions the syntax may have changed regarding the firewall ruleset so as mentioned in my guide I would try always first with disabled FW. There is a GUI option for the FW but you need to google for the howto because I have no good internet access atm. Pls let me know if it works with disabled FW and if you need to have the FW enabled and can not live with a disabled FW let me know, too. As I'm on vacation until 13th of October I can look into this then first but I will read and answer my mails/forum replies all the time though.

    Best regards

     

Log in to post a comment.