Englanti (muuta) 
Otetaan vilkaista meidän nginx palvelimeen ja sivuston virhe & käyttölokeista, ja jos löytää ne.
Sinulla on yksi pari nginx tukkien palvelimen laajuinen ja toisen jokaiselle sivustolle, ellet pois ne. Virhelokit tehdä juuri niin, kirjaudu mahdolliset virheet. Käyttölokeista näyttää, mitä Web-elementit on ratkaistu IP-osoite ja milloin.
Jotka seurasivat käytetään useita sivustot ja blogit Virtual Hosts kartoittanut sijainti tukkien kutakin aluetta tai Blogit Virtual Hosts-tiedoston tai, jos mukana jokaisen sivuston asetuksia sinun nginx.conf tiedoston sijaintia tiedostoa annetaan siellä.
Tässä on muistutus joka tapauksessa.
20 copy / paste toimia .. nollasta sankari, tyhjän ruudun cute-kuin Linux-palvelimelle.
Selaa alas koko sarjan indeksi.
Joten, hei, irtoa jaettu & Viva Virtual! Hope it helps. The_guv
Luetella ne: --
ls -l /usr/local/nginx/logs
Or to open them:-
sudo nano /usr/local/nginx/logs/error.log
.. substituting error.log for access.log as appropriate.
Or if you installed Nginx using the package manager, rather than compiling from source as is recommended in the VPS Bible, they're here:-
sudo nano /etc/nginx/logs
sudo nano /home/public_html/someSite.com/log/access.log
And the error page:-
sudo nano /home/public_html/someSite.com/log/error.log
In the case of the error log, hopefully it is indeed empty. With the access log, maybe it's just too darn big and is taking a long time to open. If you really want to look at it, be patient. Else delete it and add a new, empty one:-
sudo rm /home/public_html/someSite.com/log/access.log && sudo nano /home/public_html/someSite.com/log/access.log
.. saving the empty file.
Serve multi sites & blogs on a budget .. at the fastest possible speed .. with the least downtime .. in the most secure environment .. and future-proofed for easy admin.
That's what the VPS Bible is about, stepped out in simple copy & paste guides.
From high traffic WordPress blogs to startup web hosts, here's what you need.
Set it up?
ls -l /usr/local/nginx/logs
Or to open them:-
sudo nano /usr/local/nginx/logs/error.log
.. substituting error.log for access.log as appropriate.
Or if you installed Nginx using the package manager, rather than compiling from source as is recommended in the VPS Bible, they're here:-
sudo nano /etc/nginx/logs
sudo nano /home/public_html/someSite.com/log/access.log
And the error page:-
sudo nano /home/public_html/someSite.com/log/error.log
In the case of the error log, hopefully it is indeed empty. With the access log, maybe it's just too darn big and is taking a long time to open. If you really want to look at it, be patient. Else delete it and add a new, empty one:-
sudo rm /home/public_html/someSite.com/log/access.log && sudo nano /home/public_html/someSite.com/log/access.log
.. saving the empty file.
Serve multi sites & blogs on a budget .. at the fastest possible speed .. with the least downtime .. in the most secure environment .. and future-proofed for easy admin.
That's what the VPS Bible is about, stepped out in simple copy & paste guides.
From high traffic WordPress blogs to startup web hosts, here's what you need.
Set it up? Click here for the 21 part follow-up .. V-P-S Admin
THE_GUV NEEDS YOU!!
.. to improve this post ..
Please clue me in. What's wrong or missing?
Or, hey, just pile on the praise ;) Ah, yup, and fix a feed, fella.
Or link the page to your social network!
thank you, thanx, tx, ta, t, tsst, twaddle, cheek, cheers, cheerio