Dear Forum People,
I have recently moved our ONE management with its database to a new server.
ONED running, all good on that side.
However, Sunstone is struggling to step into play…
The short version of the problem that I am facing (or what I have gathered I am facing) is that I cannot start Sunstone service as it complains about its dependencies (more specifically NoVNC).
Long version and my findings:
I, [2017-05-10T16:21:13.630096 #9582] INFO – : Starting VNC proxy: python2 /usr/share/one/websockify/websocketproxy.py --target-config=/var/lib/one/sunstone_vnc_tokens --cert /etc/ssl/certs/ng.xx.yz.crt --key /etc/ssl/certs/ng.xx.yz.key.pem 80
WebSocket server settings:
- Listen on :80
- Flash security policy server
- SSL/TLS support
Traceback (most recent call last):
File “/usr/share/one/websockify/websocketproxy.py”, line 471, in
File “/usr/share/one/websockify/websocketproxy.py”, line 419, in websockify_init
File “/usr/share/one/websockify/websocket.py”, line 905, in start_server
File “/usr/share/one/websockify/websocket.py”, line 694, in socket
File “/usr/lib64/python2.7/socket.py”, line 224, in meth
socket.error: [Errno 13] Permission denied
I, [2017-05-10T16:21:14.638699 #9582] INFO – : Deleting stale lock file
E, [2017-05-10T16:21:14.638859 #9582] ERROR – : Error starting VNC proxy
Now, “novnc-server start” starts the service if entered on its own however if I try to start Sunstone afterwards, it complains that the socket is already in use - not so surprising.
The permissions error is however is a very curious thing for me, I am running all services as superuser.
To complicate things we have our ONED+SUNSTONE running behind a NGINX server.
I believe this should not be causing the issue as configuration has not changed on NGINX and networking/naming of the new server was done to take the place of our previous OpenNebula deployment.
To show how things are linked up, here is a diagram (hopefully it is clear enough ):
Thanks in advance!
I think my problems might be stemming from installation of a gem called “rack”. When I run the install_gems script, I receive the following:
gem install --no-ri --no-rdoc rack --version “< 2.0.0”
ERROR: Could not find a valid gem ‘rack’ (< 2.0.0), here is why:
Unable to download data from https://rubygems.org/ - Errno::ECONNRESET: Connection reset by peer - SSL_connect (https://rubygems.org/specs.4.8.gz)
Error executing gem install --no-ri --no-rdoc rack --version “< 2.0.0”
Currently investigating whether our corporate firewall would be causing the issues with the gem installation.
Successfully edited the “install_gems” script to utilise proxy and managed to install the gems.