Re: [Linux-PowerEdge] dsu and http (not https)
[EXTERNAL EMAIL] It looks like I made an incorrect assumption. The DSU installation already *is* using HTTP URLs. I guess I'd better go dig into the logs again, to figure out why it broke when I was updating a few hundred of them at once. Lloyd On 7/28/20 8:59 AM, Lloyd Brown wrote: > [EXTERNAL EMAIL] > > Is there an easy way to get DSU tools to pull files from linux.dell.com > via HTTP, instead of HTTPS? > > We're trying to use a squid caching proxy, rather than creating our own > local mirror. But while something like squid can proxy the HTTPS > traffic via a CONNECT tunnel, it can't actually cache it. If we can get > it to use HTTP, then I'm pretty sure it would be easily cache-able. > > The other alternative is to MitM it via squid's sslBump mechanism, but > I'd *really* rather not do that. > > The linux.dell.com server is actually still serving HTTP, at least for > now (eg. http://linux.dell.com/repo/hardware/dsu/os_independent/ instead > of https://linux.dell.com/repo/hardware/dsu/os_independent/), so in > theory, it should be possible. > > -- Lloyd Brown HPC Systems Administrator Office of Research Computing Brigham Young University http://marylou.byu.edu ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge
[Linux-PowerEdge] dsu and http (not https)
[EXTERNAL EMAIL] Is there an easy way to get DSU tools to pull files from linux.dell.com via HTTP, instead of HTTPS? We're trying to use a squid caching proxy, rather than creating our own local mirror. But while something like squid can proxy the HTTPS traffic via a CONNECT tunnel, it can't actually cache it. If we can get it to use HTTP, then I'm pretty sure it would be easily cache-able. The other alternative is to MitM it via squid's sslBump mechanism, but I'd *really* rather not do that. The linux.dell.com server is actually still serving HTTP, at least for now (eg. http://linux.dell.com/repo/hardware/dsu/os_independent/ instead of https://linux.dell.com/repo/hardware/dsu/os_independent/), so in theory, it should be possible. -- Lloyd Brown HPC Systems Administrator Office of Research Computing Brigham Young University http://marylou.byu.edu ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Re: [Linux-PowerEdge] List responses not showing up
That's fun. I sent a response to my own posting about 10 minutes before you did, and it still hasn't shown up. I sent it to the list alone. Note that this message is going to both the list, and you. I strongly suspect it won't show up in the list either. Lloyd On 05/18/2017 10:29 AM, Patrick Boutilier wrote: > On 05/18/2017 01:08 PM, Lloyd Brown wrote: >> Is anyone else having trouble with responses to list postings not >> showing up? I'm not sure if it's something on my end, or something on >> the list end, but I've sent at least one response to the following >> messages, and they're not showing up in the online archive. >> >> http://lists.us.dell.com/pipermail/linux-poweredge/2017-April/051079.html >> >> http://lists.us.dell.com/pipermail/linux-poweredge/2017-May/051138.html >> http://lists.us.dell.com/pipermail/linux-poweredge/2017-May/051159.html >> >> >> >> > > No troubles here. > > > ___ > Linux-PowerEdge mailing list > Linux-PowerEdge@dell.com > https://lists.us.dell.com/mailman/listinfo/linux-poweredge -- Lloyd Brown Systems Administrator Fulton Supercomputing Lab Brigham Young University http://marylou.byu.edu ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Re: [Linux-PowerEdge] List responses not showing up
And because I've had messages addressed to both me and the list, show up in my inbox, but not on the list, I suspect it's a problem with the list server. Thus far the initial posts on a thread seem okay. It's only subsequent messages in response. On 05/18/2017 10:42 AM, Patrick Boutilier wrote: > Yup, not showing up on list or in archive. Weird. > > > http://lists.us.dell.com/pipermail/linux-poweredge/2017-May/051160.html > > > > On 05/18/2017 01:37 PM, Lloyd Brown wrote: >> That's fun. I sent a response to my own posting about 10 minutes >> before you did, and it still hasn't shown up. >> >> I sent it to the list alone. Note that this message is going to both >> the list, and you. I strongly suspect it won't show up in the list >> either. >> >> Lloyd >> >> >> On 05/18/2017 10:29 AM, Patrick Boutilier wrote: >>> On 05/18/2017 01:08 PM, Lloyd Brown wrote: >>>> Is anyone else having trouble with responses to list postings not >>>> showing up? I'm not sure if it's something on my end, or something on >>>> the list end, but I've sent at least one response to the following >>>> messages, and they're not showing up in the online archive. >>>> >>>> http://lists.us.dell.com/pipermail/linux-poweredge/2017-April/051079.html >>>> >>>> http://lists.us.dell.com/pipermail/linux-poweredge/2017-May/051138.html >>>> >>>> http://lists.us.dell.com/pipermail/linux-poweredge/2017-May/051159.html >>>> >>>> >>>> >>>> >>>> >>> >>> No troubles here. >>> >>> >>> ___ >>> Linux-PowerEdge mailing list >>> Linux-PowerEdge@dell.com >>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge >> >> -- >> Lloyd Brown >> Systems Administrator >> Fulton Supercomputing Lab >> Brigham Young University >> http://marylou.byu.edu >> > -- Lloyd Brown Systems Administrator Fulton Supercomputing Lab Brigham Young University http://marylou.byu.edu ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge
[Linux-PowerEdge] List responses not showing up
Is anyone else having trouble with responses to list postings not showing up? I'm not sure if it's something on my end, or something on the list end, but I've sent at least one response to the following messages, and they're not showing up in the online archive. http://lists.us.dell.com/pipermail/linux-poweredge/2017-April/051079.html http://lists.us.dell.com/pipermail/linux-poweredge/2017-May/051138.html http://lists.us.dell.com/pipermail/linux-poweredge/2017-May/051159.html -- Lloyd Brown Systems Administrator Fulton Supercomputing Lab Brigham Young University http://marylou.byu.edu ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge
[Linux-PowerEdge] BIOS upgrade requirements
Does anyone know what underlying OS components are needed, to be able to manually run a BIOS update package downloaded from support.dell.com? For example, I've got two NFS-root bootable images, both based on RHEL 7.3, using the same kernel/initrd. I've got one image, which I want to use to update BIOS Firmware, etc., but I get this (excerpt): > [root@m7stage-1-2 ~]# ./BIOS_VCKYF_LN_2.5.2.BIN -f -q > Collecting inventory... > ... > > Executing update... > WARNING: DO NOT STOP THIS PROCESS OR INSTALL OTHER PRODUCTS WHILE > UPDATE IS IN PROGRESS. > THESE ACTIONS MAY CAUSE YOUR SYSTEM TO BECOME UNSTABLE! > . > Enough contiguous physical memory is not available to perform the BIOS > update running under this Operating System. Reboot and try again. > > [root@m7stage-1-2 ~]# But when I boot the same node onto the other image, it works (excerpt) > [root@m7stage-1-2 ~]# ./BIOS_VCKYF_LN_2.5.2.BIN -f -q > ... > Executing update... > WARNING: DO NOT STOP THIS PROCESS OR INSTALL OTHER DELL PRODUCTS WHILE > UPDATE IS IN PROGRESS. > THESE ACTIONS MAY CAUSE YOUR SYSTEM TO BECOME UNSTABLE! > > The system should be restarted for the update to take effect. > [root@m7stage-1-2 ~]# The obvious question is, "well, what's different between the two images?" To which I can only say ... "a whole lot." That's the point. I'm hoping for some guidance here. So far, I'm comparing kernel module list (lsmod output), as well as RPM package lists (eg. rpm -qa | sort), but I'm having trouble isolating the critical difference, among all the long list of differences. -- Lloyd Brown Systems Administrator Fulton Supercomputing Lab Brigham Young University http://marylou.byu.edu ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge
[Linux-PowerEdge] DSU return codes (was: Re: DSU, proxy)
Okay. After several days of digging, I think I have dsu working well enough. But I still have one or two questions; hopefully someone has looked into this before: Do the exit codes of a "dsu --non-interactive" or similar, happen to indicate whether or not a reboot is needed? Is there some other automated way of determining whether a reboot would be needed? You see, we want to automate this process across about 1000 nodes, but don't want to reboot unnecessarily (eg. when an iDRAC needs updated). But without an automated way to determine whether it's necessary, it's hard to know for certain. I've been testing the exit codes of a "dsu --non-interactive", and here's what I've found so far: no updates -> exit code 1 iDRAC update only -> exit code 0 BIOS update only -> exit code 8 Updates including BIOS, iDRAC, Ethernet -> exit code 8 Now, I'd like to think that this is causal, and I can rely on it for this purpose. But since I can't find any documentation about the exit codes of the dsu application, I'm a little nervous to assume this. On 04/28/2017 08:36 AM, Lloyd Brown wrote: > > I actually had already set a similar "proxy" line in /etc/yum.conf, > and it didn't seem to be effective. I've also put proxy lines in the > specific /etc/yum.repos.d/dell* location, as you suggest, and had > similar issues. > > I have had some luck by setting the "http_proxy" environment variable, > but even then, it still seems to be error-ing out, thus why I was > wondering if anyone else has gotten it to work and it's just me, or if > there's something else going on: > >> [root@m7stage-1-2 ~]# export http_proxy=http://proxy1: >> [root@m7stage-1-2 ~]# dsu --inventory >> Dell System Update 1.4 >> Copyright (C) 2014 Dell Proprietary. >> Verifying catalog installation ... >> Installing catalog from repository ... >> Fetching dsucatalog ... >> Reading the catalog ... >> Fetching invcol_RPTVF_LN64_17.03.200.987_A00 ... >> Could not download inventory collector >> Retrying ... >> Fetching invcol_RPTVF_LN64_17.03.200.987_A00 ... >> Could not download inventory collector >> Exiting DSU! >> [root@m7stage-1-2 ~]# >> > > > I guess it's time to pull out the strace again, and see if I can > figure out what exactly is failing. > > > Lloyd > > > > On 04/27/2017 08:42 PM, 603912411 wrote: >> hi， >> >> dell dsu for linux use YUM to download dups, so you should setting >> proxy for dell yum repo, and dsu will download dups by proxy. >> >> like this: >> >> [dell-dsu] >> name=dell dsu >> baseurl=http://linux.dell.com/repo/hardware/dsu/os_independent/ >> proxy=http://proxyhost:proxyport >> gpgcheck=0 >> >> >> 2017-04-28 >> >> 603912411 >> >> >> *发件人：*Lloyd Brown <lloyd_br...@byu.edu> >> *发送时间：*2017-04-28 04:28 >> *主题：*[Linux-PowerEdge] DSU, proxy >> >> *收件人：*"linux-powere...@lists.us.dell.com"<linux-powere...@lists.us.dell.com> >> *抄送：* >> >> Has anyone successfully used dsu to update firmware from Linux, working >> through an http proxy? Given the storage requirements, I'd rather do >> that, than have a local copy of the entire linux.dell.com repository. A >> caching proxy would give me most of the advantage of local storage, >> without requiring me to download EVERYTHING. >> >> Of course, to make things more complicated, this is a RHEL7 system, >> booted using an NFS root, therefore most of the / volume is read-only, >> unless I explicitly list it in /etc/rwtab, /etc/rwtab.d/*, or >> /etc/statetab, etc. I've already added the following to rwtab.d, and >> therefore are bind-mounted on a tmpfs, but there may be something else >> I'm missing: >> >> > # cat /etc/rwtab.d/dell /etc/rwtab.d/yum_cache >> > files /opt/dell >> > files /usr/libexec/dell_dup/ >> > files /var/cache/yum >> >> Thanks, >> >> Lloyd >> >> -- >> Lloyd Brown >> Systems Administrator >> Fulton Supercomputing Lab >> Brigham Young University >> http://marylou.byu.edu >> >> ___ >> Linux-PowerEdge mailing list &g
Re: [Linux-PowerEdge] DSU, proxy
I actually had already set a similar "proxy" line in /etc/yum.conf, and it didn't seem to be effective. I've also put proxy lines in the specific /etc/yum.repos.d/dell* location, as you suggest, and had similar issues. I have had some luck by setting the "http_proxy" environment variable, but even then, it still seems to be error-ing out, thus why I was wondering if anyone else has gotten it to work and it's just me, or if there's something else going on: > [root@m7stage-1-2 ~]# export http_proxy=http://proxy1: > [root@m7stage-1-2 ~]# dsu --inventory > Dell System Update 1.4 > Copyright (C) 2014 Dell Proprietary. > Verifying catalog installation ... > Installing catalog from repository ... > Fetching dsucatalog ... > Reading the catalog ... > Fetching invcol_RPTVF_LN64_17.03.200.987_A00 ... > Could not download inventory collector > Retrying ... > Fetching invcol_RPTVF_LN64_17.03.200.987_A00 ... > Could not download inventory collector > Exiting DSU! > [root@m7stage-1-2 ~]# > I guess it's time to pull out the strace again, and see if I can figure out what exactly is failing. Lloyd On 04/27/2017 08:42 PM, 603912411 wrote: > hi， > > dell dsu for linux use YUM to download dups, so you should setting > proxy for dell yum repo, and dsu will download dups by proxy. > > like this: > > [dell-dsu] > name=dell dsu > baseurl=http://linux.dell.com/repo/hardware/dsu/os_independent/ > proxy=http://proxyhost:proxyport > gpgcheck=0 > > > 2017-04-28 > -------- > 603912411 > > > *发件人：*Lloyd Brown <lloyd_br...@byu.edu> > *发送时间：*2017-04-28 04:28 > *主题：*[Linux-PowerEdge] DSU, proxy > > *收件人：*"linux-powere...@lists.us.dell.com"<linux-powere...@lists.us.dell.com> > *抄送：* > > Has anyone successfully used dsu to update firmware from Linux, working > through an http proxy? Given the storage requirements, I'd rather do > that, than have a local copy of the entire linux.dell.com repository. A > caching proxy would give me most of the advantage of local storage, > without requiring me to download EVERYTHING. > > Of course, to make things more complicated, this is a RHEL7 system, > booted using an NFS root, therefore most of the / volume is read-only, > unless I explicitly list it in /etc/rwtab, /etc/rwtab.d/*, or > /etc/statetab, etc. I've already added the following to rwtab.d, and > therefore are bind-mounted on a tmpfs, but there may be something else > I'm missing: > > > # cat /etc/rwtab.d/dell /etc/rwtab.d/yum_cache > > files /opt/dell > > files /usr/libexec/dell_dup/ > > files /var/cache/yum > > Thanks, > > Lloyd > > -- > Lloyd Brown > Systems Administrator > Fulton Supercomputing Lab > Brigham Young University > http://marylou.byu.edu > > ___ > Linux-PowerEdge mailing list > Linux-PowerEdge@dell.com > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > -- Lloyd Brown Systems Administrator Fulton Supercomputing Lab Brigham Young University http://marylou.byu.edu ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge
