Operating System - HP-UX
1838721 Members
5980 Online
110129 Solutions
New Discussion

Re: memory core dump when issuing swinstall -s SD_CDROM

 
Edward J. Segura
Frequent Advisor

memory core dump when issuing swinstall -s SD_CDROM

I mkdir for SD_CDROM on a K580 box and issue the swinstall -s SD_CDROM command and first it goes to unable to find hostname then cancel out of that and it tries to reach target, it ends up gettin memory core dump and swinstall fails. I am at a stand still help!
11 REPLIES 11
steven Burgess_2
Honored Contributor

Re: memory core dump when issuing swinstall -s SD_CDROM

Hello

Couple of initial questions...

Do you have the hostname of your server in /etc/hosts ?

Have you mounted the SD_CDROM directory onto the target of the cdrom drive ?

ie

mount /dev/dsk/c#t#d# /SD_CDROM

Does the cdrom have a valid software depot on it ?

Check the swagentd logfile for further clues

/var/adm/sw/swagentd.log

HTH

Steve
take your time and think things through
Michael Tully
Honored Contributor

Re: memory core dump when issuing swinstall -s SD_CDROM

Restart the swagent daemon first.


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

The next problem you have is you haven't actually selected a bundle to be loaded. What are you trying to install?

normally something like this:
# swinstall -s /SD_CDROM/mydepot autoreboot=true \*

not swinstall -s SD_CDROM
Anyone for a Mutiny ?
Edward J. Segura
Frequent Advisor

Re: memory core dump when issuing swinstall -s SD_CDROM

I have mounted the SD_CDROM to the target device i.e dev/dsk/c2t2d0 and issued swinstall by itself and with swistall -s SD_CDROM neither one works....any other suggestions? thx
steven Burgess_2
Honored Contributor

Re: memory core dump when issuing swinstall -s SD_CDROM

Hello

Try

swinstall -s `hostname`:/SD_CDROM

Check the logfile

HTH

Steve
take your time and think things through
Sundar_7
Honored Contributor

Re: memory core dump when issuing swinstall -s SD_CDROM

You need to be able to resolve your own hostname before being able to issue anyof the SD-UX commands.

# ping

If it cannot resolve then add entries to /etc/hosts file and also to /etc/nsswitch.conf file

# vi /etc/hosts

#

# vi /etc/nsswitch.conf
hosts: dns [NOTFOUND=continue UNAVAIL=continue] files
#

# ping

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

Now this should work.
Learn What to do ,How to do and more importantly When to do ?
Edward J. Segura
Frequent Advisor

Re: memory core dump when issuing swinstall -s SD_CDROM

Sorry! all I am trying to do is get device drivers for J3514A NIC card on to the box. I am using the 1 of 5 cd's from 11.o
Edward J. Segura
Frequent Advisor

Re: memory core dump when issuing swinstall -s SD_CDROM

I have added the host to /etc/hosts and added hosts: dns [NOTFOUND=continue] files to /etc/nsswitch. I still can't ping the hostname, the correct error I am getting is a "memory fault coredump". Is there any other suggestions out there?? Thanks!!
steven Burgess_2
Honored Contributor

Re: memory core dump when issuing swinstall -s SD_CDROM

strange

are you installing on the server you are running the swinstall ?

past your /etc/hosts entry and the command you are using to ping your host

can you ping the machine from your pc

can the machine see other hosts on the network

if you do a

file core

whats the output

Steve

take your time and think things through
Edward J. Segura
Frequent Advisor

Re: memory core dump when issuing swinstall -s SD_CDROM

This was a restored system from ignite(recovery box). We have added the hostname to /etc/hosts, but still can't ping the hostname. We have also added the NOTFOUND stuff in /etc/nsswitch. SD_CDROM when running swinstall gets memory fault core dump.
steven Burgess_2
Honored Contributor

Re: memory core dump when issuing swinstall -s SD_CDROM

have you added the ip address as well as the hostname ?
take your time and think things through
Edward J. Segura
Frequent Advisor

Re: memory core dump when issuing swinstall -s SD_CDROM

Thanks for all the responses posted, it turned out to be DNS issue, and resolved by uncommenting out DNS. Also some filesystems had to be increased in order for the install to complete.