Quantcast
Channel: Nginx Forum - Other discussion
Viewing all 972 articles
Browse latest View live
↧

Re: nginx application error 0xC0000142 on Windows shutdown

May 11, 2016, 5:57 am
$
0
0
OK - the link appears to be http://nginx-win.ecsds.eu/download/

From Readme first.txt

Version 23:13 15-3-2015 (1.3b) In some cases the nginx processes won't stop normally
when it's service is stopped, it is adviced to add this line:
TASKKILL /F /IM "nginx*"
at the end of your 'ngx_stop.cmd' file
script adjusted

This looks promising, even though 'ngx_stop.cmd' does not appear to be in the download.

FYI: nginx is installed as part of our application's automated installer, which uses InstallShield technology.

Thanks.
↧
Search

Re: nginx application error 0xC0000142 on Windows shutdown

May 11, 2016, 6:45 am
$
0
0
papertape Wrote:
-------------------------------------------------------
> when it's service is stopped, it is adviced to add this line:
> TASKKILL /F /IM "nginx*"
>
> This looks promising, even though 'ngx_stop.cmd' does not appear to be
> in the download.
>
> FYI: nginx is installed as part of our application's automated
> installer, which uses InstallShield technology.

Look in to the Install_nginx_php_services.zip tools on site.
↧
↧

Re: Every other 60 second timeouts

May 22, 2016, 12:31 pm
$
0
0
Did you've find a solution for this problem?
We're facing probably a similiar problem, where the apache backend is running fine for some hours and then nginx get 504 error from time to time, with an exact time difference of 1/3/5/9 minutes, the the backends run fine again for 1-2-3 hours.

The upstream is an Centos7/Apache2.4/PHP 5.6 cluster and there in absolutely no load on nginx and the upstreams, maxium 1 client from time to time. Both backend servers shows these problems, with an Apache running on windows this problem has never been occured.

I'm pretty sure it's not directly an nignx issue but after days of researching I have no idea what to try next.....

2016/05/22 11:33:55 [notice] 4904#6056: using sockapi from "4;"
2016/05/22 11:33:55 [notice] 4268#5176: sockinit() attempting to access sockapi
2016/05/22 11:33:55 [notice] 4268#5176: Access to sockapi succeded!
2016/05/22 11:33:55 [notice] 4268#5176: using sockapi from "4;"
2016/05/22 11:33:55 [notice] 2396#1404: sockinit() attempting to access sockapi
2016/05/22 11:33:55 [notice] 2396#1404: Access to sockapi succeded!
2016/05/22 11:33:55 [notice] 2396#1404: using sockapi from "4;"

2016/05/22 13:03:11 [warn] 5884#1340: *1770011 upstream server temporarily disabled while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:03:11 [error] 5884#1340: *1770011 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:06:11 [warn] 2292#5648: *1770018 upstream server temporarily disabled while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:06:11 [error] 2292#5648: *1770018 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:17:11 [warn] 4268#6072: *1770041 upstream server temporarily disabled while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.14:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:17:11 [error] 4268#6072: *1770041 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.14:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:18:11 [warn] 4268#6072: *1770044 upstream server temporarily disabled while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:18:11 [error] 4268#6072: *1770044 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:19:11 [warn] 5884#1340: *1770048 upstream server temporarily disabled while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.14:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:19:11 [error] 5884#1340: *1770048 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.14:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:21:11 [warn] 5884#1340: *1770053 upstream server temporarily disabled while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.14:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:21:11 [error] 5884#1340: *1770053 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.14:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:22:11 [warn] 6088#540: *1770056 upstream server temporarily disabled while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:22:11 [error] 6088#540: *1770056 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:43:11 [warn] 592#5524: *1770100 upstream server temporarily disabled while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:43:11 [error] 592#5524: *1770100 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:45:11 [warn] 4996#2736: *1770105 upstream server temporarily disabled while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:45:11 [error] 4996#2736: *1770105 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:51:11 [warn] 1768#5656: *1770145 upstream server temporarily disabled while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:51:11 [error] 1768#5656: *1770145 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:56:11 [warn] 1812#4888: *1770156 upstream server temporarily disabled while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 13:56:11 [error] 1812#4888: *1770156 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 14:16:11 [warn] 4268#6072: *1770198 upstream server temporarily disabled while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
2016/05/22 14:16:11 [error] 4268#6072: *1770198 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 69.162.124.236, server: wahl2.hannover-stadt.de, request: "HEAD / HTTP/1.1", upstream: "http://192.168.57.88:80/wrs/", host: "wahl2.hannover-stadt.de"
↧

