- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: cfg_ksm_memreq failed message.
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
тАО04-15-2005 12:01 AM
тАО04-15-2005 12:01 AM
cfg_ksm_memreq failed message.
Yesterday, my customer added some EMC Clariion storage to his system and did a scsi scan, no problem.
Today, some more storage was added on another Clariion in the same fabric and he did a scsi scan again. The devices are now visible and accessible, but he periodically got the following message at the prompt:
"cfg_ksm_memreq failed"
The messages disappeared when the ssh session was closed, but he is still curious as to what caused them.
Any ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2005 06:19 PM
тАО04-19-2005 06:19 PM
Re: cfg_ksm_memreq failed message.
Was 'collect' running by any chance?
Can you post the syslogs?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2005 09:34 PM
тАО04-19-2005 09:34 PM
Re: cfg_ksm_memreq failed message.
No messages in the logs around this time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2005 10:30 PM
тАО04-19-2005 10:30 PM
Re: cfg_ksm_memreq failed message.
Does the message pop up even if you stop 'collect'?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2005 01:08 AM
тАО04-20-2005 01:08 AM
Re: cfg_ksm_memreq failed message.
The customer is only curious as to what the messages actually meant. Is it something he needs to worry about?
Thanks for you help so far.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2005 04:10 PM
тАО04-20-2005 04:10 PM
Re: cfg_ksm_memreq failed message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2005 06:14 PM
тАО04-20-2005 06:14 PM
Re: cfg_ksm_memreq failed message.
Also, did you check if you are able to playback the files generated by 'collect'? Especially, does the 'Disk Info' contain correct values?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2005 07:18 PM
тАО04-20-2005 07:18 PM
Re: cfg_ksm_memreq failed message.
I'll have a look at the collect files, thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2005 11:12 PM
тАО04-20-2005 11:12 PM
Re: cfg_ksm_memreq failed message.
the memory allocation has failed.
Could be for not enough memory at disposal when scan scsi.
Could be a accumulated memory leak issue with hwmgr too ..
Need to check the relevant logs.
-Srinivas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-21-2005 12:01 AM
тАО04-21-2005 12:01 AM
Re: cfg_ksm_memreq failed message.
I'm now seeing this on another system too. Extra disks were added this morning. scsi scan picked them up fine.
I have two sessions open on the system, but only one of them is showing the message.
Collect files are also working fine.
Could not find anything out of the ordinary in the log files.
Anything in particular you would have looked at?