[Spacewalk-list] CentOS7 and Spacewalk Proxy 2.3 facing an odd Issue /proc not mounted?

Wed Aug 12 19:35:02 UTC 2015

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

CentOS7 and Spacewalk Proxy 2.3  facing an odd Issue

Hello List,

i'm kinda wondered we face an issue i've never seen before.

The OS we make use of is CentOS7.

In Detail:
- ---------------------------------------------------------------------
CentOS Linux release 7.1.1503 (Core)
3.10.0-229.7.2.el7.x86_64 #1 SMP Tue Jun 23 22:06:11 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
- ------------------------------------------------------------------------
- -

The following Packages are installed on our Proxy System:
- ----------------------------------------------------
[root at proxy1 httpd]# rpm -qa |grep space
spacewalk-backend-libs-2.3.52-1.el7.noarch
spacewalk-base-minimal-2.3.53-1.el7.noarch
spacewalk-proxy-broker-2.3.23-1.el7.noarch
spacewalk-setup-jabberd-2.3.2-1.el7.noarch
perl-XML-NamespaceSupport-1.11-10.el7.noarch
spacewalk-proxy-html-2.3.1-1.el7.noarch
spacewalk-base-minimal-config-2.3.53-1.el7.noarch
spacewalk-proxy-docs-2.3.1-1.el7.noarch
spacewalk-certs-tools-2.3.3-1.el7.noarch
spacewalk-backend-2.3.52-1.el7.noarch
spacewalk-proxy-common-2.3.23-1.el7.noarch
spacewalk-proxy-redirect-2.3.23-1.el7.noarch
spacewalk-proxy-selinux-2.0.1-1.el7.noarch
spacewalk-proxy-installer-2.3.13-1.el7.noarch
spacewalk-ssl-cert-check-2.4-1.el7.noarch
spacewalk-proxy-package-manager-2.3.23-1.el7.noarch
spacewalk-proxy-management-2.3.23-1.el7.noarch
- ----------------------------------------------------------------

If we try to upgrade several SLES clients with zypper dup the Apache
log gets spammed with the following warning.

warning: Failed to read auxiliary vector, /proc not mounted?
warning: Failed to read auxiliary vector, /proc not mounted?
warning: Failed to read auxiliary vector, /proc not mounted?
warning: Failed to read auxiliary vector, /proc not mounted?

if we check for proc everything looks good.

[root at proxy1 httpd]# mount  |grep proc
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs
(rw,relatime,fd=37,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)

So if we try to upgrade our clients .......

zypper dup

168 packages to upgrade, 16 to downgrade, 14 new, 2 to reinstall, 6 to
remove, 3  to change vendor.
Overall download size: 162.0 MiB. After the operation, additional 31.1
MiB will be used.
Continue? [y/n/? shows all options] (y): y
Retrieving package libnfnetlink0-1.0.0+git1-9.5.56.x86_64 (1/200),
22.0 KiB (45.0 KiB unpacked)
Retrieving: libnfnetlink0-1.0.0+git1-9.5.56.x86_64.rpm [error]
File './getPackage/libnfnetlink0-1.0.0+git1-9.5.56.x86_64.rpm' not
found on medium
'https://proxy1.example.com/XMLRPC/GET-REQ/sles11-sp4-pool-x86_64?head_r
equests=no'

Abort, retry, ignore? [a/r/i/? shows all options] (a): a
Failed to provide Package libnfnetlink0-1.0.0+git1-9.5.56. Do you want
to retry retrieval?

[spacewalk:sles11-sp4-pool-x86_64|plugin:spacewalk?channel=sles11-sp4-po
ol-x86_64]
Can't provide file
'./getPackage/libnfnetlink0-1.0.0+git1-9.5.56.x86_64.rpm' from
repository 'spacewalk:sles11-sp4-pool-x86_64'
History:
 - File './getPackage/libnfnetlink0-1.0.0+git1-9.5.56.x86_64.rpm' not
found on medium
'https://proxy.example.com/XMLRPC/GET-REQ/sles11-sp4-pool-x86_64?head_re
quests=no'

 - Can't provide ./getPackage/libnfnetlink0-1.0.0+git1-9.5.56.x86_64.rpm

Abort, retry, ignore? [a/r/i] (a): a
Problem occured during or after installation or removal of packages:
Installation aborted by user

