I wanted to install webSocket proxy on another host, but I got an error 
when setting up engine.

[root@proxy ~]# engine-setup 
[ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup
          Configuration files: 
          Log file: 
          Version: otopi-1.4.1 (otopi-1.4.1-1.el6)
[ INFO  ] Stage: Environment packages setup
[ INFO  ] Yum Downloading: ovirt-3.6-epel/primary_db 1.9 M(32%)
[ INFO  ] Yum Downloading: virtio-win-stable/primary_db (0%)
[ INFO  ] Stage: Programs detection
[ INFO  ] Stage: Environment setup
[ INFO  ] Stage: Environment customization
          --== PRODUCT OPTIONS ==--
          Configure Engine on this host (Yes, No) [Yes]: no
          Configure VM Console Proxy on this host (Yes, No) [Yes]: 
          Configure WebSocket Proxy on this host (Yes, No) [Yes]: 
          --== PACKAGES ==--
[ INFO  ] Checking for product updates...
[ INFO  ] No product updates found
          --== ALL IN ONE CONFIGURATION ==--
          --== NETWORK CONFIGURATION ==--
          Host fully qualified DNS name of this server [proxy.horebdata.cn]: 
[WARNING] Failed to resolve proxy.horebdata.cn using DNS, it can be resolved 
only locally
          Setup can automatically configure the firewall on this system.
          Note: automatic configuration of the firewall may overwrite current 
          Do you want Setup to configure the firewall? (Yes, No) [Yes]: 
[ INFO  ] iptables will be configured as firewall manager.
          Host fully qualified DNS name of the engine server 
[proxy.horebdata.cn]: engine.horebdata.cn
[WARNING] Failed to resolve engine.horebdata.cn using DNS, it can be resolved 
only locally
[WARNING] Failed to resolve engine.horebdata.cn using DNS, it can be resolved 
only locally
          --== DATABASE CONFIGURATION ==--
          --== STORAGE CONFIGURATION ==--
          Default SAN wipe after delete (Yes, No) [No]: 
          --== PKI CONFIGURATION ==--
          Setup will need to do some actions on the remote engine server. 
Either automatically, using ssh as root to access it, or you will be prompted 
to manually perform each such action.
          Please choose one of the following:
          1 - Access remote engine server using ssh as root
          2 - Perform each action manually, use files to copy content around
          (1, 2) [1]: 1
          ssh port on remote engine server [22]: 
          root password on remote engine server engine.horebdata.cn: 
[ INFO  ] Signing the WebSocket Proxy certificate on the engine server
[ INFO  ] WebSocket Proxy certificate signed successfully
          --== APACHE CONFIGURATION ==--
          --== SYSTEM CONFIGURATION ==--
          --== MISC CONFIGURATION ==--
          --== END OF CONFIGURATION ==--
[ INFO  ] Stage: Setup validation
          Generated iptables rules are different from current ones.
          Do you want to review them? (Yes, No) [No]: 
          --== CONFIGURATION PREVIEW ==--
          Default SAN wipe after delete           : False
          Firewall manager                        : iptables
          Update Firewall                         : True
          Host FQDN                               : proxy.horebdata.cn
          Engine installation                     : False
          Configure VMConsole Proxy               : True
          Engine Host FQDN                        : engine.horebdata.cn
          Configure WebSocket Proxy               : True
          Please confirm installation settings (OK, Cancel) [OK]: 
[ INFO  ] Stage: Transaction setup
[ INFO  ] Stopping engine service
[ INFO  ] Stopping ovirt-fence-kdump-listener service
[ INFO  ] Stopping websocket-proxy service
[ INFO  ] Stage: Misc configuration
[ INFO  ] Stage: Package installation
[ INFO  ] Stage: Misc configuration
[ ERROR ] Failed to execute stage 'Misc configuration': 'NoneType' object has 
no attribute 'execute'
[ INFO  ] Yum Performing yum transaction rollback
[ INFO  ] Stage: Clean up
          Log file is located at 
[ INFO  ] Generating answer file 
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed

Users mailing list

Reply via email to