wikipbx - new forum posts

Re: Install Issues Centos 5.4

Thu, 11 Mar 2010 17:44:48 +0000

mickey_mouse — can you make sure freeswitch is pulling the configuration from freeswitch?

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Thu, 11 Mar 2010 17:42:30 +0000

Should be no need to touch event_socket.conf.xml, wikipbx will serve that up dynamically. I double checked and the install docs don't mention anything about event_socket.conf.xml

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Thu, 11 Mar 2010 15:48:17 +0000

Make sure that freeswitch has correct event_socket.conf.xml file - it should be the same host/port/password as event socket config you have in the web interface. The same goes to xml_curl.conf.xml - it should be able to reach your server (described in install guide). If that doesn't help, be more specific and check if there are any related errors in freeswitch logs.

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Thu, 11 Mar 2010 12:06:04 +0000

got passed that one..

but having trouble getting extensions and SIP trunks to register

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Thu, 11 Mar 2010 11:17:34 +0000

That's not normal behavior. Could be something with your database. Do you use postgres or something else? Which version and driver (django supports 2 of them)?

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Thu, 11 Mar 2010 07:16:51 +0000

just one more question if I may..

every time i try to add a end point, it seems to hang ?

any ideas..

thanks again..

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Thu, 11 Mar 2010 05:04:21 +0000

not panic…

i rebooted the server and it is fine..

im in there..

i'll see how i go driving it..

thanks for all the help..

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Thu, 11 Mar 2010 04:52:42 +0000

well i started from scratch with a Debian VM and have it up and running..

can even see the web page..

but can not log in.. using the root user i have made ??

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Wed, 10 Mar 2010 08:28:57 +0000

It's described in mod_wsgi docs.

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Wed, 10 Mar 2010 03:13:34 +0000

starting from scratch again..

gee i love VM servers..

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Wed, 10 Mar 2010 01:09:47 +0000

I just googled that error and got this..

http://discuss.joyent.com/viewtopic.php?id=11174

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Wed, 10 Mar 2010 00:50:44 +0000

I completely forgot about this document:

http://www.venkysblog.com/2009/12/centos-python-wsgi-dango/

which was linked from the installation manual and centos-install-notes but it was kind of buried.

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Wed, 10 Mar 2010 00:49:49 +0000

I have remd the mod_python out.. now new error..

i'll get thorough this if i dont die of old age first…

error-----—-

[Errno 13] Permission denied: '/root/.python-eggs'

The Python egg cache directory is currently set to:

/root/.python-eggs

is there any easy way to fix this ??

by the way i really appreciate the help..

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Wed, 10 Mar 2010 00:45:34 +0000

If you need both, check out http://wikipbx.subwiki.com/install-mod-wgi#toc9 Otherwise just get rid of mod_python if you don't need it for anything else.

No rpm or deb packages yet… kind of hoping for someone with a lot of experience packaging python web apps to come along and offer some help.

The thing is the user base seems to be about 50/50 split among Ubuntu/Deb and CentOS, so it would be nice to have a solution that worked on both.

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Wed, 10 Mar 2010 00:10:28 +0000

well it is loading both..
has anyone made a rpm for all this ??

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Tue, 09 Mar 2010 23:43:53 +0000

Ummm.. that looks way off the mark.

For starters you need to use mod_wsgi instead of mod_python

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Tue, 09 Mar 2010 23:24:38 +0000

close enough..

I have included the settings in the apache.conf..

it seems that the web server is not reading !! the python files even though it is loading the module..

this is from my python config..

LoadModule python_module modules/mod_python.so

Override type-map handler for /var/www/manual

SetHandler default-handler

is that correct ?

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Tue, 09 Mar 2010 22:33:19 +0000

Did you do the steps listed here?

http://wikipbx.subwiki.com/configure-wikipbx-mod-wsgi

You should see a page with a wikipbx logo and a link that says "add root user"

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Tue, 09 Mar 2010 22:14:36 +0000

there is nothing else on the page..
if i just use http://host/ i get the apache test page..
there doesn't seem to be a default page set..
what should the default page be ?

thanks for this..

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Tue, 09 Mar 2010 13:04:07 +0000

Is there anything else on that page besides those 3 lines?

Btw, you're supposed to access just http://host/ , wikipbx.wsgi is mod_wsgi handler that isn't exposed in the URLs.

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Tue, 09 Mar 2010 09:57:38 +0000

that is what is displayed in the browser when trying to access http://host/wikipbx.wsgi

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Tue, 09 Mar 2010 08:24:27 +0000

You've pasted only a piece of code from wikipbx, not the actual error message that you've had.

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Tue, 09 Mar 2010 04:48:52 +0000

PS is there anyone the can install this professionally ?

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Tue, 09 Mar 2010 03:39:43 +0000

well i have progressed, i have a new error..

I would like to help.. Generally dont in fear of leading someone astray..

New Error..

os.environ['DJANGO_SETTINGS_MODULE'] = 'wikipbx.settings'
import django.core.handlers.wsgi
application = django.core.handlers.wsgi.WSGIHandler()

any ideas anyone ?

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Mon, 08 Mar 2010 23:13:37 +0000

Unfortunately no ..

My advice would be to go through the installation manual and refer to the forum post that you mentioned to do things the Centos way when appropriate. (eg, install python packages from source rather than relying on apt-get package manager).

Any contributions on the forum or wiki you could make for other Centos users would be greatly appreciated .. its definitely one of the Linux flavors we want to support as much as possible.

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Freeswitch SVN (1.0.2) WikiPBX SVN (61) CentOS 5.1 Installation Instructions

Mon, 08 Mar 2010 23:09:08 +0000

Update: as of version 0.8, wikipbx requires python 2.5 or later

Forum category: WikiPBX / General
Forum thread: Freeswitch SVN (1.0.2) WikiPBX SVN (61) CentOS 5.1 Installation Instructions

Re: Great work you guys!

Mon, 08 Mar 2010 23:06:56 +0000

Checked into svn in the contrib/solo9300 directory. Thanks again for the contribution!

Forum category: WikiPBX / General
Forum thread: Great work you guys!

Re: Install Issues Centos 5.4

Mon, 08 Mar 2010 22:52:05 +0000

is there any easy to follow install instruction for Centos 5 ?

regards Fred

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Install Issues Centos 5.4

Mon, 08 Mar 2010 22:32:53 +0000

This version was written for an older version of wikipbx, in v.0.8 that script isn't needed and doesn't exist.

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Install Issues Centos 5.4

Mon, 08 Mar 2010 22:20:00 +0000

I have followed the install procedure at ' http://wikipbx.subwiki.com/forum/t-115012/freeswitch-svn-1-0-2-wikipbx-svn-61-centos-5-1-installation-instructions '
and after completing there is no ' initserver.py '
I would greatly appreciate some help..

thanks in advance Fred

Forum category: WikiPBX / Technical Support
Forum thread: Install Issues Centos 5.4

Re: Upgrading data from 0.5 to 0.8 Not Working

Thu, 25 Feb 2010 18:49:21 +0000

you should add a domain name for your account (tenant). It's possible to use the ip as the domain name, but that's discouraged.

By the way this can/should be done after the successful import

Forum category: WikiPBX / Technical Support
Forum thread: Upgrading data from 0.5 to 0.8 Not Working

Re: Upgrading data from 0.5 to 0.8 Not Working

Thu, 25 Feb 2010 06:12:34 +0000

OK it looks like the export had a bug and didn't include the userprofile attribute for one endpoint.

The easiest thing would be to delete this endpoint:

or hack in a userprofile, eg:

Does that fix it?

Also don't miss this warning — "Warning: no domain for profile, using name. You will need to fix this" — you should add a domain name for your account (tenant). It's possible to use the ip as the domain name, but that's discouraged.

Forum category: WikiPBX / Technical Support
Forum thread: Upgrading data from 0.5 to 0.8 Not Working

Re: Upgrading data from 0.5 to 0.8 Not Working

Thu, 25 Feb 2010 01:24:27 +0000

Hi again,

Sorry for the delay. I updated to svn r251 now.

Here is the new log snip. I believe it is not liking the endpoints that I have that do not have a web user associated with them. It goes through with the import and dies with the following:

 [Fri Feb 19 08:38:56 2010] [error] Will use sip profile: sip profile: MY.IP.IS.HERE:5060 [Fri Feb 19 08:38:56 2010] [error] elt: wikipbx [Fri Feb 19 08:38:56 2010] [error] account:  [Fri Feb 19 08:38:56 2010] [error] account name: MyAccountNameHere [Fri Feb 19 08:38:56 2010] [error] Warning: no domain for profile, using name. You will need to fix this [Fri Feb 19 08:38:56 2010] [error] userprofile:  [Fri Feb 19 08:38:56 2010] [error] email: info@example.com [Fri Feb 19 08:38:56 2010] [error] account: MyAccountNameHere [Fri Feb 19 08:38:56 2010] [error] userprofile:  [Fri Feb 19 08:38:56 2010] [error] email: steffler@example.com [Fri Feb 19 08:38:56 2010] [error] account: MyAccountNameHere [Fri Feb 19 08:38:56 2010] [error] userprofile:  [Fri Feb 19 08:38:56 2010] [error] email: barry@example.com [Fri Feb 19 08:38:56 2010] [error] account: MyAccountNameHere [Fri Feb 19 08:38:56 2010] [error] endpoint:  [Fri Feb 19 08:38:56 2010] [error] account: MyAccountNameHere [Fri Feb 19 08:38:56 2010] [error] endpoint:  [Fri Feb 19 08:38:56 2010] [error] account: MyAccountNameHere [Fri Feb 19 08:38:56 2010] [error] endpoint:  [Fri Feb 19 08:38:56 2010] [error] account: MyAccountNameHere [Fri Feb 19 08:38:56 2010] [error] endpoint:  [Fri Feb 19 08:38:56 2010] [error] account: MyAccountNameHere [Fri Feb 19 08:38:56 2010] [error] User matching query does not exist. [Fri Feb 19 08:38:56 2010] [error] Got exception, rolling back [Fri Feb 19 08:44:26 2010] [notice] caught SIGTERM, shutting down

Forum category: WikiPBX / Technical Support
Forum thread: Upgrading data from 0.5 to 0.8 Not Working

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Thu, 25 Feb 2010 01:17:08 +0000

I didn't realize it was editable by anyone. I will try to add what I learned from my experiences, and maybe I can prepare a page about FreeBSD.

Thanks!

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Upgrading data from 0.5 to 0.8 Not Working

Sat, 20 Feb 2010 02:57:08 +0000

If you were already using the 0.8 branch, then you'll just need to svn up to r251

Forum category: WikiPBX / Technical Support
Forum thread: Upgrading data from 0.5 to 0.8 Not Working

Re: Upgrading data from 0.5 to 0.8 Not Working

Sat, 20 Feb 2010 02:56:14 +0000

Please switch to the 0.8 branch using these instructions: zip2branch

Then retry your test and post the log output. Hopefully from that it will be apparent.

Are there any statements that say: "looking up user with email: x" with no corresponding
statements: "creating user with email: x" (eg, user with email x was never created and so lookups fail).

The "creating user with email" statements should appear earlier in the log file

Forum category: WikiPBX / Technical Support
Forum thread: Upgrading data from 0.5 to 0.8 Not Working

Re: Upgrading data from 0.5 to 0.8 Not Working

Thu, 18 Feb 2010 22:38:39 +0000

Ah … here's the key line:

 Got exception, rolling back

I think we should have made that a little louder ;)

Give us credit though .. everything was done in a transaction, and so when it encountered an error, it rolled back the transaction and did NOT leave you in a half-upgraded, half-working state. Instead everything got rolled back so its as if the failed import attempt had never happened. (Why don't more coders do this?)

And thank you for posting the installation log! It's nice having smart users, sure makes our job easier. I have to say, having such a heinous installation process has such a nice side effect!

Anyway .. to get to the bottom of this error we will need to update the code to print out the detailed error message. How did you install the code?

0.8 zip file
0.8 branch
Other branch (trunk?)

Let me know and we'll go from there

Forum category: WikiPBX / Technical Support
Forum thread: Upgrading data from 0.5 to 0.8 Not Working

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Thu, 18 Feb 2010 20:04:46 +0000

So, the new WikiPBX loaded successfully after all of that! :D

Excellent!

I will start a new thread now on another problem I have ran into…;-)

Saw that one, will try to get back to you tonight. That import script has been tested (I used it), I'm surprised it's not working. We'll have to debug it. (PS: the profile name doesn't matter)

I wouldn't have missed this if the formatting were consistent. Nothing major just thought I'd mention it.

Yeah, that was badly done, but now it's fixed — thanks for pointing it out. As Stas mentioned you can also update the wiki yourself, but mentioning it in the forum is fine too. The important thing is that it gets fixed and the next user has an improved experience.

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Thu, 18 Feb 2010 17:42:41 +0000

There's nothing stopping you from making our documentation better - it's a wiki, after all.

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Upgrading data from 0.5 to 0.8 Not Working

Thu, 18 Feb 2010 17:25:40 +0000

After a lengthy difficult process upgrading my WikiPBX to 0.8, I have finally gotten the new version working with a lot of help from tleyden and stas_shtin. Thanks guys! :)

I now see the WikiPBX [ ADD ROOT ] option on the main page of WikiPBX after I load it in my browser. I click Add Root, and I fill in all the information required. I use the same info I had on my root login on the old version of WikiPBX.

I'm confused about the migration instructions from here onward. The website says "Create a sip profile if you have not done so already". Does this mean I create a SIP Profile which matches the information of the profiles from the old WikiPBX I need to import? Should I name it the same? Because I did name it the same as my old profile in WikiPBX 0.5, and it seems to work correctly to do so, with no complaints.

However, after I select the XML file I put into /tmp, and select the new profile I created, then click the Initiate Import button, it says "Import Successful" or something like that, and that I should be able to see the information in the GUI now. However, I don't see any information at all, and WikiPBX is still blank of other users (that were in the XML export) as well as blank of the stuff I imported (either as a new profile or as part of the one that I created).

Dialplan, users, etc, all seem to be blank as if they are new, without any info successfully imported. Here is what I saw in the Apache logfile during the import process (edited for privacy concerns):

 [Thu Feb 18 16:55:47 2010] [notice] Apache/2.2.11 (FreeBSD) mod_ssl/2.2.11 OpenSSL/0.9.8e mod_wsgi/3.1 Python/2.5.4 PHP/5.2.9 configured -- resuming normal operations [Thu Feb 18 16:56:54 2010] [error] restart_profiles called [Thu Feb 18 16:56:54 2010] [error] get_fs_connections() [Thu Feb 18 16:56:54 2010] [error] no eventsockets [Thu Feb 18 16:56:54 2010] [error] get_fs_connections() done [Thu Feb 18 16:57:20 2010] [error] restart_profiles called [Thu Feb 18 16:57:20 2010] [error] get_fs_connections() [Thu Feb 18 16:57:20 2010] [error] 1 eventsockets [Thu Feb 18 16:57:20 2010] [error] creating eslconnection [Thu Feb 18 16:57:58 2010] [error] Will use sip profile: sip profile: MY.IP.IS.HERE:5060 [Thu Feb 18 16:57:58 2010] [error] elt: wikipbx [Thu Feb 18 16:57:58 2010] [error] account:  [Thu Feb 18 16:57:58 2010] [error] account name: MYPROFILENAME [Thu Feb 18 16:57:58 2010] [error] Warning: no domain for profile, using name. You will need to fix this [Thu Feb 18 16:57:58 2010] [error] userprofile:  [Thu Feb 18 16:57:58 2010] [error] email: email@address.here [Thu Feb 18 16:57:58 2010] [error] account: MYPROFILENAME [Thu Feb 18 16:57:58 2010] [error] userprofile:  [Thu Feb 18 16:57:58 2010] [error] email: myname@admin.account.com [Thu Feb 18 16:57:58 2010] [error] account: MYPROFILENAME [Thu Feb 18 16:57:58 2010] [error] userprofile:  [Thu Feb 18 16:57:58 2010] [error] email: friend@gmail.com [Thu Feb 18 16:57:58 2010] [error] account: MYPROFILENAME [Thu Feb 18 16:57:58 2010] [error] endpoint:  [Thu Feb 18 16:57:58 2010] [error] account: MYPROFILENAME [Thu Feb 18 16:57:58 2010] [error] endpoint:  [Thu Feb 18 16:57:58 2010] [error] account: MYPROFILENAME [Thu Feb 18 16:57:58 2010] [error] endpoint:  [Thu Feb 18 16:57:58 2010] [error] account: MYPROFILENAME [Thu Feb 18 16:57:58 2010] [error] User matching query does not exist. [Thu Feb 18 16:57:58 2010] [error] Got exception, rolling back [Thu Feb 18 16:59:04 2010] [error] restart_profiles called [Thu Feb 18 16:59:04 2010] [error] get_fs_connections() [Thu Feb 18 16:59:04 2010] [error] 1 eventsockets [Thu Feb 18 16:59:04 2010] [error] creating eslconnection [Thu Feb 18 17:00:30 2010] [error] restart_profiles called [Thu Feb 18 17:00:30 2010] [error] get_fs_connections() [Thu Feb 18 17:00:30 2010] [error] 1 eventsockets [Thu Feb 18 17:00:30 2010] [error] creating eslconnection [Thu Feb 18 17:00:46 2010] [notice] caught SIGTERM, shutting down

