Re: Bug#993821: After upgrading libc, some services are unable to restart (including systemd-resolved)

2021-09-07 Thread Michael Hudson-Doyle 
On Wed, 8 Sept 2021 at 07:04, Michael Biebl  wrote:

> Hi Aurelien
>
> Am 07.09.21 um 12:41 schrieb Aurelien Jarno:
> > Hi,
> >
> > On 2021-09-07 10:39, Michael Hudson-Doyle wrote:
>
> >> What's happening is that systemd is running with the old glibc, forks
> and
> >> then does NSS things that cause the new glibc's NSS modules to load and
> >> they don't necessarily work, leading to failures in any unit that
> specifies
> >> User=. At least for Ubuntu's builds the NSS modules seem to be ABI
> >> compatible between 2.32 and 2.33 (I didn't try 2.31 vs 2.32) but they
> are
> >> definitely not between 2.33 and 2.34.
> >
> > Thanks for this feedback and the pointer to the patch used in Ubuntu. It
> > seems to be a good solution, and matches what is done for other init
> > systems.
> >
> > On the other hand, the problem is supposed to only happen for major
> > glibc version upgrade where the NSS modules might have a different ABI.
> > In that regard, I would be tempted to restart it only for major versions
> > upgrade like it's done for other daemons. Now if the systemd maintainers
> > consider it's fine restarting it for each glibc upgrade, we should
> > probably go that way.
>
> I guess you are in a better position to make a judgement call here. If I
> read the glibc bug report correctly, there aren't strictly any
> guarantees regarding NSS modules. What that means for glibc minor
> updates, I'm not really in a position to tell.
>

I think in practice minor version updates are probably going to be fine
here, but also I think careful reexecing on every update is also likely to
be fine in practice.

If you wanted to be suuurrr paranoid, I guess you could embed in
the glibc postinst knowledge of which prior versions have binary-compatible
NSS modules but that seems like a lot of work for not much benefit (would
you only have to care about nss_files compatibility, or the full set?).


> Fwiw, I don't have a better proposal then Michael's patch he added to
> Ubuntu. We could run with that and if it causes problems, reiterate on it.
>

Yeah, the point where we start to offer updates to 21.10 will at the least
provide some data on how safe Ubuntu's approach is...

Cheers,
mwh

Bug#993821: marked as done (After upgrading libc, some services are unable to restart (including systemd-resolved))

2021-09-07 Thread Debian Bug Tracking System 
Your message dated Tue, 07 Sep 2021 20:34:14 +
with message-id 
and subject line Bug#993821: fixed in glibc 2.32-2
has caused the Debian Bug report #993821,
regarding After upgrading libc, some services are unable to restart (including 
systemd-resolved)
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 ow...@bugs.debian.org
immediately.)


-- 
993821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 247.9-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hey!

After upgrading to libc6 2.32-1, some services are unable to restart.
In my case, systemd-resolved, systemd-timesyncd and colord. Using
"systemctl daemon-reexec" fixes the issue. Unsure if there is really
something to be fixed but as I didn't find anything about that, a bug
report may help others. I suppose the problem is related to NSS.

Sep 06 23:06:43 chocobo systemd[1]: Starting Network Time Synchronization...
Sep 06 23:06:43 chocobo systemd[236983]: systemd-timesyncd.service: Failed to 
determine user credentials: No such process
Sep 06 23:06:43 chocobo systemd[236983]: systemd-timesyncd.service: Failed at 
step USER spawning /lib/systemd/systemd-timesyncd: No such process



- -- Package-specific info:

