Connection refused error code 111

In this article, we will learn what is the ConnectionRefusedError, basically this error indicates that the client is unable to connect to the port on the system running the server script.
  1. Why the ConnectionRefusedError: [Errno 111] Connection refused Occurs in Python
  2. How to Solve the ConnectionRefusedError: [Errno 111] Connection refused in Python
  3. Conclusion

ConnectionRefusedError: [Errno 111] Connection Refused

This error indicates that the client cannot connect to the port on the server script’s system. Since you can ping the server, it should not be the case.

This might be caused by many reasons, such as improper routing to the destination. The second possibility is that you have a firewall between your client and server, which may be either on the server or the client.

There shouldn’t be any routers or firewalls that may stop the communication since, based on your network addresses, both the server and the client should be on the same Local Area Network.

Why the ConnectionRefusedError: [Errno 111] Connection refused Occurs in Python

This error arises when the client cannot access the server because of an invalid IP or port or if the address is not unique and used by another server.

The connection refused error also arises when the server is not running, so the client cannot access the server as the server should accept the connection first.

Code example:

# server code
import socket

s = socket.socket()
host = socket.gethostname()
port = 1717
s.bind((host, port))

s.listen(5)
while True:
    c,addr = s.accept()
    print("Got connection ", addr)
    c.send("Meeting is at 10am")
    c.close()

# client code
import socket

s = socket.socket()
host = '192.168.1.2'
port = 1717

s.connect((host,port))
print(s.recv(1024))
s.close

Output:

socket.error: [Errno 111] Connection refused

How to Solve the ConnectionRefusedError: [Errno 111] Connection refused in Python

Try to keep the receiving socket as accessible as possible. Perhaps accessibility would only take place on one interface, which would not impact the Local Area Network.

On the other hand, one case can be that it exclusively listens to the address 127.0.0.1, making connections from other hosts impossible.

Code example:

import socket

s = socket.socket()
host = socket.gethostname()
port = 1717
s.bind(('', port))

s.listen(5)
while True:
    c,addr = s.accept()
    print("Got connection ", addr)
    c.send("The Meeting is at 10 am")
    c.close()

import socket

s = socket.socket()
host = socket.gethostname()
port = 1717
s.bind(('', port))

s.connect((host, port))
print(s.recv(1024))
s.close()

Output:

Got connection('192.168.1.2')
The meeting is at 10 am

When you run the command python server.py, you will receive the message Got connection. At the same time when you run the command python client.py, you will receive a message from the server.

The DNS resolution can be the other reason behind this problem. Since the socket.gethostname() returns the hostname, an error will be returned if the operating system cannot translate it to a local address.

The Linux operating system can edit the host file by adding one line.

host = socket.gethostname()
port = 1717
s.bind((host,port))

Use gethostbyname

host = socket.gethostbyname("192.168.1.2")
s.bind((host, port))

Thus, you must use the identical technique on the client and server sides to access the host. For instance, you would apply the procedure described above in a client’s case.

You can also access through local hostname hostnamehost = socket.gethostname() or specific name for local host host = socket.gethostbyname("localhost").

host = socket.gethostname()
s.connect((host, port))

host = socket.gethostbyname("localhost")
s.connect((host, port))

Conclusion

ConnectionRefusedError in Python arises when the client cannot connect to the server. Several reasons include the client not knowing the IP or port address and the server not running when the client wants to connect.

There are several methods mentioned above to resolve this connection issue.

Источник

Содержание

  1. ConnectionRefusedError: [Errno 111] Connection Refused
  2. Why the ConnectionRefusedError: [Errno 111] Connection refused Occurs in Python
  3. How to Solve the ConnectionRefusedError: [Errno 111] Connection refused in Python
  4. Use gethostbyname
  5. Conclusion
  6. «socket.error: [Errno 111] Connection refused» while training on ADE20K #215
  7. Comments
  8. ConnectionRefusedError: [Errno 111] Connection refused
  9. ss -lt
  10. ss -lt
  11. 1 Answer 1
  12. socket.error: [Errno 111] Connection refused [JIRA: CLIENTS-41] #375
  13. Comments
  14. connect() failed (111: Connection refused) while connecting to upstream
  15. 8 Answers 8
  16. Summary:

ConnectionRefusedError: [Errno 111] Connection Refused

This error indicates that the client cannot connect to the port on the server script’s system. Since you can ping the server, it should not be the case.

