[opensuse] Problems with zypper
To cut down on the amount of emails I have to send if your replied to my first email my responce will be in this one.
What is the zypper version?
Stano My version of zypper is 0.6.15
Hi Adam,
have you updated libzypp today. There was several patches available.
-- Regards, Rajko. I added the update list to smart and it installed a couple of packages for zypper and libzypp but I'm not sure if they are the patches, seeing as I'm still having the same problem
Zypper or one of its' libraries is broken. There are a number of buglist threads open in the buglist mailing lists. One of note is:
https://bugzilla.novell.com/show_bug.cgi?id=297647#c24
If you wipe the SQL database as mentioned in that thread and allow zypper to rebuild it, I have had good results in getting it to work again well enough to allow updates and most normal activities. I see that they are forcing some zypper updates out also so you probably do want to try to fix the database so the update can take effect.
Richard Thanks for the link I will try that out and see if it works for me
On Friday 17 August 2007 09:57:04 am Adam Jimerson wrote:
To cut down on the amount of emails I have to send if your replied to my first email my responce will be in this one.
What is the zypper version?
Stano
My version of zypper is 0.6.15
Hi Adam,
have you updated libzypp today. There was several patches available.
-- Regards, Rajko.
I added the update list to smart and it installed a couple of packages for zypper and libzypp but I'm not sure if they are the patches, seeing as I'm still having the same problem
Zypper or one of its' libraries is broken. There are a number of buglist threads open in the buglist mailing lists. One of note is:
https://bugzilla.novell.com/show_bug.cgi?id=297647#c24
If you wipe the SQL database as mentioned in that thread and allow zypper to rebuild it, I have had good results in getting it to work again well enough to allow updates and most normal activities. I see that they are forcing some zypper updates out also so you probably do want to try to fix the database so the update can take effect.
Richard
Thanks for the link I will try that out and see if it works for me
The only fix I see in https://bugzilla.novell.com/show_bug.cgi?id=297647#c24 is to remove the /var/cache/zypp/zypp.db then run zypper -r, I don't know if that is want you are talking about but for some reason I do not have zypp.db in /var/cache/zypp so there is nothing to remove. Also running zypper -r has no effect because I don't have rug installed on my system so there is nothing for zypper to rebuild itself with.
On Friday 17 August 2007 09:26, Adam Jimerson wrote:
On Friday 17 August 2007 09:57:04 am Adam Jimerson wrote:
To cut down on the amount of emails I have to send if your replied to my first email my responce will be in this one.
What is the zypper version?
Stano
My version of zypper is 0.6.15
have you updated libzypp today. There was several patches available.
I added the update list to smart and it installed a couple of packages for zypper and libzypp but I'm not sure if they are the patches, seeing as I'm still having the same problem
Zypper or one of its' libraries is broken. There are a number of buglist threads open in the buglist mailing lists. One of note is:
https://bugzilla.novell.com/show_bug.cgi?id=297647#c24
If you wipe the SQL database as mentioned in that thread and allow zypper to rebuild it, I have had good results in getting it to work again well enough to allow updates and most normal activities. I see that they are forcing some zypper updates out also so you probably do want to try to fix the database so the update can take effect.
Richard
Thanks for the link I will try that out and see if it works for me
The only fix I see in https://bugzilla.novell.com/show_bug.cgi?id=297647#c24 is to remove the /var/cache/zypp/zypp.db then run zypper -r, I don't know if that is want you are talking about but for some reason I do not have zypp.db in /var/cache/zypp so there is nothing to remove. Also running zypper -r has no effect because I don't have rug installed on my system so there is nothing for zypper to rebuild itself with.
You are running 10.1 or 10.2, and advice was for 10.3 Beta1. Taking the error message: "Unable to create installation source from URL 'http://download.opensuse.org/distribution/10.2/repo/oss'. Details: Bad Media attach point: http://download.opensuse.org/distribution/10.2/repo/oss/" It would be good to see where YaST tried to mount repository. Look in /var/log/YaST2/y2log. For instance: grep attach /var/log/YaST2/y2log should list only lines with string "attach", or: grep \<5\> /var/log/YaST2/y2log will list all critical errors "<5>". Than when you find something interesting look in logs under that time. You may also try again to run YaST and look the end of the log. BTW, your message came without "In-Reply-To" field and it is listed as new message. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 17 August 2007 19:59, Rajko M. wrote: ...
It would be good to see where YaST tried to mount repository. Look in /var/log/YaST2/y2log. ... Just tried google for "Bad Media attach point" (with quotes) and guess what: http://www.tiglo.co.uk/ has a link to: http://www.tiglo.co.uk/technology/linux/yastzypper-bad-media-attach-point.ht...
Though it should be: tail -f /var/log/YaST2/y2log or better tail -f /var/log/YaST2/y2log | grep attach than run in another console yast2 sw_single& and watch in first what is going on. It will be a lot of text, but you can scroll back and look for something like: /var/adm/mount/AP_0x00000001. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 17 August 2007 09:34:05 pm Rajko M. wrote:
On Friday 17 August 2007 19:59, Rajko M. wrote: ...
It would be good to see where YaST tried to mount repository. Look in /var/log/YaST2/y2log.
... Just tried google for "Bad Media attach point" (with quotes) and guess what: http://www.tiglo.co.uk/ has a link to: http://www.tiglo.co.uk/technology/linux/yastzypper-bad-media-attach-point.h tml
Though it should be: tail -f /var/log/YaST2/y2log or better tail -f /var/log/YaST2/y2log | grep attach than run in another console yast2 sw_single& and watch in first what is going on. It will be a lot of text, but you can scroll back and look for something like: /var/adm/mount/AP_0x00000001.
-- Regards, Rajko.
Here is what I get wen I run tail -f /var/log/YaST2/y2long | grep attach 2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-17 10:19:29 <1> SE-02(11253) [media] MediaAccess.cc(close):209 Close: http(http://download.opensuse.org/distribution/10.2/repo/oss/ not attached; localRoot "") (OK) 2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(removeAttachPoint):177 MediaHandler - checking if to remove attach point 2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-17 10:19:29 <1> SE-02(11253) [media] MediaAccess.cc(close):209 Close: cd(cd:///?devices=/dev/sr0,/dev/sr1 not attached; localRoot "") (OK) 2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(removeAttachPoint):177 MediaHandler - checking if to remove attach point 2007-08-18 20:03:00 <1> SE-02(7042) [media] MediaAccess.cc(open):142 Opened: cd(cd:///?devices=/dev/sr0,/dev/sr1 not attached; localRoot "") 2007-08-18 20:04:45 <0> SE-02(7042) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-18 20:04:45 <1> SE-02(7042) [media] MediaAccess.cc(close):209 Close: cd(cd:///?devices=/dev/sr0,/dev/sr1 not attached; localRoot "") (OK) 2007-08-18 20:04:45 <0> SE-02(7042) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-18 20:04:45 <0> SE-02(7042) [media] MediaHandler.cc(removeAttachPoint):177 MediaHandler - checking if to remove attach point I see no meantion of anything that looks like /var/adm/mount/AP_0x00000001.
On Saturday 18 August 2007 08:37:18 pm Adam Jimerson wrote:
On Friday 17 August 2007 09:34:05 pm Rajko M. wrote:
On Friday 17 August 2007 19:59, Rajko M. wrote: ...
It would be good to see where YaST tried to mount repository. Look in /var/log/YaST2/y2log.
... Just tried google for "Bad Media attach point" (with quotes) and guess what: http://www.tiglo.co.uk/ has a link to: http://www.tiglo.co.uk/technology/linux/yastzypper-bad-media-attach-point .h tml
Though it should be: tail -f /var/log/YaST2/y2log or better tail -f /var/log/YaST2/y2log | grep attach than run in another console yast2 sw_single& and watch in first what is going on. It will be a lot of text, but you can scroll back and look for something like: /var/adm/mount/AP_0x00000001. ...
Here is what I get wen I run tail -f /var/log/YaST2/y2log | grep attach
2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-17 10:19:29 <1> SE-02(11253) [media] MediaAccess.cc(close):209 Close: http(http://download.opensuse.org/distribution/10.2/repo/oss/ not attached; localRoot "") (OK) 2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(removeAttachPoint):177 MediaHandler - checking if to remove attach point 2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-17 10:19:29 <1> SE-02(11253) [media] MediaAccess.cc(close):209 Close: cd(cd:///?devices=/dev/sr0,/dev/sr1 not attached; localRoot "") (OK) 2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(removeAttachPoint):177 MediaHandler - checking if to remove attach point 2007-08-18 20:03:00 <1> SE-02(7042) [media] MediaAccess.cc(open):142 Opened: cd(cd:///?devices=/dev/sr0,/dev/sr1 not attached; localRoot "") 2007-08-18 20:04:45 <0> SE-02(7042) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-18 20:04:45 <1> SE-02(7042) [media] MediaAccess.cc(close):209 Close: cd(cd:///?devices=/dev/sr0,/dev/sr1 not attached; localRoot "") (OK) 2007-08-18 20:04:45 <0> SE-02(7042) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-18 20:04:45 <0> SE-02(7042) [media] MediaHandler.cc(removeAttachPoint):177 MediaHandler - checking if to remove attach point
I see no meantion of anything that looks like /var/adm/mount/AP_0x00000001.
After starting tail -f /var/log/YaST2/y2log | grep attach Than you have to start in another console yast2 sw_single that will log messages in /var/log/YaST2/y2log which you can see in first console in real time, thanks to 'tail -f' command. The pipe (vertical line) to grep attach is there only to isolate only lines that contain string 'attach' (it will include for instance reattach, attached, attachment). You can try to isolate only lines that contain string '/var/adm/', or 'AP_0' that would be grep '/var/adm/' /var/log/YaST2/y2log or grep 'AP_0' /var/log/YaST2/y2log What article suggest is to look in /var/adm/mount and remove subdirectories. They should not exist. If YaST ends without problems it will remove subdirectories, if not they will hang in there. The rest is way to search where yast is trying to mount external media. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 18 August 2007 11:28:45 pm Rajko M. wrote:
On Saturday 18 August 2007 08:37:18 pm Adam Jimerson wrote:
On Friday 17 August 2007 09:34:05 pm Rajko M. wrote:
On Friday 17 August 2007 19:59, Rajko M. wrote: ...
It would be good to see where YaST tried to mount repository. Look in /var/log/YaST2/y2log.
... Just tried google for "Bad Media attach point" (with quotes) and guess what: http://www.tiglo.co.uk/ has a link to: http://www.tiglo.co.uk/technology/linux/yastzypper-bad-media-attach-poi nt .h tml
Though it should be: tail -f /var/log/YaST2/y2log or better tail -f /var/log/YaST2/y2log | grep attach than run in another console yast2 sw_single& and watch in first what is going on. It will be a lot of text, but you can scroll back and look for something like: /var/adm/mount/AP_0x00000001.
...
Here is what I get wen I run tail -f /var/log/YaST2/y2log | grep attach
2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-17 10:19:29 <1> SE-02(11253) [media] MediaAccess.cc(close):209 Close: http(http://download.opensuse.org/distribution/10.2/repo/oss/ not attached; localRoot "") (OK) 2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(removeAttachPoint):177 MediaHandler - checking if to remove attach point 2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-17 10:19:29 <1> SE-02(11253) [media] MediaAccess.cc(close):209 Close: cd(cd:///?devices=/dev/sr0,/dev/sr1 not attached; localRoot "") (OK) 2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-17 10:19:29 <0> SE-02(11253) [media] MediaHandler.cc(removeAttachPoint):177 MediaHandler - checking if to remove attach point 2007-08-18 20:03:00 <1> SE-02(7042) [media] MediaAccess.cc(open):142 Opened: cd(cd:///?devices=/dev/sr0,/dev/sr1 not attached; localRoot "") 2007-08-18 20:04:45 <0> SE-02(7042) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-18 20:04:45 <1> SE-02(7042) [media] MediaAccess.cc(close):209 Close: cd(cd:///?devices=/dev/sr0,/dev/sr1 not attached; localRoot "") (OK) 2007-08-18 20:04:45 <0> SE-02(7042) [media] MediaHandler.cc(release):704 Request to release media - not attached; eject 0 2007-08-18 20:04:45 <0> SE-02(7042) [media] MediaHandler.cc(removeAttachPoint):177 MediaHandler - checking if to remove attach point
I see no meantion of anything that looks like /var/adm/mount/AP_0x00000001.
After starting tail -f /var/log/YaST2/y2log | grep attach Than you have to start in another console yast2 sw_single that will log messages in /var/log/YaST2/y2log which you can see in first console in real time, thanks to 'tail -f' command. The pipe (vertical line) to grep attach is there only to isolate only lines that contain string 'attach' (it will include for instance reattach, attached, attachment).
You can try to isolate only lines that contain string '/var/adm/', or 'AP_0' that would be grep '/var/adm/' /var/log/YaST2/y2log or grep 'AP_0' /var/log/YaST2/y2log
What article suggest is to look in /var/adm/mount and remove subdirectories. They should not exist. If YaST ends without problems it will remove subdirectories, if not they will hang in there. The rest is way to search where yast is trying to mount external media.
-- Regards, Rajko. Thanks for the help Rajko, it seemed YaST made subdirectories left and right with in /var/adm/mount, after checking I saw that there was 999 different subdirectories. Now that I removed all of them YaST is accepting URLs again. Which means that fixed my zypper problem. Again thank you for all your help.
participants (2)
-
Adam Jimerson
-
Rajko M.