kcore: Value too large for defined data type

[awreneau]

OUL 5.4 64 bit
2gb ram
VM running on ESX

I'm trying to install Landesk on a server and I'm getting the error when I execute the command to take an inventory:

"kcore: Value too large for defined data type"

The box has roughly 2GB of ram and each time I run the command it generates this error:
"kcore: Value too large for defined data type"

google has not turned any explanation or solutions, hoping I might find an answer here.

The thread on Landesk's site is

http : / / community.landesk.com/support/message/50229#50229]LANDesk User Community: error on ldiscan.sh

Remove the spaces at the beginning of the http

[Rubberman]

What OS are you running in the VM? Basically, this sort of error indicates that something has specified a value that exceeds the capability of some variable/parameter type. Example, trying to assign a value over 65535 to a 16-bit unsigned integer.

[awreneau]

OUL = Oracle Unbreakable Linux

Which is RH5.4.

OUL is identical to RH w/ the exception to branding. Below is the result of ulimit -a


core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 16384
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 65535
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 16384
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

[Rubberman]

Are you running 32-bit (i386) or 64-bit (x86_64)?

[awreneau]

OUL 5.4 64 bit
2gb ram
VM running on ESX

[Rubberman]

Hmmm. Well, I have to wonder if it is an issue with the Landesk application software. I read your posing on the landesk.com forum and other than your assumption about /proc/kcore mirroring the amount of RAM (I have 8GB ram and /proc/kcore is 4KB on my CentOS 5.5 system and appears to contain kernel crash dump data in case it panics). Anyway, a message from kcore is likely a kernel message, so the comments to your landesk.com posting about a variable size issue may be relevant. IE, it is possible that something in the landesk software is making a kernel call with a mis-sized component. At this point, guessing is as good as I can get. I would suggest however that you contact Oracle about this. CentOS is also an RHEL clone, though I think Oracle has made more kernel mods than CentOS or Scientific Linux (both free RHEL clones) do.