Re: Every other 60 second timeouts

May 22, 2016, 1:42 pm
$
0
0
Your best bet is to use wireshark to see exactly what is going on on the wire and who's reacting to who and mostly when it logs a failure what wireshark logs.

It feels like some sort of handshake error.
↧

Re: Every other 60 second timeouts

May 23, 2016, 1:15 am
$
0
0
Some other 'solutions' you can try;

https://www.scalescale.com/tips/nginx/upstream-timed-out/
http://serverfault.com/questions/647411/nginx-lots-of-connection-timed-out-errors
https://kb.plesk.com/en/120210
http://stackoverflow.com/questions/28347184/upstream-timed-out-110-connection-timed-out-for-static-content
↧
↧

Problem with building nginx with rtmp module over the cygwin

May 24, 2016, 11:34 pm
$
0
0
Problem with building nginx with rtmp module over the cygwin
↧

Re: Problem with building nginx with rtmp module over the cygwin

May 24, 2016, 11:36 pm
$
0
0
objs/addon/nginx-rtmp-module-master/ngx_rtmp_stat_module.o \
objs/addon/nginx-rtmp-module-master/ngx_rtmp_control_module.o \
objs/ngx_modules.o \
-lcrypt ../pcre-8.38/.libs/libpcre.a -lssl -lcrypto ../zlib-1.2.8/libz.a \
-Wl,-E
/usr/lib/gcc/x86_64-pc-cygwin/5.3.0/../../../../x86_64-pc-cygwin/bin/ld: warning: --export-dynamic is not supported for PE+ targets, did you mean --export-all-symbols?
sed -e "s|%%PREFIX%%|/usr/local/nginx|" \
-e "s|%%PID_PATH%%|/usr/local/nginx/logs/nginx.pid|" \
-e "s|%%CONF_PATH%%|/usr/local/nginx/conf/nginx.conf|" \
-e "s|%%ERROR_LOG_PATH%%|/usr/local/nginx/logs/error.log|" \
< man/nginx.8 > objs/nginx.8
make[1]: Leaving directory '/tmp/nginx-1.9.15'
↧

Re: Every other 60 second timeouts

May 25, 2016, 12:06 am
$
0
0
The only way to really dig into this issue is wireshark/tcpdump on both ends to determine if calls arrive, what happens with them and what happens when they return to nginx (port closures, handshake error, timeout, etc.)

We serve loads of tomcat backends which are really slow sometimes and rarely see errors like these, yes they do occur but like once a week when too many users hit the backend (filling out their time-sheets).

Also have a good look at the settings of the network cards, energy saving mode, tcp offloading, qos, top/dis-responders, dns settings (like auto register this machine at....), unused netbios, calls to active directory which may interrupt, etc.
↧
Search

rate limit on udp streams

June 1, 2016, 11:22 am
$
0
0
Hi all!

I know the directive "limit_req_zone" is only allowed on http context, but there is a way to throttle the requests made in a TCP/UDP stream?

Thanks!

Wilson Hipolito
↧
↧

About nginx security advisory (CVE-2016-4450)

June 3, 2016, 12:53 am
$
0
0
For some reason I can't update my Nginx version right now.

can I just set client_body_buffer_size to 51Mb (client_max_body_size is 50Mb) to sovle this security issue?
↧

caching security

June 5, 2016, 3:37 am
$
0
0
Hi, I want to enable caching on some sites that are behind my nginx reverse proxy such as owncloud and gitlab, both of these are log in based with separate users, but I dont want a situation the same as steam recently encountered where they were caching a particular users page for all other users and other people could see other peoples profiles, see the link: http://store.steampowered.com/news/19852/

So are there any special config options that I can include to make sure that this does not happen to my sites.

Thanks for any responses, Ben
↧

Re: caching security

June 5, 2016, 3:51 am
$
0
0
Ah I have found something:

How Does NGINX Determine Whether or Not to Cache Something?

By default, NGINX respects the Cache-Control headers from origin servers. It does not cache responses with Cache-Control set to Private, No-Cache, or No-Store or with Set-Cookie in the response header. NGINX only caches GET and HEAD client requests. You can override these defaults as described in the answers below.


