topic Problem kicking off swinstall from console. in Operating System - HP-UX

Problem kicking off swinstall from console.

Nick Zraika — Sun, 06 Feb 2005 22:58:27 GMT

I'm on a HP 700/92 console attached to a HP D270. This server is currently "standalone" not connected to a Network.

I'm trying to launch swinstall &
get the following error:

swinstall Couldn't bring up the initial window. This may occur when you specify an incorrect display.
ERROR: The interactive UI failed to start. If you wish to run non ineractively, you must specify some software as part of the swinstall command.

Now, i don't want any replies on "manual - command line ways" of getting the software to install (i know about that) just want to find out why the swinstall menu doesn't work.

Looked at previous posts and setting the TERM to vt100 did the trick for most, not the case here...

I have already done the following:

- unset DISPLAY
- stopped then started swagentd
- read the sw logs under /var/adm/sw, only useful message was in swagentd.log

WARNING: Failure registering as Remote Procedure Call server using protocol sequence "ncacn_ip_tcp" with endpoint "2121". No addresses (dce / rpc)

Any ideas/suggestions welcome!

Re: Problem kicking off swinstall from console.

Steven E. Protter — Sun, 06 Feb 2005 23:04:14 GMT

Things to check.

Is /etc/nsswitch.conf set.

11i v1 early versions shipped without a default and if its not set swagentd won't run.

ps -ef | grep swagentd

Is swagentd running. If that daemon is down you can't install software.

/sbin/swagentd -r

or

/sbin/swagentd stop
/sbin/swagentd start

Make sure there is enough room in /var to install something, if this involves patches.

Try TERM=hp

It appears this box has a lot of network setup for one that is not on a network. This may be interfering with normal operations.

SEP

Re: Problem kicking off swinstall from console.

Nick Zraika — Sun, 06 Feb 2005 23:13:56 GMT

There is no nsswitch.conf file present under /etc ??? is this required for swinstall ?

Its running HP-UX 10.20 (sorry should have pointed this out earlier)

Tried the following to no avail:

/sbin/swagentd -r

or

/sbin/swagentd stop
/sbin/swagentd start

Make sure there is enough room in /var to install something, if this involves patches.

Try TERM=hp

Re: Problem kicking off swinstall from console.

Artyom Voronchihin — Mon, 07 Feb 2005 06:15:16 GMT

It seems to be a name resolution problem. Does /etc/hosts file exist and contains record for localhost?

Re: Problem kicking off swinstall from console.

MarkSyder — Mon, 07 Feb 2005 06:42:35 GMT

Sorry if this is insulting, but did you export the TERM after you'd set it?

Also, try vt220 or dtterm.

Mark Syder (like the drink but spelt different)

Re: Problem kicking off swinstall from console.

Nick Zraika — Mon, 07 Feb 2005 18:01:25 GMT

Sounds like a names resolution problem to me too....

yes, the /etc/hosts file exists.
yes, there is an entry for local host:

127.0.0.1 localhost

Nothing else in the file (not attached to any network as per my 1st post)

Yes i did export the TERM :)
tried vt220, no luck either..

hmmmmmm

Re: Problem kicking off swinstall from console.

Ranjith_5 — Mon, 07 Feb 2005 18:18:50 GMT

Hi Nick,

Are you able to use sam in GUI? Or only problem with swinstall?

what is the output of
#ping $(hostname)

you are getting reply?

Is the hostname set properly in /etc/hosts?
I mean apart from localhost try adding the hostname in /etc/hosts.

Regards,
Syam

Re: Problem kicking off swinstall from console.

Nick Zraika — Mon, 07 Feb 2005 18:28:29 GMT

Hi Syam,

1) SAM works fine, its just swinstall.
2) ping $(hostname) was successful
3) After adding the hostname (earth) to the /etc/hosts file with a "dummy IP address" as its not on a network, i.e so that the hosts file looked like:

127.0.0.1 localhost
192.172.54.107 earth

the ping $(hostname) no longer worked. I got:

PING earth: 64 byte packets
ping: sendto: Network is unreachable
ping: wrote earth 64 chars, ret=-1
ping: sendto: Network is unreachable
ping: wrote earth 64 chars, ret=-1
etc etc

Re: Problem kicking off swinstall from console.

Nick Zraika — Mon, 07 Feb 2005 19:04:49 GMT

When i do a ps -ef |grep swagentd
all i get is:

root 1786 1 0 11:00:04 ? 0:00 /usr/sbin/swagentd
root 1788 1308 0 11:00:08 console 0:00 grep swagentd

So i decided to do a:

/usr/sbin/swagentd -r

and the ps -ef |grep swagentd now shows:

the swagentd -r process

still no luck with swinstall..

tried:

/sbin/init.d/swagentd stop
/sbin/init.d/swagentd start

no luck.

Re: Problem kicking off swinstall from console.

Nick Zraika — Mon, 07 Feb 2005 19:09:59 GMT

HOLD THE PHONE!!

GUYS!! IT WAS A VERY STUPID MISTAKE!!

Suprised no-one picked up on it too! in my 1st post i mentioned "exactly" what i was doing..

DDDDDDDDRrrrrrrrrrrrrrrrr i was typing a & after the swinstall command!!!

Now that deserves a slap! :)

Thanks all for your help ...

Re: Problem kicking off swinstall from console.

Ranjith_5 — Mon, 07 Feb 2005 20:35:24 GMT

Hi Nick,

Yor sentence "I m trying to launch swinstall & get the following error" was read by me as "Im trying to launch swinstall and get the following error"

So couldnot find any mistake in that....!!

Anyways hope now your problem is solved.

regards,
Syam

Re: Problem kicking off swinstall from console.

Ranjith_5 — Mon, 07 Feb 2005 20:40:25 GMT

Hi Nick,

I dont find any mistake in using

#swinstall &

because this also will give you the GUI. I am able to use this and I have been using this way only since I may need the shell prompt for some other work during the installation. I used to use #swinstall & only .

I am running this from my windows PC with Exceed.

Regards,
Syam

Re: Problem kicking off swinstall from console.

Nick Zraika — Mon, 07 Feb 2005 23:52:06 GMT

Please see my previous posts. I'm on the console... running the swinstall with the & symbol won't work! there is no GUI.

Anyways' thanks all ...

problem fixed.

Nick