I have an ubuntu 14 server running nginx. I use it for a WordPress website
Out of the blue for no reason the php5-fpm shuts down automatically (I am not sure it even is called shutdown, I get the nginx error page).
This is the message I get now on my site::
An error occurred.
Sorry, the page you are looking for is currently unavailable. Please
try again later.
If you are the system administrator of this resource then you should
check the error log for details.
Faithfully yours, nginx.
I restarted the php5-fpm from the command line and my site goes up for 30-40 seconds and then it goes down again.
What can be the reason? How can the php5-fpm decided on itself to do this? If it helps I'll add that this is a digital ocean server
Thanks upfront!
I faced the same problem, Click here! to solve.
Its because your resource was fully utilized by xmlrpc.php. Possibly Brute force attack.
Block access to xmlrpc.php in nginx config.
Related
I have project developed in Node + react combination. We have deployed it on aws. But from last some days site stopped working. I have checked domain but i didnt find any issue with domain. Actully when I checked with terminal I noticed that I didnt receive any request from client side when I hit the website from browser.
So I checked with nginx status but its showing me failed. I have attached image which shows nginx status. Can anyone tell me how I can make nginx up and running again. I am completely new to handling server things. So I dont have that much knowledge about it. Thanks in advance
Sir, My sites are not able to access from web browser till they have apache restart.!
My sites opening in web browser only when I restart my apache then afater few minutes it again goes to offline !
Why It happening with my server ?
Please Help Me..!
check for any issues in the 'ErrorLog'. The location of the error log can be obtained from your apache config file which is located in /etc/apache2/http.conf
Edit:
look for /etc/apache2/httpd.conf Sorry for the typo
Try to run your wamp/Xamp Server , Run as Administrator.
I have a window 2003 server running exchange 2003 on IIS 6. Everything worked until I installed Tomcat/Railo on the server.
After the Tomcat install I am unable to reach the exchange server on the OWA. I understand that Tomcat is processing the servlets for railo but I am not sure how it is effecting OWA and how to fix it.
Since this has been running so long I am not sure where the files are to reinstall OWA are.
When I hit the exchange OWA site it does ask me to login but then IIS give me a 404 error
I obviously need to get this up and running since every in the company uses the OWA help!
Added info:
I have added a new virtual directory to the default website that contains an image. I can hit this with no problem so it appears that what is no longer working are the virutal directories originally added by the install.
/exchadmin \\.\backofficeStorage
/exchange \\.\backofficeStaorage
/exchweb C:\Program Files\Exchsrvr\ExchWeb
etc
These also appear to be ASP.NET related pages. Is it possible that installing railo/Tomcat messed up the asp processing for this site?
I suspect that both IIS and Tomcat are trying to listen on Port 80, only one can bind at a time. If you look in IIS you may find your default website is stopped.
#Gavin Totall put me on the right track for this. What ever happened during the Tomcat install hosed all of the application pool settings for the default site I found this page
http://support.microsoft.com/?id=883380
on how to reset all the default OWA virtual directorys and everything started working again. Hopefully this post will save someone the hours I spent on this. Thanks again #Gavin
I'm trying to set up Nagios on Nginx and I'm having trouble. I used this as a guide, but I still can't access Nagios from the web.
Just to confirm, I have nagios, fcgiwrap and php-cgi running. When i go to example.com/nagios, it brings up the nagios pages. But when i click on anything substantial, i get a message saying "Error: Could not read host and service status information!". I am sure it has something to do with permissions, but I can't figure out what the problem is.
Anyone know what i can do?
thanks in advance!
Found out my problem. It had to do with file permissions for the nagios files. Nginx ran under a different user, so it didn't have the right permissions to access the nagios files.
When I attempt to update the code on a IIS webserver by replacing the old code with my new code, I receive 503 Service Unavailable replys when attempting to access any of the replaced pages on the server.
What is the cause of this failure and what steps can I take to correct such errors?
Thanks!
I would do a few things:
Check the windows event logs for any web related errors.
Check the IIS logs to see if there is anything odd with the requests.
Double check the permissions of all the new files, make sure they match the files that do work.
Perform an IISReset after you deployed.
Make sure your virtual directory, or sub folders are set up correctly in IIS and didn't change in the deployment.
If the associated ApplicationPool is disabled you also get the 'Service Unavailable' exception. (can be seen in the logs)
Re this answer, I seem to remember having a problem like this, and it turned out that it was because I was updating the files via ftp, and the there was some conflict between the rights of the FTP user and the IIS user.
I have spent hours looking for solution for Service Unavailable, 503 on IIS in Windows 2012 Server. In the end it helps to restart the server and everything works. Restart the IIS was not enough.
It is not the first time the restart help, the same issue was with FTP server on Windows 2012 Server.
Could be lots of things. Did you try iisreset after updating the pages?
I agree with Eugene. It could be lots of things. If you publish locally, can your local IIS run the pages?
You probably need to get together with whomever has access to the server to look at the errors. Short of that, can you try putting the old code back to see if it still works? If not, it's likely a configuration error.
Also, editing the web.config will get the application restarted. It's a useful trick when you can't access IIS.