This might be caused by many reasons, such as improper routing to the destination. The second possibility is that you have a firewall between your client and server, which may be either on the server or the client.

There shouldn’t be any routers or firewalls that may stop the communication since, based on your network addresses, both the server and the client should be on the same Local Area Network.

Why the ConnectionRefusedError: [Errno 111] Connection refused Occurs in Python

This error arises when the client cannot access the server because of an invalid IP or port or if the address is not unique and used by another server.

The connection refused error also arises when the server is not running, so the client cannot access the server as the server should accept the connection first.

How to Solve the ConnectionRefusedError: [Errno 111] Connection refused in Python

Try to keep the receiving socket as accessible as possible. Perhaps accessibility would only take place on one interface, which would not impact the Local Area Network.

On the other hand, one case can be that it exclusively listens to the address 127.0.0.1 , making connections from other hosts impossible.

When you run the command python server.py , you will receive the message Got connection . At the same time when you run the command python client.py , you will receive a message from the server.

The DNS resolution can be the other reason behind this problem. Since the socket.gethostname() returns the hostname, an error will be returned if the operating system cannot translate it to a local address.

The Linux operating system can edit the host file by adding one line.

Use gethostbyname

Thus, you must use the identical technique on the client and server sides to access the host. For instance, you would apply the procedure described above in a client’s case.

You can also access through local hostname hostnamehost = socket.gethostname() or specific name for local host host = socket.gethostbyname(«localhost») .

Conclusion

ConnectionRefusedError in Python arises when the client cannot connect to the server. Several reasons include the client not knowing the IP or port address and the server not running when the client wants to connect.

There are several methods mentioned above to resolve this connection issue.

Zeeshan is a detail oriented software engineer that helps companies and individuals make their lives and easier with software solutions.

Источник

«socket.error: [Errno 111] Connection refused» while training on ADE20K #215

I am getting following error after few data iteration @ 551/22210:

File «train.py», line 201, in
trainer.training(epoch)
File «train.py», line 142, in training
for i, (data, target) in enumerate(tbar):
File «/usr/local/lib/python2.7/dist-packages/tqdm/_tqdm.py», line 930, in iter
for obj in iterable:
File «/usr/local/lib/python2.7/dist-packages/mxnet/gluon/data/dataloader.py», line 222, in next
return self.next()
File «/usr/local/lib/python2.7/dist-packages/mxnet/gluon/data/dataloader.py», line 218, in next
idx, batch = self._data_queue.get()
File «/usr/lib/python2.7/multiprocessing/queues.py», line 117, in get
res = self._recv()
File «/usr/local/lib/python2.7/dist-packages/mxnet/gluon/data/dataloader.py», line 88, in recv
return pickle.loads(buf)
File «/usr/lib/python2.7/pickle.py», line 1388, in loads
return Unpickler(file).load()
File «/usr/lib/python2.7/pickle.py», line 864, in load
dispatchkey
File «/usr/lib/python2.7/pickle.py», line 1139, in load_reduce
value = func(*args)
File «/usr/local/lib/python2.7/dist-packages/mxnet/gluon/data/dataloader.py», line 53, in rebuild_ndarray
fd = multiprocessing.reduction.rebuild_handle(fd)
File «/usr/lib/python2.7/multiprocessing/reduction.py», line 156, in rebuild_handle
conn = Client(address, authkey=current_process().authkey)
File «/usr/lib/python2.7/multiprocessing/connection.py», line 169, in Client
c = SocketClient(address)
File «/usr/lib/python2.7/multiprocessing/connection.py», line 308, in SocketClient
s.connect(address)
File «/usr/lib/python2.7/socket.py», line 228, in meth
return getattr(self._sock,name)(*args)
socket.error: [Errno 111] Connection refused

I am using latest nightly of MXNET along with Sync BatchNorm, This error comes with and without SyncBatchNorm layer.

I am using MXNET docker

Any help is much appreciated.

The text was updated successfully, but these errors were encountered:

Источник

ConnectionRefusedError: [Errno 111] Connection refused

I get «connection refused 111» when trying to communicate over sockets in Python. When the connection is refused, THE LISTENER STOPS LISTENING. Same problem occurs using import of multiprocessing.connection, socket, zeromq.

My feeling is that the link between Python and the OS/network doesn’t work. However the NC and socket commands issued in a ubuntu terminal can communicate over the same port.

