unable to create socket on dockerXXXXXX

Currently reading
unable to create socket on dockerXXXXXX

196
36
NAS
DS920+, DS918+, DS214+, DS211j
Operating system
  1. Linux
  2. Windows
Mobile operating system
  1. Android
  2. iOS
Hi Guys!

Out of a sudden, I received a message from my NAS (DS918+, DSM 7.0.1-42218 Update 3) that I should shutdown the device properly or attach an USV in order to avoid data loss. This event was created at 1 o'clock this morning. There has not been any power outage, all other NAS or running properly and of course I've an USV connected to all DS.

Nevertheless, since then I see many logs in /var/log/messages that weren't logged before this point:

Code:
2022-03-24T07:04:28+01:00 DS918 ntpd[8125]: bind(42) AF_INET6 fe80::2477:40ff:fe18:5aa1%1547#123 flags 0x11 failed: Cannot assign requested address
2022-03-24T07:04:28+01:00 DS918 ntpd[8125]: unable to create socket on docker0eff399 (1144) for fe80::2477:40ff:fe18:5aa1%1547#123
2022-03-24T07:04:56+01:00 DS918 ntpd[8125]: bind(42) AF_INET6 fe80::6c93:40ff:fec4:b03f%1549#123 flags 0x11 failed: Cannot assign requested address
2022-03-24T07:04:56+01:00 DS918 ntpd[8125]: unable to create socket on docker9fff419 (1146) for fe80::6c93:40ff:fec4:b03f%1549#123
2022-03-24T07:05:25+01:00 DS918 ntpd[8125]: bind(42) AF_INET6 fe80::cd6:bdff:fe99:b9fc%1551#123 flags 0x11 failed: Cannot assign requested address
2022-03-24T07:05:25+01:00 DS918 ntpd[8125]: unable to create socket on docker81e93d8 (1148) for fe80::cd6:bdff:fe99:b9fc%1551#123
2022-03-24T07:05:53+01:00 DS918 ntpd[8125]: bind(42) AF_INET6 fe80::4f7:39ff:fe46:6bf1%1553#123 flags 0x11 failed: Cannot assign requested address
2022-03-24T07:05:53+01:00 DS918 ntpd[8125]: unable to create socket on dockerdf6dc24 (1150) for fe80::4f7:39ff:fe46:6bf1%1553#123
2022-03-24T07:06:22+01:00 DS918 ntpd[8125]: bind(42) AF_INET6 fe80::1034:52ff:fea5:a451%1555#123 flags 0x11 failed: Cannot assign requested address
2022-03-24T07:06:22+01:00 DS918 ntpd[8125]: unable to create socket on dockerb044dc0 (1152) for fe80::1034:52ff:fea5:a451%1555#123
2022-03-24T07:07:48+01:00 DS918 ntpd[8125]: bind(42) AF_INET6 fe80::a4d3:c2ff:fe56:b6fa%1561#123 flags 0x11 failed: Cannot assign requested address
2022-03-24T07:07:48+01:00 DS918 ntpd[8125]: unable to create socket on docker29f8e10 (1156) for fe80::a4d3:c2ff:fe56:b6fa%1561#123
2022-03-24T07:08:16+01:00 DS918 ntpd[8125]: bind(42) AF_INET6 fe80::704a:1dff:fea7:32d5%1563#123 flags 0x11 failed: Cannot assign requested address
2022-03-24T07:08:16+01:00 DS918 ntpd[8125]: unable to create socket on docker7f9f5e1 (1158) for fe80::704a:1dff:fea7:32d5%1563#123
2022-03-24T07:10:11+01:00 DS918 ntpd[8125]: bind(39) AF_INET6 fe80::50c3:b6ff:febd:bc4%1571#123 flags 0x11 failed: Cannot assign requested address
2022-03-24T07:10:11+01:00 DS918 ntpd[8125]: unable to create socket on dockeredc25c1 (1163) for fe80::50c3:b6ff:febd:bc4%1571#123
2022-03-24T07:10:39+01:00 DS918 ntpd[8125]: bind(42) AF_INET6 fe80::f831:46ff:fec1:7f0c%1573#123 flags 0x11 failed: Cannot assign requested address
2022-03-24T07:10:39+01:00 DS918 ntpd[8125]: unable to create socket on dockerb39e876 (1165) for fe80::f831:46ff:fec1:7f0c%1573#123

When shutting down the docker application, those messages disappear. When restarting again, the logs come up again.
As said, I've looked back in messages in order to find similar logs, to no avail - there are none.

So, any clue what happens here and how to avoid this kind of logs? I'm running an IPv4 network, btw.

cu,
Michael
 
Last edited:
I'm running an IPv4 network, btw.
Are you sure? The log output indicates that docker tries to assign a ipv6 link-local-address to the containers.
Kind of looks like ipv6 is enabled on your system.

There must be an inconsistency somewhere:
- ipv6 enabled on network interface?
- ipv6 enabled in docker network using the ui or the cli?
- ipv6 enabled in dockerd.json (If you don't remember editing it from the cli, then you high likely didn't)
 
OK, I've found an active assignment of IPv6 on LAN2 that I've now switched off. Thanks for the reminder!
Never thought about LAN2 ;-)

There was no manual edit of any further config file, neither in docker nor in any other system file.

Just checked docker again, especially the network interfaces, bridges and custom ones. Each of them shows disabled IPv6 protocols, at least in DSM.

Nevertheless, those log entries still appear.
 
Just switched the NTP-server in DSM settings to another local NTP service and after refreshing date/time I found this in messages:
Code:
2022-03-24T16:46:38+01:00 DS918 ntpdate[29804]: Sync with time server 192.168.0.1 offset +0.040473
sec.2022-03-24T16:46:40+01:00 DS918 ntpd[29978]: MS-SNTP signd operations currently block ntpd degrading service to all clients.

So basically, is the second line of any help? At least this did not prevent those other message from re-appearing again in system log, but maybe this is a possible cause of the issue?

As mentioned above, this happened after an forced/unplanned shutdown of this DS this early morning and those logs have not been created before...
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

  • Solved
A bit late to this. It does seem that the new network doesn't have external network access, or if nothing...
Replies
8
Views
539
No, I just mentioned docker.sock because in my ignorance thought that had something to do with my problem...
Replies
2
Views
2,535
  • Question
could it be that your docker volume mapping is wrong?
Replies
6
Views
7,629
Contact me in pm, I'll help you out with a few of them to get the hang of it. We can do a remote session...
Replies
1
Views
1,305
Replies
5
Views
5,876
  • Question
Pihole UI will not work on 80, as 80 is in use by Synology's nginx (as it is 443), just bind it to some...
Replies
8
Views
10,507
As i was creating this post to ask if anyone solved it, i think i solved it. What's interesting is even...
Replies
9
Views
6,688

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Back
Top