in our master-slave setup, syncing channels fails for some channels with the following error:
+++ sending log as an email +++
SYNC ERROR: unhandled exception occurred:
(Check logs/email for potentially more detail)
EOFError()
After removing /var/cache/rhn/satsync/* it succeeds.
Case closed ? Saldy no.
Now other channels (that did work before) fail with the following error:
Importing: +++ sending log as an email +++
SYNC ERROR: unhandled exception occurred:
(Check logs/email for potentially more detail)
UnicodeDecodeError('ascii', 'ERROR: Encountered IntegrityError: \
FEHLER: doppelter Schl\\xc3\\xbcsselwert verletzt Unique-Constraint \\xc2\\xbbrhn_package_id_pk\\xc2\\xab\
DETAIL: Schl\\xc3\\xbcssel \\xc2\\xbb(id)=(36931)\\xc2\\xab existiert bereits.\
\
consider removing satellite-sync cache at /var/cache/rhn/satsync/* and re-run satellite-sync with same options.\
If this error persits after removing cache, please contact Red Hat support.', 59, 60, 'ordinal not in range(128)')
'ascii' codec can't decode byte 0xc3 in position 59: ordinal not in range(128)
It does not help to remove /var/cache/rhn/satsync/* again
The error message is partly in german. It says: Duplicate key word violates Unique-Constraint rhn_package_id. Key (id)=(36931) already exists.
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:
Visit http://www.suse.com/support and search the knowledgebase and/or check all
the other support options available.
If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot…
after playing around with deleting channels and satsync cache I was able to sync all custom and suse channels!
That worked for about 3 days (1 complete sync for all channels per day).
Now it stopped working again.
I get this error on custom channels:
[CODE]+++ sending log as an email +++
SYNC ERROR:
(Check logs/email for potentially more detail)
RhnSyncException(’
Error Message:
The requested channel version does not match the upstream version
Error Class Code: 3013
Error Class Info: Invalid channel version
',)
Error Message:
The requested channel version does not match the upstream version
Error Class Code: 3013
Error Class Info: Invalid channel version
[/CODE]
and this error on suse channels:
2019-02-18 05:10:57,185 [DefaultQuartzScheduler_Worker-15] ERROR com.redhat.rhn.taskomatic.task.MgrSyncRefresh - Executing a task threw an exception: org.quartz.JobExecutionException
2019-02-18 05:10:57,185 [DefaultQuartzScheduler_Worker-15] ERROR com.redhat.rhn.taskomatic.task.MgrSyncRefresh - Message: Command '[/usr/bin/mgr-inter-sync]' exited with error code 137
2019-02-18 05:10:57,185 [DefaultQuartzScheduler_Worker-15] ERROR com.redhat.rhn.taskomatic.task.MgrSyncRefresh - Cause: null
2019-02-18 05:10:57,185 [DefaultQuartzScheduler_Worker-15] ERROR com.redhat.rhn.taskomatic.task.MgrSyncRefresh - Stack trace:org.quartz.JobExecutionException: Command '[/usr/bin/mgr-inter-sync]' exited with error code 137
at com.redhat.rhn.taskomatic.task.RhnJavaJob.executeExtCmd(RhnJavaJob.java:111)
at com.redhat.rhn.taskomatic.task.MgrSyncRefresh.execute(MgrSyncRefresh.java:80)
at com.redhat.rhn.taskomatic.task.RhnJavaJob.execute(RhnJavaJob.java:88)
at com.redhat.rhn.taskomatic.TaskoJob.execute(TaskoJob.java:199)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)
IIRC the SUSE Manager license includes support per default. Your best approach therefore might be to open a service request and have SUSE Support have a closer look at this.
in case you’re not going the “service request” route:
which version of SUSE Manager are you running on master and slave? Are both at the same level? Are you already on 3.2.4?
Having had a look at the Spacewalk code available on the net, I see that “The requested channel version does not match the upstream version” is the result of channel time stamp mismatches (last_modified != db_last_modified). I have not checked if these time stamps are dependent on the local clock of the satellite (I don’t believe they are), but could you please check that the system times are in sync, for good measure?
If you set debug to at least level three, you should find information on the time stamps found in the debug log. Maybe that gives a hint on the root cause.
thank you for your advice!
Opening a service request is still a viable option, and makes totally sense!
In posting my problem here I had the idea of getting quick advice like yours. Thanks again.
In fact I just saw ntp daemon is not running, although time is running correctly here, but you never know …
I’m still looking into that problem, but it’s confusing … cause today all channels synced successfully … whereas yesterday there were many errors …
If those errors pop up again then I will open an SR!
