Thanks once again to Sun-managers..quick and accurate as always:
My solution came in 2 parts from 4 different people. Here's the summary
of both:
First the problem:
> I am installing Solaris 2.2 on some SPARCclassics. The machine I brought up
> from CD-ROM runs fine. I am attempting to bring up another one by cloning a
> disk image from my first machine. I have dumped and restored all the important
> file systems (root, /usr, /var, /opt) onto the new disk, updated the /etc/hosts
> tables, and the /etc/hostname.le0 and the /etc/nodename file and things seems to
> come up fine with one exception: sac goes crazy!
>
> I get a constant disk clammering for about 10-20 mins after I first bring up
> the box. This disk clammering is sac writing to it's log file the following
> message:
>
> Wed Jul 7 17:20:35 1993; 1209; starting port monitor <tcp>
> Wed Jul 7 17:20:36 1993; 188; <tcp> has died - trying to restart
> Wed Jul 7 17:20:36 1993; 1210; starting port monitor <tcp>
> Wed Jul 7 17:20:36 1993; 188; <tcp> has died - trying to restart
> Wed Jul 7 17:20:36 1993; 1211; starting port monitor <tcp>
> Wed Jul 7 17:20:37 1993; 188; <tcp> has died - trying to restart
> Wed Jul 7 17:20:37 1993; 1212; starting port monitor <tcp>
> Wed Jul 7 17:20:38 1993; 188; <tcp> has died - trying to restart
> Wed Jul 7 17:20:38 1993; 1213; starting port monitor <tcp>
> Wed Jul 7 17:20:38 1993; 188; <tcp> has FAILED
>
> When <tcp> finally fails, the disk rattling stops.
>
> I am fairly new to the world of SysV and have no idea why my first machine
> is running fine and this cloned machine is messed up with this error. Is there
> something host specific that I missed?
Response from springer@hau.eri.com:
> I am not sure if this will help but there are actually 6 files that hold the
> machines host name in Solaris 2.2 (or 2.1 for that matter)
> The three you already modified and in the /etc/net directory there are three
> subdirectories (ticlts,ticots,and ticotsord). There is a hosts file in each of
> those three directories that have the hostname in there. Change those and see
> if your problem goes away.
Response from: casper@fwi.uva.nl:
> In /etc/saf/tcp you'll find a number of files. The file _pmtab contains
> something like this:
> # VERSION=4
> lp::root:reserved:reserved:reserved:::p::/var/spool/lp/fifos/listenS5#
> lpd::root:reserved:reserved:reserved:\x00020203923204140000000000000000::p::/var/spool/lp/fifos/listenBSD#
> 0::root:reserved:reserved:reserved:\x00020ACE923204140000000000000000::c::/usr/lib/saf/nlps_server#
> The last two entries contain coded internet addresses:
> \x00020ACE923204140000000000000000
> ^^^^^^^^ hex internet address
> You'll have to change it to match the address of the current host.
-------------------------
The combination of these two fixes (the /etc/net/*/hosts && /etc/saf/tcp/_pmtab), my
problem is solved.
Also Thanks to David.Miner@East.Sun.COM && Birger.Wathne@vest.sdata.no for their
reponses.
Thanks once again.
-- Adam Fox
Systems Programmer/Adminstrator
Supercomputing Research Center
Bowie, MD USA
adamfox@super.org
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:08:00 CDT