cfg_ksm_memreq failed message.

[Christof Schoeman]

Hi

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?

[Venkatesh BL]

What is the OS & patch version?

Was 'collect' running by any chance?

Can you post the syslogs?

[Christof Schoeman]

The OS version is 5.1B PK4 and yes, collect was running.

No messages in the logs around this time.

[Venkatesh BL]

Are you able to see the devices thru "hwmgr -view devices" command?

Does the message pop up even if you stop 'collect'?

[Christof Schoeman]

Yes, all the devices are visible and accessible. The messages were only displayed on the one ssh session and disappeared when the ssh session was disconnected.

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.

[Venkatesh BL]

I suspect that the error was thrown out by 'collect'. It happens if collect is unable to get configuration info from the kernel. But, not sure about the connection with 'ssh'. Anyway, I don't think the customer need to worry about this.

[Venkatesh BL]

btw, is this a cluster node?.

Also, did you check if you are able to playback the files generated by 'collect'? Especially, does the 'Disk Info' contain correct values?

[Christof Schoeman]

This is not a cluster node.

I'll have a look at the collect files, thanks.

[Mulgund]

It would be interesting to see for what reason
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

[Christof Schoeman]

Mmmmm...

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?