Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
Hi,
there seems to be a general problem running postorius with Django 1.4.
Postorius alpha1 was released the same day Django 1.4 was, so we haven't had anyone on the team so far who was running 1.4 while working on postorius.
@Shayan, could you file a bug on https://launchpad.net/postorius and paste your traceback into the description field? I will try to get into it as soon as possible.
Thanks! Florian
Am 29.03.12 10:51, schrieb Odhiambo Washington:
On Thu, Mar 29, 2012 at 11:12, Shayan Md mdoshayan@gmail.com wrote:
On Thu, Mar 29, 2012 at 1:07 PM, Odhiambo Washington odhiambo@gmail.comwrote:
On Thu, Mar 29, 2012 at 10:33, Shayan Md mdoshayan@gmail.com wrote:
On Thu, Mar 29, 2012 at 12:28 PM, Odhiambo Washington < odhiambo@gmail.com> wrote:
On Wed, Mar 28, 2012 at 22:31, Florian Fuchs f@state-of-mind.de wrote:
Hi Odhiambo,
Am 28.03.12 18:47, schrieb Odhiambo Washington: > One more thing: > > In settings.py, I have this: > > REST_SERVER = 'http://192.168.40.252:8001' > > However, this doesn't seem to be respected when I do runserver: > > [root@jaribu] /usr/home/wash/Tools/Mailman/MM3/postorius/dev_setup# > python manage.py runserver > Validating models... > > 0 errors found > Django version 1.4, using settings 'dev_setup.settings' > Development server is running at http://127.0.0.1:8000/ > Quit the server with CONTROL-C. > > > [root@jaribu] /usr/home/wash# sockstat -l | grep 800 > root python 77906 3 tcp4 127.0.0.1:8000 > http://127.0.0.1:8000 *:* > root python 14108 43 tcp4 127.0.0.1:8001 > http://127.0.0.1:8001 *:* > > Since I am not using the server as a Desktop, I need a way to access it > remotely, not via 127.0.0.1
The REST_SERVER setting defines the location of Mailman's rest API (which is frequently accessed by postorius), *not* the address of postorius itself. The API can only be accessed from localhost, so the setting has to be 'http://localhost:8001'.
If you'd like to access postorius from a different machine as the one you're running it on, that's no problem:
Just run the development server like this and you're good to go:
python manage.py runserver 192.168.x.xxx:8000
(Don't do that on a machine that is exposed to the web though, since Django's dev server is not meant to be run in a production environment.)
Hope that helps!
Florian
My current quest is to see what MM3 web UI looks like, but it appears I am still way behind. I get these errors in the backend when I run posturious and try to access it:
Looks like you didn't start mailman server. Go through this[1] page to setup mailman3.
[1] http://wiki.list.org/display/DEV/A+5+minute+guide+to+get+the+Mailman+web+UI+...
Maybe and maybe not, as I was following this very guide!
[wash@jaribu ~/public_html]$ ps ax | grep mailman 70295 ?? Is 0:00.40 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/master 70298 ?? S 0:01.52 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=news:0:1 70299 ?? S 0:01.57 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=in:0:1 70300 ?? S 0:01.46 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=digest:0:1 70301 ?? S 0:01.49 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=pipeline:0:1 70302 ?? S 0:01.45 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=archive:0:1 70303 ?? S 0:01.46 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=out:0:1 70304 ?? I 0:00.41 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=retry:0:1 70305 ?? S 0:01.17 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=rest:0:1 70306 ?? S 0:01.46 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=bounces:0:1 70307 ?? S 0:00.43 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=lmtp:0:1 70308 ?? S 0:01.45 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=command:0:1 70309 ?? S 0:01.50 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=virgin:0:1 78850 1 S+ 0:00.01 grep mailman
Is there something amiss?
[root@jaribu] /usr/home/wash# sockstat -l | grep 800 root python 70442 3 tcp4 192.168.40.252:8000 *:* root python 70305 43 tcp4 127.0.0.1:8001 *:*
I suppose the 8001 is mailman and 8000 is posturious.
Downgrading to django 1.3 might do the trick. Same error here https://answers.launchpad.net/graphite/+question/191549
Okay. I have to figure out why the consensus is that I am running django 1.4 while I actually installed 1.3.1:
[root@jaribu] /usr/ports/www/py-django# ls -al /var/db/pkg/ | grep django drwxr-xr-x 2 root wheel 512 Mar 26 18:20 py27-django-1.3.1 drwxr-xr-x 2 root wheel 512 Mar 26 18:20 py27-django-extensions-0.8
Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/f%40state-of-mind....
Security Policy: http://wiki.list.org/x/QIA9
On Thu, Mar 29, 2012 at 13:53, Florian Fuchs f@state-of-mind.de wrote:
Hi,
there seems to be a general problem running postorius with Django 1.4.
Postorius alpha1 was released the same day Django 1.4 was, so we haven't had anyone on the team so far who was running 1.4 while working on postorius.
@Florian,
My issue here is that I am not running Django 1.4 - unless I am missing something. I am not sure where it is coming from. I am on FreeBSD and I installed django-1.3.1 from the ports. A check on my installed apps shows just that. There is a port for py-django-devel but I did not install that at all:
See this
[root@jaribu] /usr/ports/www/py-django-devel# make fetch
===> py27-django-devel-17269,1 conflicts with installed package(s): py27-django-1.3.1
They install files into the same place.
You may want to stop build with Ctrl + C.===> License check disabled, port has not defined LICENSE => Django-r17269.tar.xz doesn't seem to exist in /usr/ports/distfiles/python. => Attempting to fetch http://people.cs.nctu.edu.tw/~lwhsu/ports/distfiles/Django-r17269.tar.xz Django-r17269.tar.xz 85% of 4135 kB 135 kBps 00m04s
That shows I have django-1.3.1 installed.
I went as far as this:
mv /usr/local/lib/python2.7/site-packages/django /usr/local/lib/python2.7/site-packages/_django-1.4
Then reinstalled django-1.3.1, but I am pretty sure that the above action
wasn't necessary.
So I wiped put everything - python, django, mailman, mailman.client, py-sqlite3 - and reinstalled. Mailman gave me enough grief with bin/test and I had to wipe and reinstall several times. Perhaps it wasn't getting all the files during bin/build.
Now things look promising, but I still get errors about some templates I need to create - 500.html, 400.html....
Traceback (most recent call last):
File "/usr/local/lib/python2.7/site-packages/django/core/servers/basehttp.py", line 283, in run self.result = application(self.environ, self.start_response)
File "/usr/local/lib/python2.7/site-packages/django/core/handlers/wsgi.py", line 272, in __call__ response = self.get_response(request)
File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 169, in get_response response = self.handle_uncaught_exception(request, resolver, sys.exc_info())
File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 218, in handle_uncaught_exception return callback(request, **param_dict)
File "/usr/local/lib/python2.7/site-packages/django/utils/decorators.py", line 93, in _wrapped_view response = view_func(request, *args, **kwargs)
File "/usr/local/lib/python2.7/site-packages/django/views/defaults.py", line 30, in server_error t = loader.get_template(template_name) # You need to create a 500.html template.
File "/usr/local/lib/python2.7/site-packages/django/template/loader.py", line 157, in get_template template, origin = find_template(template_name)
File "/usr/local/lib/python2.7/site-packages/django/template/loader.py", line 138, in find_template raise TemplateDoesNotExist(name)
TemplateDoesNotExist: 500.html
How do I create these and where do I place them? Where is the guide??
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223
I can't hear you -- I'm using the scrambler. Please consider the environment before printing this email.
participants (2)
-
Florian Fuchs -
Odhiambo Washington