Hello @lucaskanashiro,
it may work differently in a container because the problem may be
triggered by a combination of libc components and possibly the kernel
(only a speculation). I can reproduce the problem on another hirsute
machine, postfix was never used there. I `dpkg-reconfigure`d it as a
"satellite system" and sent an email. Sure enough, it got stuck in the
queue the same way:
crosser@journey:~$ mailq
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
6712B36270B 422 Tue Feb 23 21:36:05 cros...@journey.average.org
(unknown mail transport error)
cros...@average.org
-- 0 Kbytes in 1 Request.
I am attaching all relevant files.
> not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu
Well, nothing in the local configuration changed between Feb 20 when
delivery worked and Feb 21 when it stopped to work...
> provide a more complete description of the problem
The most complete I could provide short of recompiling postfix and adding debug
printouts was that strace looks like libc's `getservbyname()` returned failure
when it was called from a chrooted process, without trying to access
`/etc/services` or even opening `/etc/nsswitch.conf` (but checked `stat` of the
latter, which was successful).
> explain why you believe this is a bug in Ubuntu rather than a problem
> specific to your
system
As I explained in my first report (and another time above), there were
no local changes (other than package upgrades) between the moment
deliver worked and the moment after which it stopped working.
?field.comment=Hello @lucaskanashiro,
it may work differently in a container because the problem may be
triggered by a combination of libc components and possibly the kernel
(only a speculation). I can reproduce the problem on another hirsute
machine, postfix was never used there. I `dpkg-reconfigure`d it as a
"satellite system" and sent an email. Sure enough, it got stuck in the
queue the same way:
crosser@journey:~$ mailq
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
6712B36270B 422 Tue Feb 23 21:36:05 cros...@journey.average.org
(unknown mail transport error)
cros...@average.org
-- 0 Kbytes in 1 Request.
I am attaching all relevant files.
> not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu
Well, nothing in the local configuration changed between Feb 20 when
delivery worked and Feb 21 when it stopped to work...
> provide a more complete description of the problem
The most complete I could provide short of recompiling postfix and adding debug
printouts was that strace looks like libc's `getservbyname()` returned failure
when it was called from a chrooted process, without trying to access
`/etc/services` or even opening `/etc/nsswitch.conf` (but checked `stat` of the
latter, which was successful).
> explain why you believe this is a bug in Ubuntu rather than a problem
> specific to your
system
As I explained in my first report (and another time above), there were
no local changes (other than package upgrades) between the moment
deliver worked and the moment after which it stopped working.
** Attachment added: "tar contains compressed /etc/postfix, mail.log, smtp
process strace etc."
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1916541/+attachment/5466342/+files/postfix-debug-data.tar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916541
Title:
smtp "fatal: unknown service: smtp/tcp", probably after libc upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1916541/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
