May-19-2019, 09:57 AM
Thank you for the advices . I asked the same question on Centos forum and some of the administrators answered me that in his opinion there is everything fine with operating system, it’s just that it has nothing to respond with. All your advices and the answer from Centos forum pointed me in the right direction.
It found out that the problem was that cherrypy server wasn’t active at all, because of the wrong initiation method. It should be started in background and not as usual Python script (otherwise it stops working every time system administrator goes back to prompt shell).
So in fact cherrypy server wasn’t working even though its process was visible and it was operating on the right port.
Here is the solution:
instead of this command:
python3 cherrypy_script.py
should be this one:
nohub python3 cherrypy_script.py &
(cherrypy run in background)
(all output, including any error messages, are written to the file nohup.out in the working directory, or in home directory)
(‘&’ means: ‘go back to shell prompt’)
It found out that the problem was that cherrypy server wasn’t active at all, because of the wrong initiation method. It should be started in background and not as usual Python script (otherwise it stops working every time system administrator goes back to prompt shell).
So in fact cherrypy server wasn’t working even though its process was visible and it was operating on the right port.
Here is the solution:
instead of this command:
python3 cherrypy_script.py
should be this one:
nohub python3 cherrypy_script.py &
(cherrypy run in background)
(all output, including any error messages, are written to the file nohup.out in the working directory, or in home directory)
(‘&’ means: ‘go back to shell prompt’)