Your message dated Tue, 28 Dec 2021 18:03:47 +0100
with message-id <[email protected]>
and subject line Fixed in Eventlet
has caused the Debian Bug report #989600,
regarding /usr/bin/swift-container-reconciler: reconciler's memcache
connections fail when using hostnames
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
989600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989600
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: swift-container
Version: 2.26.0-10
Severity: important
File: /usr/bin/swift-container-reconciler
Dear Maintainer,
I'm experimenting with Swift on Bullseye and came across a problem with
container-reconciler (possibly others) when using hostnames in
memcache_servers. Namely these errors:
Jun 08 09:54:08 ms-be-01 swift-container-reconciler[70736]: Timeout getting a
connection to memcached: HOST1:11211: MemcachePoolTimeout (1.0s) (txn:
txf2bfe46649374ed6b1a47-0060bf3e3f)
Jun 08 09:54:09 ms-be-01 swift-container-reconciler[70736]: Timeout getting a
connection to memcached: HOST2:11211: MemcachePoolTimeout (1.0s) (txn:
txf2bfe46649374ed6b1a47-0060bf3e3f)
and I have HOST1 HOST2 in container-reconciler.conf:
memcache_servers = HOST1:11211,HOST2:11211
Manually testing the connection works as expected, and after some debugging it
looks like using ip addresses in the configuration works, unlike using
hostnames. In this case hostname resolution happens via DNS, which makes me
think this is related to #971530. The bug is possibly affecting other parts of
swift + memcache, though I haven't been able to find other examples in my
testing so far.
best,
Filippo
-- System Information:
Debian Release: 11.0
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing-debug'), (500,
'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-6-cloud-amd64 (SMP w/1 CPU thread)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages swift-container depends on:
ii init-system-helpers 1.60
ii lsb-base 11.1.0
ii openstack-pkg-tools 117
ii python3 3.9.2-3
ii python3-pastescript 2.0.2-4
ii python3-swift 2.26.0-10
ii rsync 3.2.3-4
ii swift 2.26.0-10
ii uwsgi-plugin-python3 2.0.19.1-6
Versions of packages swift-container recommends:
pn swift-drive-audit <none>
swift-container suggests no packages.
-- Configuration Files:
/etc/swift/container-reconciler.conf [Errno 13] Permission denied:
'/etc/swift/container-reconciler.conf'
/etc/swift/container-server.conf [Errno 13] Permission denied:
'/etc/swift/container-server.conf'
/etc/swift/internal-client.conf [Errno 13] Permission denied:
'/etc/swift/internal-client.conf'
/etc/swift/swift-container-server-uwsgi.ini [Errno 13] Permission denied:
'/etc/swift/swift-container-server-uwsgi.ini'
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
This bug was fixed in Eventlet in both Stable and Unstable, and the bug
wasn't in swift. Closing this bug accordingly.
Cheers,
Thomas Goirand (zigo)
--- End Message ---
