[Mailman-Users] Upgrade problems (2.0.13 -> 2.1); Incoming qrunner dies

Ed Osinski osinski at cs.nyu.edu
Tue Jan 14 20:32:42 CET 2003


I've upgraded from 2.0.13 to 2.1, and am having problems:

When running "bin/mailmanctl start", I get a series of errors:

Traceback (most recent call last):
  File "/usr/mailman/bin/qrunner", line 270, in ?
     main()
  File "/usr/mailman/bin/qrunner", line 230, in main
     qrunner.run()
  File "/usr/mailman/Mailman/Queue/Runner.py", line 59, in run
     filecnt = self._oneloop()
  File "/usr/mailman/Mailman/Queue/Runner.py", line 88, in _oneloop
     msg, msgdata = self._switchboard.dequeue(filebase)
  File "/usr/mailman/Mailman/Queue/Switchboard.py", line 144, in dequeue
     data = self._ext_read(dbfile)
  File "/usr/mailman/Mailman/Queue/Switchboard.py", line 245, in _ext_read
     dict = marshal.load(fp)
EOFError :  EOF read where object expected 

This is repeated 11 times.  When I run ps to look for qrunner
processes, I find:

 mailman 18209 18202  0 13:21:29 ?        0:01 qrunner /usr/mailman/bin/qrunner --runner=VirginRunner:0:1 -s
 mailman 18203 18202  0 13:21:28 ?        0:01 qrunner /usr/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
 mailman 18208 18202  0 13:21:29 ?        0:01 qrunner /usr/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
 mailman 18204 18202  0 13:21:28 ?        0:01 qrunner /usr/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
 mailman 18205 18202  0 13:21:28 ?        0:01 qrunner /usr/mailman/bin/qrunner --runner=CommandRunner:0:1 -s
 mailman 18207 18202  0 13:21:28 ?        0:01 qrunner /usr/mailman/bin/qrunner --runner=NewsRunner:0:1 -s

There is no IncomingRunner.  

I created a test list.  The web interface seems to work for both
admins and users, so I subscribed myself.  I got the subscription
message, but messages _to_ the test list appear in the qfiles/in
subdirectory (both a .msg and a .db file is created for each incoming
message) but aren't delivered to the list.

Any ideas?

I have another problem with an existing list, but I'll send that in
another message.

- Ed



More information about the Mailman-Users mailing list