[Spacewalk-list] ERROR: (23, 'ERROR: duplicate key value violates unique constraint "rhn_cnp_cid_nid_uq"', 'Could not update database entry.')

[Robert Paschedag]

> Gesendet: Dienstag, 17. Juli 2018 um 11:28 Uhr
> Von: "Giles Coochey" <giles at coochey.net>
> An: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
> Betreff: [Spacewalk-list] ERROR: (23, 'ERROR: duplicate key value violates unique constraint "rhn_cnp_cid_nid_uq"', 'Could not update database entry.')
>
> I'm getting the unique contrainst violation on attempting to reposync my 
> Centos 6 OS updates.
> 
> I've googled the error and see that in the past it is due to misnaming 
> of packages in the repo, but it doesn't help me find which package might 
> be the root cause of this (prior reports seem to indicate a different 
> package to what might be at fault now, the prior thread dates back to 2016).
> 
> There is a more recent report with regard to satellite-sync here: 
> https://access.redhat.com/solutions/511223 (which appears to be from 
> June 2018).
> 
> Unfortunately, I don't have a Redhat login/subscription so I'm not privy 
> to the potential solution.
> 
> Anybody able to assist or provide information as to what the 511223 
> solution on the Redhat knowledgebase refers to?
> 
> The precise error I get is as follows:
> 
> 10:23:09     516/520 : yum-plugin-versionlock-1.1.30-41.el6.noarch.rpm
> 10:23:09     517/520 : yum-updateonboot-1.1.30-41.el6.noarch.rpm
> 10:23:10     518/520 : yum-utils-1.1.30-41.el6.noarch.rpm
> 10:23:10     519/520 : zsh-html-4.3.11-8.el6.centos.x86_64.rpm
> 10:23:10     520/520 : zsh-4.3.11-8.el6.centos.x86_64.rpm
> 10:23:11
> 10:23:11   Importing packages to DB:
>                 Importing packages: 
> |##################################################| 100.0%
> 10:27:34
> 10:27:34   Linking packages to the channel.
> 10:27:40 ERROR: (23, 'ERROR:  duplicate key value violates unique 
> constraint "rhn_cnp_cid_nid_uq"', 'Could not update database entry.')
> Traceback (most recent call last):
>    File "/usr/bin/spacewalk-repo-sync", line 264, in <module>
>      sys.exit(abs(main() or 0))
>    File "/usr/bin/spacewalk-repo-sync", line 247, in main
>      elapsed_time, channel_ret_code = sync.sync()
>    File 
> "/usr/lib/python2.6/site-packages/spacewalk/satellite_tools/reposync.py", 
> line 540, in sync
>      [self.channel_label], [], "server.app.yumreposync")
>    File 
> "/usr/lib/python2.6/site-packages/spacewalk/server/taskomatic.py", line 
> 69, in add_to_repodata_queue_for_channel_package_subscription
>      add_to_repodata_queue(channel, caller, reason[:128])
>    File 
> "/usr/lib/python2.6/site-packages/spacewalk/server/taskomatic.py", line 
> 53, in add_to_repodata_queue
>      queue.add(entry)
>    File 
> "/usr/lib/python2.6/site-packages/spacewalk/server/taskomatic.py", line 
> 44, in add
>      bypass_filters=self._boolean_as_char(entry.bypass_filters))
>    File 
> "/usr/lib/python2.6/site-packages/spacewalk/server/rhnSQL/sql_base.py", 
> line 151, in execute
>      return self._execute_wrapper(self._execute, *p, **kw)
>    File 
> "/usr/lib/python2.6/site-packages/spacewalk/server/rhnSQL/driver_postgresql.py", 
> line 302, in _execute_wrapper
>      raise sql_base.SQLSchemaError(error_code, e.pgerror, e)
> spacewalk.server.rhnSQL.sql_base.SQLSchemaError: (99999, 'ERROR: current 
> transaction is aborted, commands ignored until end of transaction 
> block', '', InternalError('current transaction is aborted, commands 
> ignored until end of transaction block\n',))

I don't know the full correct path right now from my mind, but you can look into
the postgres DB logs somewhere in /var/lib/pgdata/logs/<weekday>.log (I think).

There should be some more detail.

Robert
> 
> 
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list