Can not get update SuSe 11 SP2

SUSE Linux Enterprise Server SLES Updates
1

Hello!

Please help me.

I can not get update for SuSe 11 SP2
I try configure online from yast and from command line

But zypper not use my proxy settings and I receive error

# zypper refresh-services -r
Download (curl) error for 'https://nu.novell.com//repo/repoindex.xml?credentials=NCCcredentials':
Error code: Connection failed
Error message: couldn't connect to host

register was ok

suse_register -n -a email=qqq@gmail.com -a regcode-sles=qqq -a moniker=qqq -L /tmp/suse_register.log
Registration finished successfully

I configure proxy from yast.

# set |grep proxy ftp_proxy=http://10.200.5.5:3128 http_proxy=http://10.200.5.5:3128 https_proxy=http://10.200.5.5:3128 

# cat /etc/sysconfig/proxy |grep -v "#"
PROXY_ENABLED="yes"
HTTP_PROXY="http://10.200.5.5:3128"
HTTPS_PROXY="http://10.200.5.5:3128"
FTP_PROXY="http://10.200.5.5:3128"
GOPHER_PROXY=""
NO_PROXY="localhost, 127.0.0.1"

I see zypper log and found that zypper not read /etc/sysconfig/proxy

/var/log/zypper.log

2012-06-22 08:29:00 <1> lnx-tst107(9877) [zypp++] MediaCurl.cc(setupEasy):564 Proxy: -none-
2

There are some other bits required;

Your proxy should should accept Novell domain (or at least selected
sites used like nu.novell.com and secure.novell.com) without
authentication.

You need to add two lines with your proxy information to /etc/profile,
for example:

export http_proxy="http://10.10.1.1:8081/"
export https_proxy="https://10.10.1.1:8081/"

You also need to add in /root/.curlrc

–
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.31-0.9-default
up 8:05, 2 users, load average: 0.94, 0.85, 0.81
GPU GeForce 8600 GTS Silent - Driver Version: 302.11

3

Thanks for reply.

I have proxy without authentication.
I try you recommendation without success
zypper never use proxy :frowning:

# grep proxy /etc/profile
export http_proxy="http://10.200.5.5:3128/"
export https_proxy="http://10.200.5.5:3128/"
# cat .curlrc 
# Changed by YaST2 module proxy 06/22/2012
--proxy "http://10.200.5.5:3128"
4

Hi Alex,

[CODE]# man zypper
[…]
Repository Management
Zypper is able to work with YaST, RPM-MD (yum) software repositories, and plain directories containing .rpm files.

   Repositories are primarily identified using their URI or alias.  Alias serves as a shorthand for the long URI or name of the repository.  The name of the repository should briefly describe the repository and is shown to the user in tables and messages. The name is not required, and if not known,  the
   alias is shown instead. The alias is required and uniquely identifies the repository on the system.

   The alias, name, URI, or the number from zypper repos list can be used to specify a repository as an argument of various zypper commands and options like refresh, --repo, or --from.

   Supported URI formats:

   CD or DVD drive
          Optionally with devices list for probing.

          cd:///
          dvd:/subdir?devices=/dev/sr0,/dev/sr1

   FTP/HTTP/HTTPS directory tree
          The ftp URL scheme supports absolute and relative paths to the default ftp server directory (RFC1738, Section 3.2.2). To use an absolute path, you have to prepend the path with an additional slash, what results in a "/%2f" combination (second "/" encoded to "%2f") at the begin of the URL path.
          This is important, especially in user authenticated ftp, where the users home is usually the default directory of the server (except when the server chroots into the users home directory).

          [B]Explicit proxy settings may be passed via optional parameters proxy, proxyport, proxyuser and proxypass.[/B]

          HTTP authentication methods to use can be defined as comma separated list via optional parameter auth. Valid methods are e.g. 'basic', 'digest', 'ntlm', 'negotiate'. Note, that this list depends on the list of methods supported by the curl library.

          ftp://user:pass@server/path/to/media/dir
          ftp://user:pass@server/%2fhome/user/path/to/media/dir
          http://user:pass@server/path
          https://user:pass@server/path?[B]proxy=foo[/B]&proxyuser=me&proxypass=pw

[…]
[/CODE]

Maybe that helps?

Regards,
Jens

5

big thanks!
It`s work!
I add proxy parameter to /etc/zypp/services.d/nu_novell_com.service

# cat /etc/zypp/services.d/nu_novell_com.service
  url = https://nu.novell.com/?credentials=NCCcredentials&proxy=http://myproxy:3128