but my question is do I need to set up the backend web server to add the headers or will the website (owncloud and gitlab) automatically add these when on pages that shouldn't be cached
↧

Re: caching security

June 5, 2016, 6:58 am
$
0
0
Ha I have answered my own question... should have researched a bit more before postingm if you go into dev tools in chrome and into network you can see the headers and the cache control, so owncloud should work fine by just enabling cache in nginx, as it caches the css and static files I guess but dosent cache anything it shouldn't, anyway good idea to check this before anyone else enables caching on their site.

Thanks, Ben
↧
↧

robots.txt

June 8, 2016, 7:52 am
$
0
0
Hi All,

I am using 4 nginx servers. When I do www.example.com/robots.txt it shows

Request-rate: 1/10 # maximum rate is one page every 10 seconds
Crawl-delay: 10 # 10 seconds between page requests V
isit-time: 0400-0845 # only visit between 04:00 and 08:45 UTC

I have not configured robots.txt any where in my nginx.conf and also verified the LB setting too.

I also couldn't find a file named robots.txt any where in my Linux machine where nginx was installed.

Could someone help me to understand from where the above values fetched in nginx. Its really urgent?

Thank you,

Sreejith
↧

Re: nginx 1.8.1 : multiple client certificate issue

June 8, 2016, 9:08 am
$
0
0
Simon,
I'm running into similar issue. Did you resolve your problem?
↧
Search

Re: Every other 60 second timeouts

June 13, 2016, 1:45 am
$
0
0
Might be unrelated but this could also be a reason:
https://social.technet.microsoft.com/Forums/office/en-US/c277b434-fb99-4694-9933-15fbe3761e70/no-network-activity-for-60-sec-after-a-destination-host-unreachable-error?forum=w7itpronetworking

Multiple LAN cards and using more than one default gateway (ARP/MAC ‘blocking’).
↧

proxy_ssl_trusted_certificate contains dummy certificate

August 4, 2016, 12:47 am
$
0
0
Hi,

I use the following nginx configuration to proxy traffic to upstream hosts:

*** nginx.conf; location level
proxy_ssl_trusted_certificate trusted.pem;
proxy_pass https://host:443;

When my 'trusted.pem' contains correct certificates meaning the root-ca and intermediate-ca nginx proxies the traffic accordingly, but this is also the case when my 'trusted.pem' contains dummy certificates.

Can somebody explain this?

Regards,
↧
↧

Nginx Caching Error Response Code like 400 , 500 , 503 ,etc

August 6, 2016, 1:13 am
$
0
0
Hi Everyone,

We are using Nginx as Caching Server .

As per Nginx Documentation by default nginx caches 200, 301 & 302 response code but we are observing that if Upstream server gives error 400 or 500 or 503, etc , response is getting cached and all other requests for same file becomes HIT.

Though if we set proxy_cache_valid specifying response code ( like proxy_cache_valid 200 15m; ) then also its caching the error response code but its not caching 301 & 302 in that case. Why the same is not getting applied for error response code.

Is this the behaviour of Nginx or bug in Nginx ? We are using 1.4.0 version of Nginx

Please help so that error response codes should not get cached as this is giving the same error response to users who are requesting for the file though upstream server is healthy and ok to serve the request.

Regards,
Anish
↧

Nginx MP4 Seeking results to video error

August 7, 2016, 1:59 pm
$
0
0
When using ?start=secs with nginx mp4, video doesn't play for about 8 seconds although the audio keep playing well.

example:

http ://server/video.mp4 >>> plays correctly

http ://server/video.mp4?end=60 >>> plays correctly

http ://server/video.mp4?start=120 >>> starts audio playing with static image (video not working) for about 7-8 seconds.

I tried many MP4 files, all of them show first 7-8 seconds without video. All files have moov atom at beginning.

Seems like nginx don't get the starting video frame correctly, any advice?
↧

All nginx worker processors D state and no longer respond to any request

August 11, 2016, 12:52 am
$
0
0
Hello

our nginx version is nginx-1.9.7

nginx.conf include:
worker_processes auto;
output_buffers 1 128k;
sendfile on;
tcp_nopush on;
sendfile_max_chunk 128k;
keepalive_timeout 8;
server_tokens off;
client_max_body_size 10M;
......

all nginx worker include cache manager is D state after startup 7 days, more importantly, the situation has appeared on other three servers

