Let's take a quick look at our Nginx server and site error & access logs, and where to find them.
You have one pair of Nginx logs server-wide and another for each site, unless you omitted them. The error logs do just that, log any errors. The access logs show what web elements have been resolved by IP address and when.
Those who followed Serve Multiple Sites & Blogs with Virtual Hosts mapped out the location of the logs in each site or blogs virtual host file or, if you bundled each site's configuration in your nginx.conf file, the locations to the files are given there.
Here's a reminder anyhow.
Set Up an Unmanaged VPS (4 Newbies) .. The V-P-S Bible
In 20 copy/paste steps .. from zero to hero, blank box to cute-as Linux server.
Scroll down for the full series index.
So, hey, shed shared & viva virtual! Hope it helps. the_guv
Nginx Web Server Error & Access Log Locations
To list them:-
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
Web Site Error & Access Log Locations
sudo nano /home/public_html/someSite.com/log/access.log
And the error page:-
sudo nano /home/public_html/someSite.com/log/error.log
My Error or Access Log is a Blank File/Won't Open.
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.
Congratulations! You have one humdinger of a web server! If you followed the Bible to a T, it's speedy, solid & secure.
But. As explained in Part 16, the Nginx web server has no compatible control panel .. yet. Then again, even if it did, do you really want the resource drain?
In the VPS Admin series is every maintenance procedure you'll need to know. And, hey, using these is a darn sight faster than using a control panel anyhow.
Set it up? Click here for the 21 part follow-up .. V-P-S Admin
Go back? Click here for the original series .. The V-P-S Bible
- * Includes video tutorial.
- Not linked = not published. Won't be long. Fix a feed for updates.
If you liked that ...
-
When I started this series I figured I'd cover it in maybe 7 or 8 posts.
I had more hair in those days, and you were younger too.
Apart from underestimating the subject, fact is, with the intended audience for the [...]
-
Sites I like to surf are really uncluttered, with everything barely more than a click, or a mouse movement, away.
That's how I hope this site is. A really usable web design.
The website requirement
The kind of [...]
-
Installing & configuring Nginx web server, tweaking the default file structure, then setting up a vhost file with symlink is the subject of this copy/paste how-to. So open up that CLI and I'll explain.
So [...]
-
If you're using nginx, and your domain name exceeds 32 characters, you may receive an error message when you restart the web server.
Quite likely, you need to tell nginx to allow for longer domain names.
To do so, [...]
-
Create additional sites & blogs quickly & easily. After creating the DNS entries, just add a vhost file, its symlink, restart Nginx and go play.
OK. So I did this guide already, already! But as this is one [...]
-
Bolt on PHP5 for server-side web applications, Xcache to speed things up and MySQL to handle our databases. And tweak that lot for optimum performance of platforms from WordPress to Drupal.
From the first seven [...]
... maybe you'll like these?
Moses January 19th, 2010 at 3:07 am
G'Day Guv,
A nice alternative to clearing the access log is
sudo rm /home/public_html/someSite.com/log/access.log && sudo touch /home/public_html/someSite.com/log/access.log
I have this as part of my daily backup script, the access.log was approaching 1GB after a few weeks which was accounting for more than 50% of my backup!
the_guv January 20th, 2010 at 8:02 pm
cheers Moses .. that's a nice tip, appreciated.