systemd-timesyncd: Address family not supported by protocol
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- linux
- Domain
- networking, operating-systems
Research direction
Start with the reported ipv6.disable=1 setting in /boot/cmdline.txt and inspect the systemd-timesyncd service status and syslog output. Reproduce the stalled connection to the IPv6 NTP server, compare it with restarting the service, and document the conditions that trigger the address-family error.
Written by the indexing model from the issue text.
Description
Prerequisites:
ipv6.disable=1 is set in /boot/cmdline.txt
Issue:
As of lately, systemd-timesyncd sometimes gets stuck trying to connect to an ipv6 NTP server, while ipv6 is disabled at boot.
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
└─disable-with-time-daemon.conf
Active: active (running) since Thu 2019-04-11 16:24:00 BST; 1 months 8 days ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 260 (systemd-timesyn)
Status: "Connecting to time server [2a03:b0c0:0:1010::3:4001]:123 (2.debian.pool.ntp.org)."
CPU: 7.937s
CGroup: /system.slice/systemd-timesyncd.service
└─260 /lib/systemd/systemd-timesyncd
syslog:
systemd-timesyncd[260]: Failed to setup connection socket: Address family not supported by protocol
Restarting the systemd service solves the issue, but I've never experienced this in the last years, while it regularly pops up since a few weeks.
I'll update this report when I can pinpoint some more data or find a way to reproduce this.
- Dominant language
- C
- Stars
- 13.2k
- Forks
- 5.5k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 21
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/linux
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7415 · 2 comments · 1 reaction ·
-
rp1-cfe doesn't forward V4L2_EVENT_SOURCE_CHANGE event from csi-2 sensor driver to userspace app Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raspberrypi/linux#7399 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
raspberrypi/linux#7357 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7054 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
raspberrypi/linux#7634 · 8 comments · 1 reaction ·
All issues in raspberrypi/linux
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zephyrproject-rtos/zephyr#119726 ·
-
[Bounty proposal] fix(web): memory insights count an evening memory on the next day ($25 proposed) Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BasedHardware/omi#15320 ·
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarbourMasters/Shipwright#7229 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
riscv-software-src/riscv-isa-sim#2435 · 1 comment ·