[Spacewalk-list] ERROR: duplicate key value violates unique constraint "rhn_pkg_clr_pid_cld_uq"
Hello, i have problems with some rpm not being pushed into spacewalk with this error message in postgres log: ERROR: duplicate key value violates unique constraint "rhn_pkg_clr_pid_cld_uq" STATEMENT: insert into rhnPackageChangeLogRec (package_id, changelog_data_id, id) values (746638, 813286, 673903952) Any suggestions how to fix this ? Thanks regards frank - FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher.service failed
I don't know if this would apply to your situation. But I have had an issue
changing both the spacewalk servername and client name. I use the standard Cert
and the names didn't match after the name change.
Reinstalling the standard cert fixed it for me.
Not sure if that helps though.
-Original Message-
From: spacewalk-list-boun...@redhat.com On
Behalf Of Robert Paschedag
Sent: Tuesday, November 19, 2019 10:09 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] osa-dispatcher.service failed
EXTERNAL EMAIL: Ensure you trust this sender and know the content is safe
before clicking on any links or attachments.
Look into /var/log/messages for errors.
Also changing a hostname (of course!) breaks the SSL verification, unless the
new hostname is mentioned as SAN (subject alternative name) within the
certificate or the certificate is a wildcard certificate that Assisi matches
the new hostname.
Robert
sent from my mobile device
Originale Nachricht
Von: Raymond Setchfield
Gesendet: Tue Nov 19 17:04:20 GMT+01:00 2019
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] osa-dispatcher.service failed
Hi All,
Can anyone assist on this issue?
Ray
On Wed, Nov 6, 2019 at 11:44 AM Raymond Setchfield <
raymond.setchfi...@gmail.com> wrote:
> Hi All,
>
> Been testing this to see if I could potentially recreate the fault.
>
> I have taken a copy of the instance which was working (vanilla install
> with spacewalk applied). When the copy starts up. It appears to be
> loaded and running fine. When I made a change to the server. For
> example, the hostname. The OSAD failed after reboot.
> I then made another machine from known working copy and changed the
> sshd_config file. Rebooted the machine and osad then failed.again.
>
> The failure seems to be the same, and there is nothing within the logs
> which suggest why its failed. It appears to be a time out. anything
> else I could potentially look into?
>
> Thanks
>
> Ray
>
> -- Forwarded message -
> From: Raymond Setchfield
> Date: Tue, Nov 5, 2019 at 10:00 AM
> Subject: osa-dispatcher.service failed
> To:
>
>
> Hi All,
>
> I have been following this guide to install the SSL certificate, and
> it appears to have worked fine. As I can see the certificate when
> logging into spacewalk etc.
>
> However, when restarting the services it appears that the
> osa-dispatcher has failed. There is little or no information to go
> with to figure out why it has failed.
>
> ● postgresql.service - PostgreSQL database server
>Loaded: loaded (/usr/lib/systemd/system/postgresql.service;
> enabled; vendor preset: disabled)
>Active: active (running) since Tue 2019-11-05 09:50:15 UTC; 4min 41s ago
> Process: 12341 ExecStop=/usr/bin/pg_ctl stop -D ${PGDATA} -s -m fast
> (code=exited, status=0/SUCCESS)
> Process: 12504 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p
> ${PGPORT} -w -t 300 (code=exited, status=0/SUCCESS)
> Process: 12487 ExecStartPre=/usr/bin/postgresql-check-db-dir
> ${PGDATA} (code=exited, status=0/SUCCESS) Main PID: 12518 (postgres)
>CGroup: /system.slice/postgresql.service
>├─12518 /usr/bin/postgres -D /var/lib/pgsql/data -p 5432
>├─12529 postgres: logger process
>├─12531 postgres: checkpointer process
>├─12532 postgres: writer process
>├─12533 postgres: wal writer process
>├─12534 postgres: autovacuum launcher process
>├─12535 postgres: stats collector process
>├─12590 postgres: rhnuser rhnschema 127.0.0.1(44062) idle
>├─12591 postgres: rhnuser rhnschema 127.0.0.1(44065) idle
>├─12592 postgres: rhnuser rhnschema 127.0.0.1(44064) idle
>├─12593 postgres: rhnuser rhnschema 127.0.0.1(44068) idle
>├─12594 postgres: rhnuser rhnschema 127.0.0.1(44070) idle
>├─12762 postgres: rhnuser rhnschema 127.0.0.1(44074) idle
>├─12867 postgres: rhnuser rhnschema 127.0.0.1(44076) idle
>├─12868 postgres: rhnuser rhnschema 127.0.0.1(44078) idle
>├─12869 postgres: rhnuser rhnschema 127.0.0.1(44080) idle
>├─12870 postgres: rhnuser rhnschema 127.0.0.1(44082) idle
>├─12871 postgres: rhnuser rhnschema 127.0.0.1(44084) idle
>├─12872 postgres: rhnuser rhnschema 127.0.0.1(44086) idle
>├─12873 postgres: rhnuser rhnschema 127.0.0.1(44088) idle
>├─12874 postgres: rhnuser rhnschema 127.0.0.1(44090) idle
>├─12875 postgres: rhnuser rhnschema 127.0.0.1(44092) idle
>├─12876 postgres: rhnuser rhnschema 127.0.0.1(44094) idle
>├─12877 postgres: rhnuser rhnschema 127.0.0.1(44096) idle
>├─12878 postgres: rhnuser rhnschema 127.0.0.1(44098) idle
>├─12879 postgres: rhnuser rhnschema 127.0.0.1(44100) idle
>├─12880 postgres: rhnuser rhnschema 127.0.0.1(44102) idle
>├─12881 pos
Re: [Spacewalk-list] osa-dispatcher.service failed
Look into /var/log/messages for errors.
Also changing a hostname (of course!) breaks the SSL verification, unless the
new hostname is mentioned as SAN (subject alternative name) within the
certificate or the certificate is a wildcard certificate that Assisi matches
the new hostname.
Robert
sent from my mobile device
Originale Nachricht
Von: Raymond Setchfield
Gesendet: Tue Nov 19 17:04:20 GMT+01:00 2019
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] osa-dispatcher.service failed
Hi All,
Can anyone assist on this issue?
Ray
On Wed, Nov 6, 2019 at 11:44 AM Raymond Setchfield <
raymond.setchfi...@gmail.com> wrote:
> Hi All,
>
> Been testing this to see if I could potentially recreate the fault.
>
> I have taken a copy of the instance which was working (vanilla install
> with spacewalk applied). When the copy starts up. It appears to be loaded
> and running fine. When I made a change to the server. For example, the
> hostname. The OSAD failed after reboot.
> I then made another machine from known working copy and changed the
> sshd_config file. Rebooted the machine and osad then failed.again.
>
> The failure seems to be the same, and there is nothing within the logs
> which suggest why its failed. It appears to be a time out. anything else I
> could potentially look into?
>
> Thanks
>
> Ray
>
> -- Forwarded message -
> From: Raymond Setchfield
> Date: Tue, Nov 5, 2019 at 10:00 AM
> Subject: osa-dispatcher.service failed
> To:
>
>
> Hi All,
>
> I have been following this guide to install the SSL certificate, and it
> appears to have worked fine. As I can see the certificate when logging into
> spacewalk etc.
>
> However, when restarting the services it appears that the osa-dispatcher
> has failed. There is little or no information to go with to figure out why
> it has failed.
>
> ● postgresql.service - PostgreSQL database server
>Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled;
> vendor preset: disabled)
>Active: active (running) since Tue 2019-11-05 09:50:15 UTC; 4min 41s ago
> Process: 12341 ExecStop=/usr/bin/pg_ctl stop -D ${PGDATA} -s -m fast
> (code=exited, status=0/SUCCESS)
> Process: 12504 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p
> ${PGPORT} -w -t 300 (code=exited, status=0/SUCCESS)
> Process: 12487 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA}
> (code=exited, status=0/SUCCESS)
> Main PID: 12518 (postgres)
>CGroup: /system.slice/postgresql.service
>├─12518 /usr/bin/postgres -D /var/lib/pgsql/data -p 5432
>├─12529 postgres: logger process
>├─12531 postgres: checkpointer process
>├─12532 postgres: writer process
>├─12533 postgres: wal writer process
>├─12534 postgres: autovacuum launcher process
>├─12535 postgres: stats collector process
>├─12590 postgres: rhnuser rhnschema 127.0.0.1(44062) idle
>├─12591 postgres: rhnuser rhnschema 127.0.0.1(44065) idle
>├─12592 postgres: rhnuser rhnschema 127.0.0.1(44064) idle
>├─12593 postgres: rhnuser rhnschema 127.0.0.1(44068) idle
>├─12594 postgres: rhnuser rhnschema 127.0.0.1(44070) idle
>├─12762 postgres: rhnuser rhnschema 127.0.0.1(44074) idle
>├─12867 postgres: rhnuser rhnschema 127.0.0.1(44076) idle
>├─12868 postgres: rhnuser rhnschema 127.0.0.1(44078) idle
>├─12869 postgres: rhnuser rhnschema 127.0.0.1(44080) idle
>├─12870 postgres: rhnuser rhnschema 127.0.0.1(44082) idle
>├─12871 postgres: rhnuser rhnschema 127.0.0.1(44084) idle
>├─12872 postgres: rhnuser rhnschema 127.0.0.1(44086) idle
>├─12873 postgres: rhnuser rhnschema 127.0.0.1(44088) idle
>├─12874 postgres: rhnuser rhnschema 127.0.0.1(44090) idle
>├─12875 postgres: rhnuser rhnschema 127.0.0.1(44092) idle
>├─12876 postgres: rhnuser rhnschema 127.0.0.1(44094) idle
>├─12877 postgres: rhnuser rhnschema 127.0.0.1(44096) idle
>├─12878 postgres: rhnuser rhnschema 127.0.0.1(44098) idle
>├─12879 postgres: rhnuser rhnschema 127.0.0.1(44100) idle
>├─12880 postgres: rhnuser rhnschema 127.0.0.1(44102) idle
>├─12881 postgres: rhnuser rhnschema 127.0.0.1(44104) idle
>├─12887 postgres: rhnuser rhnschema 127.0.0.1(44106) idle
>├─12888 postgres: rhnuser rhnschema 127.0.0.1(44108) idle
>├─12889 postgres: rhnuser rhnschema 127.0.0.1(44110) idle
>├─12890 postgres: rhnuser rhnschema 127.0.0.1(44112) idle
>├─12891 postgres: rhnuser rhnschema 127.0.0.1(44114) idle
>├─12930 postgres: rhnuser rhnschema 127.0.0.1(44118) idle
>├─12931 postgres: rhnuser rhnschema 127.0.0.1(44120) idle
>├─12941 postgres: rhnuser rhnschema 127.0.0.1(44126) idle
>├─12942 postgres: rhnuser rhns
Re: [Spacewalk-list] osa-dispatcher.service failed
Hi All,
Can anyone assist on this issue?
Ray
On Wed, Nov 6, 2019 at 11:44 AM Raymond Setchfield <
raymond.setchfi...@gmail.com> wrote:
> Hi All,
>
> Been testing this to see if I could potentially recreate the fault.
>
> I have taken a copy of the instance which was working (vanilla install
> with spacewalk applied). When the copy starts up. It appears to be loaded
> and running fine. When I made a change to the server. For example, the
> hostname. The OSAD failed after reboot.
> I then made another machine from known working copy and changed the
> sshd_config file. Rebooted the machine and osad then failed.again.
>
> The failure seems to be the same, and there is nothing within the logs
> which suggest why its failed. It appears to be a time out. anything else I
> could potentially look into?
>
> Thanks
>
> Ray
>
> -- Forwarded message -
> From: Raymond Setchfield
> Date: Tue, Nov 5, 2019 at 10:00 AM
> Subject: osa-dispatcher.service failed
> To:
>
>
> Hi All,
>
> I have been following this guide to install the SSL certificate, and it
> appears to have worked fine. As I can see the certificate when logging into
> spacewalk etc.
>
> However, when restarting the services it appears that the osa-dispatcher
> has failed. There is little or no information to go with to figure out why
> it has failed.
>
> ● postgresql.service - PostgreSQL database server
>Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled;
> vendor preset: disabled)
>Active: active (running) since Tue 2019-11-05 09:50:15 UTC; 4min 41s ago
> Process: 12341 ExecStop=/usr/bin/pg_ctl stop -D ${PGDATA} -s -m fast
> (code=exited, status=0/SUCCESS)
> Process: 12504 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p
> ${PGPORT} -w -t 300 (code=exited, status=0/SUCCESS)
> Process: 12487 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA}
> (code=exited, status=0/SUCCESS)
> Main PID: 12518 (postgres)
>CGroup: /system.slice/postgresql.service
>├─12518 /usr/bin/postgres -D /var/lib/pgsql/data -p 5432
>├─12529 postgres: logger process
>├─12531 postgres: checkpointer process
>├─12532 postgres: writer process
>├─12533 postgres: wal writer process
>├─12534 postgres: autovacuum launcher process
>├─12535 postgres: stats collector process
>├─12590 postgres: rhnuser rhnschema 127.0.0.1(44062) idle
>├─12591 postgres: rhnuser rhnschema 127.0.0.1(44065) idle
>├─12592 postgres: rhnuser rhnschema 127.0.0.1(44064) idle
>├─12593 postgres: rhnuser rhnschema 127.0.0.1(44068) idle
>├─12594 postgres: rhnuser rhnschema 127.0.0.1(44070) idle
>├─12762 postgres: rhnuser rhnschema 127.0.0.1(44074) idle
>├─12867 postgres: rhnuser rhnschema 127.0.0.1(44076) idle
>├─12868 postgres: rhnuser rhnschema 127.0.0.1(44078) idle
>├─12869 postgres: rhnuser rhnschema 127.0.0.1(44080) idle
>├─12870 postgres: rhnuser rhnschema 127.0.0.1(44082) idle
>├─12871 postgres: rhnuser rhnschema 127.0.0.1(44084) idle
>├─12872 postgres: rhnuser rhnschema 127.0.0.1(44086) idle
>├─12873 postgres: rhnuser rhnschema 127.0.0.1(44088) idle
>├─12874 postgres: rhnuser rhnschema 127.0.0.1(44090) idle
>├─12875 postgres: rhnuser rhnschema 127.0.0.1(44092) idle
>├─12876 postgres: rhnuser rhnschema 127.0.0.1(44094) idle
>├─12877 postgres: rhnuser rhnschema 127.0.0.1(44096) idle
>├─12878 postgres: rhnuser rhnschema 127.0.0.1(44098) idle
>├─12879 postgres: rhnuser rhnschema 127.0.0.1(44100) idle
>├─12880 postgres: rhnuser rhnschema 127.0.0.1(44102) idle
>├─12881 postgres: rhnuser rhnschema 127.0.0.1(44104) idle
>├─12887 postgres: rhnuser rhnschema 127.0.0.1(44106) idle
>├─12888 postgres: rhnuser rhnschema 127.0.0.1(44108) idle
>├─12889 postgres: rhnuser rhnschema 127.0.0.1(44110) idle
>├─12890 postgres: rhnuser rhnschema 127.0.0.1(44112) idle
>├─12891 postgres: rhnuser rhnschema 127.0.0.1(44114) idle
>├─12930 postgres: rhnuser rhnschema 127.0.0.1(44118) idle
>├─12931 postgres: rhnuser rhnschema 127.0.0.1(44120) idle
>├─12941 postgres: rhnuser rhnschema 127.0.0.1(44126) idle
>├─12942 postgres: rhnuser rhnschema 127.0.0.1(44128) idle
>└─12943 postgres: rhnuser rhnschema 127.0.0.1(44130) idle
>
> ● jabberd.service - Jabber Server
>Loaded: loaded (/usr/lib/systemd/system/jabberd.service; enabled;
> vendor preset: disabled)
>Active: active (exited) since Tue 2019-11-05 09:50:14 UTC; 4min 42s ago
> Process: 12486 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
> Main PID: 12486 (code=exited, status=0/SUCCESS)
>CGroup: /system.slice/jabberd.service
>
> ● tomcat.service - Apache Tomcat Web Applicati
