Description

Describe the bug...

Steps to reproduce

1. Attempt to get "info" for any page.

Example

http://www.grizz.org/gpc/FrontPage?action=info

Component selection

• general

Details

No Moin traceback. I get a 500 server error and the following

[Sun Feb 28 11:23:02 2010] [error] [client 68.183.193.239] mod_wsgi (pid=19497): Exception occurred processing WSGI script '/var/www/grizz/moin/gpc/moin.wsgi'.
[Sun Feb 28 11:23:02 2010] [error] [client 68.183.193.239] Traceback (most recent call last):
[Sun Feb 28 11:23:02 2010] [error] [client 68.183.193.239]   File "/usr/lib/python2.6/site-packages/MoinMoin/support/werkzeug/utils.py", line 248, in __call__
[Sun Feb 28 11:23:02 2010] [error] [client 68.183.193.239]     return self.app(environ, start_response)
[Sun Feb 28 11:23:02 2010] [error] [client 68.183.193.239]   File "/usr/lib/python2.6/site-packages/MoinMoin/wsgiapp.py", line 251, in __call__
[Sun Feb 28 11:23:02 2010] [error] [client 68.183.193.239]     if not lang:
[Sun Feb 28 11:23:02 2010] [error] [client 68.183.193.239]   File "/usr/lib/python2.6/site-packages/MoinMoin/wsgiapp.py", line 70, in run
[Sun Feb 28 11:23:02 2010] [error] [client 68.183.193.239]     """ Run a context trough the application. """
[Sun Feb 28 11:23:02 2010] [error] [client 68.183.193.239]   File "/usr/lib/python2.6/site-packages/MoinMoin/wsgiapp.py", line 118, in dispatch
[Sun Feb 28 11:23:02 2010] [error] [client 68.183.193.239]     else:
[Sun Feb 28 11:23:02 2010] [error] [client 68.183.193.239]   File "/usr/lib/python2.6/site-packages/MoinMoin/wsgiapp.py", line 177, in handle_action
[Sun Feb 28 11:23:02 2010] [error] [client 68.183.193.239]     msg += " " + _("Login and try again.")
[Sun Feb 28 11:23:02 2010] [error] [client 68.183.193.239]   File "/usr/lib/python2.6/site-packages/MoinMoin/action/info.py", line 375, in execute
[Sun Feb 28 11:23:02 2010] [error] [client 68.183.193.239]     history(page, pagename, request)
[Sun Feb 28 11:23:02 2010] [error] [client 68.183.193.239]   File "/usr/lib/python2.6/site-packages/MoinMoin/action/info.py", line 79, in history
[Sun Feb 28 11:23:02 2010] [error] [client 68.183.193.239]     paging = request.cfg.history_paging
[Sun Feb 28 11:23:02 2010] [error] [client 68.183.193.239] AttributeError: 'Config' object has no attribute 'history_paging'

Workaround

An easy work around is just to add

    history_paging = False

to my wikiconfig.py

Discussion

hmm, this wiki runs tip so why can't I reproduce it here? -- ReimarBauer 2010-02-28 22:12:14

Quote from MoinMoin/config/multiconfig.py:

    ('history_paging', True, "Enable paging for history. Warning: because event log functions are rather unefficient, enabling this option may lead to possibility of producing heavy requests!"),

Thus, this bug should not happen. Are you sure you use current code and all files have been upgraded correctly? Did you use setup.py? With --force?

I installed like this

rm -rf /usr/lib/python2.6/site-packages/MoinMoin/*
rm -rf /usr/share/moin/*
python2.6 setup.py install

After I encountered the error/traceback 3 times, I patched MoinMoin/action/info.py as indicated in my initial report. Then I realized the easier workaround was to simply define history_paging in my wikiconfig.py so I did that and removed the patch.

Then I saw that while I was doing all that, 1.9.2 had been released with the only apparent change other than docs being to the text describing the option, but I downloaded and installed the moin-1.9.2.tar.gz tarball. I then tried removing the history_paging definition from my wikiconfig.py, and I didn't see the problem again.

So the bottom line is I can't duplicate it either.

There was a flaw (now fixed) in my update procedure. The procedure moves my moin.wsgi script aside and replaces it with a "Down for maintenance" script, and later moves the original back. I run mod_wsgi in daemon mode, and initially, I was not touching those scripts after moving them, so it is possible that when I encountered the exception, I had updated the software but not reloaded the mod_wsgi daemon. Logs don't show the daemon reloads, so I can't be completely sure, but this may have been the case. I would have expected this to cause bigger problems, but this may be the reason for the problem I saw.

Sorry for the spurious report.
-- MarkSapiro 2010-03-01 05:25:02

P.S. I realized that there are INFO messages in moin.log regarding the logging config and the wiki config that occur the first time MoinMoin starts after the mod_wsgi daemon has restarted. Using these, I am able to verify that the daemon did not restart between my first installing the 1.9.2pre upgrade and my seeing these errors. This was undoubtedly the reason for this problem. It was my own fault. Again, my apologies for this spurious report.
-- MarkSapiro 2010-03-01 18:08:04

No problem, better than a bug. -- ThomasWaldmann 2010-03-01 18:34:00

Plan

• Priority:
• Assigned to:
• Status: can't reproduce. incomplete installation/update?

CategoryMoinMoinNoBug