Happy Tuesday, Graylog community

>From time-to-time, I find that the web interface cannot contact a graylog 
server. This occurs in both clustered and non-clustered environments. To 
simplify things, I'm focusing only on the all-in-one instances for now. 
This is a Graylog 1.1.4 instance running in AWS under the provided AMI. 
Workload is steady, but load average looks fine, node stats don't show 
exhausted buffers, machine is spec'd well enough (4 proc, 32gb RAM). 
Refreshing the page once or twice is usually enough to bring it back to 
life. 

When this occurs, I don't see errors in 

/var/log/graylog/elasticsearch/current
/var/log/graylog/server/current
/var/log/graylog/mongodb/current


I do see some connection errors in /var/log/graylog/nginx/error.log (IPs 
and DNS masked)


2015/07/26 21:06:44 [error] 32592#0: *3 connect() failed (111: Connection 
refused) while connecting to upstream, client: x.x.x.x, server: , request: 
"GET /a/metrics/info?t=1437944810321 HTTP/1.1", upstream: 
"http://127.0.0.1:9000/a/metrics/info?t=1437944810321";, host: 
"example.com", referrer: 
"https://example.com/search?rangetype=relative&relative=604800&q=&interval=hour&page=1&fields=message%2Csource&sortField=timestamp&sortOrder=desc";
2015/07/26 21:06:44 [error] 32592#0: *3 connect() failed (111: Connection 
refused) while connecting to upstream, client: x.x.x.x, server: , request: 
"GET /a/connection/available HTTP/1.1", upstream: 
"http://127.0.0.1:9000/a/connection/available";, host: "example.com", 
referrer: "https://example.com/disconnected";
2015/07/26 21:07:55 [error] 32592#0: *14 upstream prematurely closed 
connection while reading upstream, client: x.x.x.x, server: , request: 
"POST /a/metrics/383/biyvtlrv/xhr?t=1437944870413 HTTP/1.1", upstream: 
"http://127.0.0.1:9000/a/metrics/383/biyvtlrv/xhr?t=1437944870413";, host: 
"example.com", referrer: "https://example.com/search";
2015/07/26 21:07:55 [error] 32592#0: *9 connect() failed (111: Connection 
refused) while connecting to upstream, client: x.x.x.x, server: , request: 
"POST /a/metrics/433/qfc23hgj/xhr?t=1437944881323 HTTP/1.1", upstream: 
"http://127.0.0.1:9000/a/metrics/433/qfc23hgj/xhr?t=1437944881323";, host: 
"example.com", referrer: 
"https://example.com/search?rangetype=relative&relative=604800&q=&interval=hour&page=1&fields=message%2Csource&sortField=timestamp&sortOrder=desc";
2015/07/26 21:07:56 [error] 32592#0: *9 connect() failed (111: Connection 
refused) while connecting to upstream, client: x.x.x.x, server: , request: 
"GET /a/connection/available HTTP/1.1", upstream: 
"http://127.0.0.1:9000/a/connection/available";, host: "example.com", 
referrer: "https://example.com/disconnected";
2015/07/26 21:08:41 [error] 508#0: *1 connect() failed (111: Connection 
refused) while connecting to upstream, client: x.x.x.x, server: , request: 
"GET /a/connection/available HTTP/1.1", upstream: 
"http://127.0.0.1:9000/a/connection/available";, host: "example.com", 
referrer: "https://example.com/disconnected";
2015/07/26 21:08:42 [error] 508#0: *4 connect() failed (111: Connection 
refused) while connecting to upstream, client: x.x.x.x, server: , request: 
"GET /a/metrics/info?t=1437944917665 HTTP/1.1", upstream: 
"http://127.0.0.1:9000/a/metrics/info?t=1437944917665";, host: 
"example.com", referrer: "https://example.com/search";
2015/07/26 21:08:42 [error] 508#0: *4 connect() failed (111: Connection 
refused) while connecting to upstream, client: x.x.x.x, server: , request: 
"GET /a/system/notifications HTTP/1.1", upstream: 
"http://127.0.0.1:9000/a/system/notifications";, host: "example.com", 
referrer: "https://example.com/search";
2015/07/26 21:08:43 [error] 508#0: *1 connect() failed (111: Connection 
refused) while connecting to upstream, client: x.x.x.x, server: , request: 
"GET /a/connection/available HTTP/1.1", upstream: 
"http://127.0.0.1:9000/a/connection/available";, host: "example.com", 
referrer: "https://example.com/disconnected";



Since everything is self-contained, I'm not sure why a call to 
127.0.0.1:9000 would be refused. ufw is disabled.

Any ideas where else to look?

-- 
You received this message because you are subscribed to the Google Groups 
"graylog2" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to graylog2+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to