Notwithstanding the inconvenience it’s causing me, there is obviously a severe security risk if an invalid connection request causes a socket to stop listening. Ideal for denial of service attacks.

I have two programs:

When I start the listener (f5 in IDLE), it seems to start ok.

and the socket starts listening:

ss -lt

State Recv-Q Send-Q Local Address:Port Peer Address:Port Process

LISTEN 0 1 192.168.1.100:16001 0.0.0.0:*

However, when I start the client (f5 in IDLE) I get this:

and the listening socket disappears.

ss -lt

State Recv-Q Send-Q Local Address:Port Peer Address:Port Process

LISTEN 0 5 127.0.0.1:ipp 0.0.0.0:* LISTEN 0 1 127.0.0.1:36093
0.0.0.0:*
LISTEN 0 5 [::1]:ipp [::]:*

Ive tried changing port numbers, setting FW rules, IP addresses from hard-coded to «localhost», . remote client (on Windows) etc etc. Nothing works although symptoms vary.

Ive tried programming the connection using the «socket import» and have exactly the same results. zeromq doesn’t work either.

However the NC and socket commands issued in a terminal can communicate over the same port.

fwiw Im running Ubuntu 20.04.2 LTS. Apart from the one client I tried on windows, all testing is done on a single ubuntu system. Its a fairly new install, so its unlikely I’ve broken something.

Please can someone tell me what I’m doing wrong?

My feeling is that the link between Python and the OS/network doesn’t work.

Notwithstanding the inconvenience it’s causing me, there is obviously a severe security risk if an invalid connection request causes a socket to stop listening. Ideal for denial of service attacks.

1 Answer 1

I couldn’t reproduce your issue, thus not sure what’s the problem. But, some remarks.

I added a simple ping-pong exchange to your code:

and also changed the listening address to one from the link-local subnet 127.0.0.0/8 .

Then simply using 2 terminal tabs/windows, run t2.py then t1.py 3 times:

The server process continues to run, as expected. The client tab:

Please pay attention. You may think these things you named are the same — but they are significantly different:

multiprocessing.connection, socket, zeromq.

The python-builtin import socket module is direct translation of the classic BSD sockets API. The «sockets API» is what defines such things as: port, listening on a port, connecting to a port, accepting a connection, send , recv , close and a few more functions. A book on network programming may help (e.g. this one as a random example — I don’t endorse it). The sockets API is almost 40 years old, so you’ll also easily find free learning materials online.

Next, import multiprocessing module. It’s a completely different story. It provides helpers for multi-process Python programs. Those create multiple PIDs and can run on multiple processor cores. Almost certainly you’ll want these processes to talk to each other to do useful work. This is where sockets come handy: since processes are isolated by OS from each other, network provides a way to build that communication (even if it’s localhost-only). The sub-module multiprocessing.connection provides ergonomic helpers exactly for that.

Next, ØMQ is altogether a separate project (it’s not python-builtin; neither it’s python-specific). It does something interesting; it redefines another «socket API». ØMQ socket ≠ BSD socket. Zeromq sockets can do things which BSD sockets can’t (pub/sub, fanout, app-level routing). Zeromq sockets are built «on top of» BSD sockets; if you have troubles with the lower-level API, I would recommend to approach ZMQ only after you get comfortable with bare basic sockets.

Nothing works although symptoms vary.

Again, you should get comfortable with interpreting network failure modes. The raised error codes have precisely defined meanings. For example, the classic Connection refused errno 111 means that the initial SYN packet to the host you connect() to was responded with an RST packet instead of the normal SYN+ACK — which usually happens when there’s no program listening to the given port on the remote computer you connect() to.

One more remark with regards to your security concerns. You should always assume that the network is adversarial (hostile), regardless if it’s indeed true at that point in space & time — even the localhost network. This is why the higher-level multiprocessing API has the authkey parameter; it’s practically always needed. The password bytestring is one of the worst values for authkey imaginable, try something better. An active network adversary could, theoretically, explain your issue; there’s something called «RST injection attack». You might’ve simply exhausted the listen backlog/SOMAXCONN, too.

Источник

socket.error: [Errno 111] Connection refused [JIRA: CLIENTS-41] #375