nginx is used to as cdn node , and load is not very high

does the reason is nginx itself or xfs filesystem or others？

any response will be appreciated.

analysis：
it look like all nginx worker blocked on a file that one worker write but others read , because we found that file "/data01/nginx_proxy_cache/cache/e7/c2/aa3d638afdddd44220bdf1954f5dc2e7" was accessed by 11 workers, and one of ps FD is 50u
but we can't explain this situation , please help.
------------------------------------------------------------------------------------------------------------------------------------------------------------------
[root@w-fc12 conf]# for i in `ps aux | awk '$NF=="process" {print $2}'` ; do lsof -p $i|grep /data01/nginx_proxy_cache/cache/e7/c2/aa3d638afdddd44220bdf1954f5dc2e7; done
nginx 15269 nobody 270r REG 251,0 41144 268717925 /data01/nginx_proxy_cache/cache/e7/c2/aa3d638afdddd44220bdf1954f5dc2e7
nginx 15269 nobody 760r REG 251,0 41144 268717925 /data01/nginx_proxy_cache/cache/e7/c2/aa3d638afdddd44220bdf1954f5dc2e7
nginx 15273 nobody 50r REG 251,0 41144 268717925 /data01/nginx_proxy_cache/cache/e7/c2/aa3d638afdddd44220bdf1954f5dc2e7
nginx 15274 nobody 931r REG 251,0 41144 268717925 /data01/nginx_proxy_cache/cache/e7/c2/aa3d638afdddd44220bdf1954f5dc2e7
nginx 15277 nobody 622r REG 251,0 41144 268717925 /data01/nginx_proxy_cache/cache/e7/c2/aa3d638afdddd44220bdf1954f5dc2e7
nginx 15285 nobody 50u REG 251,0 41144 268717925 /data01/nginx_proxy_cache/cache/e7/c2/aa3d638afdddd44220bdf1954f5dc2e7
nginx 15291 nobody 131r REG 251,0 41144 268717925 /data01/nginx_proxy_cache/cache/e7/c2/aa3d638afdddd44220bdf1954f5dc2e7
nginx 15291 nobody 714r REG 251,0 41144 268717925 /data01/nginx_proxy_cache/cache/e7/c2/aa3d638afdddd44220bdf1954f5dc2e7
nginx 15294 nobody 56r REG 251,0 41144 268717925 /data01/nginx_proxy_cache/cache/e7/c2/aa3d638afdddd44220bdf1954f5dc2e7
nginx 15294 nobody 400r REG 251,0 41144 268717925 /data01/nginx_proxy_cache/cache/e7/c2/aa3d638afdddd44220bdf1954f5dc2e7
nginx 15307 nobody 594r REG 251,0 41144 268717925 /data01/nginx_proxy_cache/cache/e7/c2/aa3d638afdddd44220bdf1954f5dc2e7

