get rid of non existing VGs from sanity checks while booting up

[cokehpux]

Need help tp get rid of these two errors

I see them while booting up the server

Thsi server is a newly built server - with only one disk in it.

I got rid of the not existing disks usng lvreduce -m 1 -k (used key name)

but i am unable to get rid of these non existing VGs

# strings /etc/lvmtab 
/dev/vg00
/dev/dsk/c2t0d0
#

==

the other errors, if you can help me with:
unknown host, swagentd.log etc

Many thanks

Firmware Version 50.40

Duplex Console IO Dependent Code (IODC) revision 1

Firmware Version 50.40

Duplex Console IO Dependent Code (IODC) revision 1
------------------------------------------------------------------------------
(c) Copyright 1995-2004, Hewlett-Packard Company, All rights reserved
------------------------------------------------------------------------------

Processor Speed State CoProcessor State Cache Size
Number State Inst Data
--------- -------- --------------------- ----------------- ------------
0 1000 MHz Active Functional 67108864 67108864
1 1000 MHz Idle Functional 67108864 67108864
2 1000 MHz Idle Functional 67108864 67108864
3 1000 MHz Idle Functional 67108864 67108864

Central Bus Speed (in MHz) : 200
Available Memory : 4194304 KB
Good Memory Required : Not initialized. Defaults to 32 MB.

Primary boot path: 0/1/1/0.0
Alternate boot path: 0/1/1/0.1
Console path: 0/7/1/1.0
Keyboard path: 0/0/4/0.0

Processor is booting from the first available device.

To discontinue, press any key within 10 seconds.

10 seconds expired.
Proceeding...

Trying Primary Boot Path
------------------------
Booting...
Boot IO Dependent Code (IODC) revision 1

HARD Booted.

ISL Revision A.00.44 Mar 12, 2003

ISL booting hpux -lq

Boot
: disk(0/1/1/0.0.0.0.0.0.0;0)/stand/vmunix
15372288 + 4534272 + 6867048 start 0x22e3e8

alloc_pdc_pages: Relocating PDC from 0xfffffff0f0c00000 to 0x3e900000.
DoCalllist done

Memory Class Setup
-------------------------------------------------------------------------
Class Physmem Lockmem Swapmem
-------------------------------------------------------------------------
System : 4094 MB 4094 MB 4094 MB
Kernel : 4094 MB 4094 MB 4094 MB
User : 3692 MB 3215 MB 3228 MB
-------------------------------------------------------------------------

Warning: Setting the expanded_node_host_names parameter to 1 will allow administrators to set node and host names larger than 8 and 64 characters/bytes, respectively. It is strongly recommended that all the documentation included with the NodeHostNameXpnd product bundle be understood before setting larger names. Larger names can cause some applications which use those names to exhibit anomalous or incorrect behavior.
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: cachefs_link(): File system was registered at index 4.
NOTICE: nfs3_link(): File system was registered at index 7.
igelan0: INITIALIZING HP PCI 1000Base-T Core at hardware path 0/1/2/0
iether2: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/3/1/0
iether3: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/3/1/1
iether4: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/4/1/0
iether5: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/4/1/1

System Console is on the Built-In Serial Interface
Logical volume 64, 0x4 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x3 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 24576000
Starting the STREAMS daemons-phase 1
Checking root file system.
file system is clean - log replay is not required
Root check done.
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: B11.23_LR FLAVOR=perf Fri Mar 19 15:24:05 PST 2004 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 4192256 Kbytes, lockable: 3140204 Kbytes, available: 3626392 Kbytes

/sbin/ioinitrc:
/sbin/krs_sysinit:
NOTICE: mod_fs_reg: Cannot retrieve configured loading phase from KRS for module: cifs. Setting to load at INIT

* The module 'ipf' has been loaded.
* The module 'dmphdsalua' has been loaded.
* The module 'dmphpalua' has been loaded.
* The module 'dmpjbod' has been loaded.
* The module 'dmpapf' has been loaded.
* The module 'dmpapg' has been loaded.
* The module 'dmpap' has been loaded.
* The module 'dmpaaa' has been loaded.
* The module 'dmpaa' has been loaded.
* The module 'fdd' has been loaded.
* The module 'rng' has been loaded.