Is there yet another glaring thing I am doing wrong here? :-) I have confirmed that the export file does in fact contain the XML from the old installation, and it is in the correct location. Furthermore, I receive no errors or complaints during the import procedure except if I turn Apache debug logging on, just blank end results. Help would be greatly appreciated.

Forum category: WikiPBX / Technical Support
Forum thread: Upgrading data from 0.5 to 0.8 Not Working

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Thu, 18 Feb 2010 17:14:31 +0000

stas_shtin, That would have been great if it were linked on the mod_wsgi installation instructions page… Can a link be added for other users like me who have never heard of mod_wsgi before attempting to get it working with WikiPBX?

Sorry for all the confusion, I appreciate the hands-on help you have provided.

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Thu, 18 Feb 2010 17:12:33 +0000

Ahh, I didn't see that additional step (make pymod). I have ran gmake pymod and I had to make some edits to the Makefile, even though I am running an SVN build of FreeSWITCH from last week.

So, the new WikiPBX loaded successfully after all of that! :D

Just a suggestion: It would be great if the line in the Wiki that has the "Run make pymod" text was not just a bullet point, as it is a crucial step maybe it should have the same treatment as the "Start Apache2" section below it (where the command the user is meant to type is in a code/PRE block and not just part of a point form note.) I wouldn't have missed this if the formatting were consistent. Nothing major just thought I'd mention it.

I will start a new thread now on another problem I have ran into…;-)

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Thu, 18 Feb 2010 13:07:35 +0000

Btw, mod_wsgi installation inssues page describes how you should build mod_python and mod_wsgi in order for them to coexist without problems.

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Thu, 18 Feb 2010 10:36:27 +0000

Older versions of wikipbx didn't use ESL (Freeswitch's Event Socket Library). It looks like you haven't compiled it. ESL.py is the python wrapper that is present in Freeswitch sources, but it uses _ESL.so shared library that needs to be compiled first.

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Thu, 18 Feb 2010 02:44:23 +0000

In my case I have the following in my apache config:

 WSGIPythonPath [snip]:/usr/src/freeswitch_13501/libs/esl/python

and when I list contents of /usr/src/freeswitch_13501/libs/esl/python I see

 -rw-r--r-- 1 tleyden src 4.8K 2009-05-28 19:08 ESL.py -rwxr-xr-x 1 tleyden src 199K 2009-07-10 12:16 _ESL.so

How is your setup different? (aside from the fact you are hopefully using a new fs :)

Did you run "make pymod" as described here: http://wikipbx.subwiki.com/installation-manual-0-8#toc35

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Thu, 18 Feb 2010 01:08:53 +0000

I had to disable mod_python, which was enabled on my Apache because I use it on some of my other virtual hosted sites.

Disabling mod_python made the WSGI connection work.

HOWEVER… :-)

Now I get this error when I hit my domain in the browser:

 ViewDoesNotExist at / Could not import wikipbx.wikipbxweb.views. Error was: No module named _ESL Request Method: GET Request URL: http://MYHOSTNAMEHERE/ Exception Type: ViewDoesNotExist Exception Value: Could not import wikipbx.wikipbxweb.views. Error was: No module named _ESL Exception Location: /usr/src/django/django/core/urlresolvers.py in _get_callback, line 128

When I go into a Python terminal with the PYTHONPATH set to the new one that works :), I see this happening when I try to import esl:

 # python Python 2.5.4 (r254:67916, Nov 5 2009, 18:40:44) [GCC 4.2.1 20070719 [FreeBSD]] on freebsd7 Type "help", "copyright", "credits" or "license" for more information. >>> import ESL Traceback (most recent call last): File "", line 1, in  File "/usr/src/freeswitch/libs/esl/python/ESL.py", line 7, in  import _ESL ImportError: No module named _ESL

As you can see, it's reading the PYTHONPATH and seeing /usr/src/freeswitch/libs/esl/python/ESL.py, but something is causing it not to load it correctly. This is the exact same ESL.py and the exact same django, Python, and FS installation that works with the older WikiPBX.

Any ideas on this one? I really appreciate your help so far! I'm almost there…

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Thu, 18 Feb 2010 00:44:11 +0000

OK, editing the PYTHONPATH as you described caused the ./manage.py to work correctly! Thanks for that tip!

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Tue, 16 Feb 2010 17:00:34 +0000

I would try to get a "hello world" python script running under mod_wsgi and see if that segfaults. If you google around or check the mod_wsgi docs you can probably find one.

I've personally never seen that happen.. so I'm not sure what to advise.

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Mon, 15 Feb 2010 16:51:39 +0000

The short answer is to change your PYTHONPATH from:

 PYTHONPATH=/usr/src:/usr/src/freeswitch/scripts/python:/usr/local/lib/python2.5/site-packages

 PYTHONPATH=/usr/src/wikipbx0.8:/usr/src/freeswitch/scripts/python:/usr/local/lib/python2.5/site-packages

The part of my PYTHONPATH that says /usr/src (the first entry) is where wikipbx is. There is /usr/src/wikipbx and /usr/src/wikipbx0.8 there. The installation instructions said I could put them side by side with eachother. My PYTHONPATH worked for the old version, and the new version is still located in the PYTHONPATH because it is in /usr/src.

You only want to have the new wikipbx0.8 on your PYTHONPATH. (see above)

The docs need to be updated to clarify this, but please try the change mentioned above and report new behavior with the syncdb command. At this point it should now pickup the correct settings.py and we can go from there.

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Mon, 15 Feb 2010 16:29:00 +0000

I didn't get an import error, and there aren't any symlinks in site-packages besides the one to /usr/src/django (which is the same version of django the new version depends on).

The part of my PYTHONPATH that says /usr/src (the first entry) is where wikipbx is. There is /usr/src/wikipbx and /usr/src/wikipbx0.8 there. The installation instructions said I could put them side by side with eachother. My PYTHONPATH worked for the old version, and the new version is still located in the PYTHONPATH because it is in /usr/src.

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Mon, 15 Feb 2010 09:44:26 +0000

