[SOLVED]Trying to bring my server back!

Connectivity
1

Hello Everyone!
New to the forums here, but not new to MineOs.

I installed mineOs on top of my Ubuntu Linux around 2 years ago… I haven’t updated it since…
No issues back then. The UI and processes worked like a charmed.
But then, for some XY reasons I had to shutdown the server and put it for pasture for a while.

Many changes have occurred to the server ever since, however nothing related to mineOs has been touched.
Today I tried to start the service, using :

sudo service mineos start

"… which looks like it worked, since nothing blew up on me.
However when I tried to log into the UI using my http://localhost:8080, the UI never loaded.
I checked the mineos.conf, and I confirmed that was the right port.

So when I checked the log located at /var/log/mineos.log … I noticed there was an error on some pyton script…
Error is show as below:

[23/Aug/2017:18:24:19] ENGINE Bus STARTING
[23/Aug/2017:18:24:19] ENGINE Forking once.
[23/Aug/2017:18:24:19] ENGINE Daemonized to PID: 16553
[23/Aug/2017:18:24:19] ENGINE Forking twice.
[23/Aug/2017:18:24:19] ENGINE Started monitor thread ‘Autoreloader’.
[23/Aug/2017:18:24:19] ENGINE PID 16553 written to ‘/var/run/mineos.pid’.
[23/Aug/2017:18:24:19] ENGINE Started monitor thread ‘Monitor’.
[23/Aug/2017:18:24:19] ENGINE Started monitor thread ‘_TimeoutMonitor’.
[23/Aug/2017:18:24:19] ENGINE Serving on 0.0.0.0:8080
[23/Aug/2017:18:24:19] ENGINE Bus STARTED
[23/Aug/2017:18:24:23] ENGINE Error in HTTPServer.tick
Traceback (most recent call last):
File “/usr/local/lib/python2.7/dist-packages/cherrypy/wsgiserver/wsgiserver2.py”, line 1837, in start
self.tick()
File “/usr/local/lib/python2.7/dist-packages/cherrypy/wsgiserver/wsgiserver2.py”, line 1902, in tick
s, ssl_env = self.ssl_adapter.wrap(s)
File “/usr/local/lib/python2.7/dist-packages/cherrypy/wsgiserver/ssl_builtin.py”, line 52, in wrap
keyfile=self.private_key, ssl_version=ssl.PROTOCOL_SSLv23)
File “/usr/lib/python2.7/ssl.py”, line 911, in wrap_socket
ciphers=ciphers)
File “/usr/lib/python2.7/ssl.py”, line 579, in init
self.do_handshake()
File “/usr/lib/python2.7/ssl.py”, line 808, in do_handshake
self._sslobj.do_handshake()
SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:590)

[23/Aug/2017:18:24:33] ENGINE Error in HTTPServer.tick
Traceback (most recent call last):
File “/usr/local/lib/python2.7/dist-packages/cherrypy/wsgiserver/wsgiserver2.py”, line 1837, in start
self.tick()
File “/usr/local/lib/python2.7/dist-packages/cherrypy/wsgiserver/wsgiserver2.py”, line 1902, in tick
s, ssl_env = self.ssl_adapter.wrap(s)
File “/usr/local/lib/python2.7/dist-packages/cherrypy/wsgiserver/ssl_builtin.py”, line 52, in wrap
keyfile=self.private_key, ssl_version=ssl.PROTOCOL_SSLv23)
File “/usr/lib/python2.7/ssl.py”, line 911, in wrap_socket
ciphers=ciphers)
File “/usr/lib/python2.7/ssl.py”, line 579, in init
self.do_handshake()
File “/usr/lib/python2.7/ssl.py”, line 808, in do_handshake
self._sslobj.do_handshake()
SSLError: (‘_ssl.c:574: The handshake operation timed out’,)

[23/Aug/2017:18:24:33] ENGINE Error in HTTPServer.tick
Traceback (most recent call last):
File “/usr/local/lib/python2.7/dist-packages/cherrypy/wsgiserver/wsgiserver2.py”, line 1837, in start
self.tick()
File “/usr/local/lib/python2.7/dist-packages/cherrypy/wsgiserver/wsgiserver2.py”, line 1902, in tick
s, ssl_env = self.ssl_adapter.wrap(s)
File “/usr/local/lib/python2.7/dist-packages/cherrypy/wsgiserver/ssl_builtin.py”, line 52, in wrap
keyfile=self.private_key, ssl_version=ssl.PROTOCOL_SSLv23)
File “/usr/lib/python2.7/ssl.py”, line 911, in wrap_socket
ciphers=ciphers)
File “/usr/lib/python2.7/ssl.py”, line 579, in init
self.do_handshake()
File “/usr/lib/python2.7/ssl.py”, line 808, in do_handshake
self._sslobj.do_handshake()
SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:590)

Anybody has any idea what this issue is?

2

So after reading all the post in the forums I came to conclusion the Python based one has been put up for pasture…
I will try to re-install the NodeJs based one.

3

Did you update your distro via apt-get? If so, there’s a good likelihood that you also upgraded cherrypy:

Cherrypy back in version 3.2.5 introduced some new bugs that broke the Built-In SSL module.

It does not appear that the issue had ever gotten resolved, but workarounds exist.

This Stackoverflow post says you can get it working by installing a new Python SSL module and then changing around some of the values in the code itself.

I haven’t done it myself, and it very likely could work…that is, if you value the time to tool around with these instructions versus trying out the new Nodejs based webui. If you did successfully change out the Python module, you should expect the Python webui to work indefinitely.

But also, if this is the issue, you can downgrade your version of cherrypy instead to 3.2.3 (last known working with SSL) and circumvent all that other business.