I am using RIAK Python client for my project and RIAK amazon instance.I got this error while running my project and its related to RIAK instance.My error log is :-
Traceback (most recent call last):
File «ironjob/ai/index.py», line 36, in application
returnval = mManager.process(api)
File «ironjob/ai/ironMainManager.py», line 94, in process
return self.mUserManager.process(listitem)
File «ironjob/ai/ironUserManager.py», line 27, in process
return self.userVerification(listitem)
File «ironjob/ai/ironUserManager.py», line 62, in userVerification
self.mCacheManager.addData(BUCKET_AI, datadict[KEY_SESSID], sessionData, cacheStart=1, cacheEnd=3, timeout=60)
File «ironjob/ai/ironCacheManager.py», line 55, in addData
self.mRiakClient.addData(bucket, key, dataVals, nestedKey=innerKey, timeout=timeout)
File «ironjob/ai/ironRiakClient.py», line 53, in addData
currentData = <> if bucket.get(key).get_data() == None else bucket.get(key).get_data()
File «build/bdist.linux-x86_64/egg/riak/bucket.py», line 326, in get
File «build/bdist.linux-x86_64/egg/riak/riak_object.py», line 459, in reload
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 251, in get
File «build/bdist.linux-x86_64/egg/riak/transports/feature_detect.py», line 76, in quorum_controls
File «build/bdist.linux-x86_64/egg/riak/util.py», line 61, in get
File «build/bdist.linux-x86_64/egg/riak/transports/feature_detect.py», line 95, in server_version
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 178, in _server_version
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 206, in get_server_info
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 528, in send_msg_code
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 559, in send_pkt
File «build/bdist.linux-x86_64/egg/riak/transports/pbc.py», line 113, in maybe_connect
File «build/bdist.linux-x86_64/egg/riak/transports/connection.py», line 166, in maybe_connect

File «», line 1, in connect
socket.error: [Errno 111] Connection refused

Please help me out.Thanks in advance.

The text was updated successfully, but these errors were encountered:

Connection refused means exactly what it says. Whatever port you tried to connect to, the Riak server is not listening on or is otherwise inaccessible. Possible causes/solutions:

Источник

connect() failed (111: Connection refused) while connecting to upstream

I’m experiencing 502 Gateway errors when accessing a PHP file in a directory ( http://example.com/dev/index.php ). The logs simply says this:

I’ve never experienced this before. What is the solution for this type of 502 Gateway error?

This is the nginx.conf :

8 Answers 8

It sounds like you haven’t started and configured the backend for Nginx. Start php-fpm and add the following to nginx.conf , in the http context:

This answer is only for those who get an error like this:

connect() failed (111: Connection refused) while connecting to upstream, client . fastcgi://[::1]:9000

Rewrite your nginx config to use ip, not dns. For instance, 127.0.0.1 instead of localhost , or remove the ipv6 alias from /etc/hosts.

Got errors like this too. Problem was my abstract backend referencing two servers. php-fpm was only listing to socket.

Had the same problem with proxied requests to a Node server listening on port 5000. Requests would result with 200 OK but sometime 502 Bad Gateway randomly. NGINX showed the error:

  1. Set node HTTP server to listen strictly for ipv4 by including localhost as host: server.listen(5000, ‘localhost’);
  2. Removed any ipv6 listen directives ( listen [::]:80; or listen [::]:443 ssl default_server; ).
  3. Changed location block proxy_pass to use IPs: proxy_pass http://127.0.0.1:5000 (not proxy_pass http://localhost:5000 ).

Hope this helps someone.

In my case the error was a bad location for the error_log file for php5.6-fpm service and thus the php-fpm service was failing to start and nginx was not able to connect to it. You can find it in /etc/php/5.6/fpm/php.ini (you can replace 5.6 with the version you are running).

Same problem has occured for me and finally I found firewalld was blocking required ports after installation and I was missing to open ports in firewall (port 9000 in your logs).

Just in case somebody is deperately trying to fix their problem just to realize there is nothing wrong with their reverse proxy setup:

In my case, the error persisted even after I’ve removed all location directives but a single one that only provides static content.

The error message was caused because Nginx wasn’t able to log it’s log to the syslog server:

Summary:

If you are using a syslog log server, make sure it is available. To test whether the error originates from the logging setup, comment out all logging configs so that Nginx falls back to the native logging scheme.

I hope this saves some people time debugging a fully valid reverse proxy config, just to fid the error somewhere else 😀

Источник

Источник

After upgrading and building from master, (using config to increase server_names_hash_bucket_size + client_max_body_size) I’m not able to access my services via ingress routes.

The error I’m getting is..

[error] 26#26: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 10.36.5.79, server: gogs.default.beast.fabric8.io, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:8181/", host: "gogs.default.beast.fabric8.io"

My Ingress looks like:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: gogs
spec:
  rules:
  - host: gogs.default.beast.fabric8.io
    http:
      paths:
      - backend:
          serviceName: gogs
          servicePort: 80
status:
  loadBalancer: {}

I can successfully access the gogs service from within the nginx ingress controller pod if I install curl and use the kubernetes service: curl http://gogs, so the cluster dns all seems to work fine.

By no means am I ruling out something I’ve done but I’ve checked a number of things and now out of ideas, I’m wondering if this upstream section in the logs is correct?

upstream default-gogs-gogs.default.beast.fabric8.io-gogs {

    server 127.0.0.1:8181;
}

The full log with the nginx config used and error at the bottom:

I0726 09:15:30.392509       1 nginx.go:234] Writing NGINX conf to /etc/nginx/nginx.conf

