provided by Star2Billing S.L.

Im using the latest a2billing and recently something is weird, it seems that a2billing-callb is not ending so what happens is everytime this is started its eating the memory.

log at 7am
--------
top - 07:47:34 up 22 min, 1 user, load average: 0.00, 0.00, 0.00
Tasks: 84 total, 1 running, 83 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 1032400k total, 186632k used, 845768k free, 6460k buffers
Swap: 3903776k total, 0k used, 3903776k free, 51620k cached


log at 10.am
-----------------------
top - 10:01:24 up 2:36, 1 user, load average: 0.14, 0.06, 0.01
Tasks: 218 total, 2 running, 216 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 1032400k total, 719412k used, 312988k free, 21856k buffers
Swap: 3903776k total, 0k used, 3903776k free, 69224k cached

what can we do it seems that we have to keep rebooting this server.
HELP!!!

I've not experienced this myself on v1.3.3. What does the debug log say?

Yes i double check and it is 1.32 what do you think well need to do with this problem.

I really have no idea what the problem might be. I ran callback on v1.3.2 for a long time with no reported issues.

This was found to be caused by a cron job launching a new instance of the callback-daemon every minute.

A very long time ago, I have had a similar issue. I have traced the issue to an init script that was not compatible with gentoo. The init script were not finding the already running instance of the callback-daemon. So we were having multiple daemon running at the same time.