SUSE Manager spacewalk-repo-sync is failing with database lock error
This document (7016242) is provided subject to the disclaimer at the end of this document.
SUSE Manager 1.7
[Thread-6613] ERROR com.redhat.rhn.taskomatic.task.RepoSyncTask -
(process:15994): GLib-CRITICAL **: g_timer_stop: assertion `timer != NULL' failed
(process:15994): GLib-CRITICAL **: g_timer_destroy: assertion `timer != NULL' failed
Traceback (most recent call last):
File "/usr/lib64/python2.6/site-packages/spacewalk/satellite_tools/reposync.py", line 167, in sync
self.import_packages(repo, data['id'], data['source_url'])
File "/usr/lib64/python2.6/site-packages/spacewalk/satellite_tools/reposync.py", line 842, in import_packages
packages = plug.list_packages(filters)
File "/usr/lib64/python2.6/site-packages/spacewalk/satellite_tools/repo_plugins/yum_src.py", line 185, in list_packages
self.sack.populate(self.repo, 'metadata', None, 0)
File "/usr/lib64/python2.6/site-packages/yum/yumRepo.py", line 186, in populate
dobj = repo_cache_function(xml, csum)
File "/usr/lib64/python2.6/site-packages/sqlitecachec.py", line 42, in getPrimary
2015/02/20 16:02:20 | TypeError: Can not create db_info table: database is locked
Do not send byte range lock requests to the server. This is necessary for certain applications that break with cifs style mandatory byte range locks (and most cifs servers do not yet support requesting advisory byte range locks).
The other option would be to not put /var/cache/ on CIFS.
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7016242
- Creation Date: 26-Feb-2015
- Modified Date:03-Mar-2020
- SUSE Manager
For questions or concerns with the SUSE Knowledgebase please contact: email@example.com