unable to lock process in memory: Not enough space

[John Ferrara]

I have a K220 running 10.20 (12/2001 patch) generating thousands of error msg in syslog.log file:

May 16 08:18:25 abmtln06 /usr/lbin/ups_mond[7462]: /usr/lbin/ups_mond: UPS Monitor daemon starting; using configuration file /etc/ups_conf
May 16 08:18:26 abmtln06 /usr/lbin/ups_mond[7462]: /usr/lbin/ups_mond: exiting; unable to lock process in memory: Not enough space

It refers to 'Not enough space', disk or memory? I have plenty of both. This box was rebooted yesterday and that is when it started.

I have disabled the UPS deamon via SAM.

John

[Helen French]

Hi John:

One thought:

Take a quick look in /etc/ups_conf to make a note of the tty ports being used, and then a comparison done against the tty ports set to respawn in /etc/inittab, should reveal that you have a getty respawning on the same port as the UPS connection is configured for.


In /etc/inittab either set the rogue getty entries to off or remove them completely. Then:

# init q

HTH,
Shiju

[Mladen Despic]

From HP's Knowledge Base:

The 'ups_mond' error indicates that you do not have enough lockable
memory.

You can increase the amount of lockable memory by decreasing the
'unlockable_mem' kernel parameter, or by increasing your physical memory.
HP recommends that you increase the physical memory because decreasing
'unlockable_mem' could generate other problems.

The 'unlockable_mem' parameter defines the minimum amount of memory that
is always available for virtual memory management and system overhead.
Increasing the amount of unlockable memory decreases the amount of
lockable memory:

Total available system memory - unlockable_mem = lockable memory

[John Ferrara]

I checked those files:

cat /etc/ups_conf
shutdown_delay_mins:4
shutdown_timeout_mins:9
upstty:/dev/tty0p1:SOLA

more /etc/inittab
init:4:initdefault:
ioin::sysinit:/sbin/ioinitrc >/dev/console 2>&1
tape::sysinit:/sbin/mtinit > /dev/console 2>&1
muxi::sysinit:/sbin/dasetup /dev/console 2>&1 # mux init
stty::sysinit:/sbin/stty 9600 clocal icanon echo opost onlcr ixon icrnl ignpar <
/dev/systty
brc1::bootwait:/sbin/bcheckrc /dev/console 2>&1 # fsck, etc.
link::wait:/sbin/sh -c "/sbin/rm -f /dev/syscon; /sbin/ln
/dev/systty /dev/syscon" >/dev/console 2>&1
cprt::bootwait:/sbin/cat /etc/copyright >/dev/syscon # legal req
sqnc::wait:/sbin/rc /dev/console 2>&1 # system init
powf::powerwait:/sbin/powerfail >/dev/console 2>&1 # powerfail
cons:123456:respawn:/usr/sbin/getty console console # system console
vue :4:respawn:/usr/vue/bin/vuerc # VUE invocation
#ttp1:234:respawn:/usr/sbin/getty -h tty0p1 9600
#ttp2:234:respawn:/usr/sbin/getty -h tty0p2 9600
#ttp3:234:respawn:/usr/sbin/getty -h tty0p3 9600
#ttp4:234:respawn:/usr/sbin/getty -h tty0p4 9600
#ttp5:234:respawn:/usr/sbin/getty -h tty0p5 9600
ShPr::respawn:/opt/sharedprint/bin/spserver
ups1::off:rtprio 0 /usr/lbin/ups_mond -f /etc/ups_conf

Notice that the getty stuff is commented out.


John

[Helen French]

Hi John:

Check this document if it helps (TKB #S3100004783):

http://us-support2.external.hp.com/cki/bin/doc.pl/sid=f52de4a80ef80c31db/screen=ckiDisplayDocument?docId=200000049809916

HTH,
Shiju

[John Ferrara]

Unlockable memory is set to 0.

swapinfo
Kb Kb Kb PCT START/ Kb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 1048576 13740 1034836 1% 0 - 1 /dev/vg00/lvol2
reserve - 268256 -268256
memory 395784 269100 126684 68%

John

[Steve Steel]

Hi

This is maybe not logical but it will be correct.

1)If possible boot again. May suffice.

2)Post the syslog and /etc/rc.log


3)In /var/adm/syslog/syslog.log look at the
memory figures and check that you did not lose any.

You do not have that much swap free.

Steve Steel

[Stefan Farrelly]

You dont have enough free configuous memory available. This is proved by the USED column on your swapinfo command showing over 13MB used -ie. 13MB of processes have been actually paged out to disk (which means youve used your RAM Size + 13MB).

Reduce your memory pressure. Close down some processes if you can which are hogging lots of memory. Run this command to see the memory hoggers in order of who uses most first;

UNIX95= ps -e -o vsz=Kbytes -o ruser -o pid,args=Command-Line | sort -rnk1 | more

[Helen French]

Hi John:

Just another thought - Check your kernel parameter - dbc_max_pct. If set to the default -50% - then reduce it to a lower value (15% ?).

HTH,
Shiju

[John Ferrara]

Ooops! This is the only one of my servers that doesn't have a UPS. Sorry. Thanks for all of the assistance anyway.