Please see the above error message for a hint.
~ #

What we tried so far.....
Restartig Proxy Services.....
Restarting the Box several times.

After Restarting the Box no further /proc Warnings.

Box restart...

root at proxy1 ~]# cd /var/log/httpd/
[root at proxy1 httpd]# tail -f error_log
[Tue Aug 11 09:58:37.899828 2015] [suexec:notice] [pid 968] AH01232:
suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Aug 11 09:58:37.940523 2015] [core:warn] [pid 968] AH00117:
Ignoring deprecated use of DefaultType in line 16 of
/etc/httpd/conf.d/spacewalk-proxy.conf.
[Tue Aug 11 09:58:37.940548 2015] [core:warn] [pid 968] AH00117:
Ignoring deprecated use of DefaultType in line 21 of
/etc/httpd/conf.d/spacewalk-proxy.conf.
[Tue Aug 11 09:58:37.940557 2015] [core:warn] [pid 968] AH00117:
Ignoring deprecated use of DefaultType in line 26 of
/etc/httpd/conf.d/spacewalk-proxy.conf.
[Tue Aug 11 09:58:37.940564 2015] [core:warn] [pid 968] AH00117:
Ignoring deprecated use of DefaultType in line 31 of
/etc/httpd/conf.d/spacewalk-proxy.conf.
[Tue Aug 11 09:58:37.940572 2015] [core:warn] [pid 968] AH00117:
Ignoring deprecated use of DefaultType in line 36 of
/etc/httpd/conf.d/spacewalk-proxy.conf.
[Tue Aug 11 09:58:37.942664 2015] [auth_digest:notice] [pid 968]
AH01757: generating secret for digest authentication ...
[Tue Aug 11 09:58:37.944509 2015] [lbmethod_heartbeat:notice] [pid
968] AH02282: No slotmem from mod_heartmonitor
[Tue Aug 11 09:58:37.949929 2015] [mpm_prefork:notice] [pid 968]
AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips mod_wsgi/3.4
Python/2.7.5 configured -- resuming normal operations
[Tue Aug 11 09:58:37.949961 2015] [core:notice] [pid 968] AH00094:
Command line: '/usr/sbin/httpd -D FOREGROUND'

So we tried again...

In five of seven Reboots  the very same result.

Overall download size: 162.0 MiB. After the operation, additional 31.1
MiB will be used.
Continue? [y/n/? shows all options] (y): y
Retrieving package libnfnetlink0-1.0.0+git1-9.5.56.x86_64 (1/200),
22.0 KiB (45.0 KiB unpacked)
 - File './getPackage/libnfnetlink0-1.0.0+git1-9.5.56.x86_64.rpm' not
found on medium
'https://proxy.example.com/XMLRPC/GET-REQ/sles11-sp4-pool-x86_64?head_re
quests=no'

 - Can't provide ./getPackage/libnfnetlink0-1.0.0+git1-9.5.56.x86_64.rpm

What makes this really odd... is if you wait for nearly an hour it
works again.

What we found so far is this Bug Entry

https://bugzilla.redhat.com/show_bug.cgi?id=1190233

The Bug itself is marked as duplicate and the Original is marked as
private, so we cant
check for a possible root cause.

Has somebody faced the same Problem, as we do?

kind regards

Bernd Helber

- -- 
with kind regards

 Bernd Helber
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVy5/mAAoJEHxIkeoL34IfG4oIAMB3wE7PqTZhepJIxxO0GZpT
dhTM+LrqhjWGLR9mOzZu6hiIG8/5/3Hkc01aS5nC4z1W1LCB2pq/TScE6N3xwYXR
gL892+laKG6pT60keeCyqUDGAS74X24XiS4SCstOKgJCpDzfqLVdNSOS/ONVsjNJ
7azp5J1hDYxYszbtqiVEKh3H2lIBuIOiymQ4pV+1H/xo99FaVdjdRd7M2jFq3rhT
ehAf+vek/yurA94UC/QNE+YZAXgXFBATgcJAIJo7nXgM1BOSSTCwkBQpuFro8son
JHysA4ZzDRTuj3LQYz8YOUpJPrWSCWKUpH30ZaxLHThcsjJs4YSgSdsIDntq7Zg=
=glQr
-----END PGP SIGNATURE-----