Bugzilla – Bug 745295
zypper + proxy + patch:OpenSUSE-2011-103-1-noarch
Last modified: 2012-02-06 15:06:33 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 I installed opensuse 12.1 with netinstall. When the system was up i added the community repositories and made an online update (alternative; zypper patch). The patches patch:OpenSUSE-2011-1-2-noarch und patch:OpenSUSE-2011-103-1-noarch were installed. After that nothing was working anymore with zypper or the yast package manager. The error message was something like: Download (curl) error for 'http://download.opensuse.org/update/12.1/repodata/repomd.xml': Error code: Connection failed Error message: Failed to connect to 2001:67c:2178:8::13: Network is unreachable Abort, retry, ignore? [a/r/i/?] (a): Zypper obviously wanted to search an ipv6 address. Neither echo -e "disable-ipv6=true\n" > /root/.aria2c.conf nor export ZYPP_ARIA2C=0 nor using ipv6.disable=1 in a boot option nor switching off ipv6 in yast could make zypper look for ipv4 Any other network tools like wget were still working fine. I am sitting behind a web-proxy. I tried the same things in another network without a proxy, and zypper was doing fine, also with the patch. In that "proxyless" network i downgraded zypper by installing: zypper-log-1.6.16-5.3.1.noarch libzypp-10.3.2-1.1.1.x86_64 zypper-1.6.16-5.3.1.x86_64 Then i went back to the proxy-network, and everything worked. So, something must have happend during the step to zypper-1.6.18 Is there an easy workaround or do i have to wait for the next zypper upgrade? Reproducible: Always Steps to Reproduce: You have to be behind a web-proxy 1. install patch:OpenSUSE-2011-103-1-noarch 2. do e.g. 'zypper ref' Actual Results: zypper and yast package management are not working anymore behind a proxy Expected Results: a month ago, before patch:OpenSUSE-2011-103-1-noarch zypper was still working This issue is also the thread "patch:OpenSUSE-2011-103-1-noarch" in the German lanuage mailinglist opensuse-de@opensuse.org
(In reply to comment #0) > Zypper obviously wanted to search an ipv6 address. Neither > echo -e "disable-ipv6=true\n" > /root/.aria2c.conf > nor > export ZYPP_ARIA2C=0 JFYI: Zypper does not use aria unless you explictly enabled it. It is per defalut based on libcurl. - Please attach the zypper logfile /var/log/zypper.log (or an older /var/log/zypper.log-YYYYMMDD.bz2) that shows the reported behavior. You can execute 'grep main.cc /var/log/zypper.log' (or 'zgrep main.cc /var/log/zypper.log-YYYYMMDD.bz2') to see execution dates and commands the log contains. - Your proxy is configured in /etc/sysconfig/proxy? - Please make sure the package libproxy-tools is installed ,and send the output of `_PX_DEBUG=1 proxy http://download.opensuse.org`
Created attachment 474564 [details] zypper.log Thank you for your help, Michael. zypper.log is in ths attachment. The output of grep main.cc /var/log/zypper.log is : 2012-02-03 14:48:52 <1> 149.217.44.170(19031) [zypper] main.cc(main):75 ===== Hi, me zypper 1.6.16 2012-02-03 14:48:52 <1> 149.217.44.170(19031) [zypper] main.cc(main):76 ===== 'zypper' '--terse' 'tos' '-l' ===== 2012-02-03 14:48:52 <1> 149.217.44.170(19031) [zypper] main.cc(~Bye):60 ===== Exiting main() ===== 2012-02-03 14:48:52 <1> 149.217.44.170(19033) [zypper] main.cc(main):75 ===== Hi, me zypper 1.6.16 2012-02-03 14:48:52 <1> 149.217.44.170(19033) [zypper] main.cc(main):76 ===== 'zypper' '--terse' 'tos' '-l' ===== 2012-02-03 14:48:52 <1> 149.217.44.170(19033) [zypper] main.cc(~Bye):60 ===== Exiting main() ===== 2012-02-03 15:09:37 <1> aida44170(3324) [zypper] main.cc(main):75 ===== Hi, me zypper 1.6.16 2012-02-03 15:09:37 <1> aida44170(3324) [zypper] main.cc(main):76 ===== '/usr/bin/zypper' 'ar' '-f' 'http://download.opensuse.org/repositories/science/openSUSE_12.1/' 'science' ===== 2012-02-03 15:09:38 <1> aida44170(3324) [zypper] main.cc(~Bye):60 ===== Exiting main() ===== 2012-02-03 15:09:38 <1> aida44170(3332) [zypper] main.cc(main):75 ===== Hi, me zypper 1.6.16 2012-02-03 15:09:38 <1> aida44170(3332) [zypper] main.cc(main):76 ===== '/usr/bin/zypper' 'ar' '-f' 'http://download.videolan.org/pub/vlc/SuSE/12.1' 'vlc' ===== 2012-02-03 15:09:38 <1> aida44170(3332) [zypper] main.cc(~Bye):60 ===== Exiting main() ===== 2012-02-03 15:11:54 <1> aida44170(5242) [zypper] main.cc(main):75 ===== Hi, me zypper 1.6.18 2012-02-03 15:11:54 <1> aida44170(5242) [zypper] main.cc(main):76 ===== 'zypper' 'ref' ===== 2012-02-06 14:36:21 <1> aida44170(2723) [zypper] main.cc(main):75 ===== Hi, me zypper 1.6.18 2012-02-06 14:36:21 <1> aida44170(2723) [zypper] main.cc(main):76 ===== 'zypper' 'ref' ===== 2012-02-06 14:41:31 <1> aida44170(3533) [zypper] main.cc(main):75 ===== Hi, me zypper 1.6.18 2012-02-06 14:41:31 <1> aida44170(3533) [zypper] main.cc(main):76 ===== 'zypper' 'ref' ===== Yes, the proxy is configured in /etc/sysconfig/proxy. Additionally in the environment variables http_proxy and ftp_proxy The output of _PX_DEBUG=1 proxy http://download.opensuse.org is: Using config: 20kde_config_extension Using ignore: Config is: direct:// direct://
> The output of _PX_DEBUG=1 proxy http://download.opensuse.org is: > > Using config: 20kde_config_extension There is a difference in using "su" or "su -" to create the root shell launching zypper. In the first case the user environment is preserved and libproxy sees you are in a kde/gnome session and thus uses the kde/gnome configuration. If you do "su -" you have a root login shell, and libproxy reads and prefers the configuration from /etc/sysconfig/proxy (which is what YaST writes). You can test this using _PX_DEBUG=1 proxy for both cases. *** This bug has been marked as a duplicate of bug 732886 ***
only "su": Using config: 20kde_config_extension Using ignore: Config is: direct:// direct:// with "su -": Using config: 26sysconfig_config_extension Using ignore: Config is: http://web-proxy.mpia-hd.mpg.de:3128 http://web-proxy.mpia-hd.mpg.de:3128 and now 'zypper ref' works in the "su -" shell. Ok - I never tested the console (alt-cntrl -F1): there 'zypper ref' works as well. Now the question is: How can I make kde/gnome config see the proxy - or: why did it work up to zypper 1.6.16?
Due to a bug ;( In our build system libzypp failed to detect libproxy, so it felt back to always reading /etc/sysconfig. This works for your setup, but has other drawbacks. We'll try to fix zypper to ignore the missing desktop settings and use environment or /etc/sysconfig. Until this is done, using 'su -' is the recommended workaround.
Thank you for the hints. 'su -' is doing it. As well as setting the proxy in the kde systemsettings. I can live with these workarounds until the next fix. Thanks again for all your help