When I join another host machine as a worker to my swarm the log gives me this error
ERRO[2021-05-06T16:27:16.208574765+07:00] Could not open netlink handle during vni population for ns /var/run/docker/netns/1-p0wju48aad: failed to set into network namespace 21 while creating netlink socket: invalid argument
How to solve this guys?
Well this error could just a random error in my VM for no reason so this could be ignored
Related
Our application is docker based and requires Nat network to be created on the host machine in order to communicate since its a web service. It was working since last 4 months and suddenly stopped working. Checked and found that docker service is stopped. Manually tried restarting the service but it failed to start. Below is the error in the event log:
Error:
fatal: failed to start deamon: Error initializing network controller: Error creating default network: failed during hnsCallRawResponse: hnsCall failed in Win32: There are no more endpoints available from endpoint mapper. (0x6d9)
Tried the below steps:
Deleted the hns.data and restarted the hns service. Then restarted the docker engine service. The issue persists.
Tried running MOFCOMP. Same issue.
Tried removing docker and reinstalling it. Doesn't work.
Tried creating nat network manually. But getting the above mentioned error.
Can someone help here? what needs to be checked or what could be the reason for this issue?
during OpenShift installation from a local mirror registry, after I started the bootstrap machine i see the following error in the journal log:
release-image-download.sh[1270]:
Error: error pulling image "quay.io/openshift-release-dev/ocp-release#sha256:999a6a4bd731075e389ae601b373194c6cb2c7b4dadd1ad06ef607e86476b129":
unable to pull quay.io/openshift-release-dev/ocp-release#sha256:999a6a4bd731075e389ae601b373194c6cb2c7b4dadd1ad06ef607e86476b129: unable to pull image:
Error initializing source docker://quay.io/openshift-release-dev/ocp-release#sha256:999a6a4bd731075e389ae601b373194c6cb2c7b4dadd1ad06ef607e86476b129:
(Mirrors also failed: [my registry:5000/ocp4/openshift4#sha256:999a6a4bd731075e389ae601b373194c6cb2c7b4dadd1ad06ef607e86476b129: Error reading manifest
sha256:999a6a4bd731075e389ae601b373194c6cb2c7b4dadd1ad06ef607e86476b129 in my registry:5000/ocp4/openshift4: manifest unknown: manifest unknown]):
quay.io/openshift-release-dev/ocp-release#sha256:999a6a4bd731075e389ae601b373194c6cb2c7b4dadd1ad06ef607e86476b129: error pinging docker registry quay.io:
Get "https://quay.io/v2/": dial tcp 50.16.140.223:443: i/o timeout
Does anyone have any idea what it can be?
The answer is here in the error:
... dial tcp 50.16.140.223:443: i/o timeout
Try this on the command line:
$ podman pull quay.io/openshift-release-dev/ocp-release#sha256:999a6a4bd731075e389ae601b373194c6cb2c7b4dadd1ad06ef607e86476b129
You'll need to be authenticated to actually download the content (this is what the pull secret does). However, if you can't get the "unauthenticated" error then this would more solidly point to some network configuration.
That IP resolves to a quay host (you can verify that with "curl -k https://50.16.140.223"). Perhaps you have an internet filter or firewall in place that's blocking egress?
Resolutions:
fix your network issue, if you have one
look at doing an disconnected /airgap install -- https://docs.openshift.com/container-platform/4.7/installing/installing-mirroring-installation-images.html has more details on that
(If you're already doing an airgap install and it's your local mirror that's failing, then your local mirror is failing)
I'm getting this error in the docker logs of my haproxy:
[ALERT] 135/235942 (8) : sendmsg()/writev() failed in logger #1: No such file or directory (errno=2)
My setup is described in the following question:
HAProxy in docker
Can anyone suggest how to fix that?
Also, how can I view/enable logs of actual accesses to the haproxy and routing activity to the different servers?
Thanks
Check if there is /var/lib/haproxy/dev/log - if not, restart rsyslogd.
I have been running Docker on my windows with Docker ToolBox all fine for last 6 months. Suddenly, when starting my docker console I started getting following error:
Error creating machine: Error running provisioning: Could not find matching IP for MAC address 0800270a0700
I came across many threads on GitHub and SO and most of the people suggested completely removing Docker setup including Virtual Box and re-installing it. Which I did however I am getting the same error even on a clean set up.
I tried following things so far:
Clean re-install of docker and Virtual Box
Making sure that all the docker related folders that I find are removed before the next install(Removed both .docker and .virtualbox folders)
also removed default docker-machine on existing set up after the new installation failed by doing docker-machine rm default
Also, one thing to notice that when I do a clean install, I can see that when I fire up the docker quickstart for the first time it starts everything from the scratch except one thing. I see this message that it
Found a new host-only adapter: "VirtualBox Host-Only Ethernet Adapter#2
Which raises the questions that if if found it then it must not be new right? and also why is it #2? why not #1 or no number? The reason I am bringing this up is because I am suspecting that when a clean-install happens, it is really not clean, I think it is getting some screwed up settings from somewhere and that somewhere can very well be this network adapter
If I look at the logs inside the Docker-machine then logs look like following. Now sure if that is any help
00:00:48.657014 VMMDev: Guest Log: 00:00:00.009234 vminfo rtldrNativeLoad: dlopen('libdbus-1.so.3', RTLD_NOW | RTLD_LOCAL) failed: libdbus-1.so.3: cannot open shared object file: No such file or directory
00:00:48.657044 VMMDev: Guest Log: 00:00:00.009268 vminfo Error: Unable to connect to system D-Bus (1/3): D-Bus not installed
00:00:48.659892 VMMDev: Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:48.805170 NAT: IPv6 not supported
00:00:50.624628 NAT: DHCP offered IP address 10.0.2.15
00:00:50.624913 NAT: DHCP offered IP address 10.0.2.15
00:00:53.656655 VMMDev: Guest Log: 00:00:05.010825 vminfo Error: Unable to connect to system D-Bus (2/3): D-Bus not installed
00:00:58.658074 VMMDev: Guest Log: 00:00:10.012264 vminfo Error: Unable to connect to system D-Bus (3/3): D-Bus not installed
00:01:00.230853 VMMDev: SetVideoModeHint: Got a video mode hint (800x600x0)#(0x0),(1;0) at 0
00:01:44.873806 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:01:45.187049 PDMR3Suspend: 313 213 266 ns run time
00:01:45.187066 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:01:45.187073 Console: Machine state changed to 'Paused'
00:01:48.209792 Changing the VM state from 'SUSPENDED' to 'RESUMING'
00:01:48.247728 Changing the VM state from 'RESUMING' to 'RUNNING'
00:01:48.247754 Console: Machine state changed to 'Running'
00:06:42.762538 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:06:42.958664 PDMR3Suspend: 196 100 930 ns run time
00:06:42.958705 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:06:42.958714 Console: Machine state changed to 'Paused'
I have had no luck so far. Any help?
Are you using a VPN like Citrix? If so, disconnect it and then try to create the machine.
I have a java program that runs inside a docker container.
This program tries to connect to a Ipv4 socket.
I get the following Invalid argument exception
Caused by: java.net.SocketException: Invalid argument: /135.250.15.104:6524
at sun.nio.ch.Net.connect0(Native Method)
at sun.nio.ch.Net.connect(Net.java:454)
at sun.nio.ch.Net.connect(Net.java:446)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648)
at io.netty.channel.socket.nio.NioSocketChannel.doConnect(NioSocketChannel.java:209)
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.connect(AbstractNioChannel.java:199)
at io.netty.channel.DefaultChannelPipeline$HeadContext.connect(DefaultChannelPipeline.java:1089)
at io.netty.channel.AbstractChannelHandlerContext.invokeConnect(AbstractChannelHandlerContext.java:543)
at io.netty.channel.AbstractChannelHandlerContext.connect(AbstractChannelHandlerContext.java:528)
at io.netty.handler.ssl.SslHandler.connect(SslHandler.java:415)
at io.netty.channel.AbstractChannelHandlerContext.invokeConnect(AbstractChannelHandlerContext.java:543)
at io.netty.channel.AbstractChannelHandlerContext.connect(AbstractChannelHandlerContext.java:528)
at io.netty.channel.ChannelOutboundHandlerAdapter.connect(ChannelOutboundHandlerAdapter.java:47)
at io.netty.channel.AbstractChannelHandlerContext.invokeConnect(AbstractChannelHandlerContext.java:543)
at io.netty.channel.AbstractChannelHandlerContext.connect(AbstractChannelHandlerContext.java:528)
at io.netty.channel.DefaultChannelPipeline.connect(DefaultChannelPipeline.java:914)
at io.netty.channel.AbstractChannel.connect(AbstractChannel.java:208)
at io.netty.bootstrap.Bootstrap$2.run(Bootstrap.java:167)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:357)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)
at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
Now I have tried setting -Djava.net.preferIPv4Stack=true JVM option, but no luck.
I am using open-jdk 8 and from java:openjdk-8u72-jre is the entry in my DockerFile .
Note that the same IP address is ping-able from the docker container.
The problem was solved when I used --net=host see docker reference in my docker run command and network_mode : "host" in my docker-compose file see compose reference.
Also see a related stackoverflow post.
The problem seems to get exposed only when the socket connection uses a per-defined local socket address instead of letting the NIO choose a free local address.
But the exception stack trace says "Invalid argument" for the remote address which kind of is weird and that is why it took time for me to figure out the problem.