It chose to run against the old DB, potentially based on my PYTHONPATH but I don't see what's wrong with it.

There's no path to wikipbx in your PYTHONPATH, that's definitely wrong :-) You didn't add it, so the only module that could be imported is the old version that you've symlinked in python's site-packages directory. And if there was no symlink in site-packages you'd probably get an ImportError.

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Mon, 15 Feb 2010 01:33:03 +0000

tleyden,

I managed to get more debugging info out of apache. Here is what is happening when it tries to run the WSGI script:

 [Mon Feb 15 01:30:00 2010] [info] mod_wsgi (pid=61553): Attach interpreter ''. [Mon Feb 15 01:30:00 2010] [info] mod_wsgi (pid=61553): Adding '/usr/src/wikipbx0.8' to path. [Mon Feb 15 01:30:00 2010] [info] mod_wsgi (pid=61553): Adding '/usr/src/django' to path. [Mon Feb 15 01:30:00 2010] [info] mod_wsgi (pid=61553): Adding '/usr/src/freeswitch/libs/esl/python' to path. [Mon Feb 15 01:30:00 2010] [debug] proxy_util.c(1801): proxy: grabbed scoreboard slot 1 in child 61553 for worker proxy:reverse [Mon Feb 15 01:30:00 2010] [debug] proxy_util.c(1820): proxy: worker proxy:reverse already initialized [Mon Feb 15 01:30:00 2010] [debug] proxy_util.c(1914): proxy: initialized single connection worker 1 in child 61553 for (*) [Mon Feb 15 01:30:05 2010] [info] mod_wsgi (pid=61551): Create interpreter 'MYHOSTNAMEHERE|'. [Mon Feb 15 01:30:05 2010] [info] mod_wsgi (pid=61551): Adding '/usr/src/wikipbx0.8' to path. [Mon Feb 15 01:30:05 2010] [info] mod_wsgi (pid=61551): Adding '/usr/src/django' to path. [Mon Feb 15 01:30:05 2010] [info] mod_wsgi (pid=61551): Adding '/usr/src/freeswitch/libs/esl/python' to path. [Mon Feb 15 01:30:05 2010] [notice] child pid 61551 exit signal Segmentation fault (11) [Mon Feb 15 01:30:05 2010] [info] mod_wsgi (pid=61689): Attach interpreter ''. [Mon Feb 15 01:30:05 2010] [info] mod_wsgi (pid=61689): Adding '/usr/src/wikipbx0.8' to path. [Mon Feb 15 01:30:05 2010] [info] mod_wsgi (pid=61689): Adding '/usr/src/django' to path. [Mon Feb 15 01:30:05 2010] [info] mod_wsgi (pid=61689): Adding '/usr/src/freeswitch/libs/esl/python' to path. [Mon Feb 15 01:30:05 2010] [debug] proxy_util.c(1801): proxy: grabbed scoreboard slot 1 in child 61689 for worker proxy:reverse [Mon Feb 15 01:30:05 2010] [debug] proxy_util.c(1820): proxy: worker proxy:reverse already initialized [Mon Feb 15 01:30:05 2010] [debug] proxy_util.c(1914): proxy: initialized single connection worker 1 in child 61689 for (*)

Note the segfault that is happening there. I believe this is what is causing the blank screen in my browser upon loading. But… I have no idea how to fix that! According to the mod_wsgi FAQ here http://code.google.com/p/modwsgi/wiki/FrequentlyAskedQuestions, I have to essentially rebuild all my Apache modules to make sure that nothing in any of the older modules on my system is linked against a different version of a library than what is currently on my system. Not a lot of fun. :(

I guess I will get back to the other problem (my PYTHONPATH?) after I fix my apache up.

Steve

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Mon, 15 Feb 2010 00:59:56 +0000

stas_shtin: Is that something that needs to be added to the upgrading guide to help others who may run into this issue? Because I wasn't explicitly running it on the old database. I was running it in the new directory of a new installation of 0.8 and the settings.py in that directory had correct DB info for the new database. It chose to run against the old DB, potentially based on my PYTHONPATH but I don't see what's wrong with it.

UPDATE: OK, since upgrading side by side didn't work, I made some backups and attempted an "in place" upgrade.

I followed the "in place" upgrade instructions on the installation guide exactly, edited WSGIPythonPath in my apache config, dropped/re-created the DB, re-ran the manage.py (it created a new DB structure this time, asked for django auth setup, etc as per the Installation guide). Still, after restarting Apache, I get a blank page in my browser, with no errors in any logs.

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Mon, 15 Feb 2010 00:37:28 +0000

So syncdb works fine, you just where running it on existing database and it didn't have to change anything.

In order to run the new code you should include path to wikiPBX 0.8 in the head of your PYTHONPATH variable when you run ./manage.py commands as well as WSGIPythonPath in your apache config.

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Sun, 14 Feb 2010 23:57:29 +0000

Just an update, I have confirmed that the manage.py is using the old installations' settings.py by running ./manage.py diffsettings. It revealed that the DB settings were the ones from the 0.5 settings.py file.

Where do I go from here?

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Sun, 14 Feb 2010 23:55:44 +0000

