vxconfigd experiencing memory allocation errors
Article ID: 100019164
Updated On:
Resolution
Although vmstat reported that there was enough memory available on the system, only a small amount was configured as shared memory. Once the amount of shared memory was increased and the system rebooted there were no further occurrences of the issue.
Issue/Introduction
'Memory allocation failure' reported when running vx commands on a SF 5.0/Solaris system
#vxdg list VxVM vxdg ERROR V-5-1-10128 Memory allocation failure #vxdisk list VxVM vxdisk ERROR V-5-1-462 Cannot get records from vxconfigd: Memory allocation failure The truss output for vxconfigd "V-5-1-8013 Interprocess communication failure: Not enough space".
29768/1: V -5 - 1 - 8 0 1 3 I n t e r p r o c e s s c o m m u n i c
29768/1: a ti o n f a i l u r e : N o t e n o u g h s p a c e
29768/1:72.6399 write(2, "\n", 1) = 1
vmstat reported enough free space and restarting vxconfigd would alleviate the issue for a few hours.
Was this article helpful?
Yes
No
Powered by