insf: Installing special files for ipmi instance 0 address 16

/sbin/bcheckrc:
Checking for LVM volume groups and Activating (if any exist)
Volume group "/dev/vg00" has been successfully changed.
Resynchronized volume group /dev/vg00
Checking hfs file systems
/sbin/fsclean: /dev/vg00/lvol1 (mounted) ok
HFS file systems are OK, not running fsck
Checking vxfs file systems
UX:vxfs fsck: INFO: V-3-20913: /dev/vg00/lvol4:sanity check: root file system OK (mounted read/write)
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol5:sanity check: /dev/vg00/lvol5 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol6:sanity check: /dev/vg00/lvol6 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol7:sanity check: /dev/vg00/lvol7 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol8:sanity check: /dev/vg00/lvol8 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol9:sanity check: /dev/vg00/lvol9 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol10:sanity check: /dev/vg00/lvol10 OK
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg01/lvoldE11:sanity check failed: cannot stat /dev/vg01/lvoldE11
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg01/lvorastage805:sanity check failed: cannot stat /dev/vg01/lvorastage805
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg01/lvsaparch2:sanity check failed: cannot stat /dev/vg01/lvsaparch2
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg02/lvsapinstall:sanity check failed: cannot stat /dev/vg02/lvsapinstall
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg02/lvsapput:sanity check failed: cannot stat /dev/vg02/lvsapput
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg02/lvusrsap:sanity check failed: cannot stat /dev/vg02/lvusrsap
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg02/lvepic:sanity check failed: cannot stat /dev/vg02/lvepic
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata1:sanity check failed: cannot stat /dev/vg03/lvsapdata1
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata2:sanity check failed: cannot stat /dev/vg03/lvsapdata2
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata3:sanity check failed: cannot stat /dev/vg03/lvsapdata3
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata4:sanity check failed: cannot stat /dev/vg03/lvsapdata4
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata5:sanity check failed: cannot stat /dev/vg03/lvsapdata5
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata6:sanity check failed: cannot stat /dev/vg03/lvsapdata6
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata7:sanity check failed: cannot stat /dev/vg03/lvsapdata7
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata8:sanity check failed: cannot stat /dev/vg03/lvsapdata8
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata9:sanity check failed: cannot stat /dev/vg03/lvsapdata9
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata10:sanity check failed: cannot stat /dev/vg03/lvsapdata10
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata11:sanity check failed: cannot stat /dev/vg03/lvsapdata11
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata12:sanity check failed: cannot stat /dev/vg03/lvsapdata12
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata13:sanity check failed: cannot stat /dev/vg03/lvsapdata13
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata14:sanity check failed: cannot stat /dev/vg03/lvsapdata14
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata15:sanity check failed: cannot stat /dev/vg03/lvsapdata15
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvE11sapmnt:sanity check failed: cannot stat /dev/vg03/lvE11sapmnt
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvoraprd817:sanity check failed: cannot stat /dev/vg03/lvoraprd817
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvoraprd8170:sanity check failed: cannot stat /dev/vg03/lvoraprd8170
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvE11sapreorg:sanity check failed: cannot stat /dev/vg03/lvE11sapreorg
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvE11saparch:sanity check failed: cannot stat /dev/vg03/lvE11saparch
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvE11mirrlogB:sanity check failed: cannot stat /dev/vg03/lvE11mirrlogB
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvE11saplog1:sanity check failed: cannot stat /dev/vg03/lvE11saplog1
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvE11orahome:sanity check failed: cannot stat /dev/vg03/lvE11orahome
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lv920_64_04:sanity check failed: cannot stat /dev/vg03/lv920_64_04
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lv920_64:sanity check failed: cannot stat /dev/vg03/lv920_64
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata16:sanity check failed: cannot stat /dev/vg03/lvsapdata16
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata17:sanity check failed: cannot stat /dev/vg03/lvsapdata17
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata18:sanity check failed: cannot stat /dev/vg03/lvsapdata18
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata19:sanity check failed: cannot stat /dev/vg03/lvsapdata19
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata20:sanity check failed: cannot stat /dev/vg03/lvsapdata20
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata21:sanity check failed: cannot stat /dev/vg03/lvsapdata21
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata22:sanity check failed: cannot stat /dev/vg03/lvsapdata22
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata23:sanity check failed: cannot stat /dev/vg03/lvsapdata23
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata24:sanity check failed: cannot stat /dev/vg03/lvsapdata24
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata25:sanity check failed: cannot stat /dev/vg03/lvsapdata25
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata26:sanity check failed: cannot stat /dev/vg03/lvsapdata26
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata27:sanity check failed: cannot stat /dev/vg03/lvsapdata27
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata28:sanity check failed: cannot stat /dev/vg03/lvsapdata28
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata29:sanity check failed: cannot stat /dev/vg03/lvsapdata29
UX:vxfs fsck: ERROR: V-3-20908: /dev/vg03/lvsapdata30:sanity check failed: cannot stat /dev/vg03/lvsapdata30
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg01/lvoldE11:cannot stat /dev/vg01/lvoldE11
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg01/lvorastage805:cannot stat /dev/vg01/lvorastage805
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg01/lvsaparch2:cannot stat /dev/vg01/lvsaparch2
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg02/lvsapinstall:cannot stat /dev/vg02/lvsapinstall
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg02/lvsapput:cannot stat /dev/vg02/lvsapput
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg02/lvusrsap:cannot stat /dev/vg02/lvusrsap
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg02/lvepic:cannot stat /dev/vg02/lvepic
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata1:cannot stat /dev/vg03/lvsapdata1
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata2:cannot stat /dev/vg03/lvsapdata2
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata3:cannot stat /dev/vg03/lvsapdata3
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata4:cannot stat /dev/vg03/lvsapdata4
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata5:cannot stat /dev/vg03/lvsapdata5
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata6:cannot stat /dev/vg03/lvsapdata6
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata7:cannot stat /dev/vg03/lvsapdata7
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata8:cannot stat /dev/vg03/lvsapdata8
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata9:cannot stat /dev/vg03/lvsapdata9
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata10:cannot stat /dev/vg03/lvsapdata10
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata11:cannot stat /dev/vg03/lvsapdata11
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata12:cannot stat /dev/vg03/lvsapdata12
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata13:cannot stat /dev/vg03/lvsapdata13
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata14:cannot stat /dev/vg03/lvsapdata14
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata15:cannot stat /dev/vg03/lvsapdata15
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvE11sapmnt:cannot stat /dev/vg03/lvE11sapmnt
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvoraprd817:cannot stat /dev/vg03/lvoraprd817
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvoraprd8170:cannot stat /dev/vg03/lvoraprd8170
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvE11sapreorg:cannot stat /dev/vg03/lvE11sapreorg
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvE11saparch:cannot stat /dev/vg03/lvE11saparch
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvE11mirrlogB:cannot stat /dev/vg03/lvE11mirrlogB
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvE11saplog1:cannot stat /dev/vg03/lvE11saplog1
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvE11orahome:cannot stat /dev/vg03/lvE11orahome
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lv920_64_04:cannot stat /dev/vg03/lv920_64_04
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lv920_64:cannot stat /dev/vg03/lv920_64
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata16:cannot stat /dev/vg03/lvsapdata16
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata17:cannot stat /dev/vg03/lvsapdata17
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata18:cannot stat /dev/vg03/lvsapdata18
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata19:cannot stat /dev/vg03/lvsapdata19
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata20:cannot stat /dev/vg03/lvsapdata20
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata21:cannot stat /dev/vg03/lvsapdata21
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata22:cannot stat /dev/vg03/lvsapdata22
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata23:cannot stat /dev/vg03/lvsapdata23
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata24:cannot stat /dev/vg03/lvsapdata24
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata25:cannot stat /dev/vg03/lvsapdata25
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata26:cannot stat /dev/vg03/lvsapdata26
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata27:cannot stat /dev/vg03/lvsapdata27
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata28:cannot stat /dev/vg03/lvsapdata28
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata29:cannot stat /dev/vg03/lvsapdata29
UX:vxfs fsck: ERROR: V-3-20945: /dev/vg03/lvsapdata30:cannot stat /dev/vg03/lvsapdata30