Here are the results:

 BEGIN; CREATE TABLE "wikipbxweb_eventsocketconfig" ( "id" serial NOT NULL PRIMARY KEY, "server_id" integer NOT NULL, "listen_ip" varchar(25) NOT NULL, "listen_port" integer CHECK ("listen_port" >= 0) NOT NULL, "password" varchar(25) NOT NULL ); CREATE TABLE "wikipbxweb_sofiagateway" ( "id" serial NOT NULL PRIMARY KEY, "name" varchar(100) NOT NULL, "account_id" integer NOT NULL, "username" varchar(25) NOT NULL, "password" varchar(25) NOT NULL, "proxy" varchar(50) NOT NULL, "register" boolean NOT NULL, "direction" varchar(20) NOT NULL, "extension" varchar(50) NOT NULL, "realm" varchar(50) NOT NULL, "from_domain" varchar(50) NOT NULL, "expire_seconds" integer CHECK ("expire_seconds" >= 0) NULL, "retry_seconds" integer CHECK ("retry_seconds" >= 0) NULL, "caller_id_in_from" boolean NOT NULL, "max_concurrent" integer CHECK ("max_concurrent" >= 0) NOT NULL, "in_progress_calls" integer CHECK ("in_progress_calls" >= 0) NULL ); CREATE TABLE "wikipbxweb_account" ( "id" serial NOT NULL PRIMARY KEY, "name" varchar(50) NOT NULL, "server_id" integer NOT NULL, "enabled" boolean NOT NULL, "ext_rtp_ip" varchar(50) NOT NULL, "ext_sip_ip" varchar(50) NOT NULL, "domain" varchar(50) NOT NULL, "accept_blind_reg" boolean NOT NULL, "sip_port" integer CHECK ("sip_port" >= 0) NOT NULL, UNIQUE ("sip_port", "ext_sip_ip") ); ALTER TABLE "wikipbxweb_sofiagateway" ADD CONSTRAINT account_id_refs_id_7f3f62da9c27bf6d FOREIGN KEY ("account_id") REFERENCES "wikipbxweb_account" ("id") DEFERRABLE INITIALLY DEFERRED; CREATE TABLE "wikipbxweb_endpoint" ( "id" serial NOT NULL PRIMARY KEY, "userid" varchar(100) NOT NULL, "password" varchar(100) NOT NULL, "account_id" integer NOT NULL REFERENCES "wikipbxweb_account" ("id") DEFERRABLE INITIALLY DEFERRED, "userprofile_id" integer NULL, "is_registered" boolean NOT NULL, "last_registered" timestamp with time zone NULL, "contact_addr" varchar(100) NOT NULL ); CREATE TABLE "wikipbxweb_voicemailtrigger" ( "id" serial NOT NULL PRIMARY KEY, "name" varchar(100) NOT NULL, "callerid" varchar(100) NOT NULL ); CREATE TABLE "wikipbxweb_extension" ( "id" serial NOT NULL PRIMARY KEY, "account_id" integer NOT NULL REFERENCES "wikipbxweb_account" ("id") DEFERRABLE INITIALLY DEFERRED, "dest_num" varchar(75) NOT NULL, "desc" varchar(250) NOT NULL, "actions_xml" text NOT NULL, "is_temporary" boolean NOT NULL, "endpoint_id" integer NULL REFERENCES "wikipbxweb_endpoint" ("id") DEFERRABLE INITIALLY DEFERRED, "priority_position" integer NOT NULL ); CREATE TABLE "wikipbxweb_emailconfig" ( "id" serial NOT NULL PRIMARY KEY, "server_id" integer NOT NULL, "account_id" integer NULL REFERENCES "wikipbxweb_account" ("id") DEFERRABLE INITIALLY DEFERRED, "from_email" varchar(100) NOT NULL, "email_host" varchar(100) NOT NULL, "email_port" integer CHECK ("email_port" >= 0) NOT NULL, "auth_user" varchar(100) NOT NULL, "auth_password" varchar(100) NOT NULL, "use_tls" boolean NOT NULL ); CREATE TABLE "wikipbxweb_soundclip" ( "id" serial NOT NULL PRIMARY KEY, "account_id" integer NOT NULL REFERENCES "wikipbxweb_account" ("id") DEFERRABLE INITIALLY DEFERRED, "name" varchar(100) NOT NULL, "desc" varchar(100) NOT NULL ); CREATE TABLE "wikipbxweb_phonecontact" ( "id" serial NOT NULL PRIMARY KEY, "name" varchar(100) NOT NULL, "number" varchar(100) NOT NULL, "ext" varchar(20) NOT NULL, "userprofile_id" integer NULL, "is_explicit" boolean NOT NULL, "is_private" boolean NOT NULL ); CREATE TABLE "wikipbxweb_server" ( "id" serial NOT NULL PRIMARY KEY, "application_root" varchar(75) NOT NULL, "http_port" integer CHECK ("http_port" >= 0) NOT NULL, "ip" varchar(24) NOT NULL, "fqdn" varchar(100) NOT NULL ); ALTER TABLE "wikipbxweb_eventsocketconfig" ADD CONSTRAINT server_id_refs_id_3f40fdf16445b95a FOREIGN KEY ("server_id") REFERENCES "wikipbxweb_server" ("id") DEFERRABLE INITIALLY DEFERRED; ALTER TABLE "wikipbxweb_account" ADD CONSTRAINT server_id_refs_id_4b9a60cc52c7a6a4 FOREIGN KEY ("server_id") REFERENCES "wikipbxweb_server" ("id") DEFERRABLE INITIALLY DEFERRED; ALTER TABLE "wikipbxweb_emailconfig" ADD CONSTRAINT server_id_refs_id_59aed97c3df98a27 FOREIGN KEY ("server_id") REFERENCES "wikipbxweb_server" ("id") DEFERRABLE INITIALLY DEFERRED; CREATE TABLE "wikipbxweb_serverlog" ( "id" serial NOT NULL PRIMARY KEY, "server_id" integer NOT NULL REFERENCES "wikipbxweb_server" ("id") DEFERRABLE INITIALLY DEFERRED, "account_id" integer NULL REFERENCES "wikipbxweb_account" ("id") DEFERRABLE INITIALLY DEFERRED, "logtime" timestamp with time zone NULL, "message" text NOT NULL ); CREATE TABLE "wikipbxweb_completedcall" ( "id" serial NOT NULL PRIMARY KEY, "account_id" integer NOT NULL REFERENCES "wikipbxweb_account" ("id") DEFERRABLE INITIALLY DEFERRED, "uuid" varchar(100) NOT NULL, "caller_id_number" varchar(100) NOT NULL, "destination_number" varchar(100) NOT NULL, "chan_name" varchar(100) NOT NULL, "answered_time" timestamp with time zone NOT NULL, "hangup_time" timestamp with time zone NOT NULL, "cdr_xml" text NOT NULL ); CREATE TABLE "wikipbxweb_voicemaillabel" ( "id" serial NOT NULL PRIMARY KEY, "name" varchar(100) NOT NULL, "incompatible_labels" varchar(200) NOT NULL ); CREATE TABLE "wikipbxweb_ivr" ( "id" serial NOT NULL PRIMARY KEY, "name" varchar(100) NOT NULL, "language_ext" varchar(20) NOT NULL, "account_id" integer NULL REFERENCES "wikipbxweb_account" ("id") DEFERRABLE INITIALLY DEFERRED ); CREATE TABLE "wikipbxweb_voicemail" ( "id" serial NOT NULL PRIMARY KEY, "account_id" integer NOT NULL REFERENCES "wikipbxweb_account" ("id") DEFERRABLE INITIALLY DEFERRED, "userprofile_id" integer NULL, "date_listened" timestamp with time zone NULL, "uuid" varchar(100) NOT NULL ); CREATE TABLE "wikipbxweb_userprofile" ( "user_id" integer NOT NULL PRIMARY KEY REFERENCES "auth_user" ("id") DEFERRABLE INITIALLY DEFERRED, "account_id" integer NOT NULL REFERENCES "wikipbxweb_account" ("id") DEFERRABLE INITIALLY DEFERRED, "mailbox" varchar(40) NOT NULL, "vm_password" varchar(100) NOT NULL ); ALTER TABLE "wikipbxweb_endpoint" ADD CONSTRAINT userprofile_id_refs_user_id_18780d21781a98bf FOREIGN KEY ("userprofile_id") REFERENCES "wikipbxweb_userprofile" ("user_id") DEFERRABLE INITIALLY DEFERRED; ALTER TABLE "wikipbxweb_phonecontact" ADD CONSTRAINT userprofile_id_refs_user_id_256522f5346dfd26 FOREIGN KEY ("userprofile_id") REFERENCES "wikipbxweb_userprofile" ("user_id") DEFERRABLE INITIALLY DEFERRED; ALTER TABLE "wikipbxweb_voicemail" ADD CONSTRAINT userprofile_id_refs_user_id_5832b70c52f6936c FOREIGN KEY ("userprofile_id") REFERENCES "wikipbxweb_userprofile" ("user_id") DEFERRABLE INITIALLY DEFERRED; CREATE TABLE "wikipbxweb_account_admins" ( "id" serial NOT NULL PRIMARY KEY, "account_id" integer NOT NULL REFERENCES "wikipbxweb_account" ("id") DEFERRABLE INITIALLY DEFERRED, "userprofile_id" integer NOT NULL REFERENCES "wikipbxweb_userprofile" ("user_id") DEFERRABLE INITIALLY DEFERRED, UNIQUE ("account_id", "userprofile_id") ); CREATE TABLE "wikipbxweb_voicemail_labels" ( "id" serial NOT NULL PRIMARY KEY, "voicemail_id" integer NOT NULL REFERENCES "wikipbxweb_voicemail" ("id") DEFERRABLE INITIALLY DEFERRED, "voicemaillabel_id" integer NOT NULL REFERENCES "wikipbxweb_voicemaillabel" ("id") DEFERRABLE INITIALLY DEFERRED, UNIQUE ("voicemail_id", "voicemaillabel_id") ); CREATE INDEX "wikipbxweb_eventsocketconfig_server_id" ON "wikipbxweb_eventsocketconfig" ("server_id"); CREATE INDEX "wikipbxweb_sofiagateway_account_id" ON "wikipbxweb_sofiagateway" ("account_id"); CREATE INDEX "wikipbxweb_account_server_id" ON "wikipbxweb_account" ("server_id"); CREATE INDEX "wikipbxweb_endpoint_account_id" ON "wikipbxweb_endpoint" ("account_id"); CREATE INDEX "wikipbxweb_endpoint_userprofile_id" ON "wikipbxweb_endpoint" ("userprofile_id"); CREATE INDEX "wikipbxweb_extension_account_id" ON "wikipbxweb_extension" ("account_id"); CREATE INDEX "wikipbxweb_extension_endpoint_id" ON "wikipbxweb_extension" ("endpoint_id"); CREATE INDEX "wikipbxweb_emailconfig_server_id" ON "wikipbxweb_emailconfig" ("server_id"); CREATE INDEX "wikipbxweb_emailconfig_account_id" ON "wikipbxweb_emailconfig" ("account_id"); CREATE INDEX "wikipbxweb_soundclip_account_id" ON "wikipbxweb_soundclip" ("account_id"); CREATE INDEX "wikipbxweb_phonecontact_userprofile_id" ON "wikipbxweb_phonecontact" ("userprofile_id"); CREATE INDEX "wikipbxweb_serverlog_server_id" ON "wikipbxweb_serverlog" ("server_id"); CREATE INDEX "wikipbxweb_serverlog_account_id" ON "wikipbxweb_serverlog" ("account_id"); CREATE INDEX "wikipbxweb_completedcall_account_id" ON "wikipbxweb_completedcall" ("account_id"); CREATE INDEX "wikipbxweb_ivr_account_id" ON "wikipbxweb_ivr" ("account_id"); CREATE INDEX "wikipbxweb_voicemail_account_id" ON "wikipbxweb_voicemail" ("account_id"); CREATE INDEX "wikipbxweb_voicemail_userprofile_id" ON "wikipbxweb_voicemail" ("userprofile_id"); CREATE INDEX "wikipbxweb_userprofile_user_id" ON "wikipbxweb_userprofile" ("user_id"); CREATE INDEX "wikipbxweb_userprofile_account_id" ON "wikipbxweb_userprofile" ("account_id"); COMMIT;

