- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: ignite bootsys error
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-01-2006 02:37 AM
тАО08-01-2006 02:37 AM
ignite bootsys error
root@hemlock:/opt/ignite/boot/Rel_B.11.11 # bootsys -v -w osattst1
Getting information for "osattst1"
sh: rcp: Execute permission denied.
Fatal error on "osattst1": (rcp error on /opt/ignite/lbin/bootsys_prep)
I can ping osattst1 from hemlock without a problem - there are on the same vlan.
root@hemlock:/opt/ignite/boot/Rel_B.11.11 # ping osattst1
PING osattst1.dublin.esat.ie: 64 byte packets
64 bytes from 10.40.3.239: icmp_seq=0. time=0. ms
64 bytes from 10.40.3.239: icmp_seq=1. time=0. ms
64 bytes from 10.40.3.239: icmp_seq=2. time=0. ms
instl_adm -T does not report any errors.
Thanks in advance
Shane
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-01-2006 02:45 AM
тАО08-01-2006 02:45 AM
Re: ignite bootsys error
UNIX because I majored in cryptology...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-01-2006 02:49 AM
тАО08-01-2006 02:49 AM
Re: ignite bootsys error
root@osattst1:/root # ll .rhosts
-rwxrwxrwx 1 root root 57 Aug 1 14:04 .rhosts
root@osattst1:/root # cat .rhosts
hemlock root
hemlock.dublin.esat.ie root
10.40.3.35 root
root@osattst1:/root #
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-01-2006 02:52 AM
тАО08-01-2006 02:52 AM
Re: ignite bootsys error
also it would not hurt to check the execute permission on rcp on both nodes but I highly doubt this is the problem.
UNIX because I majored in cryptology...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-01-2006 03:17 AM
тАО08-01-2006 03:17 AM
Re: ignite bootsys error
/var/adm/inetd.sec does not exist on the client. I did change the permissions of rcp on osattst1 as shown.
root@osattst1:/root # chmod 777 /usr/bin/rcp
root@osattst1:/root # ll /usr/bin/rcp
-rwxrwxrwx 1 root bin 49152 Nov 7 2001 /usr/bin/rcp.
This enabled me to get a little further:
root@hemlock:/var/opt/ignite/data # bootsys -v -w osattst1
Getting information for "osattst1"
Cannot access server file: "/opt/ignite/boot/Rel_B.11.00/WINSTALL".
root@hemlock:/var/opt/ignite/data #
It looks like my Ignite-UX server does not support 11.00 installs. (only 11i).
How can I add 11.00 installed to it
regards,
Shane
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-01-2006 07:59 PM
тАО08-01-2006 07:59 PM
Re: ignite bootsys error
If you download the latest ignite-ux software, it should give you the option of including the 10.20-11.23 and all in between. This should assist in recovering an 11.00 server.
Hope it does.
JASH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-02-2006 12:50 AM
тАО08-02-2006 12:50 AM
Re: ignite bootsys error
I have downloaded the 11.00 Ignite and installed it. When I "BO lan.10.40.3.35 install" i get the following
Trying Primary Boot Path
------------------------
Booting...
Boot IO Dependent Code (IODC) revision 1
HARD Booted.
ISL Revision A.00.38 OCT 26, 1994
ISL booting hpux (;0)/stand/WINSTALL
Boot
: disk(0/0/1/1.2.0.0.0.0.0;0)/stand/WINSTALL
12005376 + 2187352 + 2631488 start 0x201568
alloc_pdc_pages: Relocating PDC from 0xffff800000 to 0x7fa03000.
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: nfs3_link(): File system was registered at index 4.
NOTICE: autofs_link(): File system was registered at index 6.
NOTICE: cachefs_link(): File system was registered at index 7.
td: claimed Tachyon XL2 Fibre Channel Mass Storage card at 0/10/0/0
td: claimed Tachyon XL2 Fibre Channel Mass Storage card at 0/12/0/0
System Console is on the Built-In Serial Interface
Swap device table: (start & size given in 512-byte blocks)
entry 0 - auto-configured on root device; ignored - no room
WARNING: no swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
Starting the STREAMS daemons-phase 1
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 6291456 Kbytes, lockable: 4775440 Kbytes, available: 5507200 Kbytes
======= 08/02/06 08:40:15 EDT HP-UX Installation Initialization. (Wed Aug 02
08:40:15 EDT 2006)
@(#)Ignite-UX Revision C.6.8.152
@(#)ignite/init (opt) $Revision: 10.448.1.32 $ $Date: 2006/03/31
19:24:56 $
version 4 layout
16384 sectors, 16384 blocks of size 1024, log size 1024 blocks
unlimited inodes, largefiles not supported
16384 data blocks, 15288 free data blocks
1 allocation units of 32768 blocks, 32768 data blocks
last allocation unit has 16384 data blocks
* Scanning system for IO devices...
* Querying disk device: 0/0/1/1.2.0 ...
* Querying disk device: 0/0/2/0.2.0 ...
NOTE: Default (boot) source does not appear to be a valid (or complete)
install source, switching source to Network
* Bringing up Network (lan0)
add net default: gateway 10.40.3.1
* Reading configuration information from server...
* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
NOTE: Retrying loadfile command...
* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
NOTE: Retrying loadfile command...
* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
NOTE: Retrying loadfile command...
* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
NOTE: Retrying loadfile command...
* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
NOTE: Retrying loadfile command...
* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
ERROR: Failed to read "INDEX" file from install server. Check that the
install server's IP address is correct and the server has the
"Ignite-UX" product loaded and is available via the tftp(1) service.
delete net default: gateway 10.40.3.1
Failed to startup networking, user interaction required
Press Return to continue:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-02-2006 02:55 AM
тАО08-02-2006 02:55 AM
Re: ignite bootsys error
Also, make sure you do not have a firewall with any restrictions between the client system and the ignite server.
UNIX because I majored in cryptology...