--------------------------------------------------------------------------------------------------------------------------------------------------------------------
[liuguirong@w-fc12 conf]$ ps axu|grep nginx
root 4879 0.0 0.1 9687712 89016 ? Ds Aug04 0:00 nginx: master process /usr/local/nginx/sbin/nginx
nobody 15268 1.3 2.2 9740068 1454828 ? D Aug05 123:55 nginx: worker process
nobody 15269 1.3 2.2 9736804 1451504 ? D Aug05 123:06 nginx: worker process
nobody 15270 1.3 2.2 9738568 1453272 ? D Aug05 123:17 nginx: worker process
nobody 15271 1.3 2.2 9739520 1454184 ? D Aug05 123:14 nginx: worker process
nobody 15272 1.3 2.2 9740440 1455216 ? D Aug05 124:39 nginx: worker process
nobody 15273 1.3 2.2 9742540 1457160 ? D Aug05 123:52 nginx: worker process
nobody 15274 1.3 2.2 9737832 1452544 ? D Aug05 123:43 nginx: worker process
nobody 15275 1.3 2.2 9741376 1456092 ? D Aug05 122:14 nginx: worker process
nobody 15276 1.3 2.2 9738660 1453544 ? D Aug05 122:46 nginx: worker process
nobody 15277 1.3 2.2 9740412 1455124 ? D Aug05 123:37 nginx: worker process
nobody 15278 1.3 2.2 9740344 1455000 ? D Aug05 121:52 nginx: worker process
nobody 15279 1.3 2.2 9740736 1455484 ? D Aug05 123:00 nginx: worker process
nobody 15281 1.3 2.2 9741164 1455864 ? D Aug05 123:54 nginx: worker process
nobody 15282 1.3 2.2 9738420 1453128 ? D Aug05 123:08 nginx: worker process
nobody 15285 1.3 2.2 9739764 1454368 ? D Aug05 123:42 nginx: worker process
nobody 15286 1.3 2.2 9739528 1454308 ? D Aug05 123:13 nginx: worker process
nobody 15288 1.3 2.2 9739628 1454332 ? D Aug05 124:28 nginx: worker process
nobody 15289 1.3 2.2 9741004 1455664 ? D Aug05 123:23 nginx: worker process
nobody 15290 1.3 2.2 9740816 1455540 ? D Aug05 123:55 nginx: worker process
nobody 15291 1.3 2.2 9739840 1454544 ? D Aug05 122:31 nginx: worker process
nobody 15293 1.3 2.2 9740448 1455316 ? D Aug05 123:45 nginx: worker process
nobody 15294 1.3 2.2 9738528 1453240 ? D Aug05 123:50 nginx: worker process
nobody 15295 1.3 2.2 9739184 1453912 ? D Aug05 123:06 nginx: worker process
nobody 15296 1.3 2.2 9739888 1454664 ? D Aug05 122:55 nginx: worker process
nobody 15298 1.3 2.2 9738940 1453556 ? D Aug05 122:40 nginx: worker process
nobody 15300 1.3 2.2 9740828 1455596 ? D Aug05 122:52 nginx: worker process
nobody 15302 1.3 2.2 9739664 1454412 ? D Aug05 124:54 nginx: worker process
nobody 15303 1.3 2.2 9738036 1452784 ? D Aug05 122:56 nginx: worker process
nobody 15304 1.3 2.2 9741260 1455968 ? D Aug05 123:23 nginx: worker process
nobody 15305 1.3 2.2 9740756 1455660 ? D Aug05 124:17 nginx: worker process
nobody 15306 1.3 2.2 9738720 1453452 ? D Aug05 123:35 nginx: worker process
nobody 15307 1.3 2.2 9738908 1453692 ? D Aug05 124:22 nginx: worker process
nobody 15308 0.0 2.0 9669052 1358768 ? D Aug05 6:31 nginx: cache manager process

--------------------------------------------------------------------------------------------------------------------------------------------------------

