wikipbx

I've done that yet to avoid a segmentation fault, as you can see in ESL.so.

[root@wikipbx python]# ldd _ESL.so
libpython2.6.so.1.0 => /opt/python2.6/lib/libpython2.6.so.1.0 (0x00002ad1010bf000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00002ad10146e000)
libm.so.6 => /lib64/libm.so.6 (0x00002ad10176e000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002ad1019f2000)
libc.so.6 => /lib64/libc.so.6 (0x00002ad101c00000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00002ad101f57000)
libdl.so.2 => /lib64/libdl.so.2 (0x00002ad102173000)
libutil.so.1 => /lib64/libutil.so.1 (0x00002ad102377000)
/lib64/ld-linux-x86-64.so.2 (0x00002ad100c7a000)

OK, I give up. What's the answer? :)

How are your python skills? If we tell you to "create a trivial wsgi script which tries to make an ESL connection", could you handle it? Let me know and I will elaborate.

I'm a complet newbie in python; if you could help me on that script and how to execute it, it would be great.

Lluís

I've been able to execute this from python console:

con=ESL.ESLconnection("127.0.0.1","8021","ClueCon")
esl = con.sendRecv('api sofia status')
print(esl.getBody())

Name Type Data State

external profile sip:612.35.61.271|aifos_dom#612.35.61.271|aifos_dom:5060 RUNNING (0)
ticsolutions.lan alias external ALIASED

1 profile 1 alias

So, it seems ESL is working fine.

I've been able to install all running ok on Debian Lenny, but our company is more used to Centos 5; I think is a problem related to httpd but I really don't know how to fix it.

I will try to follow this howto to fix apache problem:
http://www.freshblurbs.com/tutorial-installing-django-1-1-centos-5-4

Has anybody WikiPBX 0.8 running on Centos 5.4? Any help would be appreciated.

It could be useful to run the same code from apache process rather than from console. For example, put it in wikipbx.wsgi file. You should see the same message inside apache error log after viewing any wikibpx page. If it won't happen and you'll get hanging connections on all pages, then there's some problem between apache and ESL module.

There are people running wikipbx on centos, but none of the core developers do it. One of the users reported the same issues as you had, as I've mentioned before.

Thanks for reporting this.

If we find anything out on this we'll let you know.

I've tested ESL connection directly on wikipbx.wsgi and it doesn't work, it hangs forever!!

Can you check if adding this directive to apache config makes any difference:

WSGIApplicationGroup %{GLOBAL}

Put it near other WSGI configuration directives and restart apache.

I'll check your recommendation tomorrow.

Today, what I've found is that when I print(sys.executable) in wikipbx.wsgi it logs /usr/bin/python instead of /opt/python2.5/bin/python.

I've found this howto
http://chester.blog.br/archives/2010/04/howto-python-2-6-5-django-via-passenger-wsgi-at-dreamhost.html

and I've inserted next lines in wsgi script to change python executable path:

INTERP = "/opt/python2.5/bin/python"
if sys.executable != INTERP: os.execl(INTERP, INTERP, *sys.argv)

but it stops complaining "can't find mod_wsgi module"

Tomorrow more testing :-)

That approach looks like a really bad idea. You should set correct python executable with mod_wsgi configuration, not by forcing OS to replace already running process. See this message for some suggestions.

when I print sys.path from wikipbx.wsgi I get:
['/usr/src/wikipbx', '/usr/src/django', '/usr/src/freeswitch/libs/esl/python', '/opt/python2.5/lib/python2.5/site-packages/setuptools-0.6c11-py2.5.egg', '/opt/python2.5/lib/python2.5/site-packages/MySQL_python-1.2.2-py2.5-linux-x86_64.egg', '/opt/python2.5/lib/python2.5/site-packages/pytz-2008i-py2.5.egg', '/opt/python2.5/lib/python25.zip', '/opt/python2.5/lib/python2.5', '/opt/python2.5/lib/python2.5/plat-linux2', '/opt/python2.5/lib/python2.5/lib-tk', '/opt/python2.5/lib/python2.5/lib-dynload', '/opt/python2.5/lib/python2.5/site-packages']

So I've added a line in wikipbx.wsgi (as suggested in your link) to set sys.path[0:0], but it happens the same.

Presuming that:

  /home/toinbis/Desktop/programming/project/bin/python

is the Python you wanted used, what do you get when you run that and do:

  import sys
  print sys.prefix

Whatever the value of sys.prefix is for the Python you want used, add it as:

  WSGIPythonHome <value of sys.prefix>

Replacing <value of sys.prefix> as appropriate.

Do not set WSGIPythonExecutable in this case.

Alternatively, set:

  WSGIPythonExecutable /home/toinbis/Desktop/programming/project/bin/python

Do not set WSGIPythonHome in this case.

Please try that.

Tested and not working.