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

2018-07-18 Thread Giles Coochey
On 17/07/2018 20:59, Robert Paschedag wrote: Maybe you could try to delete all packages within that channel (102) and try to sync again. But you should verify, that there are no more packages with this channel id (102) within the rhnChannelNewestPackage. Sorry...currently have no other idea.

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

2018-07-17 Thread Robert Paschedag
On 07/17/18 12:54, Giles Coochey wrote: > On 17/07/2018 11:26, Robert Paschedag wrote: >> >>> Gesendet: Dienstag, 17. Juli 2018 um 11:28 Uhr >>> Von: "Giles Coochey" >>> An: "spacewalk-list@redhat.com" >>> Betreff: [Spacewalk-

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

2018-07-17 Thread Giles Coochey
On 17/07/2018 11:26, Robert Paschedag wrote: Gesendet: Dienstag, 17. Juli 2018 um 11:28 Uhr Von: "Giles Coochey" An: "spacewalk-list@redhat.com" Betreff: [Spacewalk-list] ERROR: (23, 'ERROR: duplicate key value violates unique constraint "rhn_cnp_cid_nid_uq"

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

2018-07-17 Thread Robert Paschedag
> Gesendet: Dienstag, 17. Juli 2018 um 11:28 Uhr > Von: "Giles Coochey" > An: "spacewalk-list@redhat.com" > Betreff: [Spacewalk-list] ERROR: (23, 'ERROR: duplicate key value violates > unique constraint "rhn_cnp_cid_nid_uq"', 'Could not update

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

2018-07-17 Thread Giles Coochey
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