- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Can't get kernel namelist
Operating System - HP-UX
1752270
Members
4682
Online
108786
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО12-22-2010 06:25 PM
тАО12-22-2010 06:25 PM
Hello Ux Gurus,
I have received OVO alert from one server
"Can't get kernel namelist"
if I check dmesg, it shows nothing but this.
-----------------clip-----------------------
SystemName:/:# dmesg
Dec 23 04:19
Can't get kernel namelist
SystemName:/:#
SystemName:/:# date
Thu Dec 23 04:20:01 EET 2010
-----------------clip-----------------------
whereas syslog.log is clean.
I found very similar thread, here
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=943728
And solution provided by Steve is like this..
----------------------------------------
Hi
Guess you have a stripped kernel which was generated with LDOPTS="-s" set and will not then do some things
Make sure it is unset and regenerate kernel
Steve Steel
----------------------------------------
but, I couldn't understand anything of it :(
would you please help me ?
[ 10 points to correct answer :)]
I have received OVO alert from one server
"Can't get kernel namelist"
if I check dmesg, it shows nothing but this.
-----------------clip-----------------------
SystemName:/:# dmesg
Dec 23 04:19
Can't get kernel namelist
SystemName:/:#
SystemName:/:# date
Thu Dec 23 04:20:01 EET 2010
-----------------clip-----------------------
whereas syslog.log is clean.
I found very similar thread, here
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=943728
And solution provided by Steve is like this..
----------------------------------------
Hi
Guess you have a stripped kernel which was generated with LDOPTS="-s" set and will not then do some things
Make sure it is unset and regenerate kernel
Steve Steel
----------------------------------------
but, I couldn't understand anything of it :(
would you please help me ?
[ 10 points to correct answer :)]
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2010 06:44 PM
тАО12-22-2010 06:44 PM
Solution
Programs such as ipcs require information from the kernel file (not from memory), specifically information about entry points (programming stuff) within the compiled code. If you create a new kernel but do not reboot, then the kernel file (vmunix file) does not match the running kernel in memory. The system will run OK, but it is an indicator that the kernel file is different than the code in memory.
Reboot and the problem goes away.
Bill Hassell, sysadmin
Reboot and the problem goes away.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2010 06:51 PM
тАО12-22-2010 06:51 PM
Re: Can't get kernel namelist
Thanks for the quick reply Bill :)
I will ask customer for server reboot approval and update you .
Thanks again.
I will ask customer for server reboot approval and update you .
Thanks again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2010 08:20 PM
тАО12-22-2010 08:20 PM
Re: Can't get kernel namelist
>Bill: Programs such as ipcs require information from the kernel file
Last time I looked, ipcs(1) just used pstat(2). But there are other commands that need to use nlist(3).
Last time I looked, ipcs(1) just used pstat(2). But there are other commands that need to use nlist(3).
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP