cumulus user vs root when using apt-get update command in VX 3.1.1


Userlevel 1
Has anyone had an issue with running 'apt-get update' when not logged in as root while using the sudo command? Thanks.
cumulus@cumulus:~$ sudo apt-get update
[sudo] password for cumulus:
Err http://repo3.cumulusnetworks.com CumulusLinux-3 Release.gpg
Could not resolve 'repo3.cumulusnetworks.com'
Err http://repo3.cumulusnetworks.com CumulusLinux-3-security-updates Release.gpg
Could not resolve 'repo3.cumulusnetworks.com'
...truncated
root@cumulus:~# apt-get update
Get:1 http://repo3.cumulusnetworks.com CumulusLinux-3 InRelease [7,648 B]
Get:2 http://repo3.cumulusnetworks.com CumulusLinux-3-security-updates InRelease [7,600 B]
Get:3 http://repo3.cumulusnetworks.com CumulusLinux-3-updates InRelease [7,681 B]
...truncated

6 replies

Userlevel 2
update worked for me with VX 3.2

cumulus@leaf01:/usr/share/snmp/mibs$ sudo apt-get update Hit http://repo3.cumulusnetworks.com CumulusLinux-3 InRelease Hit http://repo3.cumulusnetworks.com CumulusLinux-3-security-updates InRelease Hit http://repo3.cumulusnetworks.com CumulusLinux-3-updates InRelease Hit http://repo3.cumulusnetworks.com CumulusLinux-3/cumulus Sources Hit http://repo3.cumulusnetworks.com CumulusLinux-3/upstream Sources Hit http://repo3.cumulusnetworks.com CumulusLinux-3/cumulus amd64 Packages Hit http://repo3.cumulusnetworks.com CumulusLinux-3/upstream amd64 Packages Hit http://repo3.cumulusnetworks.com CumulusLinux-3-security-updates/cumulus Sources Hit http://repo3.cumulusnetworks.com CumulusLinux-3-security-updates/upstream Sources Hit http://repo3.cumulusnetworks.com CumulusLinux-3-security-updates/cumulus amd64 Packages Hit http://repo3.cumulusnetworks.com CumulusLinux-3-security-updates/upstream amd64 Packages Hit http://repo3.cumulusnetworks.com CumulusLinux-3-updates/cumulus Sources Hit http://repo3.cumulusnetworks.com CumulusLinux-3-updates/upstream Sources Hit http://repo3.cumulusnetworks.com CumulusLinux-3-updates/cumulus amd64 Packages Hit http://repo3.cumulusnetworks.com CumulusLinux-3-updates/upstream amd64 Packages Ign http://repo3.cumulusnetworks.com CumulusLinux-3/cumulus Translation-en_US Ign http://repo3.cumulusnetworks.com CumulusLinux-3/cumulus Translation-en Ign http://repo3.cumulusnetworks.com CumulusLinux-3/upstream Translation-en_US Ign http://repo3.cumulusnetworks.com CumulusLinux-3/upstream Translation-en Ign http://repo3.cumulusnetworks.com CumulusLinux-3-security-updates/cumulus Translation-en_US Ign http://repo3.cumulusnetworks.com CumulusLinux-3-security-updates/cumulus Translation-en Ign http://repo3.cumulusnetworks.com CumulusLinux-3-security-updates/upstream Translation-en_US Ign http://repo3.cumulusnetworks.com CumulusLinux-3-security-updates/upstream Translation-en Ign http://repo3.cumulusnetworks.com CumulusLinux-3-updates/cumulus Translation-en_US Ign http://repo3.cumulusnetworks.com CumulusLinux-3-updates/cumulus Translation-en Ign http://repo3.cumulusnetworks.com CumulusLinux-3-updates/upstream Translation-en_US Ign http://repo3.cumulusnetworks.com CumulusLinux-3-updates/upstream Translation-en Reading package lists... Done
Userlevel 4
You aren't using a proxy here by any chance are you?
Userlevel 1
Eric Pulvino wrote:

You aren't using a proxy here by any chance are you?

Yes, I am using a proxy.
Userlevel 1
Kevin Witherstine wrote:

update worked for me with VX 3.2

cumulus@leaf01:/usr/share/snmp/mibs$ sudo apt-get update Hit [...

I guess it's time for me to upgrade to VX 3.2...thanks Kevin!
Userlevel 3
Kevin Witherstine wrote:

update worked for me with VX 3.2

cumulus@leaf01:/usr/share/snmp/mibs$ sudo apt-get update Hit [...

This isn't an issue that 3.2 fixes, almost certainly. If you are using a proxy, then sudo in 3.1 and beyond won't pass the proxy env variables through by default, because it's a security issue.

If it's not a proxy, it's likely something else in your user environment that isn't making it through sudo. Many env variables aren't passed through by default (again, because they can cause security issues).

Upgrading to 3.2 is a good idea anyway, lots of bug fixes, but I doubt it will help this issue. Running 'env' before and after the sudo(by running something like:
env > normal
sudo env > su.env
diff normal su.env
is most likely going to point to the cause of the problem.

Userlevel 4
Eric Pulvino wrote:

You aren't using a proxy here by any chance are you?

Read Dave's response below. Seems like the proxy is not setup correctly. I say that because the root account is probably NOT using the proxy and it appears to work. How are you configuring your proxy?

Reply