[Spacewalk-list] unique key constraint violated... pointers needed!

Jason Ball jason at ball.net
Sun Oct 25 07:22:28 UTC 2009


Hi all,

I've been trying to configure a production instance of spacewalk after
testing the system on my test servers for the past week.

This is a clean install on a clean RHEL5 server, and I have carefully
followed all of the installation instructions on the wiki several times to
try and get around the error.

I'm finding this very reproducible at this stage...

Process:

1, Install oraclexe and spacewalk as per the installation instructions.
2. Create an admin account.
3. Create a repository for the RHEL5 base images;
4. Run:

/usr/bin/spacewalk-repo-sync --channel=rhel5-base
--url=http://<server>/apt/redhat/ES5.3/en/x86_64/RPMS.os
--type=yum --label='basepackages'

to load the base packages from my current yum repository.

After approx 500 packages I get an error as follows:

ERRORException reported from XXXXXX
Time: Sun Oct 25 17:40:39 2009
Exception type common.rhnException.rhnFault

Exception Handler Information
Traceback (most recent call last):
  File "/usr/share/rhn/satellite_tools/reposync.py", line 142, in
import_packages
    self.associate_package(pack, md5)
  File "/usr/share/rhn/satellite_tools/reposync.py", line 199, in
associate_package
    self._importer_run(package, caller, backend)
  File "/usr/share/rhn/satellite_tools/reposync.py", line 207, in
_importer_run
    importer.run()
  File "/usr/share/rhn/server/importlib/importLib.py", line 628, in run
    self.submit()
  File "/usr/share/rhn/server/importlib/packageImport.py", line 123, in
submit
    affected_channels=self.affected_channel_packages)
  File "/usr/share/rhn/server/importlib/backend.py", line 1328, in
update_newest_package_cache
    raise rhnFault(23, str(e[1]), explain=0)
rhnFault: (23, 'ORA-00001: unique constraint (SPACEWALK.RHN_CNP_CID_NID_UQ)
violated\nORA-06512: at "SPACEWALK.RHN_CHANNEL", line 1131\nORA-06512: at
line 1\n', 'Could not update database entry.')


Once this occurs any operation to manipulate the DB fails with the same
error via the UI and the command line.  There are no errors shown in the
oracle or tomcat logs, and the following error in the http log at around the
same time which may or may not be related given this was also a fresh
install:

[Sun Oct 25 17:28:11 2009] [error] (111)Connection refused: proxy: AJP:
attempt to connect to 127.0.0.1:8009 (*) failed
[Sun Oct 25 17:28:11 2009] [error] proxy: AJP: failed to make connection to
backend: localhost

In this instance the above error was preceeded by:

Exception Handler Information
Traceback (most recent call last):
  File "/usr/share/rhn/satellite_tools/reposync.py", line 142, in
import_packages
    self.associate_package(pack, md5)
  File "/usr/share/rhn/satellite_tools/reposync.py", line 199, in
associate_package
    self._importer_run(package, caller, backend)
  File "/usr/share/rhn/satellite_tools/reposync.py", line 207, in
_importer_run
    importer.run()
  File "/usr/share/rhn/server/importlib/importLib.py", line 628, in run
    self.submit()
  File "/usr/share/rhn/server/importlib/packageImport.py", line 123, in
submit
    affected_channels=self.affected_channel_packages)
  File "/usr/share/rhn/server/importlib/backend.py", line 1328, in
update_newest_package_cache
    raise rhnFault(23, str(e[1]), explain=0)
 1131\nORA-06512: at line 1\n', 'Could not update database entry.')

Any pointers as to how to find and fix this problem would be greatly
appreciated.

J.



-- 
The era of procrastination, of half measures of soothing and baffling
expedients, of delays, is coming to an end. In it's place we are entering a
period of  consequences.  - Winston Churchill
<a href=http://www.climatecrisis.net/downloads/ecards/preview-glacier1.html>An
Inconvenient Truth</a>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20091025/09cbe0da/attachment.htm>


More information about the Spacewalk-list mailing list