[root@w-fc12 conf]# ps aux | awk '$NF=="process" {print " "$0 system("cat /proc/"$2"/wchan")}'
xfs_iget nobody 15268 1.3 2.2 9740068 1454828 ? D Aug05 123:55 nginx: worker process 0
do_lookup nobody 15269 1.3 2.2 9736804 1451504 ? D Aug05 123:06 nginx: worker process 0
do_lookup nobody 15270 1.3 2.2 9738568 1453272 ? D Aug05 123:17 nginx: worker process 0
xfs_iget nobody 15271 1.3 2.2 9739520 1454184 ? D Aug05 123:14 nginx: worker process 0
do_lookup nobody 15272 1.3 2.2 9740440 1455216 ? D Aug05 124:39 nginx: worker process 0
do_lookup nobody 15273 1.3 2.2 9742540 1457160 ? D Aug05 123:52 nginx: worker process 0
xfs_buf_iowait nobody 15274 1.3 2.2 9737832 1452544 ? D Aug05 123:43 nginx: worker process 0
do_lookup nobody 15275 1.3 2.2 9741376 1456092 ? D Aug05 122:14 nginx: worker process 0
do_lookup nobody 15276 1.3 2.2 9738660 1453544 ? D Aug05 122:46 nginx: worker process 0
do_lookup nobody 15277 1.3 2.2 9740412 1455124 ? D Aug05 123:37 nginx: worker process 0
do_lookup nobody 15278 1.3 2.2 9740344 1455000 ? D Aug05 121:52 nginx: worker process 0
xfs_iget nobody 15279 1.3 2.2 9740736 1455484 ? D Aug05 123:00 nginx: worker process 0
xfs_iget nobody 15281 1.3 2.2 9741164 1455864 ? D Aug05 123:54 nginx: worker process 0
do_lookup nobody 15282 1.3 2.2 9738420 1453128 ? D Aug05 123:08 nginx: worker process 0
do_lookup nobody 15285 1.3 2.2 9739764 1454368 ? D Aug05 123:42 nginx: worker process 0
do_lookup nobody 15286 1.3 2.2 9739528 1454308 ? D Aug05 123:13 nginx: worker process 0
do_lookup nobody 15288 1.3 2.2 9739628 1454332 ? D Aug05 124:28 nginx: worker process 0
do_lookup nobody 15289 1.3 2.2 9741004 1455664 ? D Aug05 123:23 nginx: worker process 0
do_lookup nobody 15290 1.3 2.2 9740816 1455540 ? D Aug05 123:55 nginx: worker process 0
do_lookup nobody 15291 1.3 2.2 9739840 1454544 ? D Aug05 122:31 nginx: worker process 0
do_lookup nobody 15293 1.3 2.2 9740448 1455316 ? D Aug05 123:45 nginx: worker process 0
do_lookup nobody 15294 1.3 2.2 9738528 1453240 ? D Aug05 123:50 nginx: worker process 0
xfs_iget nobody 15295 1.3 2.2 9739184 1453912 ? D Aug05 123:06 nginx: worker process 0
do_lookup nobody 15296 1.3 2.2 9739888 1454664 ? D Aug05 122:55 nginx: worker process 0
do_lookup nobody 15298 1.3 2.2 9738940 1453556 ? D Aug05 122:40 nginx: worker process 0
xfs_iget nobody 15300 1.3 2.2 9740828 1455596 ? D Aug05 122:52 nginx: worker process 0
do_lookup nobody 15302 1.3 2.2 9739664 1454412 ? D Aug05 124:54 nginx: worker process 0
do_lookup nobody 15303 1.3 2.2 9738036 1452784 ? D Aug05 122:56 nginx: worker process 0
xfs_iget nobody 15304 1.3 2.2 9741260 1455968 ? D Aug05 123:23 nginx: worker process 0
do_lookup nobody 15305 1.3 2.2 9740756 1455660 ? D Aug05 124:17 nginx: worker process 0
do_lookup nobody 15306 1.3 2.2 9738720 1453452 ? D Aug05 123:35 nginx: worker process 0
xfs_iget nobody 15307 1.3 2.2 9738908 1453692 ? D Aug05 124:22 nginx: worker process 0
do_lookup nobody 15308 0.0 2.0 9669052 1358768 ? D Aug05 6:31 nginx: cache manager process0

--------------------------------------------------------------------------------------------------------------------------------------------------------

