[Spacewalk-list] yup update/install gives 404 error

Clouse, Raymond raymond.clouse at hireright.com
Mon Dec 18 21:52:28 UTC 2017

We're having a vexing issue with a new Spacewalk 2.6 installation.

We've made it a slave to a master (security reasons; only one SW is exposed to the Internet) and have everything synchronized and communicating successfully.  But when we try to do an update or install with yum, we get a 404 error like this:

Error downloading packages:
  nss-tools-3.28.4-8.el7.x86_64: failed to retrieve getPackage/nss-tools-3.28.4-8.el7.x86_64.rpm from our_repo

I find errors get logged in /var/log/httpd/error_log simultaneously like this:

[Mon Dec 18 20:02:31.638648 2017] [:error] [pid 53696] Spacewalk 53696 2017/12/18 20:02:31 +01:00: WARNING: log path not found; attempting to create /var/log/rhn
[Mon Dec 18 20:02:31.638680 2017] [:error] [pid 53696] Spacewalk 53696 2017/12/18 20:02:31 +01:00: (None, None)
[Mon Dec 18 20:02:31.638810 2017] [:error] [pid 53696] Spacewalk 53696 2017/12/18 20:02:31 +01:00: ERROR: unable to create log file path /var/log/rhn
[Mon Dec 18 20:02:31.638837 2017] [:error] [pid 53696] Spacewalk 53696 2017/12/18 20:02:31 +01:00: (<type 'exceptions.OSError'>, OSError(13, 'Permission denied'))

Of course, /var/log/rhn exists and has proper permissions.  I even set permissions to 777 just in case with no positive effect.

One other possible clue: in /var/log/rhn/rhn_taskomatic_daemon.log I found this:

INFO   | jvm 1    | 2017/12/18 20:06:32 | com.mchange.v2.cfg.DelayedLogItem [ level -> FINE, text -> "The configuration file for resource identifier '/mchange-commons.properties' could not be found. Skipping.", exception -> java.io.FileNotFoundException: Resource not found at path '/mchange-commons.properties'.]

And in Googling that I found an unreplied post here that says:
Tomcat6 is having a problem finding mchange-commons when it's starting up which causes the web / api interface to fail, causing other parts of spacewalk to fail to initialize.

How / where can I get the mchange-commons installed and linked properly so that tomcat will be able to start?

So, in summary:
- Spacewalk set up as slave
- Clients can see SW
- SW knows which systems need upgrades
- Upgrades or installs fail with 404 error

Ray Clouse | Senior Systems Application Engineer | 3349 Michelson Drive Suite 150 | Irvine, CA 92612
949.428.5880 [o] | 949.870.6935 [m]
[cid:image003.png at 01D20E7A.0BAA12E0]<http://www.hireright.com/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20171218/2f7df74e/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 4242 bytes
Desc: image001.png
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20171218/2f7df74e/attachment.png>

More information about the Spacewalk-list mailing list