우리 Nginx 서버 및 사이트 오류 및 액세스 로그를 빨리 봐, 그리고하자가 어디서 그들을 찾을 수있습니다.
당신 Nginx 한 쌍을 가지고 다양한 서버 로그를 다른 각 사이트에 대한 않으면 그들이 누락되었습니다. 오류 로그 그냥 모든 오류 로그 않습니다. 액세스 로그를 어떤 웹 요소가 IP에 의해 주소가 해결되었습니다 때 표시됩니다.
사람들은 가상과 함께 복무 여러 사이트 & 블로그 다음의 각 사이트에 로그의 위치를 밖으로 매핑된 호스트 또는 가상 호스트 파일을 블로그 또는, 만약 당신이 nginx.conf 파일에 각 사이트의 구성 번들 파일의 위치가 주어집니다.
상기 이유는 여기에 있어요.
설정 관리되지 않는 VPS (4 Newbies) .. 최대 VPS 성경
20 복사 있음 / 붙여넣기 단계 .. 제로의 영웅에서 빈 상자를 리눅스 서버 귀여운 -했다.
아래로 스크롤하여 전체 시리즈의 색인을 생성합니다.
그럼, 헤이, & 만세! 희망 가상 공유 창고에 도움이됩니다. the_guv
Nginx 웹 서버 오류 및 액세스 로그 위치
그들이 목록을하려면 : -
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, [...]
-
Welcome to the_guv's 20 part VPS how-to bible, complete with video tutorials.
If you are outgrowing your shared host, are paying big bucks for a managed VPS or want to rightsize from an old dedicated plan, this [...]
-
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 [...]
... maybe you'll like these?
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