2.0Rc3 HTTP server keeps crashing

[Southcross]

I keep getting error messages on my console (will edit post/reply with message when it does it again, it will, has done it repeatedly), and the appliance stops responding to http/https access (so I can't pull logs before rebooting it).  It seems that the PBX isn't otherwise unaffected, but when I do any log monitoring and/or tweaking of settings its almost guaranteed to crash on me at some point.

[Mateusz Viste]

Hi,

I am using RC3 as well, and never observed such problem...
What's your browser? Have you tried with another one?
Can you provide some Askozia logs of the moment when the problem occured? (if you lose access to the log page when the problem happen, then you might configure an external syslog server to get logs)

[Southcross]

not brower dependant... haven't implemented a syslog server yet, soon, very soon

the console message(s) are as follows (to the best I can type wile looking over my shoulder):

Code:

sslwrap[1326]: segfault at dff1df68 ip 08049d14 sp bff1df40 error 6 in sslwrap[8048000+4000]
dahdi : Detected time shift.
dahdi : Detected time shift.

apparently its a failure of the ssl connection component... maybe disable "require https" mode will prevent the errors from appearing until the source can be discovered

[Mateusz Viste]

Code:

sslwrap[1326]: segfault at dff1df68 ip 08049d14 sp bff1df40 error 6 in sslwrap[8048000+4000]
dahdi : Detected time shift.
dahdi : Detected time shift.

apparently its a failure of the ssl connection component... maybe disable "require https" mode will prevent the errors from appearing until the source can be discovered

Yes, it's definitely a problem with sslwrap. The point of sslwrap is to take a normal (clear-text) HTTP connection, and wrap it into a SSL stream (HTTP over SSL, better known as "HTTPS").

The short-term solution will be indeed to disable the SSL support in Askozia. Apache itself is not faulty, so it should solve your issue.

[Michael]

https has already been disabled for 2.0.0's release. There is a ticket open on the bug tracker about its unstable behavior. The sslwrap component will need to be replaced (or debugged) before https is supported again.

[Southcross]

https has already been disabled for 2.0.0's release. There is a ticket open on the bug tracker about its unstable behavior. The sslwrap component will need to be replaced (or debugged) before https is supported again.

kewl, good to know... was driving me nuts and I didn't readily see any threads in the bug forum for the issue

[Michael]

The official bug ticket is here : https://wush.net/trac/askozia/ticket/88

[Mateusz Viste]

The sslwrap component will need to be replaced (or debugged) before https is supported again.

Hi,

Why now using simply stunnel? As far as I know, stunnel is very reliable (I am using it on a day-to-day production system without any problems yet), and it is very easy to setup.