- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Automount Fails
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
Forums
Discussions
Discussions
Discussions
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
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
10-11-2001 12:44 AM
10-11-2001 12:44 AM
We have HP K9000 servers with HPUX 11. These are NIS & NFS clients. NIS & NFS server is a Linux Box wth Madrake 5.3. On one of the HPs automount daemon fails often, though its still bound to NIS domain. The mountpoints are taken from maps and not locally
Is it due to Linux being the NIS server.?
regds
Nag
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2001 03:30 AM
10-11-2001 03:30 AM
Re: Automount Fails
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2001 03:19 AM
10-12-2001 03:19 AM
Re: Automount Fails
regds
Nag
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2001 01:35 AM
10-22-2001 01:35 AM
Re: Automount Fails
Taking ur advise started updating the NFS Kernel General Performance Patch(PHNE_24034)
The servers were never updated with patches since it was installed(about 2 1/2 years back i guess). We do not have service agreement so no patch tools to analyse.
While updating certain patches which are dependencies of PHNE_24034 on Kclass HP9000/HP-UX 11.00 servers the system crashed.
patch PHNE_17662
PHKL_20170
caused sytem to crash. The swagent.log had this info
/usr/ccs/bin/ld :unsatisfied symbols
streams_cleanup(code)
allocb_dupb (code)
streams_select2 (code)
dupbn (code)
Also PHNE_17662 is supeseded by PHNE_24715 but this patch depends on PHNE_22566 and PHNE_22566.text says it depend on PHNE_17662. So i have reached a deadlock here.
Are these two patches a must since the documents say they are not critical.
On analysing the patch update failures, i feel PHNE_xxx patch fails.
2) How do i make sw depot. I am installing patch one by one .Since most of these patches needs a reboot, this is very painful task.
3)How do i remove the patch which is causing the crash.?
regds
Nag
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2001 01:44 AM
10-22-2001 01:44 AM
Solutionhttp://forums.itrc.hp.com/cm/QuestionAnswer/1,11866,0x75edc6af36b7d5118ff10090279cd0f9,00.html
Basically, it boils down to the following steps (paraphrasing from JRF):
#!/usr/bin/sh
cd /tmp
for X in PH*.htm
do
sh $X
done
mkdir /tmp/patch_depot
for X in PH*.depot
do
swcopy -s ${PWD}/${X} \* @ /tmp/patch_depot
done
swlist -s /tmp/patch_depot
exit 0
#.end.
Bundle the two patches, PHNE_22566 and PHNE_24715 together and install them on the system. This should take care of this problem. Make sure you have your old kernel just in case things fail. Hopefully you have a make_recovery tape of the system before you started (?)
-Santosh