- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Possible reason for lanadmin SIGSEGV?
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-09-2006 07:53 PM
10-09-2006 07:53 PM
as I lack experience in debugging core files I would like to ask here if someone could tell me why the lanadmin command whenever I execute it, even on read-only calls, issues a segmentation violation?
Are there sensible debugger steps I could undergo in a core file post-mortem to track the cause?
# lanadmin -x 0
Current Config = 100 Full-Duplex MANUAL
Memory fault(coredump)
# file core
core: core file from 'lanadmin' - received SIGSEGV
# model;uname -srv
9000/800/L3000-5x
HP-UX B.11.11 U
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2006 08:21 PM
10-09-2006 08:21 PM
Re: Possible reason for lanadmin SIGSEGV?
Things you could check by yourself:
- Has your lanadmin binary become corrupted somehow? Compare with another 11.11 server with the same patch level if you can.
- Are you up to date with patches?
- Are there any indications of hardware problems? Check the logs for hardware error messages. Use STM diagnostics to check out memory error statistics, just in case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2006 08:23 PM
10-09-2006 08:23 PM
Solutionone possible reason of lanadmin coredump is patches not installed ?
Patch Name: PHNE_34427
Patch Description: s700_800 11.11 LAN Patch Name: PHNE_33138
Patch Description: s700_800 11.11 100BT unified driver cumulative patchproduct cumulative patch
best regards
Joel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2006 08:41 PM
10-09-2006 08:41 PM
Re: Possible reason for lanadmin SIGSEGV?
the patch level of this box is indeed quite dated.
So you both are probably right that I miss some PHNE patch.
I also searched HP's web patch database for the keywords "lanadmin" and "SIGSEGV" and was presented a link to the following patch
http://www4.itrc.hp.com/service/patch/patchDetail.do?patchid=PHNE_34672&sel={hpux:11.11,}&BC=main|search|
But before I figure out individual patches
I decided to install the latests Support Plus CD (mine is from June 2006) GOLDQPK11i, which I am doing right now.
I hope that some ARPA transport patch or whatever fixes lanadmin will already be included.
When the box has booted the new kernel I will come back to report...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2006 09:21 PM
10-09-2006 09:21 PM
Re: Possible reason for lanadmin SIGSEGV?
installation of GOLDQPK11i seems to have fixed this bug.
# swlist -l bundle GOLD\*|grep ^[^#]
GOLDAPPS11i B.11.11.0606.446 Applications Patches for HP-UX 11i v1, June 2006
GOLDBASE11i B.11.11.0606.446 Base Patches for HP-UX 11i v1, June 2006
# swlist -l fileset -a state GOLD\*|grep ^[^#]|grep -cv configured
0
# lanadmin -x 0;ll core
Current Config = 100 Half-Duplex AUTONEG
core not found
I have no idea which of the patches fixed this but at least one of those you mentioned was included in the GOLDQPK11i.
# swlist -l fileset GOLD\*|grep PHNE_33138
# GOLDBASE11i.PHNE_33138 1.0 100BT unified driver cumulative patch
GOLDBASE11i.PHNE_33138.100BT-KRN 1.0 Networking.100BT-KRN
GOLDBASE11i.PHNE_33138.100BT-RUN 1.0 Networking.100BT-RUN
GOLDBASE11i.PHNE_33138.CORE2-KRN 1.0 OS-Core.CORE2-KRN