- -- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(101, 'experimental-debug'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.13.0-trunk-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_USER
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 systemd depends on:
ii  adduser  3.118
ii  libacl1  2.3.1-1
ii  libapparmor1 3.0.3-2
ii  libaudit11:3.0.5-1
ii  libblkid12.37.2-2
ii  libc62.32-1
ii  libcap2  1:2.44-1
ii  libcrypt11:4.4.25-2
ii  libcryptsetup12  2:2.4.0-1
ii  libgcrypt20  1.9.4-2
ii  libgnutls30  3.7.2-2
ii  libgpg-error01.42-3
ii  libip4tc21.8.7-1
ii  libkmod2 29-1
ii  liblz4-1 1.9.3-2
ii  liblzma5 5.2.5-2
ii  libmount12.37.2-2
ii  libpam0g 1.4.0-10
ii  libseccomp2  2.5.1-1
ii  libselinux1  3.1-3
ii  libsystemd0  247.9-1
ii  libzstd1 1.4.8+dfsg-2.1
ii  mount2.37.2-2
ii  systemd-timesyncd [time-daemon]  247.9-1
ii  util-linux   2.37.2-2

Versions of packages systemd recommends:
ii  dbus  1.12.20-2

Versions of packages systemd suggests:
ii  policykit-10.105-31
ii  systemd-container  247.9-1

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.140
ii  libnss-systemd   247.9-1
ii  libpam-systemd   247.9-1
ii  udev 247.9-1

- -- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
HandlePowerKey=ignore

/etc/systemd/resolved.conf changed:
[Resolve]
DNSSEC=allow-downgrade


- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAmE2jA8SHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX5HXcQAKG5+toLrAqmXBjrFCHUauoUJ1MKEXYp
gMk11uNJd61yY0gW7eQHNJ1bl1aeXQ5FBOw830xMVFn9qXcCAghrDcB8yT8Vlsw9
XQQakme/+qUNU6xg4RW9IRbrqH32AhV1hp4rkrchjVYpoLng26JOV7zKSs7PrhL/
THtVzuxRnqgyQ0j742yDmw5X6y/jqBIyOgdVWm176kYIaIvkob8i8YzF8eSjQCgq
0PEDVwtbkDUu8M79lA2QPTya+3y9xD/vp01/hbyMA7+lOfQKC5ylX5rklsMhsWez
mLwRBj3UYGGYm6jRWwYRbciSCpYLxsz0RVz6+T8FStyGqh3vNBAWFQHYn47QtypU
2t4JGgJV+Z6yDeY2eh/ltk2kk+yhsMJtDzEoY7unsG4fWa8MoxgdKeIwbQ3Hujir
uyQMD170q5/AkPWsmKeJm2OdBF9nRs8dGU+VGi80XZzld0Ociu0tcUQu9F9LbrNj
5HdvUlkY6rkW0OsTpDBjKqVyB/DMHT9ciS5o9a/C6ZwRMspyItxKrxtN+9M2VIN3
5BHv/2vuZfh5OqDCtlVVwEhj2YZUVlEmtIJ+UfA7VfupXHwNiCvI8QOWkKcOvkMJ
1FurFmmJ3WED/2qLfr25GhZgyUGDb/3NluuHHnwRIkpCBYyV4qOSnAd/z4SUa+wv
p2k968FNOmUz
=jj8P
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.32-2
Done: Aurelien Jarno 

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary

glibc_2.32-2_source.changes ACCEPTED into unstable

2021-09-07 Thread Debian FTP Masters 



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Sep 2021 21:57:34 +0200
Source: glibc
Architecture: source
Version: 2.32-2
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 993821
Changes:
 glibc (2.32-2) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/testsuite-xfail-debian.mk: Update hurd tests.
 .
   [ Aurelien Jarno ]
   * debian/rules.d/debhelper.mk: do not try to install audit/sotruss-lib.so
 in stage1 profile.
   * debian/debhelper.in/libc.postinst: grab patch from Ubuntu to carefully
 restart systemd on libc6 upgrade.  Closes: #993821.
   * debian/debhelper.in/libc.lintian-overrides: and an override about the
 systemctl call in libc6.postinst.
Checksums-Sha1:
 1ca78071ecd5d20210007a509bfe293381d19b1d 9617 glibc_2.32-2.dsc
 a298584a84e032f7cd94dc2462450ebf590b4af0 840168 glibc_2.32-2.debian.tar.xz
 276758c918bee5bed59725de733078cae908ee52 8649 glibc_2.32-2_source.buildinfo
Checksums-Sha256:
 10967c80610dc6be44a889dea8f92a5d83c2cf6564b7d4f1e7c60e9c2c630690 9617 
glibc_2.32-2.dsc
 df1977db55118d9f260a5fa9b604cd069d89e64b3ef8f8e113b70af2ad84e6cb 840168 
glibc_2.32-2.debian.tar.xz
 60077b0a88f1cdc4c88917f84237ad9c41d49579a2881d7bc5e3e33dc69cb27e 8649 
glibc_2.32-2_source.buildinfo
Files:
 631e62471c77897cf7464e80f5acaf5c 9617 libs required glibc_2.32-2.dsc
 065dc0869b8bb79788e910859e36ce49 840168 libs required 
glibc_2.32-2.debian.tar.xz
 85b2ab0a88daafdd1850878593eea5f2 8649 libs required 
glibc_2.32-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmE3xzkACgkQE4jA+Jno
M2vGpw//XOKBi7sVQBrk+S427IGsrzdGjwqUsNSn2/PGN7Prrzr3FKbwy1szEggu
UctCoX84r8xFd9Fxh82tQN/1pZW9VCcDMc1jeao7t87t3zUlucVGbJBK8JoQemdp
6V0DqAfVb2DmdnrghItY67aMMAV6Yer9KgD+YyOPd5loQ53Gu3/sccT+cEg/OMoK
nqY2lH1p2ySsX2NdHSzGgAP5e7d3mymXMsX4efmSxLOdO9JZvEAY2Qj8z38Nlja6
7Bi9JL2rxexK4TqR2LYEFM22Hy1J3lahIEhuUQo3aitiXSAoDt745cNx93YCiwcI
GqRhwG8dAJ0uJjmzML3D5I0iOQcS7Dq1TYjThowA3BhWLv95dsAndX/+CXDKHBOz
Zurofi7FfVMjplMELM8K6VBct/CRIoD/x1QPFiNRcV3gqKb5j0s7T8ectBZOheDL
eU7BS6utTeKmOGU+ShQ598wE4QOM1ELLQzXgsuwgCdseTvCWetwaaymNlkZNwOWN
zNefabcjTV0vTwzXKofVy/1d3P+K8MxHrc2tqJHuGDWNm1Xess98X3/cCq9lvQx6
duQl4Ww5s9Q9wkfT41QcmE0Sd5/iI0PYopp2tfoZxYU5yIRJKia9SzIllm6CPd/+
M2g4oGdkpky+m+de8ifVUJ/XgyfBqx30pDW7xtJAUDxGXwAKNDA=
=fmLq
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of glibc_2.32-2_source.changes

2021-09-07 Thread Debian FTP Masters 
glibc_2.32-2_source.changes uploaded successfully to localhost
along with the files:
  glibc_2.32-2.dsc
  glibc_2.32-2.debian.tar.xz
  glibc_2.32-2_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Processed: Bug#993821 marked as pending in glibc

2021-09-07 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 pending
Bug #993821 [libc6] After upgrading libc, some services are unable to restart 
(including systemd-resolved)
Ignoring request to alter tags of bug #993821 to the same tags previously set

-- 
993821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

[Git][glibc-team/glibc][glibc-2.33] 7 commits: debian/testsuite-xfail-debian.mk: Update hurd tests.

2021-09-07 Thread Aurelien Jarno (@aurel32) 


Aurelien Jarno pushed to branch glibc-2.33 at GNU Libc Maintainers / glibc


Commits:
7761c4a4 by Samuel Thibault at 2021-09-06T10:40:12+02:00
debian/testsuite-xfail-debian.mk: Update hurd tests.

- - - - -
d912597c by Aurelien Jarno at 2021-09-07T13:11:57+02:00
debian/rules.d/debhelper.mk: do not try to install audit/sotruss-lib.so in 
stage1 profile.

- - - - -
c41038a6 by Aurelien Jarno at 2021-09-07T21:48:06+02:00
debian/debhelper.in/libc.postinst: grab patch from Ubuntu to carefully restart 
systemd on libc6 upgrade.  Closes: #993821.

- - - - -
3a44265c by Aurelien Jarno at 2021-09-07T21:57:18+02:00
debian/debhelper.in/libc.lintian-overrides: and an override about the systemctl 
call in libc6.postinst.

- - - - -
3b91171b by Aurelien Jarno at 2021-09-07T21:57:42+02:00
releasing package glibc version 2.32-2

- - - - -
e9d8b821 by Aurelien Jarno at 2021-09-07T22:20:51+02:00
Merge branch sid into glibc-2.33

- - - - -
4acc0eff by Aurelien Jarno at 2021-09-07T22:24:01+02:00
debian/patches/git-updates.diff: update from upstream stable branch.

- - - - -


6 changed files:

- debian/changelog
- debian/debhelper.in/libc.lintian-overrides
- debian/debhelper.in/libc.postinst
- debian/patches/git-updates.diff
- debian/rules.d/debhelper.mk
- debian/testsuite-xfail-debian.mk


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/7fbd0beef2a6212f6b332962e47b4cc1d5cfeeb6...4acc0eff30190cff90873bca1ad0e386b069fe11

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/7fbd0beef2a6212f6b332962e47b4cc1d5cfeeb6...4acc0eff30190cff90873bca1ad0e386b069fe11
You're receiving this email because of your account on salsa.debian.org.

[Git][glibc-team/glibc] Pushed new tag debian/2.32-2

2021-09-07 Thread Aurelien Jarno (@aurel32) 


Aurelien Jarno pushed new tag debian/2.32-2 at GNU Libc Maintainers / glibc

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/tree/debian/2.32-2
You're receiving this email because of your account on salsa.debian.org.

[Git][glibc-team/glibc][sid] releasing package glibc version 2.32-2

2021-09-07 Thread Aurelien Jarno (@aurel32) 


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
3b91171b by Aurelien Jarno at 2021-09-07T21:57:42+02:00
releasing package glibc version 2.32-2

- - - - -


1 changed file:

- debian/changelog


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/3b91171bdce241dddf8724449c522cd8009c5d58

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/3b91171bdce241dddf8724449c522cd8009c5d58
You're receiving this email because of your account on salsa.debian.org.

[Git][glibc-team/glibc][sid] debian/debhelper.in/libc.lintian-overrides: and an override about the...

2021-09-07 Thread Aurelien Jarno (@aurel32) 


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
3a44265c by Aurelien Jarno at 2021-09-07T21:57:18+02:00
debian/debhelper.in/libc.lintian-overrides: and an override about the systemctl 
call in libc6.postinst.

- - - - -


2 changed files:

- debian/changelog
- debian/debhelper.in/libc.lintian-overrides


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/3a44265c8510701d4aaa47d461879b9b872f02dd

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/3a44265c8510701d4aaa47d461879b9b872f02dd
You're receiving this email because of your account on salsa.debian.org.

Processed: Bug#993821 marked as pending in glibc

2021-09-07 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 pending
Bug #993821 [libc6] After upgrading libc, some services are unable to restart 
(including systemd-resolved)
Added tag(s) pending.

-- 
993821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

[Git][glibc-team/glibc][sid] debian/debhelper.in/libc.postinst: grab patch from Ubuntu to carefully restart...

2021-09-07 Thread Aurelien Jarno (@aurel32) 


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
c41038a6 by Aurelien Jarno at 2021-09-07T21:48:06+02:00
debian/debhelper.in/libc.postinst: grab patch from Ubuntu to carefully restart 
systemd on libc6 upgrade.  Closes: #993821.

- - - - -


2 changed files:

- debian/changelog
- debian/debhelper.in/libc.postinst


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/c41038a6380be47b2c4873d4623840e51394bf5f

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/c41038a6380be47b2c4873d4623840e51394bf5f
You're receiving this email because of your account on salsa.debian.org.

Re: Bug#993821: After upgrading libc, some services are unable to restart (including systemd-resolved)

2021-09-07 Thread Michael Biebl 

Hi Aurelien

Am 07.09.21 um 12:41 schrieb Aurelien Jarno:

Hi,

On 2021-09-07 10:39, Michael Hudson-Doyle wrote:



What's happening is that systemd is running with the old glibc, forks and
then does NSS things that cause the new glibc's NSS modules to load and
they don't necessarily work, leading to failures in any unit that specifies
User=. At least for Ubuntu's builds the NSS modules seem to be ABI
compatible between 2.32 and 2.33 (I didn't try 2.31 vs 2.32) but they are
definitely not between 2.33 and 2.34.


Thanks for this feedback and the pointer to the patch used in Ubuntu. It
seems to be a good solution, and matches what is done for other init
systems.

On the other hand, the problem is supposed to only happen for major
glibc version upgrade where the NSS modules might have a different ABI.
In that regard, I would be tempted to restart it only for major versions
upgrade like it's done for other daemons. Now if the systemd maintainers
consider it's fine restarting it for each glibc upgrade, we should
probably go that way.


I guess you are in a better position to make a judgement call here. If I 
read the glibc bug report correctly, there aren't strictly any 
guarantees regarding NSS modules. What that means for glibc minor 
updates, I'm not really in a position to tell.


Fwiw, I don't have a better proposal then Michael's patch he added to 
Ubuntu. We could run with that and if it causes problems, reiterate on it.


Regards,
Michael

Bug#993874: flurm FTBFS with glibc 2.32: fatal error: sys/sysctl.h: No such file or directory

2021-09-07 Thread Helmut Grohne 
Source: slurm
Version: 0.4.3-2
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: debian-glibc@lists.debian.org

slurm fails to build from source with glibc 2.32, because sys/sysctl.h
was removed. A build ends with:

| [ 50%] Building C object CMakeFiles/slurm.dir/slurm.c.o
| /usr/bin/cc -D_HAVE_NCURSES  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -o CMakeFiles/slurm.dir/slurm.c.o -c 
/<>/slurm.c
| In file included from /<>/slurm.c:37:
| /<>/os.h:180:10: fatal error: sys/sysctl.h: No such file or 
directory
|   180 | #include 
|   |  ^~
| compilation terminated.
| make[3]: *** [CMakeFiles/slurm.dir/build.make:85: 
CMakeFiles/slurm.dir/slurm.c.o] Error 1
| make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[2]: *** [CMakeFiles/Makefile2:98: CMakeFiles/slurm.dir/all] Error 2
| make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[1]: *** [Makefile:152: all] Error 2
| make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j1 VERBOSE=1 returned 
exit code 2
| make: *** [debian/rules:3: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut

[Git][glibc-team/glibc][sid] debian/rules.d/debhelper.mk: do not try to install audit/sotruss-lib.so in stage1 profile.

2021-09-07 Thread Aurelien Jarno (@aurel32) 


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
d912597c by Aurelien Jarno at 2021-09-07T13:11:57+02:00
debian/rules.d/debhelper.mk: do not try to install audit/sotruss-lib.so in 
stage1 profile.

- - - - -


2 changed files:

- debian/changelog
- debian/rules.d/debhelper.mk


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/d912597c096cd669d6cc3172fefb2d4d78a41e4b

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/d912597c096cd669d6cc3172fefb2d4d78a41e4b
You're receiving this email because of your account on salsa.debian.org.

Re: Bug#993821: After upgrading libc, some services are unable to restart (including systemd-resolved)

2021-09-07 Thread Aurelien Jarno 
Hi,

On 2021-09-07 10:39, Michael Hudson-Doyle wrote:
> On Tue, 7 Sept 2021 at 10:21, Michael Biebl  wrote:
> 
> > Am 06.09.21 um 23:45 schrieb Vincent Bernat:
> >  > Package: systemd
> >  > Version: 247.9-1
> >  > Severity: normal
> >  >
> > > Hey!
> > >
> > > After upgrading to libc6 2.32-1, some services are unable to restart.
> > > In my case, systemd-resolved, systemd-timesyncd and colord. Using
> > > "systemctl daemon-reexec" fixes the issue. Unsure if there is really
> > > something to be fixed but as I didn't find anything about that, a bug
> > > report may help others. I suppose the problem is related to NSS.
> > >
> > > Sep 06 23:06:43 chocobo systemd[1]: Starting Network Time
> > Synchronization...
> > > Sep 06 23:06:43 chocobo systemd[236983]: systemd-timesyncd.service:
> > Failed to determine user credentials: No such process
> > > Sep 06 23:06:43 chocobo systemd[236983]: systemd-timesyncd.service:
> > Failed at step USER spawning /lib/systemd/systemd-timesyncd: No such process
> > >
> > >
> >
> >
> > @libc maintainers: any ideas what could be causing this? If this is
> > triggered by a libc6 update, should this be reassigned to glibc?
> >
> 
> We went through this in Ubuntu recently and decided that restarting systemd
> in glibc's postinst was the safest option:
> https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1942276
> 
> What's happening is that systemd is running with the old glibc, forks and
> then does NSS things that cause the new glibc's NSS modules to load and
> they don't necessarily work, leading to failures in any unit that specifies
> User=. At least for Ubuntu's builds the NSS modules seem to be ABI
> compatible between 2.32 and 2.33 (I didn't try 2.31 vs 2.32) but they are
> definitely not between 2.33 and 2.34.

Thanks for this feedback and the pointer to the patch used in Ubuntu. It
seems to be a good solution, and matches what is done for other init
systems.

On the other hand, the problem is supposed to only happen for major
glibc version upgrade where the NSS modules might have a different ABI.
In that regard, I would be tempted to restart it only for major versions
upgrade like it's done for other daemons. Now if the systemd maintainers
consider it's fine restarting it for each glibc upgrade, we should
probably go that way.

Regards,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Re: Bug#993821: After upgrading libc, some services are unable to restart (including systemd-resolved)

2021-09-07 Thread Michael Hudson-Doyle 
On Tue, 7 Sept 2021 at 17:49, Michael Biebl  wrote:

> Control: reassign -1 libc6
> Control: found -1 2.32-1
> Control: severity -1 serious
> Control: affects -1 + systemd
>
> Hi Michael
>
> Am 07.09.21 um 00:39 schrieb Michael Hudson-Doyle:
> > On Tue, 7 Sept 2021 at 10:21, Michael Biebl  > > wrote:
> >
> > Am 06.09.21 um 23:45 schrieb Vincent Bernat:
> >   > Package: systemd
> >   > Version: 247.9-1
> >   > Severity: normal
> >   >
> >  > Hey!
> >  >
> >  > After upgrading to libc6 2.32-1, some services are unable to
> restart.
> >  > In my case, systemd-resolved, systemd-timesyncd and colord. Using
> >  > "systemctl daemon-reexec" fixes the issue. Unsure if there is
> really
> >  > something to be fixed but as I didn't find anything about that, a
> bug
> >  > report may help others. I suppose the problem is related to NSS.
> >  >
> >  > Sep 06 23:06:43 chocobo systemd[1]: Starting Network Time
> > Synchronization...
> >  > Sep 06 23:06:43 chocobo systemd[236983]:
> > systemd-timesyncd.service: Failed to determine user credentials: No
> > such process
> >  > Sep 06 23:06:43 chocobo systemd[236983]:
> > systemd-timesyncd.service: Failed at step USER spawning
> > /lib/systemd/systemd-timesyncd: No such process
> >  >
> >  >
> >
> >
> > @libc maintainers: any ideas what could be causing this? If this is
> > triggered by a libc6 update, should this be reassigned to glibc?
> >
> >
> > We went through this in Ubuntu recently and decided that restarting
> > systemd in glibc's postinst was the safest option:
> > https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1942276
> > 
> >
> > What's happening is that systemd is running with the old glibc, forks
> > and then does NSS things that cause the new glibc's NSS modules to load
> > and they don't necessarily work, leading to failures in any unit that
> > specifies User=. At least for Ubuntu's builds the NSS modules seem to be
> > ABI compatible between 2.32 and 2.33 (I didn't try 2.31 vs 2.32) but
> > they are definitely not between 2.33 and 2.34.
>
> Thanks for this information. This is indeed an icky issue and I feel
> like we are between a rock and a hard place.
>

Yeah. I guess one could say that having a long running process that forks
and then does NSS stuff is skating on thin ice a bit. At least the changes
in glibc 2.34 to move nss_files functionality into glibc itself will reduce
the fallout of this considerably.


> I'm not a huge fan of going back to re-exec systemd again directly in
> libc6.postinst, but your proposed patch to at least check that the
> systemd binary can be sucessfully executed should at least deal with the
> situation sufficiently, where a library is (temporarily) missing.
> I do wonder though, if this this will mean that on dist-upgrades the
> daemon-reexec will be skipped.
>

FWIW I had a long chat with Julian (the apt maintainer) about this and he
thought there were three potential situations that could be a problem:

1) a new systemd is unpacked before its Depends
2) one of systemd dependencies has a Breaks: systemd (<< new)
3) in some cases a cycle has to be broken by removing a package with
--force-deps

It think 1) is by some margin the most likely to actually happen, and at
least in that situation systemd will be restarted shortly by its own
postinst.

Cheers,
Michael

Anyway, I think it's best to reassign this libc6 for now and mark it as
> RC so the package doesn't migrate to testing for now.
>
> Regards,
> Michael
>
>

Processed: Re: Bug#993821: After upgrading libc, some services are unable to restart (including systemd-resolved)

2021-09-07 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 libc6
Bug #993821 [systemd] After upgrading libc, some services are unable to restart 
(including systemd-resolved)
Bug reassigned from package 'systemd' to 'libc6'.
No longer marked as found in versions systemd/247.9-1.
Ignoring request to alter fixed versions of bug #993821 to the same values 
previously set
> found -1 2.32-1
Bug #993821 [libc6] After upgrading libc, some services are unable to restart 
(including systemd-resolved)
Marked as found in versions glibc/2.32-1.
> severity -1 serious
Bug #993821 [libc6] After upgrading libc, some services are unable to restart 
(including systemd-resolved)
Severity set to 'serious' from 'normal'
> affects -1 + systemd
Bug #993821 [libc6] After upgrading libc, some services are unable to restart 
(including systemd-resolved)
Added indication that 993821 affects systemd

-- 
993821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: Bug#993821: After upgrading libc, some services are unable to restart (including systemd-resolved)

2021-09-07 Thread Michael Biebl 

Control: reassign -1 libc6
Control: found -1 2.32-1
Control: severity -1 serious
Control: affects -1 + systemd

Hi Michael

Am 07.09.21 um 00:39 schrieb Michael Hudson-Doyle:
On Tue, 7 Sept 2021 at 10:21, Michael Biebl > wrote:


Am 06.09.21 um 23:45 schrieb Vincent Bernat:
  > Package: systemd
  > Version: 247.9-1
  > Severity: normal
  >
 > Hey!
 >
 > After upgrading to libc6 2.32-1, some services are unable to restart.
 > In my case, systemd-resolved, systemd-timesyncd and colord. Using
 > "systemctl daemon-reexec" fixes the issue. Unsure if there is really
 > something to be fixed but as I didn't find anything about that, a bug
 > report may help others. I suppose the problem is related to NSS.
 >
 > Sep 06 23:06:43 chocobo systemd[1]: Starting Network Time
Synchronization...
 > Sep 06 23:06:43 chocobo systemd[236983]:
systemd-timesyncd.service: Failed to determine user credentials: No
such process
 > Sep 06 23:06:43 chocobo systemd[236983]:
systemd-timesyncd.service: Failed at step USER spawning
/lib/systemd/systemd-timesyncd: No such process
 >
 >


@libc maintainers: any ideas what could be causing this? If this is
triggered by a libc6 update, should this be reassigned to glibc?


We went through this in Ubuntu recently and decided that restarting 
systemd in glibc's postinst was the safest option: 
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1942276 



What's happening is that systemd is running with the old glibc, forks 
and then does NSS things that cause the new glibc's NSS modules to load 
and they don't necessarily work, leading to failures in any unit that 
specifies User=. At least for Ubuntu's builds the NSS modules seem to be 
ABI compatible between 2.32 and 2.33 (I didn't try 2.31 vs 2.32) but 
they are definitely not between 2.33 and 2.34.


Thanks for this information. This is indeed an icky issue and I feel 
like we are between a rock and a hard place.
I'm not a huge fan of going back to re-exec systemd again directly in 
libc6.postinst, but your proposed patch to at least check that the 
systemd binary can be sucessfully executed should at least deal with the 
situation sufficiently, where a library is (temporarily) missing.
I do wonder though, if this this will mean that on dist-upgrades the 
daemon-reexec will be skipped.


Anyway, I think it's best to reassign this libc6 for now and mark it as 
RC so the package doesn't migrate to testing for now.


Regards,
Michael



OpenPGP_signature
Description: OpenPGP digital signature