Forum Discussion
CirrocumulusLDAP monitor with error : fork() failed: Cannot allocate memory
CirrocumulusHi Sarovani,
There seems to be nothing wrong with your monitor configuration, since the other F5 box shows no issues and the pool members are up.
But Mohamed ir quite right, you should restart services (or maybe even do a full_box_reboot). I would follow this general procedure:
- schedule a maintenance window (30 min should be enough)
- confirm DSC is in-sync
- force a failover
- check everything is up and running in the newly active system
- execute "full_box_reboot" on the standby system
- check status after reboot
- if all ok (LDAP monitor ok on those pool members), optionally failover again
And by the way... what version are you running? A memory leak bug may already have been corrected in newer images.
/Mike
Blue_whaleHi Mike757 Mohamed_Ahmed_Kansoh
Thank you for the reply , We have tried belo steps
On f5-lan-primary : Did a failover and made f5-lan-secondry as active .
1.Restarted the F5 from CLI - No luck
2.Restarted the F5 from VM console - issue got resolved .
But strange , why the first reboot from F5 cli did not fix the issue . We hve cse open with F5 support waiting for RCA .
Hi Blue_whale ,
Restarting services differs from Rebooting the Full VM which you restart F5 Kernel and Whole Daemons.
But I would like to Know the Reason from F5 support team.
so update us when you know about it.
