Hi
I've been seeing email warnings since upgrading to Uyuni latest over the past couple of weeks.
Taskomatic bunch update-payg-data-bunch was scheduled to run within the update-payg-default schedule.
Subtask update-payg-hosts failed.
For more information check null.
And then ten minutes later, at the next run, a second email with Subtask update-payg-hosts finished successfully and is back to normal.
These occur every day or two, always early in the morning (0130 or 0220), and there have been some other taskomatic emails referencing things other than payg-hosts.
Prior to this version, I'd only ever see these emails for repo errors.
rhn_taskomatic_daemon.log has a few entries like
* 2022-04-03 16:20:00,562 [Thread-6531] ERROR com.redhat.rhn.taskomatic.task.payg.PaygUpdateHostsTask - p11-kit: couldn't create symlink: /var/lib/ca-certificates/openssl/dbc54cab.0: File exists * 2022-05-10 02:10:00,996 [DefaultQuartzScheduler_Worker-3] ERROR com.redhat.rhn.taskomatic.task.payg.PaygUpdateHostsTask - Message: Command '[/usr/share/rhn/certs/update-ca-cert-trust.sh]' exited with error code 1: p11-kit: couldn't complete writing of file: /var/lib/ca-certificates/ca-bundle.pem.tmp: File exists
The first file exists when I check, the second does not. If I run /usr/share/rhn/certs/update-ca-cert-trust.sh manually, it completes without error. It's like the same task is being run twice concurrently but I don't know how to check; there's no duplicates in Uyuni -> Admin -> Task schedules.
Obviously not a major issue as it's apparently self-healing, but I don't want to get into the habit of ignoring emails from Uyuni so would like to get to the bottom of it.
Any ideas?
Simon Avery Linux Systems Administrator: ATASS Sports Oxygen House | Grenadier Road, Exeter Business Park | EX1 3LH
t: 01392 440 400 e: simon.avery@atass-sports.co.ukmailto:simon.avery@atass-sports.co.uk
Follow us on Twitter: @atassSportshttps://twitter.com/atassSports
NOTICE This email and any attachments confidential and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. Please notify the sender immediately. ATASS Ltd is incorporated in England and Wales with company number 04807405. See our website for further details and our privacy policy
Hi Simon,
we got the same behavior at our setup… would be nice to solve that!
Regards Oliver
Von: Simon Avery Simon.Avery@atass-sports.co.uk Datum: Dienstag, 10. Mai 2022 um 09:56 An: uyuni-users@opensuse.org uyuni-users@opensuse.org Betreff: Taskomatic errors since 2022.4 Hi
I’ve been seeing email warnings since upgrading to Uyuni latest over the past couple of weeks.
Taskomatic bunch update-payg-data-bunch was scheduled to run within the update-payg-default schedule.
Subtask update-payg-hosts failed.
For more information check null.
And then ten minutes later, at the next run, a second email with Subtask update-payg-hosts finished successfully and is back to normal.
These occur every day or two, always early in the morning (0130 or 0220), and there have been some other taskomatic emails referencing things other than payg-hosts.
Prior to this version, I’d only ever see these emails for repo errors.
rhn_taskomatic_daemon.log has a few entries like
* 2022-04-03 16:20:00,562 [Thread-6531] ERROR com.redhat.rhn.taskomatic.task.payg.PaygUpdateHostsTask - p11-kit: couldn't create symlink: /var/lib/ca-certificates/openssl/dbc54cab.0: File exists * 2022-05-10 02:10:00,996 [DefaultQuartzScheduler_Worker-3] ERROR com.redhat.rhn.taskomatic.task.payg.PaygUpdateHostsTask - Message: Command '[/usr/share/rhn/certs/update-ca-cert-trust.sh]' exited with error code 1: p11-kit: couldn't complete writing of file: /var/lib/ca-certificates/ca-bundle.pem.tmp: File exists
The first file exists when I check, the second does not. If I run /usr/share/rhn/certs/update-ca-cert-trust.sh manually, it completes without error. It’s like the same task is being run twice concurrently but I don’t know how to check; there’s no duplicates in Uyuni -> Admin -> Task schedules.
Obviously not a major issue as it’s apparently self-healing, but I don’t want to get into the habit of ignoring emails from Uyuni so would like to get to the bottom of it.
Any ideas?
Simon Avery Linux Systems Administrator: ATASS Sports Oxygen House | Grenadier Road, Exeter Business Park | EX1 3LH
t: 01392 440 400 e: simon.avery@atass-sports.co.ukmailto:simon.avery@atass-sports.co.uk
NOTICE This email and any attachments confidential and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. Please notify the sender immediately. ATASS Ltd is incorporated in England and Wales with company number 04807405. See our website for further details and our privacy policy
SWM INTERN
Hey all,
Thanks for the report. I have created and issue [1] and I'm planning to work on this one in the next days.
Cheers
[1]https://github.com/uyuni-project/uyuni/issues/5400
On 5/10/22 09:20, Musco.Oliver IT-IF-IP-WP wrote:
Hi Simon,
we got the same behavior at our setup… would be nice to solve that!
Regards
Oliver
*Von: *Simon Avery Simon.Avery@atass-sports.co.uk *Datum: *Dienstag, 10. Mai 2022 um 09:56 *An: *uyuni-users@opensuse.org uyuni-users@opensuse.org *Betreff: *Taskomatic errors since 2022.4
Hi
I’ve been seeing email warnings since upgrading to Uyuni latest over the past couple of weeks.
/Taskomatic bunch update-payg-data-bunch was scheduled to run within the update-payg-default schedule./
//
/Subtask update-payg-hosts failed./
//
/For more information check null./
And then ten minutes later, at the next run, a second email with /Subtask update-payg-hosts finished successfully and is back to normal./
//
These occur every day or two, always early in the morning (0130 or 0220), and there have been some other taskomatic emails referencing things other than payg-hosts.
Prior to this version, I’d only ever see these emails for repo errors.
rhn_taskomatic_daemon.log has a few entries like
- 2022-04-03 16:20:00,562 [Thread-6531] ERROR com.redhat.rhn.taskomatic.task.payg.PaygUpdateHostsTask - p11-kit: couldn't create symlink: /var/lib/ca-certificates/openssl/dbc54cab.0: File exists
- 2022-05-10 02:10:00,996 [DefaultQuartzScheduler_Worker-3] ERROR com.redhat.rhn.taskomatic.task.payg.PaygUpdateHostsTask - Message: Command '[/usr/share/rhn/certs/update-ca-cert-trust.sh]' exited with error code 1: p11-kit: couldn't complete writing of file: /var/lib/ca-certificates/ca-bundle.pem.tmp: File exists
The first file exists when I check, the second does not. If I run /usr/share/rhn/certs/update-ca-cert-trust.sh manually, it completes without error. It’s like the same task is being run twice concurrently but I don’t know how to check; there’s no duplicates in Uyuni -> Admin -> Task schedules.
Obviously not a major issue as it’s apparently self-healing, but I don’t want to get into the habit of ignoring emails from Uyuni so would like to get to the bottom of it.
Any ideas?
*Simon Avery*
*Linux Systems Administrator: ATASS Sports*
Oxygen House |Grenadier Road, Exeter Business Park | EX1 3LH
t:*01392 440 400
*e:*simon.avery@atass-sports.co.uk mailto:simon.avery@atass-sports.co.uk
*NOTICE* This email and any attachments confidential and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. Please notify the sender immediately. ATASS Ltd is incorporated in England and Wales with company number 04807405. See our website for further details and our privacy policy
SWM INTERN
Thank you, Ricardo. Much appreciated.
-----Original Message----- From: Ricardo Mateus rdiasmateus@suse.de Sent: 10 May 2022 10:22 To: General discussion related to the openSUSE Uyuni project users@lists.uyuni-project.org; Musco.Oliver IT-IF-IP-WP Musco.Oliver@swm.de; uyuni-users@opensuse.org Subject: [EXTERNAL EMAIL] Re: AW: Taskomatic errors since 2022.4
[You don't often get email from rdiasmateus@suse.de. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification.]
Hey all,
Thanks for the report. I have created and issue [1] and I'm planning to work on this one in the next days.
Cheers
[1]https://github.com/uyuni-project/uyuni/issues/5400
On 5/10/22 09:20, Musco.Oliver IT-IF-IP-WP wrote:
Hi Simon,
we got the same behavior at our setup… would be nice to solve that!
Regards
Oliver
*Von: *Simon Avery Simon.Avery@atass-sports.co.uk *Datum: *Dienstag, 10. Mai 2022 um 09:56 *An: *uyuni-users@opensuse.org uyuni-users@opensuse.org *Betreff: *Taskomatic errors since 2022.4
Hi
I’ve been seeing email warnings since upgrading to Uyuni latest over the past couple of weeks.
/Taskomatic bunch update-payg-data-bunch was scheduled to run within the update-payg-default schedule./
//
/Subtask update-payg-hosts failed./
//
/For more information check null./
And then ten minutes later, at the next run, a second email with /Subtask update-payg-hosts finished successfully and is back to normal./
//
These occur every day or two, always early in the morning (0130 or 0220), and there have been some other taskomatic emails referencing things other than payg-hosts.
Prior to this version, I’d only ever see these emails for repo errors.
rhn_taskomatic_daemon.log has a few entries like
- 2022-04-03 16:20:00,562 [Thread-6531] ERROR com.redhat.rhn.taskomatic.task.payg.PaygUpdateHostsTask - p11-kit: couldn't create symlink: /var/lib/ca-certificates/openssl/dbc54cab.0: File exists
- 2022-05-10 02:10:00,996 [DefaultQuartzScheduler_Worker-3] ERROR com.redhat.rhn.taskomatic.task.payg.PaygUpdateHostsTask - Message: Command '[/usr/share/rhn/certs/update-ca-cert-trust.sh]' exited with error code 1: p11-kit: couldn't complete writing of file: /var/lib/ca-certificates/ca-bundle.pem.tmp: File exists
The first file exists when I check, the second does not. If I run /usr/share/rhn/certs/update-ca-cert-trust.sh manually, it completes without error. It’s like the same task is being run twice concurrently but I don’t know how to check; there’s no duplicates in Uyuni -> Admin -> Task schedules.
Obviously not a major issue as it’s apparently self-healing, but I don’t want to get into the habit of ignoring emails from Uyuni so would like to get to the bottom of it.
Any ideas?
*Simon Avery*
*Linux Systems Administrator: ATASS Sports*
Oxygen House |Grenadier Road, Exeter Business Park | EX1 3LH
t:*01392 440 400
*e:*simon.avery@atass-sports.co.uk mailto:simon.avery@atass-sports.co.uk
*NOTICE* This email and any attachments confidential and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. Please notify the sender immediately. ATASS Ltd is incorporated in England and Wales with company number 04807405. See our website for further details and our privacy policy
SWM INTERN
-- Ricardo Mateus SUSE Manager Development Team
-
Musco.Oliver IT-IF-IP-WP -
Ricardo Mateus -
Simon Avery