Cleaning /etc/ptmp...
(c)Copyright 1983-2003 Hewlett-Packard Development Company, L.P.
(c)Copyright 1979, 1980, 1983, 1985-1993 The Regents of the Univ. of California
(c)Copyright 1980, 1984, 1986 Novell, Inc.
(c)Copyright 1986-2000 Sun Microsystems, Inc.
(c)Copyright 1985, 1986, 1988 Massachusetts Institute of Technology
(c)Copyright 1989-1993 The Open Software Foundation, Inc.
(c)Copyright 1990 Motorola, Inc.
(c)Copyright 1990, 1991, 1992 Cornell University
(c)Copyright 1989-1991 The University of Maryland
(c)Copyright 1988 Carnegie Mellon University
(c)Copyright 1991-2003 Mentat Inc.
(c)Copyright 1996 Morning Star Technologies, Inc.
(c)Copyright 1996 Progressive Systems, Inc.

RESTRICTED RIGHTS LEGEND
Use, duplication, or disclosure by the U.S. Government is subject to
restrictions as set forth in sub-paragraph (c)(1)(ii) of the Rights in
Technical Data and Computer Software clause in DFARS 252.227-7013.

Hewlett-Packard Company
3000 Hanover Street
Palo Alto, CA 94304 U.S.A.

