Update Process Using Curl is Accessing an Unconfigured Proxy Server

This document (7006744) is provided subject to the disclaimer at the end of this document.

Environment

Novell Open Enterprise Server 2 (OES 2) Linux
SUSE Linux Enterprise Server 11
SUSE Linux Enterprise Server 10
Proxy

Situation

No proxy is configured in /etc/sysconfig/proxy, but the update server still attempts to connect to a proxy server.
The supportconfig updates.txt file shows the following:
 
#==[ Command ]======================================#
# /usr/bin/curl --verbose --capath /etc/ssl/certs/ --digest --remote-time --fail -u 8f8474ba163758acd332835bdc0ae9b0:fe81fa65746cd66f6d8d74135d1f63ab -O "https://nu.novell.com/repo/repoindex.xml" 2>curl.log
* About to connect() to proxy 192.168.145.2 port 8081
*   Trying 192.168.145.2... Connection refused
* couldn't connect to host
* Closing connection #0
 
curl: (7) couldn't connect to host
 
#==[ Command ]======================================#
# env | grep -i proxy
http_proxy=http://192.168.145.2:8081
https_proxy=https://192.168.145.2:8081
 
#==[ Configuration File ]===========================#
# /etc/sysconfig/proxy
PROXY_ENABLED="no"
HTTP_PROXY=""
HTTPS_PROXY=""
FTP_PROXY=""
GOPHER_PROXY=""
NO_PROXY="localhost, 127.0.0.1"

Resolution

The update process uses curl. Even though the proxy server is not configured in /etc/sysconfig/proxy, the update process uses curl. Curl will use the proxy defined by the environment variables http_proxy and https_proxy. If http_proxy or more importantly https_proxy is defined, a proxy is configured as far as curl is concerned; regardless of the /etc/sysconfig/proxy settings.
 
1. Try to log out and log back in as root, then run echo $https_proxy to see if the variable has been cleared.
2. If it has not been cleared, you will need to check your environment files to see if those variables have been manually configured.
3. If you cannot find the variables manually configured in an environment configuration file, try rebooting the server to see if the variables have been cleared.
4. If they still have not been cleared, the variables are being set in a configuration file you have not thought to look at yet. Keep looking until you find where they have been set. 
 
Some environment files to search include, but are not limited to:
 
/etc/profile
/etc/profile.local
/etc/profile.d/*
/etc/bash.bashrc
~/.profile
~/.bashrc
~/.curlrc

Disclaimer

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:7006744
  • Creation Date: 27-Aug-2010
  • Modified Date:03-Mar-2020
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center