I'm having some problems restarting plesk on our server.
I increased the memory limit in our PHP.ini file and had stopped the server and was in the process of restarting when i've received the following error:
[root#server77-68-52-152 ~]# /etc/init.d/psa start
Starting xinetd service... done
Starting named service... done
Starting mysqld service... done
Starting postgresql service... done
Starting psa-spamassassin service... done
Plesk: Starting Mail Server... already started
Starting mail handlers tmpfs storage
Starting Plesk... failed
Starting drwebd service... failed
I'll be honest I'm very new to the dedicated server side of things so need all the help I can get!
Turns out it was an earlier SSL upgrade that broke plesk...it hadn't come to light because plesk hadn't been restarted until the point I updated the PHP file!
You should always check the log files for the exact reason. It will help in fixing the issue faster. Below the log files path of plesk. Check the reason there why plesk is failing to start.
Error log: /var/log/sw-cp-server/error_log
Access log: /usr/local/psa/admin/logs/httpsd_access_log
Panel log: /usr/local/psa/admin/logs/panel.log
Related
After some time I needed to do changes on GAE Python (2.7) First Generation app, but when I develop and run locally, it's basically nonusable due to a very slow start.
These are printed logs:
INFO 2019-10-18 07:56:35,533 devappserver2.py:278] Skipping SDK update check.
INFO 2019-10-18 07:56:35,595 api_server.py:275] Starting API server at: http://localhost:36159
INFO 2019-10-18 07:56:35,599 dispatcher.py:270] Starting module "default" running at: http://127.0.0.1:8080
INFO 2019-10-18 07:56:35,600 admin_server.py:152] Starting admin server at: http://localhost:8000
INFO 2019-10-18 08:01:01,644 instance.py:294] Instance PID: 28496
What I notice that the last line (instance.py) is printed after ~5 minutes and only after that app responds to requests, not before. Interesting that the admin server (localhost:8000) is available right away. Of course, when I do some code change it automatically reloads and it repeats again.
Things I tried/found out:
it behaves like that on my all GAE projects Python First Gen.
tried to create a bare minimal version (webapp2 with one URL), clean virtualenv, still the same behavior
tried to reinstall Google Cloud SDK. delete the whole google-cloud-sdk folder and install again, no changes
tried to install older version of Cloud SDK
used clean VM and it works ok!!!, so it looks like there could be something wrong with my system (outside of SDK), but I'm not sure what.
It's interesting that the pause between the last two log lines is always about 5 minutes, not sure why exactly that time.
Python 2.7.14
OS: OpenSuse Leap 15.0
I'm running out of ideas so any advice would be appreciated.
I solved this accidentally.
I wanted to run Jupyter notebook, but I got the error:
error: [Errno 99] Cannot assign requested address
after debugging in /tornado/netutil.py, I noticed that it tries to work with IP 192.168.1.50 which I wasn't sure where did that come from, (probably I set it since I was playing with my home network some time ago), but when I deleted it from /etc/hosts, Jupyter, as well as GAE, works ok.
What a coincidence :)
When I finished installation postgresql-10.5 and ran pgadmin4 (that came installed with postgresql) I get a configuration error that says:
An error occurred initializing the application server:
Failed to launch application server, server thread existing
It then asks me to input a python path and an application path.
Can anybody help me and and advise what to do to run pgadmin4. I tried find problem solution, but nothing helped me(
On Development Server, whenever I add an taskqueue
taskqueue.add(queue_name='default', url='/_tasks/do_something', params={'key': 1})
The following error occurred
taskqueue_stub.py:1974] Task task1 failed to execute. This task will retry in 819.200 seconds
After getting some hint from this post:
http://www.rogerthat.net/2012/03/27/google-app-engine-push-task-queues-the-development-environment/
I suspect it could be something to do with the hostname. I am using http://test.me:8088 (where test.me point to 127.0.0.1 using host file). The problem goes away when I change the hostname (test.me) to "localhost".
I can't just use localhost due to some app configuration issue.
The code edit rogerthat.net point out is no longer valid.
Any other solution?
I am trying to deploy a war file on tomcat server via tomcat manager. but each time I am getting this error:
FAIL - Deploy Upload Failed, Exception: Processing of multipart/form-data request failed. No space left on device
There is plenty of space on the server. I have only tomcat server and MySQL server running on the server, nothing else.
Can anyone tell me what is wrong and what is the workaround?
It might be you have a permission problem here.
You can try
chmod 777 /opt/apache-tomcat-X.X.XX/work/Catalina/localhost/manager
and maybe additional
chmod 777 /opt/apache-tomcat-X.X.XX/webapps/sample
where sample is your app directory ofc.
Last week, I have successfully tried the Helloworld example with sdk release 1.7.6 and python 2.7 on Windows XP SP3. Today it will not run at all and generates this error.
Can anybody help?
D:\helloworld>dev_appserver.py d:\helloworld
INFO 2013-03-24 20:16:18,187 sdk_update_checker.py:244] Checking for updates
to the SDK.
INFO 2013-03-24 20:16:19,062 sdk_update_checker.py:272] The SDK is up to dat
e.
INFO 2013-03-24 20:16:19,421 api_server.py:152] Starting API server at: http
://localhost:1868
INFO 2013-03-24 20:16:19,437 dispatcher.py:98] Starting server "default" run
ning at: http ://localhost:8080
INFO 2013-03-24 20:16:19,483 admin_server.py:117] Starting admin server at:
http ://localhost:8000
ERROR 2013-03-24 20:16:29,717 http_runtime.py:221] unexpected port response f
rom runtime ['before instance\r\n']; exiting the development server
INFO 2013-03-24 20:16:30,546 api_server.py:517] Applying all pending transac
tions and saving the datastore
INFO 2013-03-24 20:16:30,546 api_server.py:520] Saving search indexes
Could you please file a bug at:
https://code.google.com/p/googleappengine/issues/list
Also, have you added any print statements to the libraries in your Python installation?
Tim Hoffman's response:
"""Check you do not have any print statements in your code. If you do they will write to stdout which the new dev server doesn't like as it uses stdin/stdout to talk between the main task and the workers.""" is not correct. Your application can print to stdout and stderr. In your case it looks like something is printing to stdout before your application is loaded.
Check you do not have any print statements in your code. If you do they will write to stdout which the new dev server doesn't like as it uses stdin/stdout to talk between the main task and the workers. You can read more on how the new dev server functions - and how debugging with pdb etc will have to work
You can run the old version of the server by instead running old_dev_appserver.py