You can find where the non existent hostname is using this: cd /etc grep -ri oldhostnane * 2> /dev/null
I bet it is hidden somewhere in /etc. Or in the home dir of your user... On Mar 8, 2013 12:24 PM, "Smith, Ann (CTO Service Delivery)" < [email protected]> wrote: > Mark, Rick and Leeland- you guys are the best! > > Mark - you pointed me in right direction with the script > (I did open an issue with support and the guy is looking at the > script) > > Leeland - I used that 'unset DISPLAY' command as so the upgrade script > now realizes to use yast instead of YaST2 and continues on > > Rick - you are always good at explaining to the ignorant amomng us > > My predecessor must have left a hostname of a now non-existent PC coded > somewhere as default DISPLAY- I can see it on servers if I echo > $DISPLAY) > Now looking for where iti s coded. So I don't think this is an issue > others are likely to hit with SLES11 upgrade. > > Annie > > -----Original Message----- > From: Linux on 390 Port [mailto:[email protected]] On Behalf Of > Mark Post > Sent: Thursday, March 07, 2013 6:19 PM > To: [email protected] > Subject: Re: SLES10 SP4 to SLES11 SP2 upgrade issue > > >>> On 3/7/2013 at 06:03 PM, "Smith, Ann (CTO Service Delivery)" > <[email protected]> wrote: > > In this case the upgrade process script is calling YaST2 > > /sbin/yast is simply a symbolic link to /sbin/yast2. /sbin/yast2 is a > bash script that tries to figure out whether to run in ncurses mode or > GUI mode depending on a number of things it checks on the installed > system. > > > Perhaps because we chose the ssh method rather than vnc in original > > parm file > > That is exactly what I do all the time, so that's not your problem. > > -snip- > > vnc method may have required installing a product in my vmware > > If your firewalls allow access to port 5801, you can use any > Java-enabled web browser for the VNC install. (Not that having a > Java-enabled browser is a very good idea these days, but that's a > different topic.) > > -snip- > > PuTTY is allowed so opted to try ssh method (silly us) > > Not at all. As I said, that's what I do most of the time. It does > work, we just have to figure out why not for you. > > > Don't know why the install process is invoking YaST2 rather than yast > > That is the question. If you look at /usr/lib/YaST2/startup/YaST2.ssh, > it's just a shell script that checks a few things, and then makes this > call: > /usr/lib/YaST2/startup/YaST2.call installation continue > > That is also a shell script, which means that you can invoke it directly > (without going through the YaST2.ssh script) this way: > sh -x /usr/lib/YaST2/startup/YaST2.call installation continue > > Do that and send me the output off-list. I'll see if I can figure out > what's going on in your case. > > > Mark Post > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO LINUX-390 or > visit http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ************************************************************ > This communication, including attachments, is for the exclusive use of > addressee and may contain proprietary, confidential and/or privileged > information. If you are not the intended recipient, any use, copying, > disclosure, dissemination or distribution is strictly prohibited. If you > are not the intended recipient, please notify the sender immediately by > return e-mail, delete this communication and destroy all copies. > ************************************************************ > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