Rights for non-DOD U.S. Government Departments and Agencies are as set
forth in FAR 52.227-19(c)(1,2).

/sbin/auto_parms: DHCP access is disabled (see /etc/auto_parms.log)

7 Mar 13:09:42 ntpdate[644]: can't find host ntp1.ge.com
7 Mar 13:09:42 ntpdate[644]: no servers can be used, exiting
ERROR: Could not contact host "unknown" because of an invalid
protocol sequence. Protocol sequences are specified with the
"-x rpc_binding_info" option. Make sure this option is
specified correctly.
ERROR: More information may be found in the daemon logfile on this
target (default location is unknown:/var/adm/sw/swagentd.log).
ERROR: Could not contact host "unknown" because of an invalid
protocol sequence. Protocol sequences are specified with the
"-x rpc_binding_info" option. Make sure this option is
specified correctly.
ERROR: More information may be found in the daemon logfile on this
target (default location is unknown:/var/adm/sw/swagentd.log).
/sbin/rc3.d/S300tsmsched[33]: basename: not found.

HP-UX Start-up in progress
__________________________

Configure system crash dumps .

....

[Duncan Edmonstone]

Clearly this isn't a "fresh install" from a set of HP-UX installation CDs/DVDs as you wouldn't see all those other filesystems in there. Was this "fresh install" from an Ignite recovery image?

The filesystem ones are easy to fix. Just comment out everything that's not part of vg00 from /etc/fstab.

The other ones look suspiciously like the hostname/host resolution isn't working correctly. I'd be looking at the output of 

hostname

And looking at the contents of /etc/hosts and /etc/nsswitch.conf and potentially /etc/resolv.conf to determine what is going on here 

[cokehpux]

how did I miss fstab !

yes  it is easy and yes I will comment them out now - all th VGs except VG00 now

(I am about to add a disk now into this server...running a dd on that new inserted disk - will miror it)

after dd completes, in nxt 30 min I guess will reboot the server - I am sure I will get rig of those VGxx messages o booting up screen

this server is not a freshly built from ignite

inserted a disk in an emplty slot in another server(already two boot disks)

created a third mirror - removed it and inserted it in this server and booted it up

=====

after booting up the server with mirrored disk

used set_parms hostname, ip_address etc in this newly built server

hostname command worked alright

added FQDN entry of this server now in .etc/hosts. It was not present

resolv.conf file looks just like other neighbouring hpux server - alright there also

nsswitch.conf file also looks same like another hpux server