user  nginx;
worker_processes  1;

error_log  /var/log/nginx/error.log warn;
pid        /var/run/nginx.pid;


events {
    worker_connections  1024;
}


http {
    include       /etc/nginx/mime.types;
    default_type  application/octet-stream;

    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  /var/log/nginx/access.log  main;

    sendfile        on;
    #tcp_nopush     on;

    keepalive_timeout  65;

    #gzip  on;

    server_names_hash_max_size 1024;
    server_names_hash_bucket_size 512;

    include /etc/nginx/conf.d/*.conf;
}
I0726 09:15:30.393053       1 nginx.go:252] The main NGINX configuration file had been updated
I0726 09:15:30.393098       1 nginx.go:207] executing nginx
I0726 09:15:30.434586       1 controller.go:99] Adding service: elasticsearch
I0726 09:15:30.434629       1 controller.go:350] ignoring service elasticsearch: No ingress for service elasticsearch
I0726 09:15:30.434676       1 controller.go:99] Adding service: gogs-ssh
I0726 09:15:30.434680       1 controller.go:350] ignoring service gogs-ssh: No ingress for service gogs-ssh
I0726 09:15:30.434686       1 controller.go:99] Adding service: kube-dns
I0726 09:15:30.434689       1 controller.go:350] ignoring service kube-dns: No ingress for service kube-dns
I0726 09:15:30.434694       1 controller.go:99] Adding service: jenkinshift
I0726 09:15:30.434697       1 controller.go:350] ignoring service jenkinshift: No ingress for service jenkinshift
I0726 09:15:30.434709       1 controller.go:99] Adding service: kubernetes
I0726 09:15:30.434715       1 controller.go:350] ignoring service kubernetes: No ingress for service kubernetes
I0726 09:15:30.434720       1 controller.go:99] Adding service: nexus
I0726 09:15:30.434727       1 controller.go:350] ignoring service nexus: No ingress for service nexus
I0726 09:15:30.434732       1 controller.go:99] Adding service: elasticsearch-masters
I0726 09:15:30.434740       1 controller.go:350] ignoring service elasticsearch-masters: No ingress for service elasticsearch-masters
I0726 09:15:30.434745       1 controller.go:99] Adding service: fabric8-forge
I0726 09:15:30.434763       1 controller.go:350] ignoring service fabric8-forge: No ingress for service fabric8-forge
I0726 09:15:30.434770       1 controller.go:99] Adding service: grafana
I0726 09:15:30.434773       1 controller.go:350] ignoring service grafana: No ingress for service grafana
I0726 09:15:30.434780       1 controller.go:99] Adding service: kibana
I0726 09:15:30.434783       1 controller.go:350] ignoring service kibana: No ingress for service kibana
I0726 09:15:30.434792       1 controller.go:99] Adding service: prometheus
I0726 09:15:30.434796       1 controller.go:350] ignoring service prometheus: No ingress for service prometheus
I0726 09:15:30.434804       1 controller.go:99] Adding service: fabric8
I0726 09:15:30.434807       1 controller.go:350] ignoring service fabric8: No ingress for service fabric8
I0726 09:15:30.434816       1 controller.go:99] Adding service: gogs
I0726 09:15:30.434819       1 controller.go:350] ignoring service gogs: No ingress for service gogs
I0726 09:15:30.434829       1 controller.go:99] Adding service: jenkins-jnlp
I0726 09:15:30.434832       1 controller.go:350] ignoring service jenkins-jnlp: No ingress for service jenkins-jnlp
I0726 09:15:30.434837       1 controller.go:99] Adding service: fabric8-docker-registry
I0726 09:15:30.434862       1 controller.go:350] ignoring service fabric8-docker-registry: No ingress for service fabric8-docker-registry
I0726 09:15:30.434867       1 controller.go:99] Adding service: jenkins
I0726 09:15:30.434870       1 controller.go:350] ignoring service jenkins: No ingress for service jenkins
I0726 09:15:30.437675       1 controller.go:125] Adding endpoints: gogs-ssh
I0726 09:15:30.437707       1 controller.go:125] Adding endpoints: nexus
I0726 09:15:30.437713       1 controller.go:125] Adding endpoints: prometheus
I0726 09:15:30.437718       1 controller.go:125] Adding endpoints: elasticsearch-masters
I0726 09:15:30.437725       1 controller.go:125] Adding endpoints: fabric8-docker-registry
I0726 09:15:30.437730       1 controller.go:125] Adding endpoints: fabric8-forge
I0726 09:15:30.437734       1 controller.go:125] Adding endpoints: kube-controller-manager
I0726 09:15:30.437739       1 controller.go:125] Adding endpoints: kube-dns
I0726 09:15:30.437744       1 controller.go:125] Adding endpoints: elasticsearch
I0726 09:15:30.437750       1 controller.go:125] Adding endpoints: gogs
I0726 09:15:30.437755       1 controller.go:125] Adding endpoints: grafana
I0726 09:15:30.437759       1 controller.go:125] Adding endpoints: jenkins
I0726 09:15:30.437764       1 controller.go:125] Adding endpoints: kube-scheduler
I0726 09:15:30.437770       1 controller.go:125] Adding endpoints: fabric8
I0726 09:15:30.437778       1 controller.go:125] Adding endpoints: jenkins-jnlp
I0726 09:15:30.437782       1 controller.go:125] Adding endpoints: jenkinshift
I0726 09:15:30.437787       1 controller.go:125] Adding endpoints: kibana
I0726 09:15:30.437791       1 controller.go:125] Adding endpoints: kubernetes
I0726 09:15:30.437797       1 utils.go:70] Syncing default/gogs-ssh
I0726 09:15:30.437803       1 controller.go:257] Syncing endpoints default/gogs-ssh
I0726 09:15:30.437839       1 controller.go:350] ignoring service gogs-ssh: No ingress for service gogs-ssh
I0726 09:15:30.437845       1 utils.go:70] Syncing default/nexus
I0726 09:15:30.437848       1 controller.go:257] Syncing endpoints default/nexus
I0726 09:15:30.437852       1 controller.go:350] ignoring service nexus: No ingress for service nexus
I0726 09:15:30.437859       1 utils.go:70] Syncing default/prometheus
I0726 09:15:30.437862       1 controller.go:257] Syncing endpoints default/prometheus
I0726 09:15:30.437866       1 controller.go:350] ignoring service prometheus: No ingress for service prometheus
I0726 09:15:30.437870       1 utils.go:70] Syncing default/elasticsearch-masters
I0726 09:15:30.437872       1 controller.go:257] Syncing endpoints default/elasticsearch-masters
I0726 09:15:30.437876       1 controller.go:350] ignoring service elasticsearch-masters: No ingress for service elasticsearch-masters
I0726 09:15:30.437880       1 utils.go:70] Syncing default/fabric8-docker-registry
I0726 09:15:30.437882       1 controller.go:257] Syncing endpoints default/fabric8-docker-registry
I0726 09:15:30.437886       1 controller.go:350] ignoring service fabric8-docker-registry: No ingress for service fabric8-docker-registry
I0726 09:15:30.437890       1 utils.go:70] Syncing default/fabric8-forge
I0726 09:15:30.437892       1 controller.go:257] Syncing endpoints default/fabric8-forge
I0726 09:15:30.437896       1 controller.go:350] ignoring service fabric8-forge: No ingress for service fabric8-forge
I0726 09:15:30.437900       1 utils.go:70] Syncing kube-system/kube-controller-manager
I0726 09:15:30.437902       1 controller.go:257] Syncing endpoints kube-system/kube-controller-manager
I0726 09:15:30.437907       1 utils.go:70] Syncing kube-system/kube-dns
I0726 09:15:30.437909       1 controller.go:257] Syncing endpoints kube-system/kube-dns
I0726 09:15:30.437913       1 controller.go:350] ignoring service kube-dns: No ingress for service kube-dns
I0726 09:15:30.437919       1 utils.go:70] Syncing default/elasticsearch
I0726 09:15:30.437922       1 controller.go:257] Syncing endpoints default/elasticsearch
I0726 09:15:30.437926       1 controller.go:350] ignoring service elasticsearch: No ingress for service elasticsearch
I0726 09:15:30.437929       1 utils.go:70] Syncing default/gogs
I0726 09:15:30.437932       1 controller.go:257] Syncing endpoints default/gogs
I0726 09:15:30.437936       1 controller.go:350] ignoring service gogs: No ingress for service gogs
I0726 09:15:30.437939       1 utils.go:70] Syncing default/grafana
I0726 09:15:30.437942       1 controller.go:257] Syncing endpoints default/grafana
I0726 09:15:30.437946       1 controller.go:350] ignoring service grafana: No ingress for service grafana
I0726 09:15:30.437949       1 utils.go:70] Syncing default/jenkins
I0726 09:15:30.437952       1 controller.go:257] Syncing endpoints default/jenkins
I0726 09:15:30.437955       1 controller.go:350] ignoring service jenkins: No ingress for service jenkins
I0726 09:15:30.437959       1 utils.go:70] Syncing kube-system/kube-scheduler
I0726 09:15:30.437962       1 controller.go:257] Syncing endpoints kube-system/kube-scheduler
I0726 09:15:30.437965       1 utils.go:70] Syncing default/fabric8
I0726 09:15:30.437968       1 controller.go:257] Syncing endpoints default/fabric8
I0726 09:15:30.437972       1 controller.go:350] ignoring service fabric8: No ingress for service fabric8
I0726 09:15:30.437975       1 utils.go:70] Syncing default/jenkins-jnlp
I0726 09:15:30.437978       1 controller.go:257] Syncing endpoints default/jenkins-jnlp
I0726 09:15:30.437981       1 controller.go:350] ignoring service jenkins-jnlp: No ingress for service jenkins-jnlp
I0726 09:15:30.437985       1 utils.go:70] Syncing default/jenkinshift
I0726 09:15:30.437988       1 controller.go:257] Syncing endpoints default/jenkinshift
I0726 09:15:30.437993       1 controller.go:350] ignoring service jenkinshift: No ingress for service jenkinshift
I0726 09:15:30.437997       1 utils.go:70] Syncing default/kibana
I0726 09:15:30.438000       1 controller.go:257] Syncing endpoints default/kibana
I0726 09:15:30.438003       1 controller.go:350] ignoring service kibana: No ingress for service kibana
I0726 09:15:30.438007       1 utils.go:70] Syncing default/kubernetes
I0726 09:15:30.438009       1 controller.go:257] Syncing endpoints default/kubernetes
I0726 09:15:30.438013       1 controller.go:350] ignoring service kubernetes: No ingress for service kubernetes
I0726 09:15:30.438149       1 controller.go:73] Adding Ingress: gogs
I0726 09:15:30.438168       1 utils.go:70] Syncing default/gogs
I0726 09:15:30.438174       1 controller.go:316] Syncing default/gogs
I0726 09:15:30.438179       1 controller.go:331] Adding or Updating Ingress: default/gogs
I0726 09:15:30.438218       1 nginx.go:110] Updating NGINX configuration
I0726 09:15:30.438579       1 nginx.go:156] Writing NGINX conf to /etc/nginx/conf.d/default-gogs.conf

upstream default-gogs-gogs.default.beast.fabric8.io-gogs {

    server 127.0.0.1:8181;
}


server {
    listen 80;



    server_name gogs.default.beast.fabric8.io;





    location / {
        proxy_connect_timeout 60s;
        proxy_read_timeout 60s;
        client_max_body_size 2000m;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Port $server_port;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_pass http://default-gogs-gogs.default.beast.fabric8.io-gogs;
    }
}
I0726 09:15:30.439027       1 nginx.go:176] NGINX configuration file had been updated
I0726 09:15:30.439044       1 nginx.go:207] executing nginx -s reload
2016/07/26 09:15:30 [notice] 21#21: signal process started
I0726 09:15:30.456051       1 controller.go:160] Adding ConfigMap: nginx-config
I0726 09:15:30.456121       1 utils.go:70] Syncing default/nginx-config
I0726 09:15:30.456129       1 controller.go:279] Syncing configmap default/nginx-config
I0726 09:15:30.456265       1 nginx.go:234] Writing NGINX conf to /etc/nginx/nginx.conf

user  nginx;
worker_processes  1;

error_log  /var/log/nginx/error.log warn;
pid        /var/run/nginx.pid;


events {
    worker_connections  1024;
}


http {
    include       /etc/nginx/mime.types;
    default_type  application/octet-stream;

    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

I0726 09:15:30.456419       1 nginx.go:252] The main NGINX configuration file had been updated
    access_log  /var/log/nginx/access.log  main;

    sendfile        on;
    #tcp_nopush     on;

    keepalive_timeout  65;

    #gzip  on;

    server_names_hash_max_size 1024;
    server_names_hash_bucket_size 256;

    include /etc/nginx/conf.d/*.conf;
}
I0726 09:15:30.456468       1 utils.go:70] Syncing default/gogs
I0726 09:15:30.456489       1 controller.go:316] Syncing default/gogs
I0726 09:15:30.456494       1 controller.go:331] Adding or Updating Ingress: default/gogs
I0726 09:15:30.456505       1 nginx.go:110] Updating NGINX configuration
I0726 09:15:30.456715       1 nginx.go:156] Writing NGINX conf to /etc/nginx/conf.d/default-gogs.conf

upstream default-gogs-gogs.default.beast.fabric8.io-gogs {

    server 127.0.0.1:8181;
}


server {
    listen 80;



    server_name gogs.default.beast.fabric8.io;





    location / {
        proxy_connect_timeout 10s;
        proxy_read_timeout 10s;
        client_max_body_size 2000m;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Port $server_port;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_pass http://default-gogs-gogs.default.beast.fabric8.io-gogs;
    }
}
I0726 09:15:30.456979       1 nginx.go:176] NGINX configuration file had been updated
I0726 09:15:30.457230       1 nginx.go:207] executing nginx -s reload
2016/07/26 09:15:30 [notice] 25#25: signal process started
I0726 09:15:30.500502       1 controller.go:136] Endpoints kube-scheduler changed, syncing
I0726 09:15:30.500525       1 utils.go:70] Syncing kube-system/kube-scheduler
I0726 09:15:30.500529       1 controller.go:257] Syncing endpoints kube-system/kube-scheduler
I0726 09:15:32.522029       1 controller.go:136] Endpoints kube-controller-manager changed, syncing
I0726 09:15:32.522068       1 utils.go:70] Syncing kube-system/kube-controller-manager
I0726 09:15:32.522074       1 controller.go:257] Syncing endpoints kube-system/kube-controller-manager
I0726 09:15:32.716975       1 controller.go:136] Endpoints kube-scheduler changed, syncing
I0726 09:15:32.717006       1 utils.go:70] Syncing kube-system/kube-scheduler
I0726 09:15:32.717011       1 controller.go:257] Syncing endpoints kube-system/kube-scheduler
2016/07/26 09:15:34 [error] 26#26: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 10.36.5.79, server: gogs.default.beast.fabric8.io, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:8181/", host: "gogs.default.beast.fabric8.io"
10.36.5.79 - - [26/Jul/2016:09:15:34 +0000] "GET / HTTP/1.1" 502 575 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36" "-"
2016/07/26 09:15:34 [error] 26#26: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 10.36.5.79, server: gogs.default.beast.fabric8.io, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8181/favicon.ico", host: "gogs.default.beast.fabric8.io", referrer: "http://gogs.default.beast.fabric8.io/"
10.36.5.79 - - [26/Jul/2016:09:15:34 +0000] "GET /favicon.ico HTTP/1.1" 502 575 "http://gogs.default.beast.fabric8.io/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36" "-"
I0726 09:15:34.618370       1 controller.go:136] Endpoints kube-controller-manager changed, syncing
Источник

Понравилась статья? Поделить с друзьями:
  • Connection failed flowsocketconnector failed to connect to target address windows error 10060
  • Connection failed error ts 02 brother
  • Configure error libpng is required for writing png messages
  • Connection failed error code 10049
  • Configure error libpam required but missing