<div dir="ltr"><div>Hello,</div><div><br></div><div>I found my problem. </div><div>I updated my Spacewalk Server.</div><div>After downgrade (yum history undo 12), it's ok !!</div><div><br></div><div>below, list of packages updated.</div><div>What package can be problematic ? HTTPD ? JAVA ? Other ?</div><div><br></div><div>Thanks</div><div>Regards</div><div>Romain</div><div><br></div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><i>Removed:<br></i><i> NetworkManager.x86_64 1:1.4.0-19.el7_3 NetworkManager-config-server.x86_64 1:1.4.0-19.el7_3<br></i><i> NetworkManager-libnm.x86_64 1:1.4.0-19.el7_3 NetworkManager-team.x86_64 1:1.4.0-19.el7_3<br></i><i> NetworkManager-tui.x86_64 1:1.4.0-19.el7_3 bind-libs.x86_64 32:9.9.4-38.el7_3.3<br></i><i> bind-libs-lite.x86_64 32:9.9.4-38.el7_3.3 bind-license.noarch 32:9.9.4-38.el7_3.3<br></i><i> bind-utils.x86_64 32:9.9.4-38.el7_3.3 ca-certificates.noarch 0:2017.2.11-70.1.el7_3<br></i><i> container-selinux.noarch 2:2.10-2.el7 device-mapper.x86_64 7:1.02.135-1.el7_3.4<br></i><i> device-mapper-event.x86_64 7:1.02.135-1.el7_3.4 device-mapper-event-libs.x86_64 7:1.02.135-1.el7_3.4<br></i><i> device-mapper-libs.x86_64 7:1.02.135-1.el7_3.4 dmidecode.x86_64 1:3.0-2.1.el7_3<br></i><i> docker.x86_64 2:1.12.6-16.el7 docker-client.x86_64 2:1.12.6-16.el7<br></i><i> docker-common.x86_64 2:1.12.6-16.el7 docker-rhel-push-plugin.x86_64 2:1.12.6-16.el7<br></i><i> grubby.x86_64 0:8.28-21.el7_3 httpd.x86_64 0:2.4.6-45.el7_3.4<br></i><i> httpd-tools.x86_64 0:2.4.6-45.el7_3.4 initscripts.x86_64 0:9.49.37-1.el7_3.1<br></i><i> irqbalance.x86_64 3:1.0.7-6.el7_3.1 java-1.8.0-openjdk.x86_64 1:1.8.0.131-2.b11.el7_3<br></i><i> java-1.8.0-openjdk-headless.x86_64 1:1.8.0.131-2.b11.el7_3 kernel-tools.x86_64 0:3.10.0-514.16.1.el7<br></i><i> kernel-tools-libs.x86_64 0:3.10.0-514.16.1.el7 libblkid.x86_64 0:2.23.2-33.el7_3.2<br></i><i> libgudev1.x86_64 0:219-30.el7_3.8 libmount.x86_64 0:2.23.2-33.el7_3.2<br></i><i> libsss_idmap.x86_64 0:1.14.0-43.el7_3.14 libsss_nss_idmap.x86_64 0:1.14.0-43.el7_3.14<br></i><i> libuuid.x86_64 0:2.23.2-33.el7_3.2 lvm2.x86_64 7:2.02.166-1.el7_3.4<br></i><i> lvm2-libs.x86_64 7:2.02.166-1.el7_3.4 mod_ssl.x86_64 1:2.4.6-45.el7_3.4<br></i><i> nss.x86_64 0:3.28.4-1.0.el7_3 nss-sysinit.x86_64 0:3.28.4-1.0.el7_3<br></i><i> nss-tools.x86_64 0:3.28.4-1.0.el7_3 nss-util.x86_64 0:3.28.4-1.0.el7_3<br></i><i> ntpdate.x86_64 0:4.2.6p5-25.el7_3.2 oci-register-machine.x86_64 1:0-3.11.gitdd0daef.el7<br></i><i> oci-systemd-hook.x86_64 1:0.1.7-2.git2788078.el7 openssh.x86_64 0:6.6.1p1-35.el7_3<br></i><i> openssh-clients.x86_64 0:6.6.1p1-35.el7_3 openssh-server.x86_64 0:6.6.1p1-35.el7_3<br></i><i> pulseaudio-libs.x86_64 0:6.0-9.el7_3 python-perf.x86_64 0:3.10.0-514.16.1.el7<br></i><i> selinux-policy.noarch 0:3.13.1-102.el7_3.16 selinux-policy-targeted.noarch 0:3.13.1-102.el7_3.16<br></i><i> sssd-client.x86_64 0:1.14.0-43.el7_3.14 systemd.x86_64 0:219-30.el7_3.8<br></i><i> systemd-libs.x86_64 0:219-30.el7_3.8 systemd-python.x86_64 0:219-30.el7_3.8<br></i><i> systemd-sysv.x86_64 0:219-30.el7_3.8 tomcat.noarch 0:7.0.69-11.el7_3<br></i><i> tomcat-el-2.2-api.noarch 0:7.0.69-11.el7_3 tomcat-jsp-2.2-api.noarch 0:7.0.69-11.el7_3<br></i><i> tomcat-lib.noarch 0:7.0.69-11.el7_3 tomcat-servlet-3.0-api.noarch 0:7.0.69-11.el7_3<br></i><i> tzdata.noarch 0:2017b-1.el7 tzdata-java.noarch 0:2017b-1.el7<br></i><i> util-linux.x86_64 0:2.23.2-33.el7_3.2 yum-rhn-plugin.noarch 0:2.0.1-6.1.el7_3</i><i><br></i><i>Installed:<br></i><i> NetworkManager.x86_64 1:1.4.0-17.el7_3 NetworkManager-config-server.x86_64 1:1.4.0-17.el7_3<br></i><i> NetworkManager-libnm.x86_64 1:1.4.0-17.el7_3 NetworkManager-team.x86_64 1:1.4.0-17.el7_3<br></i><i> NetworkManager-tui.x86_64 1:1.4.0-17.el7_3 bind-libs.x86_64 32:9.9.4-38.el7_3.2<br></i><i> bind-libs-lite.x86_64 32:9.9.4-38.el7_3.2 bind-license.noarch 32:9.9.4-38.el7_3.2<br></i><i> bind-utils.x86_64 32:9.9.4-38.el7_3.2 ca-certificates.noarch 0:2015.2.6-73.el7<br></i><i> container-selinux.noarch 2:2.9-4.el7 device-mapper.x86_64 7:1.02.135-1.el7_3.3<br></i><i> device-mapper-event.x86_64 7:1.02.135-1.el7_3.3 device-mapper-event-libs.x86_64 7:1.02.135-1.el7_3.3<br></i><i> device-mapper-libs.x86_64 7:1.02.135-1.el7_3.3 dmidecode.x86_64 1:3.0-2.el7<br></i><i> docker.x86_64 2:1.12.6-11.el7 docker-client.x86_64 2:1.12.6-11.el7<br></i><i> docker-common.x86_64 2:1.12.6-11.el7 docker-rhel-push-plugin.x86_64 2:1.12.6-11.el7<br></i><i> grubby.x86_64 0:8.28-18.el7 httpd.x86_64 0:2.4.6-45.el7<br></i><i> httpd-tools.x86_64 0:2.4.6-45.el7 initscripts.x86_64 0:9.49.37-1.el7<br></i><i> irqbalance.x86_64 3:1.0.7-6.el7 java-1.8.0-openjdk.x86_64 1:1.8.0.121-0.b13.el7_3<br></i><i> java-1.8.0-openjdk-headless.x86_64 1:1.8.0.121-0.b13.el7_3 kernel-tools.x86_64 0:3.10.0-514.10.2.el7<br></i><i> kernel-tools-libs.x86_64 0:3.10.0-514.10.2.el7 libblkid.x86_64 0:2.23.2-33.el7<br></i><i> libgudev1.x86_64 0:219-30.el7_3.7 libmount.x86_64 0:2.23.2-33.el7<br></i><i> libsss_idmap.x86_64 0:1.14.0-43.el7_3.11 libsss_nss_idmap.x86_64 0:1.14.0-43.el7_3.11<br></i><i> libuuid.x86_64 0:2.23.2-33.el7 lvm2.x86_64 7:2.02.166-1.el7_3.3<br></i><i> lvm2-libs.x86_64 7:2.02.166-1.el7_3.3 mod_ssl.x86_64 1:2.4.6-45.el7<br></i><i> nss.x86_64 0:3.28.2-1.6.el7_3 nss-sysinit.x86_64 0:3.28.2-1.6.el7_3<br></i><i> nss-tools.x86_64 0:3.28.2-1.6.el7_3 nss-util.x86_64 0:3.28.2-1.1.el7_3<br></i><i> ntpdate.x86_64 0:4.2.6p5-25.el7_3.1 oci-register-machine.x86_64 1:0-1.11.gitdd0daef.el7<br></i><i> oci-systemd-hook.x86_64 1:0.1.4-9.git671c428.el7 openssh.x86_64 0:6.6.1p1-33.el7_3<br></i><i> openssh-clients.x86_64 0:6.6.1p1-33.el7_3 openssh-server.x86_64 0:6.6.1p1-33.el7_3<br></i><i> pulseaudio-libs.x86_64 0:6.0-8.el7 python-perf.x86_64 0:3.10.0-514.10.2.el7<br></i><i> selinux-policy.noarch 0:3.13.1-102.el7_3.15 selinux-policy-targeted.noarch 0:3.13.1-102.el7_3.15<br></i><i> sssd-client.x86_64 0:1.14.0-43.el7_3.11 systemd.x86_64 0:219-30.el7_3.7<br></i><i> systemd-libs.x86_64 0:219-30.el7_3.7 systemd-python.x86_64 0:219-30.el7_3.7<br></i><i> systemd-sysv.x86_64 0:219-30.el7_3.7 tomcat.noarch 0:7.0.69-10.el7<br></i><i> tomcat-el-2.2-api.noarch 0:7.0.69-10.el7 tomcat-jsp-2.2-api.noarch 0:7.0.69-10.el7<br></i><i> tomcat-lib.noarch 0:7.0.69-10.el7 tomcat-servlet-3.0-api.noarch 0:7.0.69-10.el7<br></i><i> tzdata.noarch 0:2017a-1.el7 tzdata-java.noarch 0:2017a-1.el7<br></i><i> util-linux.x86_64 0:2.23.2-33.el7 yum-rhn-plugin.noarch 0:2.0.1-6.el7</i></blockquote></div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-05-19 12:26 GMT+02:00 Inter Load <span dir="ltr"><<a href="mailto:interload13@gmail.com" target="_blank">interload13@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hello,</div><div><br></div><div>I invite your assistance on this problem. I do not want to open a redhat ticket on Spacewalk.</div><div>I hope that is this the right forum ?</div><div><br></div><div>We are using Spacewalk to monitor some of our systems.</div><div>Actually, there are Exclamation mark in front of repository names on Client.</div><div>After clean cache on the client (yum clean all), "yum" cannot retrieve metadata from the SpaceWalk Server.</div><div>Client system shows 0 packages in base channel.</div><div><br></div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><i># yum repolist<br></i><i>Loaded plugins: langpacks, product-id, rhnplugin, search-disabled-repos<br></i><i>This system is receiving updates from RHN Classic or Red Hat Satellite.<br></i><i>repo id repo name status<br></i><i>dev_ppr-rhel-x86_64-server-7 dev_ppr-rhel-x86_64-server-7 0<br></i><i>dev_ppr-rhel-x86_64-server-7-<wbr>extras dev_ppr-rhel-x86_64-server-7-<wbr>extras 0<br></i><i>dev_ppr-rhel-x86_64-server-7-<wbr>optional dev_ppr-rhel-x86_64-server-7-<wbr>optional 0<br></i><i>dev_ppr-rhel-x86_64-server-7-<wbr>updates dev_ppr-rhel-x86_64-server-7-<wbr>updates 0<br></i><i>dev_ppr-rhel-x86_64-server-7-<wbr>zabbix dev_ppr-rhel-x86_64-server-7-<wbr>zabbix 0<br></i><i>repolist: 0</i></blockquote><div><br></div><div><br></div><div><br></div><div> I tried this documentation (<a href="https://access.redhat.com/solutions/19303" target="_blank">https://access.redhat.com/<wbr>solutions/19303</a>) but it doesn't work.</div><div>After "yum check-update" command, I have the following error message</div><div><br></div></div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><i>One of the configured repositories failed (Unknown),<br> and yum doesn't have enough cached data to continue. At this point the only<br> safe thing yum can do is fail. There are a few ways to work "fix" this:<br> 1. Contact the upstream for the repository and get them to fix the problem.<br> 2. Reconfigure the baseurl/etc. for the repository, to point to a working<br> upstream. This is most often useful if you are using a newer<br> distribution release than is supported by the repository (and the<br> packages for the previous distribution release still work).<br> 3. Run the command with the repository temporarily disabled<br> yum --disablerepo=<repoid> ...<br> 4. Disable the repository permanently, so yum won't use it by default. Yum<br> will then just ignore the repository until you permanently enable it<br> again or use --enablerepo for temporary usage:<br> yum-config-manager --disable <repoid><br> or<br> subscription-manager repos --disable=<repoid><br> 5. Configure the failing repository to be skipped, if it is unavailable.<br> Note that yum will try to contact the repo. when it runs most commands,<br> so will have to try and fail each time (and thus. yum will be be much<br> slower). If it is a very temporary problem though, this is often a nice<br> compromise:<br> yum-config-manager --save --setopt=<repoid>.skip_if_<wbr>unavailable=true<br>failed to retrieve repodata/repomd.xml from dev_ppr-rhel-x86_64-server-7<br>error was [Errno 14] HTTP Error 400 - Bad Request</i></blockquote><div><br></div><div><br></div><div><div><br></div><div>Client system always shows 0 packages in base channel (Previously, I forced regeneration process after restart taskomatic service).</div><div><br></div><div>I tried out ideas :</div><div>- On the client system : yum clean all; rm -rf /var/cache/yum/*; rhn-profile-sync; yum update</div><div>- On the server SpaceWalk : spacewalk-service stop; rm -rf /var/cache/rhn/reposync/*; rm -rf /var/cache/rhn/repodata/*; rm -rf /var/cache/rhn/satsync/*; spacewalk-service start</div><div>- On the server SpaceWalk : Regenerate repo data for all channels : spacecmd softwarechannel_list; for i in spacecmd softwarechannel_list; do spacecmd softwarechannel_<wbr>regenerateyumcache $i; done</div><div>- Add a new client</div><div><br></div><div>For information, I noticed that a taskomatic service no regenerate repodata after restart service. I am bound to force repodata regeneration.</div><div>In /var/log/rhn/rhn_taskomatic_<wbr>daemon.log, I have the following message :</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><i><br>INFO: Initializing c3p0 pool... com.mchange.v2.c3p0.<wbr>PoolBackedDataSource@a111cc3c [ connectionPoolDataSource -> com.mchange.v2.c3p0.<wbr>WrapperConnectionPoolDataSourc<wbr>e@226fcf3b [ acquireIncrement -> 3, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> false, checkoutTimeout -> 0, connectionCustomizerClassName -> com.redhat.rhn.common.db.<wbr>RhnConnectionCustomizer, connectionTesterClassName -> com.mchange.v2.c3p0.impl.<wbr>DefaultConnectionTester, debugUnreturnedConnectionStack<wbr>Traces -> false, factoryClassLocation -> null, forceIgnoreUnresolvedTransacti<wbr>ons -> false, identityToken -> 2uut749o7rg7up15sofpp|<wbr>45a9cb94, idleConnectionTestPeriod -> 300, initialPoolSize -> 5, maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime -> 300, maxIdleTimeExcessConnections -> 0, maxPoolSize -> 20, maxStatements -> 0, maxStatementsPerConnection -> 0, minPoolSize -> 5, nestedDataSource -> com.mchange.v2.c3p0.<wbr>DriverManagerDataSource@<wbr>135e2207 [ description -> null, driverClass -> null, factoryClassLocation -> null, identityToken -> 2uut749o7rg7up15sofpp|<wbr>6c9ab334, jdbcUrl -> jdbc:postgresql:rhnschema, properties -> {user=******, password=******, driver_proto=jdbc:postgresql} ], preferredTestQuery -> select 'c3p0 ping' from dual, propertyCycle -> 0, testConnectionOnCheckin -> false, testConnectionOnCheckout -> true, unreturnedConnectionTimeout -> 0, usesTraditionalReflectiveProxi<wbr>es -> false; userOverrides: {} ], dataSourceName -> null, factoryClassLocation -> null, identityToken -> 2uut749o7rg7up15sofpp|<wbr>5727e9b9, numHelperThreads -> 3 ]</i></blockquote><div><br></div><div><br></div><div>Have you got an idea of this behavior ?</div><div><br></div><div>Thanks a lot</div><div>Romain</div><div> </div></div></div> </blockquote></div><br></div>