nscd not updated/restarted soon enough during zypper dup

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

nscd not updated/restarted soon enough during zypper dup

Olaf Hering-2
During upgrade of postfix, nscd did not work properly because some
symbols are not available. I wonder what needs to be done to make nscd
available earlier during 'zypper dup'. The %pre/%post scripts in postfix
do not use it directly, but the used getent/useradd/... binaries may try
to use it. The Requires(pre/post) in postfix.spec are apparently ok,
except the incorrect conditional for getent. glibc was upgraded before
postfix, so this is not the issue here.


Upgrade was blocked by various bugs in the last months, they got fixed
only until very recently. Thats the reason for the huge jump forward.

Olaf


root@optiplex:~ # grep -E '(release-ftp|nscd|postfix|glibc)' /var/log/zypp/history
2017-05-30 09:29:56|install|linux-glibc-devel|4.11-1.1|noarch||oss|4e6cc97a31d9aa568a3d7966364eb0fac76ac5d4|
2017-05-30 09:30:33|install|openSUSE-release-ftp|20170524-1.1|x86_64||oss|8a907ed01f6f4d4ba30fc23484e222b605ef8b6c|
2017-11-23 09:26:35|install|glibc-debuginfo|2.26-7.1|x86_64||debug|d2a3893b076e3d0b50116a8f0bcd992ab5016b43|
2017-11-23 09:26:37|install|glibc-debugsource|2.26-7.1|x86_64||debug|4562bbb692a9d7a50554eaab6bed54ec1fbc7e6b|
2017-11-23 09:34:19|install|postfix-debuginfo|3.2.4-2.1|x86_64||debug|396a383e4310daeb766a9d2aa22e8f2b27a656a4|
2017-11-23 09:34:19|install|postfix-debugsource|3.2.4-2.1|x86_64||debug|8aea6966b0a34e1d406587048b84c1b5fac1b124|
2017-11-23 09:39:44|install|nscd-debuginfo|2.26-7.1|x86_64||debug|59888b3af71ece2c8f016f267f335944a759affe|
2017-11-23 09:39:46|install|glibc-locale-debuginfo|2.26-7.1|x86_64||debug|247d10317153d3d719fd2066722235ccb71cb59a|
2017-11-23 09:39:46|install|glibc-extra-debuginfo|2.26-7.1|x86_64||debug|3b582b7085c7298b92a484f67d5fc7ab1df846e7|
2017-11-23 09:43:45|install|openSUSE-release-ftp|20171121-1.2|x86_64||oss|4df1420c4ec3f828ac975fe628bf14cddf8e8b9b|
# 2017-11-23 09:44:07 glibc-2.26-7.1.x86_64.rpm installed ok
2017-11-23 09:44:07|install|glibc|2.26-7.1|x86_64||oss|dc1094b037c47c4244925d4609a18bbb79b504f8|
2017-11-23 09:44:50|install|glibc-locale|2.26-7.1|x86_64||oss|ab520862fe10de2be7f4b6c1a07c222e0de80a2e|
2017-11-23 09:45:24|install|glibc-32bit|2.26-7.1|x86_64||oss|8a1923d118bce00891b0a08df236aa832c1a5613|
2017-11-23 09:45:41|install|linux-glibc-devel|4.14-1.1|noarch||oss|03f07945f92efe01b28148e764c002e23b6f3ae7|
2017-11-23 09:46:40|install|glibc-locale-32bit|2.26-7.1|x86_64||oss|e0d925fdeb68ea286cd6b82e3527672f7bb7c9cb|
#       /etc/permissions.d/postfix
# 2017-11-23 09:59:15 postfix-3.2.4-2.1.x86_64.rpm installed ok
# nscd: relocation error: nscd: symbol __res_maybe_init, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
# nscd: relocation error: nscd: symbol __res_maybe_init, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
# warning: /etc/postfix/main.cf created as /etc/postfix/main.cf.rpmnew
#      /etc/postfix/postfix-files /etc/postfix/postfix-script
#      /etc/postfix/post-install
# Updating /etc/sysconfig/postfix ...
2017-11-23 09:59:15|install|postfix|3.2.4-2.1|x86_64||oss|a1060870bc514f36d2f8426676227c27acb348ff|
2017-11-23 09:59:18|install|nscd|2.26-7.1|x86_64||oss|96365fe546123d842c94c0118ab60000c4075094|
2017-11-23 10:02:33|install|glibc-extra|2.26-7.1|x86_64||oss|25f1fa538db1d690d43e797a59de69a45e4e4876|
2017-11-23 10:02:36|install|glibc-devel|2.26-7.1|x86_64||oss|e68c0735b0c1f603649f3a85cc8e912fcdd574a2|


signature.asc (201 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: nscd not updated/restarted soon enough during zypper dup

Andreas Schwab-2
On Nov 23 2017, Olaf Hering <[hidden email]> wrote:

> glibc was upgraded

What was the previous version?

Andreas.

--
Andreas Schwab, SUSE Labs, [hidden email]
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: nscd not updated/restarted soon enough during zypper dup

Olaf Hering-2
On Thu, Nov 23, Andreas Schwab wrote:

> On Nov 23 2017, Olaf Hering <[hidden email]> wrote:
>
> > glibc was upgraded
> What was the previous version?

Whatever was current end of May, likely 2.25.

Olaf

signature.asc (201 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: nscd not updated/restarted soon enough during zypper dup

Andreas Schwab-2
On Nov 23 2017, Olaf Hering <[hidden email]> wrote:

> On Thu, Nov 23, Andreas Schwab wrote:
>
>> On Nov 23 2017, Olaf Hering <[hidden email]> wrote:
>>
>> > glibc was upgraded
>> What was the previous version?
>
> Whatever was current end of May, likely 2.25.

That means a major version upgrade, you need to boot into the
installation image and do the update from there.  As a workaround
stopping nscd before the upgrade may help, but is not guaranteed.

Andreas.

--
Andreas Schwab, SUSE Labs, [hidden email]
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: nscd not updated/restarted soon enough during zypper dup

Olaf Hering-2
On Thu, Nov 23, Andreas Schwab wrote:

> That means a major version upgrade, you need to boot into the
> installation image and do the update from there.  As a workaround
> stopping nscd before the upgrade may help, but is not guaranteed.

Was that part of the release announcement of the snapshot that contained
the glibc 2.25->2.26 update?

Olaf

signature.asc (201 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: nscd not updated/restarted soon enough during zypper dup

Andreas Schwab-2
On Nov 23 2017, Olaf Hering <[hidden email]> wrote:

> On Thu, Nov 23, Andreas Schwab wrote:
>
>> That means a major version upgrade, you need to boot into the
>> installation image and do the update from there.  As a workaround
>> stopping nscd before the upgrade may help, but is not guaranteed.
>
> Was that part of the release announcement of the snapshot that contained
> the glibc 2.25->2.26 update?

It's really the same as when you upgrade your running DE.  Don't do it.

Andreas.

--
Andreas Schwab, SUSE Labs, [hidden email]
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]