I suspect, as tleyden does, that the upgrade process is reading my old DB and settings, despite the new information being in the settings.py, since none of these tables are actually in the new DB that I have defined when I look in it. When I ran ./manage.py diffsettings it shows the 0.5 database user instead of the one I have defined in the new settings.py.

Steve

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Sun, 14 Feb 2010 23:51:46 +0000

I am trying to upgrade "side by side" because I don't want to disrupt my existing DB until I know the new installation works. I have created a seperate DB and configured it in the settings.py for 0.8. My old 0.5 is in /usr/src/wikipbx and the new 0.8 is in /usr/src/wikipbx0.8.

$PYTHONPATH is:
PYTHONPATH=/usr/src:/usr/src/freeswitch/scripts/python:/usr/local/lib/python2.5/site-packages

I have this symlink in /usr/local/lib/python2.5/site-packages:
lrwxr-xr-x 1 root wheel 22 Feb 21 2009 django -> /usr/src/django/django

The django in /usr/src/django is the 5024 rev, but is the same one that I set up for wikipbx 0.5.

Thank you for your prompt reply.

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Sun, 14 Feb 2010 20:04:59 +0000

Lets focus on the "syncdb" command not working.

So you are trying upgrade from 0.5 to 0.8? Are you doing it "side by side" style or "in place" style? (eg, from this doc: http://wikipbx.subwiki.com/0-5-to-0-8-migration-guide)

I think what is happening is this:

Due to a misconfigured python path, it's actually pulling the OLD code (0.5 version), as well as the OLD settings.py, which means its talking to the OLD database.
With old code and old database, syncdb thinks there's nothing to do, and so does nothing

From the command line, echo $PYTHONPATH and post what it says. Or if you created a symlink in your /usr/lib/python2.x/site-packages directory, or multiple symlinks, please specify what you have there.

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Re: Help Upgrading! Blank Screen acessing WSGI through Apache22

Sun, 14 Feb 2010 19:31:37 +0000

I'm not sure what's going on here, but it's obvious from your report that for some reason the DB tables aren't created by syncdb command. So there's no point to look into apache configs. Please show us the output of

 ./manage.py sqlall wikipbxweb

command.

FYI, I've just tested that trunk creates DB as usually, it's not broken.

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22

Help Upgrading! Blank Screen acessing WSGI through Apache22

Sun, 14 Feb 2010 18:26:51 +0000

Hi all,

Wow, for over a year I have been using WikiPBX and I must say I am impressed!

I have a functional installation on FreeBSD using a virtual server I purchased at Link2VoIP.com. It has been running the 0.5 version (r199) for a while and works great. However I want to migrate to the 0.8 trunk.

I installed mod_wsgi from source because the mod_wsgi that was in FreeBSD Ports was 2.6 (quite old). No problems there.

I have a postgres DB, called wikipbx, and I have created a new DB called wikipbx0.8 which I will use for this new version. I have exported my configuration to XML. The source for 0.8 has been downloaded into /usr/src/wikipbx0.8. I have been following along the guide on the Wiki and modifying the instructions slightly so they work on FreeBSD.

My Apache has the module loaded for WSGI and my vhost entry is as follows (The paths are correct and everything is actually located where I have defined it below):

 WSGIPythonPath /usr/src/wikipbx0.8:/usr/src/wikipbx0.8/wikipbx:/usr/src/django:/usr/src/freeswitch/libs/esl/python  ServerAdmin support@thirtytwenty.com ServerName MYHOSTNAMEHERE ErrorLog "/var/log/ipbx-error_log" CustomLog "/var/log/ipbx-access_log" common  Options Indexes FollowSymLinks AllowOverride FileInfo Order allow,deny Allow from all  # I Read online that this may be required - but I get same behaviour either way if it is commented out AddType text/html .wsgi WSGIScriptAlias / /usr/src/wikipbx0.8/wikipbx.wsgi LogLevel debug

My new DB is blank and the user and permissions are set up. I can log into the DB and use it when testing with no problems.

When I got into /usr/src/wikipbx0.8/wikipbx and I run python manage.py syncdb this is all I see:

 root# python manage.py syncdb Loading 'initial_data' fixtures... No fixtures found. root#

The database is still blank, yet there are no errors. Here is a diff of my settings.py against the default settings_template:

 root# diff settings_template.py settings.py 26,28c26,28 < DATABASE_NAME = 'wikipbx' # Or path to database file if using sqlite3. < DATABASE_USER = 'YOUR_DB_USER' # Not used with sqlite3. < DATABASE_PASSWORD = 'YOUR_DB_PASS' # Not used with sqlite3. --- > DATABASE_NAME = 'wikipbx0.8' # Or path to database file if using sqlite3. > DATABASE_USER = 'wikipbx' # Not used with sqlite3. > DATABASE_PASSWORD = 'thisisnotreallymyrealpassword' # Not used with sqlite3. 124c124 < FREESWITCH_URL_PORT = "http://127.0.0.1" --- > FREESWITCH_URL_PORT = "http://MYHOSTNAMEHERE"

The settings I have put into settings.py for the DB should be working. They are copied from my old DB except for the database name. I have added the wikipbx user to the allowed users on the new DB.

When I re-load Apache, and access my hostname in the browser, I was initially getting access denied entries in my Apache error log, until I set up a Directory definition for the /usr/src/wikipbx0.8 directory that allowed access. Now, after reloading again, when I hit http://MYHOSTNAMEHERE in my browser, I get a blank page (nothing appears in View Source either). I hit it with Lynx and Lynx says:

 root# lynx http://MYHOSTNAMEHERE Looking up MYHOSTNAMEHERE Making HTTP connection to MYHOSTNAMEHERE Sending HTTP request. HTTP request sent; waiting for response. Alert!: Unexpected network read error; connection aborted. Can't Access `http://MYHOSTNAMEHERE/' Alert!: Unable to access document. lynx: Can't access startfile root#

Even with debug logging turned on in Apache, there are no errors appearing in the access or error logs for this attempt.

I am stuck here. Any tips?

Thanks,
Steve

Forum category: WikiPBX / Technical Support
Forum thread: Help Upgrading! Blank Screen acessing WSGI through Apache22