Memory leak in PIAF Purple?

[joeg]

Anybody else having a memory leak in PIAF Purple? it's pretty serious - right after an "amportal restart" in the morning, my memory usage is 36%.

By the end of the working day it's at about 60% and by the next morning it's in the yellow 80% range with the threat to go into the red range. Over a weekend it's pretty solid red.

I have to do at least one "amportal restart" per day to tame it.

Are others having the problem? Any suggestions? And if re-install to the latest is the only answer, that's probably ok. Although I look forward to the re-install about as enthusiastically as doing a self-appendectomy.

Versions: PiaF = 1.7.5.5
FreePBX = 2.8.1.4
Asterisk = 1.8.3

 

[darmock]

You should try upgrading to asterisk 1.8.3.2 which seems to be stable.

earlier versions such as 1.8.2.x and 1.8.3 have had some memory leaks reported and fixed. Can't find anything in various bug trackers about 1.8.3.2. In fact our upcoming Pbx in a Flash version 1.7.5.6 has removed the experimental moniker from 1.8.3.2 aka purple. It is stable on the dozen or so machines I have as a test bed with no signs of memory leaks on various hardware and vm types. Of course your mileage may vary. Over the years there are odd combination's of hardware that just won't run Asterisk reliably or flaky memory chips has lead to many hours of frustration. I am rewriting my install guide to include motherboard and memory testing BEFORE you put the cd in the drive to install PIAF.


Tom

 

[RTOMikey]

I'm having the same issue here, Asterisk 1.8.2 got brave and decided to do the update source yesterday, for some reason, it goes part way through, and then get an error message #4, now exiting right after downloading digiumsource.conf Running Proxmox1.8, and have NOT chose to do the yum update or kernel. any suggestions on what I am doing wrong?

 

[joeg]

Related question - if I reinstall to 1.8.3.2, will this also have all the fixes in place for the gnarly Google Voice issues we just fought our way through? Just hoping to kill at least two birds with a single shot of the sling.

 

[womble1]

I found if I did this…

in the cli

cd /etc/asterisk
joe modules.conf

Ensure the following lines are present


noload = res_jabber.so
noload = chan_gtlak.so

Ctrl KX to save

reboot

it stopped it one of those un configured modules was the cause….

 

[darmock]

I'm having the same issue here, Asterisk 1.8.2 got brave and decided to do the update source yesterday, for some reason, it goes part way through, and then get an error message #4, now exiting right after downloading digiumsource.conf Running Proxmox1.8, and have NOT chose to do the yum update or kernel. any suggestions on what I am doing wrong?

What are you running PIAF on a real machine or a virtual machine? I suspect virtual and kvm. Can't speak for the kvm version and if update-source works as I did not write the template.

You are also running 64bit and generic Centos it seems.

All these can come together and cause problems.

Also if you used a script to install it remotely again who knows as we did not write the script for this.

Installing PIAF from an ISO file generally works just fine in proxmox using the template may cause other problems.

If it fails with error 4 it can be a segfault or interrupted system call neither of which come from PIAF programs although they come from other programs such as asterisk.....

Reinstall with current ISO and payload and see what happens.

Tom

 

[darmock]

Related question - if I reinstall to 1.8.3.2, will this also have all the fixes in place for the gnarly Google Voice issues we just fought our way through? Just hoping to kill at least two birds with a single shot of the sling.

No idea If you are running incredible then I can't predict this. If you are not running incredible then any fixes which have been incorporated into the asterisk source code (1.8.3.2 as of this moment) will be there. Ward is occupied till next week and he is the one that can speak to the incredible pbx.

Tom

 

[RTOMikey]

was actually installed by the NV article link to the 64-bit proxmox template. Everything else has been flawless for me, including 13 gv trunks, multiple scripts, such as the sms through google webpage I'm working on, etc. Even managed to get allison working, surprisingly in both my 64bit regular and 8khz licensed voices, just having a problem with upgrading the source now to get the later Asterisk. I do have a bare metal container backup every night, so am willing to try any suggestions you may have to get around this without completely rebuilding..... just went production, and with 60+ extensions in 14 locations, about 15 IVRs, countless time conditions and groups, REALLY dont want to rebuild from scratch. think I wou;d rather do an amportal restart cron job every night and deal with it first lol

 

[darmock]

Yup best thing. You can try to download and hand compile asterisk if you like.

That is really your only other option. I only use ISO in proxmox and never the template. However it is your box.... Never had a problem with ISO.

Unfortunately since you are doing this on a live system you should maybe try on a cloned prox container prior to try things. Frankly update-source is and always will be EXPERIMENTAL. It works in most cases however when it fails it does so very well.

Purple has been EXPERIMENTAL till next week. Essentially 1.8.3.2 seems "reasonably" stable so when 1756 comes out next week we have removed the experimental moniker. In fact if you were to install today using 1755 the moniker has been removed already.

In your case I would recommend you doing the manual update on a non production machine first. Be warned you will have to go thru make menuconfig and select the correct choices. The experimental update-source program does this for you.


Sorry


Tom


btw just did an update-source on one of our prox machines with a similar version of asterisk to current and it works fine. This prox vm was created with the ISO file however and does not run incredible.

 

[RTOMikey]

Boss is too cheap to buy a new box till Prove this works better than POTS, and the current box is not Hyper-V so no ISO unfortunately, just made and verified a new vzdump, re-installing to a test computer, and going to attempy a full update yum and all, see what happens, if no luck, then will go back to this one again and learn how to recompile by hand on the test container I guess. am actually very impressed with the ability og the old DL360 to handle asterisk in container alongside a full proxy sertver, 5 websites, EyeOS, and others, all without missing a beat. handles inbound trunbks for all 10 stores, corporate office, and the service center, as well as all external extensions to each of the above. Usinf Did4Sale inbound and google outbound for the moment, probably switching to didforsale exclusively once google stopsd being so generous

 

[ric9887]

I'm running 1.7.5.6, asterisk 1.8.4 and got a memory leak somewhere as what was left on the screen was showing an out of memory message and the asterisk process had closed.
Im running on a VM - 32bit versions.

I don't know much about troubleshooting a memory leak, so will have a revert back to 1.6 maybe if it keeps happening.

 

[wardmundy]

For next steps, see this thread.