# cat /etc/nsswitch.conf
#
# /etc/nsswitch.files:
#
# @(#)B11.23_LR
#
# An example file that could be copied over to /etc/nsswitch.conf; it
# does not use any name services.
#
passwd: files
group: files
hosts: files dns
ipnodes: files
services: files
networks: files
protocols: files
rpc: files
publickey: files
netgroup: files
automount: files
aliases: files
#

[cokehpux]

got rid of thise vgxx messages now

these reman

RESTRICTED RIGHTS LEGEND
Use, duplication, or disclosure by the U.S. Government is subject to
restrictions as set forth in sub-paragraph (c)(1)(ii) of the Rights in
Technical Data and Computer Software clause in DFARS 252.227-7013.

Hewlett-Packard Company
3000 Hanover Street
Palo Alto, CA 94304 U.S.A.

Rights for non-DOD U.S. Government Departments and Agencies are as set
forth in FAR 52.227-19(c)(1,2).

/sbin/auto_parms: DHCP access is disabled (see /etc/auto_parms.log)

7 Mar 14:02:17 ntpdate[360]: can't find host ntp1.ge.com
7 Mar 14:02:17 ntpdate[360]: no servers can be used, exiting
ERROR: Could not contact host "unknown" because of an invalid
protocol sequence. Protocol sequences are specified with the
"-x rpc_binding_info" option. Make sure this option is
specified correctly.
ERROR: More information may be found in the daemon logfile on this
target (default location is unknown:/var/adm/sw/swagentd.log).
ERROR: Could not contact host "unknown" because of an invalid
protocol sequence. Protocol sequences are specified with the
"-x rpc_binding_info" option. Make sure this option is
specified correctly.
ERROR: More information may be found in the daemon logfile on this
target (default location is unknown:/var/adm/sw/swagentd.log).
/sbin/rc3.d/S300tsmsched[33]: basename: not found.

HP-UX Start-up in progress
__________________________

Configure system crash dumps ................................................................................................................. ................................................................................................................................................... .............................................

[Duncan Edmonstone]

So your current /etc/nsswitch.conf file has the following line in it:

hosts: files dns

Which means that host name lookups will go first to /etc/hosts and then to whatever DNS server(s) are defined in /etc/resolv.conf

The fact that during boot you see the following message:

7 Mar 14:02:17 ntpdate[360]: can't find host ntp1.ge.com

Means that ntp1.ge.com isn't in your /etc/hosts file, and can't be resolved by whatever DNS server you have setup in /etc/resolv.conf (if anything)

I note that ntp1.ge.com isn't a public internet-facing host as if I try and do a lookup for it from my internet connected PC I get:

nslookup ntp1.ge.com
Server: UnKnown
Address: xxxx:xxxx:xxxx:x:xxx:xxxx:xxxx:xxxx

*** UnKnown can't find ntp1.ge.com: Non-existent domain

So if that NTP server exists, it must be private, which means it will either have to be in your /etc/hosts file, or known by your (private) DNS server pointed to by /etc/resolv.conf

I wouldn't be surprised if the other error messages are down to similar name resolution issues.

[cokehpux]

=---In all my servers....

/var/adm/sw/defaults - all the lines are commented out

==

i have modified ntp.conf - just one entry modified....by looking into a neighbouring working server

rebooted server - but those messages still come

9 Mar 12:38:16 ntpdate[360]: can't find host ntp1.ge.com
9 Mar 12:38:16 ntpdate[360]: no servers can be used, exiting
ERROR: Could not contact host "unknown" because of an invalid
protocol sequence. Protocol sequences are specified with the
"-x rpc_binding_info" option. Make sure this option is
specified correctly.
ERROR: More information may be found in the daemon logfile on this
target (default location is unknown:/var/adm/sw/swagentd.log).
ERROR: Could not contact host "unknown" because of an invalid
protocol sequence. Protocol sequences are specified with the
"-x rpc_binding_info" option. Make sure this option is
specified correctly.
ERROR: More information may be found in the daemon logfile on this
target (default location is unknown:/var/adm/sw/swagentd.log).
/sbin/rc3.d/S300tsmsched[33]: basename: not found.

===========

I will continue working on it..

Thanks