this is my first time use vEMan.
vEMan 0.9.6 was complete install on my centos, my ESXi server version is 5.5.0. after i login my ESXi user, it stop at there long time, later response a window display nothing, only two button Retry and Cancel. console output as below:
DEBUG: selected 192.168.1.111, root, XXXXXXX (PW hidden), button id: 23
DEBUG: making config
DEBUG: Hashed pass is: U2FsdGVkX1/UMb/OjWFmEyoBnBJ5lPoLXz0CY5RVtRg=
SRV="192.168.1.111"
DEBUG: Certificate already fetched and available
DEBUG: skipping certificate activation
No session file detected. Creating one..
HASH is U2FsdGVkX1/UMb/OjWFmEyoBnBJ5lPoLXz0CY5RVtRg=
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">V
Connection Successful\n)
DEBUG: User variable file /home/junguo/downloads/VMWare/vEMan_v0.9.6/etc/uservars_vEMan.cfg included successfully.
DEBUG: System variable file /home/junguo/downloads/VMWare/vEMan_v0.9.6/etc/sysvars_vEMan.cfg included successfully
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
DEBUG: included >F_CHKESXVER< successfully
DEBUG: included >F_MGUSR< successfully
DEBUG: included >F_ADDUSR< successfully
DEBUG: included >F_MSG< successfully
DEBUG: included >F_CHGUSR< successfully
DEBUG: included >F_USERMGR< successfully
DEBUG: included >F_REVIEWER< successfully
DEBUG: included >F_NOTREADY< successfully
DEBUG: included >F_SCANNET< successfully
DEBUG: included >F_SCANDS< successfully
DEBUG: included >F_HOSTMGR< successfully
DEBUG: included >F_SAVEOVFSET< successfully
DEBUG: included >F_VERSION< successfully
DEBUG: included >F_HELP< successfully
DEBUG: included >F_SNAPMGR< successfully
DEBUG: included >F_VMEDITOR< successfully
DEBUG: included >F_VMMGR< successfully
DEBUG: included >F_POWERACT< successfully
DEBUG: included >F_MAINLOOP< successfully
DEBUG: included >F_ACTIONS< successfully
DEBUG: included >F_AUTH< successfully
DEBUG: included >F_CHKCFG< successfully
DEBUG: included >F_CONSOLEMGR< successfully
DEBUG: included >F_CRTCOOKIE< successfully
DEBUG: included >F_CRTVMLIST< successfully
DEBUG: included >F_DEPLOVF< successfully
DEBUG: included >F_DEPLVMX< successfully
DEBUG: included >F_DETECTVNC< successfully
DEBUG: included >F_DISABLEVNC< successfully
DEBUG: included >F_ENABLEVNC< successfully
DEBUG: included >F_ERR< successfully
DEBUG: included >F_ESXMGR< successfully
DEBUG: included >F_GETCFG< successfully
DEBUG: included >F_GETFREEPORT< successfully
DEBUG: included >F_GETVMMANUAL< successfully
DEBUG: included >F_GETVMPATH< successfully
DEBUG: included >F_LOGIN< successfully
DEBUG: included >F_MKCFG< successfully
DEBUG: included >F_MKOVFCFG< successfully
DEBUG: included >F_OPENCONSOLE< successfully
DEBUG: included >F_POWER< successfully
DEBUG: included >F_SELECTVM< successfully
DEBUG: included >F_SPACECONV< successfully
DEBUG: included >F_SUSPEND< successfully
DEBUG: included >F_PARENTF< successfully
DEBUG: included >F_DEC< successfully
DEBUG: included >F_DELETEVM< successfully
DEBUG: Res before:
DEBUG: TARGETVM is , AANS is:
DEBUG: F_ESXMGR starting
DEBUG: checking config...
DEBUG: checking config reqs..
DEBUG: Setting file included..
DEBUG: No source file detected.
DEBUG: Can't find /home/junguo/.vEMan/192.168.1.111/lastovf.cfg file, nothing to include.
DEBUG: config reqs checks (F_CHKCFG) finished.
DEBUG: config ok.
HASH is U2FsdGVkX1/UMb/OjWFmEyoBnBJ5lPoLXz0CY5RVtRg=
DEBUG: checking config...
DEBUG: checking config reqs..
DEBUG: Setting file included..
DEBUG: No source file detected.
DEBUG: Can't find /home/junguo/.vEMan/192.168.1.111/lastovf.cfg file, nothing to include.
DEBUG: config reqs checks (F_CHKCFG) finished.
DEBUG: config ok.
No session file detected. Creating one..
HASH is U2FsdGVkX1/UMb/OjWFmEyoBnBJ5lPoLXz0CY5RVtRg=
tail: /home/junguo/.vEMan/192.168.1.111/progress.tmp：
tail: /home/junguo/.vEMan/192.168.1.111/progress.tmp：
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ok so in the meanwhile I had setup an ESXi v5.5 build 1331820.. and it works still fine for me!
check attachment of my result..
Well the main difference between mine and yours is at least the SDK version.
At the moment I develop only with VMware SDK 5.1 and you have 5.5.
1) So my first try would be to remove the VMware SDK for Perl 5.5 and instead install 5.1.
2) Afterwards try again
3) If that doesn't help you can download the development version of vEMan:
the current latest snapshot can be downloaded here: https://sourceforge.net/p/veman/git/ci/vmeditor/tarball
(There were many changes since 0.9.6 but the above version isn't marked as released yet because there is still very heavy work on it)
hm what do you mean with "see vmware-cmd file" ? Do you have made a clean uninstall of the previous 5.5 SDK? Otherwise when you try to install the SDK 5.1 it will detect that there is another SDK installed and you will only uninstall the 5.5 when continue (afaik). So you may need to run the 5.1 installer a second time now.
AND: Read really carefully the result when the SDK finished because there could be errors at the end summary pointing to missind dependencies of the SDK!!! So it could be that the SDK don't get installed. vmware-cmd must be available afterwards - when finished correctly.
Please also check the INSTALL file within vEMan which gaves you important hints about that and also the usual apt-get command e.g. (when using Debian/Ubuntu)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
yeah those messages can be overseen very soon.. That was happening to me in the past, too so I added a hint in the INSTALL doc..
Not very usefriendly by VMware..
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
VERY great to hear!! :o) Thanks for your patience! In vEMan v2 it is planned to drop the VMware SDK dependency completely.. but that will take some... many .. time :-/ Well it could be faster when it would be paid ;-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
DEBUG: selected 192.168.1.111, root, XXXXXXX (PW hidden), button id: 23
DEBUG: making config
DEBUG: Hashed pass is: U2FsdGVkX1/UMb/OjWFmEyoBnBJ5lPoLXz0CY5RVtRg=
SRV="192.168.1.111"
DEBUG: Certificate already fetched and available
DEBUG: skipping certificate activation
No session file detected. Creating one..
HASH is U2FsdGVkX1/UMb/OjWFmEyoBnBJ5lPoLXz0CY5RVtRg=
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">V
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">V
Connection Successful\n)
DEBUG: User variable file /home/junguo/downloads/VMWare/vEMan_v0.9.6/etc/uservars_vEMan.cfg included successfully.
DEBUG: System variable file /home/junguo/downloads/VMWare/vEMan_v0.9.6/etc/sysvars_vEMan.cfg included successfully
Hi CoderJiang!
Welcome here and thx for trying vEMan!
Please paste in the vEMan log,too:
You can also check step "A)" the vEMan new TROUBLE guide:
https://sourceforge.net/p/veman/git/ci/vmeditor/tree/docs/TROUBLE?format=raw
Never tested an ESX v5.5 until now. Maybe there are issues because of the VMware API.
Please also tell me:
Thx
Last edit: secure diversITy 2013-11-28
vEMan start is no problem, the problem only at after click Login button.
updated trouble guide link
https://sourceforge.net/p/veman/git/ci/vmeditor/tree/docs/TROUBLE?format=raw
Script 'vmware-cmd' version: 5.5.0
This is vEMan v0.9.6_BETA
DEBUG: included >F_CHKESXVER< successfully
DEBUG: included >F_MGUSR< successfully
DEBUG: included >F_ADDUSR< successfully
DEBUG: included >F_MSG< successfully
DEBUG: included >F_CHGUSR< successfully
DEBUG: included >F_USERMGR< successfully
DEBUG: included >F_REVIEWER< successfully
DEBUG: included >F_NOTREADY< successfully
DEBUG: included >F_SCANNET< successfully
DEBUG: included >F_SCANDS< successfully
DEBUG: included >F_HOSTMGR< successfully
DEBUG: included >F_SAVEOVFSET< successfully
DEBUG: included >F_VERSION< successfully
DEBUG: included >F_HELP< successfully
DEBUG: included >F_SNAPMGR< successfully
DEBUG: included >F_VMEDITOR< successfully
DEBUG: included >F_VMMGR< successfully
DEBUG: included >F_POWERACT< successfully
DEBUG: included >F_MAINLOOP< successfully
DEBUG: included >F_ACTIONS< successfully
DEBUG: included >F_AUTH< successfully
DEBUG: included >F_CHKCFG< successfully
DEBUG: included >F_CONSOLEMGR< successfully
DEBUG: included >F_CRTCOOKIE< successfully
DEBUG: included >F_CRTVMLIST< successfully
DEBUG: included >F_DEPLOVF< successfully
DEBUG: included >F_DEPLVMX< successfully
DEBUG: included >F_DETECTVNC< successfully
DEBUG: included >F_DISABLEVNC< successfully
DEBUG: included >F_ENABLEVNC< successfully
DEBUG: included >F_ERR< successfully
DEBUG: included >F_ESXMGR< successfully
DEBUG: included >F_GETCFG< successfully
DEBUG: included >F_GETFREEPORT< successfully
DEBUG: included >F_GETVMMANUAL< successfully
DEBUG: included >F_GETVMPATH< successfully
DEBUG: included >F_LOGIN< successfully
DEBUG: included >F_MKCFG< successfully
DEBUG: included >F_MKOVFCFG< successfully
DEBUG: included >F_OPENCONSOLE< successfully
DEBUG: included >F_POWER< successfully
DEBUG: included >F_SELECTVM< successfully
DEBUG: included >F_SPACECONV< successfully
DEBUG: included >F_SUSPEND< successfully
DEBUG: included >F_PARENTF< successfully
DEBUG: included >F_DEC< successfully
DEBUG: included >F_DELETEVM< successfully
DEBUG: Res before:
DEBUG: TARGETVM is , AANS is:
DEBUG: F_ESXMGR starting
DEBUG: checking config...
DEBUG: checking config reqs..
DEBUG: Setting file included..
DEBUG: No source file detected.
DEBUG: Can't find /home/junguo/.vEMan/192.168.1.111/lastovf.cfg file, nothing to include.
DEBUG: config reqs checks (F_CHKCFG) finished.
DEBUG: config ok.
HASH is U2FsdGVkX1/UMb/OjWFmEyoBnBJ5lPoLXz0CY5RVtRg=
DEBUG: checking config...
DEBUG: checking config reqs..
DEBUG: Setting file included..
DEBUG: No source file detected.
DEBUG: Can't find /home/junguo/.vEMan/192.168.1.111/lastovf.cfg file, nothing to include.
DEBUG: config reqs checks (F_CHKCFG) finished.
DEBUG: config ok.
No session file detected. Creating one..
HASH is U2FsdGVkX1/UMb/OjWFmEyoBnBJ5lPoLXz0CY5RVtRg=
tail: /home/junguo/.vEMan/192.168.1.111/progress.tmp：
tail: /home/junguo/.vEMan/192.168.1.111/progress.tmp：
ok thx - can you start vEMan from the commandline and paste the output + the output of vEMan log (see my previous post)
thanks
oh i was too slow ;-) thanks
Last edit: secure diversITy 2013-11-28
ok nothing special in the logs.
that means i need to setup an ESX v5.5 which can take some time. I come back o you asap..
thanks for your patience
[junguo@centOS vEMan_v0.9.6]$ ./vEMan
DEBUG: User variable file /home/junguo/downloads/VMWare/vEMan_v0.9.6/etc/uservars_vEMan.cfg found.
DEBUG: User variable file /home/junguo/downloads/VMWare/vEMan_v0.9.6/etc/uservars_vEMan.cfg included successfully.
DEBUG: System variable file /home/junguo/downloads/VMWare/vEMan_v0.9.6/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/junguo/downloads/VMWare/vEMan_v0.9.6/vEMan met.
DEBUG: Requirement /usr/bin/yad met.
DEBUG: Requirement /home/junguo/downloads/VMWare/vEMan_v0.9.6/vmapps/general/connect.pl met.
DEBUG: Requirement /home/junguo/downloads/VMWare/vEMan_v0.9.6/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 /usr/bin/nc met.
DEBUG: Requirement /usr/bin/esxcli met.
DEBUG: Requirement /home/junguo/downloads/VMWare/vEMan_v0.9.6/libs/runFUNCTION.vEMan met.
DEBUG: Requirement /usr/bin/openssl met.
DEBUG: Requirement /home/junguo/downloads/VMWare/vEMan_v0.9.6/vmapps/vm/vminfo.pl met.
DEBUG: Requirement /home/junguo/downloads/VMWare/vEMan_v0.9.6/vmapps/vm/vmcontrol.pl met.
DEBUG: Requirement /home/junguo/downloads/VMWare/vEMan_v0.9.6/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/junguo/downloads/VMWare/vEMan_v0.9.6/etc/uservars_vEMan.cfg included successfully.
DEBUG: System variable file /home/junguo/downloads/VMWare/vEMan_v0.9.6/etc/sysvars_vEMan.cfg included successfully.
DEBUG: setting file included successfully
Do you have the possibility to check with an ESX v4 or v5.1 or v5.0 ?
Well, i will try v5.0 at tomorrow. thank you.
ok so in the meanwhile I had setup an ESXi v5.5 build 1331820.. and it works still fine for me!
check attachment of my result..
Well the main difference between mine and yours is at least the SDK version.
At the moment I develop only with VMware SDK 5.1 and you have 5.5.
1) So my first try would be to remove the VMware SDK for Perl 5.5 and instead install 5.1.
2) Afterwards try again
3) If that doesn't help you can download the development version of vEMan:
the current latest snapshot can be downloaded here: https://sourceforge.net/p/veman/git/ci/vmeditor/tarball
(There were many changes since 0.9.6 but the above version isn't marked as released yet because there is still very heavy work on it)
There is one more problem when i install SDK 5.1, when i finish install, i naver see vmware-cmd file. do i need do more step?
hm what do you mean with "see vmware-cmd file" ? Do you have made a clean uninstall of the previous 5.5 SDK? Otherwise when you try to install the SDK 5.1 it will detect that there is another SDK installed and you will only uninstall the 5.5 when continue (afaik). So you may need to run the 5.1 installer a second time now.
AND: Read really carefully the result when the SDK finished because there could be errors at the end summary pointing to missind dependencies of the SDK!!! So it could be that the SDK don't get installed. vmware-cmd must be available afterwards - when finished correctly.
Please also check the INSTALL file within vEMan which gaves you important hints about that and also the usual apt-get command e.g. (when using Debian/Ubuntu)
Oh, i see, there is error when 5.1 install.
CPAN not able to install following Perl modules on the system. These must be
installed manually for use by vSphere CLI:
UUID 0.03 or newer
XML::LibXML::Common 0.13 or newer
XML::LibXML 1.63 or newer
yeah those messages can be overseen very soon.. That was happening to me in the past, too so I added a hint in the INSTALL doc..
Not very usefriendly by VMware..
well. after i yum some perl parcket, sdk 5.1 is ok now. and vEMan is working now too. so the problem come from SDK 5.5.
Thanks for all help.
VERY great to hear!! :o) Thanks for your patience! In vEMan v2 it is planned to drop the VMware SDK dependency completely.. but that will take some... many .. time :-/ Well it could be faster when it would be paid ;-)
Oh and can you tell me what distribution you have? You said "yum" so it is Suse,centos or redhat?
centOS 6.4