|
Bugzilla – Full Text Bug Listing |
| Summary: | Resolvable id 638433 does not exist. | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Andreas Jaeger <aj> |
| Component: | Zenworks | Assignee: | Rashmi Ranjan Mohanty <rashmiranjan.mohanty> |
| Status: | RESOLVED FIXED | QA Contact: | Mauro Parra Miranda <mauro> |
| Severity: | Critical | ||
| Priority: | P1 - Urgent | CC: | aj, andreas.hanke, giulio.alfano, meissner, mmeeks, schubi, simon.strandman, suse-beta |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
/var/log/zmd-messages.log
/var/log/zmd-backend.log zmd.db when receiving Resolvable id 740609 does not exist. |
||
|
Description
Andreas Jaeger
2006-08-16 18:37:10 UTC
Created attachment 96280 [details]
/var/log/zmd-messages.log
Created attachment 96281 [details]
/var/log/zmd-backend.log
Assigning to Tambet to take a look. It seems like a zypp bug from outset. The message comes from libzypp-backend and means either that zmd asked zypp to do something while referencing a resolvable by invalid id or zypp backend had trouble finding it. Without zmd.db taken right after it happened we'll never know. I don't have zmd.db from that time, sorry. Andreas, can you then please provide any steps to reproduce the problem? I cannot any more. Let's mark it as invalid. If I reproduce it, I'll give more details... This bug is NOT invalid. I get this too occasionally. Now I can't update or install anything. Just waiting a cuple of hours and rebooting will probably solve it temporary.
simon:~ # rug refresh
Refreshing Services...
100%
Successfully refreshed.
simon:~ # rug install kdebase3-kdm
Resolving Dependencies...
ERROR: Dependency resolution failed:
Resolvable id 170659 does not exist.
simon:~ # rug install kdebase3-kdm
Resolving Dependencies...
ERROR: Dependency resolution failed:
Resolvable id 170659 does not exist.
simon:~ # rug update
Resolving Dependencies...
ERROR: Dependency resolution failed:
Resolvable id 170628 does not exist.
I forgot to mention that this is a newly installed OpenSuse 10.1 i586 system with the latest updates. rm -rf /var/tmp/* && rczmd restart && rug refresh works around the problem. I'm not sure how to reproduce it though. It seems to happen randomly. Reopening bug and changing product to opensuse 10.1. The bug was marked invalid because noone who experiences this wants to attach his zmd.db - it's well known that this is still occuring! Next time it happens, don't do "rm -rf", but save and compress your /var/lib/zmd/zmd.db and upload it here - see comment 5 Ok, I just got this error again on another computer. This time I´ve got all the files in /var/tmp and zmd.db. The problem is that my zmd.db is 70MB bzip2ed (378MB uncompressed) and I guess that´s too large to attatch here? I think this bug came with the lates updates to zmd because I don´t remember ever having it before. Created attachment 99969 [details]
zmd.db when receiving Resolvable id 740609 does not exist.
I receive the message, when I try to update with
Resolvable id 740609 does not exist.
If you need something else let me know. Many thanks. As per Tambet's comment #5, it seems to be coming from the helper. Assigning to Duncan. This Sorry for the last message, I hit commit to soon. This is also happening quite often on SLED 10 as well. I really think that it is a caching issue with the old ID's. If a person restarts zmd then the error will go away. fixed on 10.2. Patch for 10.1 ? How intrusive the change is? Which packages need an update? Federico? I get this problem all the time in SLES 10 and SLED 10 when installing dependent packages one at a time via nautilus using the left click "Install Software" method. This bug combined with the lack of a graphical method to select multiple packages in a directory for installation makes installing packages from outside sources a real pain in the neck. Using the rug mount command is a work around but if I miss a dependent file in the rug mounted directory and then fix it, I tend to get the "Resolvable id # does not exist message" on the second attempt. Reassign to Chris in order to get more info about which packages should be added for the 10.1 patch. (In reply to comment #0) > with the latest released 10.1 package management stack I just got while running > an update with zen-updater the message "Resolvable id 638433 does not exist." > I get the same, but with "Resolvable id 740662 does not exist". I was able to clear it by switching to run level 1 and back to 5. We need to make sure this goes in for SLED10-SP1 as well. ALready checked into SLED10-SP1 branch.. Can be checked in SLE 10 SP1 Beta3 *** Bug 212201 has been marked as a duplicate of this bug. *** *** Bug 243780 has been marked as a duplicate of this bug. *** |