Menu

ERROR (1) occured while enabling console..

2013-03-18
2013-07-22
  • Toni Pérez

    Toni Pérez - 2013-03-18

    My ubuntu lauch this error "ERROR (1) occured while enabling console.." when trying to conect via console to any machine. What happends? I running ubuntu 12.04 and my esxi server is esxi 5

     
  • secure diversITy

    Hi Toni,

    thx for using vEMan!

    I need the log to investigate this. To do that try to enable the console again and when you get the error message don't touch anything (let the error message open - do not close it) but open the logfile and attach the content:

    ~/.vEMan/vEMan.log

    Thx
    Thomas

     
  • Toni Pérez

    Toni Pérez - 2013-03-19

    Paste a tail -f of vEMAN.log:

    certs/ settings vEMan.log
    progress.tmp sleepingvms.tmp
    root@CPU113:~# tail -f /home/mmgarcia/.vEMan/vEMan.log
    DEBUG: config reqs checks (F_CHKCFG) finished.
    DEBUG: config ok.
    DEBUG: openldap.opentrends.net
    DEBUG: FULLVMPATH is:
    DEBUG: woops VM is offline?!
    DEBUG: Detected a VM path (/vmfs/volumes/510078bf-5a398903-6ed9-902b34a4ea50/openldap.opentrends.net/openldap.opentrends.net.vmx
    /vmfs/volumes/510078bf-5a398903-6ed9-902b34a4ea50/openldap2.opentrends.net/openldap.opentrends.net.vmx)
    DEBUG: F_ENABLEVNC - current VNCPORT is
    DEBUG: F_ENABLEVNC - Enforcing console activation without checking...
    Doing a full Scan. This will take a while..
    nc: connect to 172.20.22.46 port 5900 (tcp) failed: Connection timed out
    Find free port at: 5900
    Usage: vmware-cmd <options> <vm-cfg-path> <vm-action> <arguments>
    vmware-cmd -s <options> <server-action> <arguments></arguments></server-action></options></arguments></vm-action></vm-cfg-path></options>

     Options:
       Connection Options:
          -H or --server <host>            specifies an ESX host or a Virtual Center
          -h or --vihost <target host>     specifies a target host if host is a virtual center
          -O <port>                        specifies an alternative port
          -Q <protocol>                    specifies an alternative protocol
          -U or --username <username>      specifies a username
          -P or --password <password>      specifies a password
          --sessionfile                    specifies a sessionfile path
          --passthroughauth                specifies a login by sspi option
          --credstore                      specifies to fetch Credential store information
          --encoding                       specifies encoding option
       General Options:
          -h More detailed help.
          -q Quiet. Minimal output
          -v Verbose.
    
     Server Operations:
       vmware-cmd -l
       vmware-cmd -s register <config_file_path> <datacenter> <resource pool>
       vmware-cmd -s unregister <config_file_path>
    
     VM Operations:
       vmware-cmd <cfg> getstate
       vmware-cmd <cfg> start <powerop_mode>
       vmware-cmd <cfg> stop <powerop_mode>
       vmware-cmd <cfg> reset <powerop_mode>
       vmware-cmd <cfg> suspend <powerop_mode>
       vmware-cmd <cfg> setguestinfo <variable> <value>
       vmware-cmd <cfg> getguestinfo <variable>
       vmware-cmd <cfg> getproductinfo <prodinfo>
       vmware-cmd <cfg> connectdevice <device_name>
       vmware-cmd <cfg> disconnectdevice <device_name>
       vmware-cmd <cfg> getconfigfile
       vmware-cmd <cfg> getuptime
       vmware-cmd <cfg> answer
       vmware-cmd <cfg> gettoolslastactive
       vmware-cmd <cfg> hassnapshot
       vmware-cmd <cfg> createsnapshot <name> <description> <quiesce> <memory>
       vmware-cmd <cfg> revertsnapshot
       vmware-cmd <cfg> removesnapshots
    

    Synopsis: OPTIONS

    Common VI options:
    --config (variable VI_CONFIG)
    Location of the VI Perl configuration file
    --credstore (variable VI_CREDSTORE)
    Name of the credential store file defaults to <home>/.vmware/credstore/vicredentials.xml on Linux and <appdata>/VMware/credstore/vicredentials.xml on Windows
    --encoding (variable VI_ENCODING, default 'utf8')
    Encoding: utf8, cp936 (Simplified Chinese), iso-8859-1 (German), shiftjis (Japanese)
    --help
    Display usage information for the script
    --passthroughauth (variable VI_PASSTHROUGHAUTH)
    Attempt to use pass-through authentication
    --passthroughauthpackage (variable VI_PASSTHROUGHAUTHPACKAGE, default 'Negotiate')
    Pass-through authentication negotiation package
    --password (variable VI_PASSWORD)
    Password
    --portnumber (variable VI_PORTNUMBER)
    Port used to connect to server
    --protocol (variable VI_PROTOCOL, default 'https')
    Protocol used to connect to server
    --savesessionfile (variable VI_SAVESESSIONFILE)
    File to save session ID/cookie to utilize
    --server (variable VI_SERVER, default 'localhost')
    VI server to connect to. Required if url is not present
    --servicepath (variable VI_SERVICEPATH, default '/sdk/webService')
    Service path used to connect to server
    --sessionfile (variable VI_SESSIONFILE)
    File containing session ID/cookie to utilize
    --url (variable VI_URL)
    VI SDK URL to connect to. Required if server is not present
    --username (variable VI_USERNAME)
    Username
    --verbose (variable VI_VERBOSE)
    Display additional debugging information
    --version
    Display version information for the script
    .opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\nforge.opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\nkaltura.opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\nmop.opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\nopenfire.opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\nopenldap2.opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\nopenldap.opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\noracletestpf\n/home/mmgarcia/VEMan/pics/on.gif\nTestADw2008\n/home/mmgarcia/VEMan/pics/on.gif\nTestAlfresco4\n/home/mmgarcia/VEMan/pics/on.gif\nvideo.opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\nwindows.test\n/home/mmgarcia/VEMan/pics/on.gif\nwin.opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\nzimbra.opentrends.net
    SLEEPING VMs:
    /home/mmgarcia/VEMan/pics/tired.png\n</appdata></home>

    DISABLED VMs:
    /home/mmgarcia/VEMan/pics/off.gif\nfreenas.opentrends.net\n/home/mmgarcia/VEMan/pics/off.gif\njasper.opentrends.net\n/home/mmgarcia/VEMan/pics/off.gif\nopenfiler.opentrends.net
    DEBUG: building 1 list of online, suspended and offline VMs..
    DEBUG: Aborted by user in F_ESXMGR
    /home/mmgarcia/VEMan/libs/runFUNCTION.vEMan: línea 3: : El fitxer o directori no existeix
    DEBUG: reached exit function
    s’ha eliminat «/home/mmgarcia/.vEMan/sessiondata»
    s’ha eliminat «/home/mmgarcia/.vEMan/onlinevms.tmp»
    s’ha eliminat «/home/mmgarcia/.vEMan/offlinevms.tmp»
    DEBUG: Cleanup end

     
  • Toni Pérez

    Toni Pérez - 2013-03-19

    And esxcli.log created on ~/esxcli.log result is:

    [root CRITICAL] Exception:(vmodl.fault.InvalidRequest) {
    dynamicType = <unset>,
    dynamicProperty = (vmodl.DynamicProperty) [],
    msg = 'Unable to resolve WSDL method name DynamicTypeMgrQueryMoInstances for namespace name urn:vim25\n\nwhile parsing SOAP body\nat line 6, column 0\n\nwhile parsing SOAP envelope\nat line 2, column 0\n\nwhile parsing HTTP request before method was determined\nat line 1, column 0',
    faultCause = <unset>,
    faultMessage = (vmodl.LocalizableMessage) []
    }
    [root CRITICAL] Traceback (most recent call last):
    File "esxcli.py", line 421, in _GetAllMoInstances
    File "/mts/dbc3-c/eleung/esx-klnext/esx-klnext/bora/build/build/vmodl/beta/generic/pyVmomi/VmomiSupport.py", line 290, in <lambda>
    File "/mts/dbc3-c/eleung/esx-klnext/esx-klnext/bora/build/build/vmodl/beta/generic/pyVmomi/VmomiSupport.py", line 126, in _InvokeMethod
    File "/mts/dbc3-c/eleung/esx-klnext/esx-klnext/bora/build/build/vmodl/beta/generic/pyVmomi/SoapAdapter.py", line 540, in InvokeMethod
    vmodl.fault.InvalidRequest: (vmodl.fault.InvalidRequest) {
    dynamicType = <unset>,
    dynamicProperty = (vmodl.DynamicProperty) [],
    msg = 'Unable to resolve WSDL method name DynamicTypeMgrQueryMoInstances for namespace name urn:vim25\n\nwhile parsing SOAP body\nat line 6, column 0\n\nwhile parsing SOAP envelope\nat line 2, column 0\n\nwhile parsing HTTP request before method was determined\nat line 1, column 0',
    faultCause = <unset>,
    faultMessage = (vmodl.LocalizableMessage) []
    }</unset></unset></lambda></unset></unset>

    [root ERROR] Unknown namespace vms
    [root CRITICAL] Exception:(vmodl.fault.InvalidRequest) {
    dynamicType = <unset>,
    dynamicProperty = (vmodl.DynamicProperty) [],
    msg = 'Unable to resolve WSDL method name DynamicTypeMgrQueryTypeInfo for namespace name urn:vim25\n\nwhile parsing SOAP body\nat line 6, column 0\n\nwhile parsing SOAP envelope\nat line 2, column 0\n\nwhile parsing HTTP request before method was determined\nat line 1, column 0',
    faultCause = <unset>,
    faultMessage = (vmodl.LocalizableMessage) []
    }
    [root CRITICAL] Traceback (most recent call last):
    File "esxcli.py", line 437, in _GetCLIInfo
    File "/mts/dbc3-c/eleung/esx-klnext/esx-klnext/bora/build/build/vmodl/beta/generic/pyVmomi/Cache.py", line 16, in fnCache
    File "/mts/dbc3-c/eleung/esx-klnext/esx-klnext/bora/build/build/vmodl/beta/generic/pyVmomi/DynamicTypeManagerHelper.py", line 43, in ImportTypes
    File "/mts/dbc3-c/eleung/esx-klnext/esx-klnext/bora/build/build/vmodl/beta/generic/pyVmomi/VmomiSupport.py", line 290, in <lambda>
    File "/mts/dbc3-c/eleung/esx-klnext/esx-klnext/bora/build/build/vmodl/beta/generic/pyVmomi/VmomiSupport.py", line 126, in _InvokeMethod
    File "/mts/dbc3-c/eleung/esx-klnext/esx-klnext/bora/build/build/vmodl/beta/generic/pyVmomi/SoapAdapter.py", line 540, in InvokeMethod
    vmodl.fault.InvalidRequest: (vmodl.fault.InvalidRequest) {
    dynamicType = <unset>,
    dynamicProperty = (vmodl.DynamicProperty) [],
    msg = 'Unable to resolve WSDL method name DynamicTypeMgrQueryTypeInfo for namespace name urn:vim25\n\nwhile parsing SOAP body\nat line 6, column 0\n\nwhile parsing SOAP envelope\nat line 2, column 0\n\nwhile parsing HTTP request before method was determined\nat line 1, column 0',
    faultCause = <unset>,
    faultMessage = (vmodl.LocalizableMessage) []
    }</unset></unset></lambda></unset></unset>

     
  • secure diversITy

    Hm it shows that the VM is offline - is that true?

    Then it would be clear why you get an error when opening the console.

    But the error message while enabling console is strange - I think its possible that this is because of the 'dots' within your VM name. I will check that and come back to you asap.

    Regards
    Thomas

     
  • Toni Pérez

    Toni Pérez - 2013-03-19

    The error persist in machine without dots. I paste the log:

    DISABLED VMs:
    /home/mmgarcia/VEMan/pics/off.gif\nfreenas.opentrends.net\n/home/mmgarcia/VEMan/pics/off.gif\njasper.opentrends.net\n/home/mmgarcia/VEMan/pics/off.gif\nopenfiler.opentrends.net
    DEBUG: building 1 list of online, suspended and offline VMs..
    DEBUG: Aborted by user in F_ESXMGR
    /home/mmgarcia/VEMan/libs/runFUNCTION.vEMan: línea 3: : El fitxer o directori no existeix
    DEBUG: reached exit function
    s’ha eliminat «/home/mmgarcia/.vEMan/sessiondata»
    s’ha eliminat «/home/mmgarcia/.vEMan/onlinevms.tmp»
    s’ha eliminat «/home/mmgarcia/.vEMan/offlinevms.tmp»
    DEBUG: Cleanup end
    tail: /home/mmgarcia/.vEMan/vEMan.log: el fitxer ha estat truncat
    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: checking config...
    DEBUG: checking config reqs..
    DEBUG: Setting file included..
    DEBUG: No source file detected.
    DEBUG: Can't find /home/mmgarcia/.vEMan/172.20.22.46/lastovf.cfg file, nothing to include.
    DEBUG: config reqs checks (F_CHKCFG) finished.
    DEBUG: config ok.
    tail: /home/mmgarcia/.vEMan/vEMan.log: el fitxer ha estat truncat
    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/mmgarcia/.vEMan/172.20.22.46/lastovf.cfg file, nothing to include.
    DEBUG: config reqs checks (F_CHKCFG) finished.
    DEBUG: config ok.
    HASH is U2FsdGVkX1974NlVrsZJ/uw6332hHAnep5GEKSUdE2w=
    DEBUG: checking config...
    DEBUG: checking config reqs..
    DEBUG: Setting file included..
    DEBUG: No source file detected.
    DEBUG: Can't find /home/mmgarcia/.vEMan/172.20.22.46/lastovf.cfg file, nothing to include.
    DEBUG: config reqs checks (F_CHKCFG) finished.
    DEBUG: config ok.
    tail: /home/mmgarcia/.vEMan/progress.tmp: el fitxer ha estat truncat

    Connection Successful
    Server Time : 2013-03-19T19:07:52.07873Z
    Valid session file detected
    DEBUG: Sleeping VMs caching file size is zero. This is no error but if you experience problems you should delete /home/mmgarcia/.vEMan/sleepingvms.tmp before starting vEMan the next time
    DEBUG: online are: alfresco.opentrends.net,forge.opentrends.net,kaltura.opentrends.net,mop.opentrends.net,openfire.opentrends.net,openldap2.opentrends.net,openldap.opentrends.net,oracletestpf,prova,TestADw2008,TestAlfresco4,video.opentrends.net,windows.test,win.opentrends.net,zimbra.opentrends.net,
    DEBUG: offline are: freenas.opentrends.net,jasper.opentrends.net,openfiler.opentrends.net,
    ENABLED VMs:
    /home/mmgarcia/VEMan/pics/on.gif\nalfresco.opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\nforge.opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\nkaltura.opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\nmop.opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\nopenfire.opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\nopenldap2.opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\nopenldap.opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\noracletestpf\n/home/mmgarcia/VEMan/pics/on.gif\nprova\n/home/mmgarcia/VEMan/pics/on.gif\nTestADw2008\n/home/mmgarcia/VEMan/pics/on.gif\nTestAlfresco4\n/home/mmgarcia/VEMan/pics/on.gif\nvideo.opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\nwindows.test\n/home/mmgarcia/VEMan/pics/on.gif\nwin.opentrends.net\n/home/mmgarcia/VEMan/pics/on.gif\nzimbra.opentrends.net
    SLEEPING VMs:
    /home/mmgarcia/VEMan/pics/tired.png\n

    DISABLED VMs:
    /home/mmgarcia/VEMan/pics/off.gif\nfreenas.opentrends.net\n/home/mmgarcia/VEMan/pics/off.gif\njasper.opentrends.net\n/home/mmgarcia/VEMan/pics/off.gif\nopenfiler.opentrends.net
    DEBUG: building 1 list of online, suspended and offline VMs..
    DEBUG: target is >|prova|<, action was 0
    DEBUG: target was stripped to >prova<, action was 0
    DEBUG: VM Manager choosen..
    DEBUG: open VM MAnager..
    DEBUG: checking config...
    DEBUG: checking config reqs..
    DEBUG: Setting file included..
    DEBUG: No source file detected.
    DEBUG: Can't find /home/mmgarcia/.vEMan/172.20.22.46/lastovf.cfg file, nothing to include.
    DEBUG: config reqs checks (F_CHKCFG) finished.
    DEBUG: config ok.
    DEBUG: getting VM info
    tail: /home/mmgarcia/.vEMan/vEMan.log: el fitxer ha estat truncat
    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: Argument given is valid (F_ENABLEVNC)
    DEBUG: User variable file /home/mmgarcia/VEMan/etc/uservars_vEMan.cfg included successfully.
    DEBUG: System variable file /home/mmgarcia/VEMan/etc/sysvars_vEMan.cfg included successfully.
    tail: /home/mmgarcia/.vEMan/vEMan.log: el fitxer ha estat truncat
    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: checking config...
    DEBUG: checking config reqs..
    DEBUG: Setting file included..
    DEBUG: No source file detected.
    DEBUG: Can't find /home/mmgarcia/.vEMan/172.20.22.46/lastovf.cfg file, nothing to include.
    DEBUG: config reqs checks (F_CHKCFG) finished.
    DEBUG: config ok.
    DEBUG: prova
    DEBUG: FULLVMPATH is:
    DEBUG: woops VM is offline?!
    DEBUG: Detected a VM path (/vmfs/volumes/510078bf-5a398903-6ed9-902b34a4ea50/prova/prova.vmx)
    DEBUG: F_ENABLEVNC - current VNCPORT is
    DEBUG: F_ENABLEVNC - Enforcing console activation without checking...
    Doing a full Scan. This will take a while..
    nc: connect to 172.20.22.46 port 5900 (tcp) failed: Connection timed out
    Find free port at: 5900

    SOAP Fault:

    Fault string: Current license or ESXi version prohibits execution of the requested operation.
    Fault detail: RestrictedVersionFault

     
  • secure diversITy

    > Fault string: Current license or ESXi version prohibits execution of the requested operation.
    

    well.. you had said that you use ESX v5 - do you have ESX 5.1 or 5.0 ?

     
  • Toni Pérez

    Toni Pérez - 2013-03-21

    My ESXI server is 5.1, The free version VMware vSphere Hypervisor

     
  • secure diversITy

    I have tested vEMan with 5.0 only. Because of your error I looked on 5.1 and saw that the API has changed in some cases...

    That means some vEMan features will not work with ESX 5.1.
    --> OVF deployment or the console feature are not working in my tests

    vEMan v2.0 will be fully implemented with the pysphere libraries - one reason is the current problem we see here but also to ease setup.

    Unfortunately I cannot tell you when v2.0 will be ready - I have started coding on it and I would say I'm at 1% :-P

    But I will try to look at least at the console feature for 5.1 in vEMan 0.9/1.0.
    So stay tuned ;o)

    Thomas

     
  • Toni Pérez

    Toni Pérez - 2013-03-21

    thank you, wait for version 2.

    :D

     
  • secure diversITy

    oh wait...
    I had taken a look on the error before the "soap" one.. the timeout is maybe because of the enabled firewall within ESX 5.1 !?

    I will check that further, give me a moment ;o)

     

    Last edit: secure diversITy 2013-03-21
  • secure diversITy

    oh .. yes! The reason for your console errors is the new ESX firewall in 5.1.

    Can you follow this guide and tell me if that solves the problem for you?

    http://bitsmarts.blogspot.de/2013/01/enable-vnc-in-vmware-esxi-51.html

    For me the above solution solves the problem!

     

    Last edit: secure diversITy 2013-03-21
  • Toni Pérez

    Toni Pérez - 2013-07-17

    I'm trying this solution but the problem persist. I change vmx of ubuntu server and try to acces in to VeMan but the error it's the same.

     
    • secure diversITy

      ...
      I change vmx of ubuntu server and try to acces in to VeMan but the error it's the same.
      ...

      Well that VMX change isn't needed (because that will be done by vEMan automatically).

      What you need to do is what I mentioned before regarding "Firewall in ESX"(!). Starting from ESX v5.1 on the ESX firewall is automatically enabled.

      You either need to disable the firewall completely (which I would not recommend but depends on you and your security concerns) or to follow the steps described here:

      The quickest and easiest way to test where the problem occurs is nevertheless to disable the ESX firewall - at least - temporarly. To do so follow those steps here:

      1. login as user "root" to your ESX by SSH
      2. execute this command:
      esxcli network firewall set --enabled false
      

      (detailed information here: http://kb.vmware.com/kb/2005284)
      1. then start vEMan and try to connect to a VM console

      If that works fine it IS a problem with the ESX firewall which is not allowing you to connect to the VM console.

      Afterwards you should enable the ESX firewall again:

      1. login as user "root" to your ESX by SSH
      2. execute this command:
      esxcli network firewall set --enabled true
      

      and go through the following guide to add the permission to connect to VM console for vEMan:

      https://sourceforge.net/p/veman/source/77/tree/trunk/docs/README_ESX5.1?format=raw

      Hope that helps you out ;o)
      Thomas

       

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.