Error message after updating provider

[lehey]

Lately, I have regular messages like this one when I update a provider account:
"Warning: fsockopen(): unable to connect to localhost:5038 in /etc/inc/pbx.inc on line 163 Warning: fsockopen(): unable to connect to localhost:5038 in /etc/inc/pbx.inc on line 163"

When I reboot, everything goes back to normal. Any idea ? Do you need more info from my part ?
Thanks,
Yann

[zetaerre]

Hi,

I've the same problem.

Scenario:

Wrap 1e with 64Mb RAM and 32 Mb CF card.
Uptime 60 days, memory at 86%.
All system is up and ready, internal and external calls are ok.

Open the browser, point it to askoziaip and BANG... Asterisk die.
Out of memory?

Restarted, like never happened, all is running and up, internal/external phone calls, I mean it's ok.

What's your hardware?

[lehey]

Wrap 266MHz, 64MB memory and 1GB CF
Before updating to the latest version, no problem, but since V1.0 or 1.1, I have regular error messages like that, and Asterisk dies (from what I see in the providers page, no provider is registered. I do not even see a red icon showing that Asterisk is up but cannot register to the provider)
Yann

[lehey]

I have just checked the system log, and here is what I found:
"kernel: pid 154 (asterisk), uid 0, was killed: out of swap space"
before I reboot.
My thoughts are that the problem lies in one of the php script. Whenever I point to the log page, memory goes from 85-88% to 97-99%
Yann

[lehey]

Correction: memory goes to 99% only when opening pbx log, not system log.
Yann

[Michael]

I have a bad feeling the new log pagination and sorting code is to blame. Depending on how its resources are managed, it could be loading those huge logs into memory before splitting and sorting.

Are you also using the logging package?

[lehey]

Yes I use it, and after posting my last message, I was thinking of deleting it.
Yann

[lehey]

Ok, so I just deleted the package. Asterisk died right after that. Rebooted the board.
Memory was 81%
looked at the system log, then pbx log...
went back to the sumary screen: memory is still 81%
So I believe further investigation should be made on how memory is managed by the package. At least for now, as keeping a log across reboots is not critical for me but only on my wish list, I will not be afraid anymore that Asterisk could die whenever the kernel needs it. 
Thanks,
Yann

[giovanni.v]

I have a bad feeling the new log pagination and sorting code is to blame.

I've already looked at this code in the past but forgot to notify... i think a first optimization can be done modifyng the SQL in the main pagination function for cdr, display_calculate_pages_sqlite().
Now you retrieve all the rows/data in the cdr table to simply get/count the number of rows using "SELECT * FROM cdr...", This can be optimized using a "SELECT id FROM cdr..." or better "SELECT COUNT(id) FROM cdr...".
You can save a lot of memory this way, especially the latest may be a lot faster, try yourself...

[Michael]

Thanks for the info Iax, as usual you're on top of things

If you're able to submit any patches please do so. I did not write that code so, if you're already taken a look and understood it, you're at an advantage.

[giovanni.v]

If you're able to submit any patches please do so.

I will test it on a fresh install monday afternoon in the lab then mail to you if no problems arise.
I'm not sure can solve all the memory problems discussed here, only a big cut of "memory spyke" hitting the cdr gui page.

[osa2]

Don't know if it help you all. But I get the same error I guess.


Warning: fsockopen(): unable to connect to localhost:5038 in /etc/inc/pbx.inc on line 163 Warning: fsockopen(): unable to connect to localhost:5038 in /etc/inc/pbx.inc on line 163

Will disable the logging package do the fix?

[osa2]

Any solutions yet on this matter? As I'm expierincing this behaviour again.

Warning: fsockopen(): unable to connect to localhost:5038 in /etc/inc/pbx.inc on line 163 Warning:
I don't have the logging package installed. Please advice on this matter.