[root@w-fc12 conf]# ps aux | awk '$NF=="process" {print " "$0 system("cat /proc/"$2"/syscall")}'
2 0x1aa3240 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4f78 0x343580f000
nobody 15268 1.3 2.2 9740068 1454828 ? D Aug05 123:55 nginx: worker process 0
2 0x20770e0 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4dd0 0x343580f000
nobody 15269 1.3 2.2 9736804 1451504 ? D Aug05 123:06 nginx: worker process 0
2 0x1d94928 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f49f0 0x343580f000
nobody 15270 1.3 2.2 9738568 1453272 ? D Aug05 123:17 nginx: worker process 0
2 0x2c4c270 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f5078 0x343580f000
nobody 15271 1.3 2.2 9739520 1454184 ? D Aug05 123:14 nginx: worker process 0
2 0x3a01228 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f5130 0x343580f000
nobody 15272 1.3 2.2 9740440 1455216 ? D Aug05 124:39 nginx: worker process 0
2 0x3835a00 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4f08 0x343580f000
nobody 15273 1.3 2.2 9742540 1457160 ? D Aug05 123:52 nginx: worker process 0
17 0x298 0x1fac850 0x1000 0x0 0x343578fee8 0x1 0x7fffbb8f4d60 0x343580f0c3
nobody 15274 1.3 2.2 9737832 1452544 ? D Aug05 123:43 nginx: worker process 0
2 0x2d2dc08 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4b10 0x343580f000
nobody 15275 1.3 2.2 9741376 1456092 ? D Aug05 122:14 nginx: worker process 0
2 0x1d99bc0 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4e88 0x343580f000
nobody 15276 1.3 2.2 9738660 1453544 ? D Aug05 122:46 nginx: worker process 0
2 0x12a0430 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4dd0 0x343580f000
nobody 15277 1.3 2.2 9740412 1455124 ? D Aug05 123:37 nginx: worker process 0
2 0x364ed98 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4cb0 0x343580f000
nobody 15278 1.3 2.2 9740344 1455000 ? D Aug05 121:52 nginx: worker process 0
2 0x3a1cea8 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4b20 0x343580f000
nobody 15279 1.3 2.2 9740736 1455484 ? D Aug05 123:00 nginx: worker process 0
2 0x3454218 0x800 0x0 0x7fffffffffffffff 0x0 0x27d3568 0x7fffbb8f4cb0 0x343580f000
nobody 15281 1.3 2.2 9741164 1455864 ? D Aug05 123:54 nginx: worker process 0
2 0x35bc1f8 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4e98 0x343580f000
nobody 15282 1.3 2.2 9738420 1453128 ? D Aug05 123:08 nginx: worker process 0
2 0x2cb4118 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4ee0 0x343580f000
nobody 15285 1.3 2.2 9739764 1454368 ? D Aug05 123:42 nginx: worker process 0
2 0x31b7c20 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4d38 0x343580f000
nobody 15286 1.3 2.2 9739528 1454308 ? D Aug05 123:13 nginx: worker process 0
2 0x29ad468 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4e98 0x343580f000
nobody 15288 1.3 2.2 9739628 1454332 ? D Aug05 124:28 nginx: worker process 0
2 0x14cf388 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4ee0 0x343580f000
nobody 15289 1.3 2.2 9741004 1455664 ? D Aug05 123:23 nginx: worker process 0
2 0x36ef640 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4b38 0x343580f000
nobody 15290 1.3 2.2 9740816 1455540 ? D Aug05 123:55 nginx: worker process 0
2 0x18980d0 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4b90 0x343580f000
nobody 15291 1.3 2.2 9739840 1454544 ? D Aug05 122:31 nginx: worker process 0
2 0x35bf950 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4c90 0x343580f000
nobody 15293 1.3 2.2 9740448 1455316 ? D Aug05 123:45 nginx: worker process 0
2 0x333f660 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f46b8 0x343580f000
nobody 15294 1.3 2.2 9738528 1453240 ? D Aug05 123:50 nginx: worker process 0
2 0x335b0a8 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4e98 0x343580f000
nobody 15295 1.3 2.2 9739184 1453912 ? D Aug05 123:06 nginx: worker process 0
2 0x2814978 0x800 0x0 0x7fffffffffffffff 0x0 0x3f832d0 0x7fffbb8f4d10 0x343580f000
nobody 15296 1.3 2.2 9739888 1454664 ? D Aug05 122:55 nginx: worker process 0
2 0x2049af8 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4ac0 0x343580f000
nobody 15298 1.3 2.2 9738940 1453556 ? D Aug05 122:40 nginx: worker process 0
2 0x1806d60 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f5078 0x343580f000
nobody 15300 1.3 2.2 9740828 1455596 ? D Aug05 122:52 nginx: worker process 0
2 0x2767718 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f48d0 0x343580f000
nobody 15302 1.3 2.2 9739664 1454412 ? D Aug05 124:54 nginx: worker process 0
2 0x2f80b88 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4d40 0x343580f000
nobody 15303 1.3 2.2 9738036 1452784 ? D Aug05 122:56 nginx: worker process 0
2 0x2b13ca8 0x800 0x0 0x7fffffffffffffff 0x0 0x1895888 0x7fffbb8f4920 0x343580f000
nobody 15304 1.3 2.2 9741260 1455968 ? D Aug05 123:23 nginx: worker process 0
2 0x24bd310 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4e30 0x343580f000
nobody 15305 1.3 2.2 9740756 1455660 ? D Aug05 124:17 nginx: worker process 0
2 0x21192b0 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4af0 0x343580f000
nobody 15306 1.3 2.2 9738720 1453452 ? D Aug05 123:35 nginx: worker process 0
2 0x231cbf0 0xc2 0x180 0x0 0x0 0x0 0x7fffbb8f4e88 0x343580f000
nobody 15307 1.3 2.2 9738908 1453692 ? D Aug05 124:22 nginx: worker process 0
87 0xff57a0 0xff57e0 0x0 0x43 0x0 0xfff 0x7fffbb8f4dc8 0x34354dc697
nobody 15308 0.0 2.0 9669052 1358768 ? D Aug05 6:31 nginx: cache manager process0
------------------------------------------------------------------------------------------------------------------------------------------------
↧
Viewing all 972 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>