Urgent newbie help - "Hit a bug" page
Never seen this before - When visiting mailman listinfo web page, I get: Bug in Mailman version 2.1.5 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. - and my lists aren't working. Restarting qrunner or rebooting (!) don't help. Anything stand out to you in the error log below? pid file missing?? How would that happen? Any help for this newbie would be greatly appreciated! Thanks - John Mar 02 07:35:40 2007 admin(5190): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(5190): [----- Mailman Version: 2.1.5 -----] admin(5190): [----- Traceback ------] admin(5190): Traceback (most recent call last): admin(5190): File "/var/lib/mailman/scripts/driver", line 110, in run_main admin(5190): main() admin(5190): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 42, in main admin(5190): listinfo_overview() admin(5190): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 88, in listinfo_overview admin(5190): if mlist.advertised: admin(5190): File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ admin(5190): raise AttributeError, name admin(5190): AttributeError: advertised admin(5190): [----- Python Information -----] admin(5190): sys.version = 2.3.5 (#2, Oct 16 2006, 19:19:48) [GCC 3.3.5 (Debian 1:3.3.5-13)] admin(5190): sys.executable = /usr/bin/python admin(5190): sys.prefix = /usr admin(5190): sys.exec_prefix = /usr admin(5190): sys.path = /usr admin(5190): sys.platform = linux2 admin(5190): [----- Environment Variables -----] admin(5190): SERVER_SOFTWARE: Apache/1.3.33 (Debian GNU/Linux) PHP/4.3.10-18 mod_ssl/2.8.22 OpenSSL/0.9.7e admin(5190): SCRIPT_NAME: /mailman/listinfo admin(5190): SERVER_SIGNATURE: <ADDRESS>Apache/1.3.33 Server at impactoveneto.org Port 80</ADDRESS> admin(5190): admin(5190): REQUEST_METHOD: GET admin(5190): SERVER_PROTOCOL: HTTP/1.1 admin(5190): QUERY_STRING: admin(5190): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) admin(5190): HTTP_CONNECTION: Keep-Alive admin(5190): SERVER_NAME: impactoveneto.org admin(5190): REMOTE_ADDR: 64.105.150.50 admin(5190): SERVER_PORT: 80 admin(5190): SERVER_ADDR: 64.105.150.51 admin(5190): DOCUMENT_ROOT: /home/impactoveneto/www/ admin(5190): PYTHONPATH: /var/lib/mailman admin(5190): SCRIPT_FILENAME: /var/lib/mailman/cgi-bin//listinfo admin(5190): SERVER_ADMIN: john@wa9als.com admin(5190): HTTP_HOST: impactoveneto.org admin(5190): REQUEST_URI: /mailman/listinfo admin(5190): HTTP_ACCEPT: */* admin(5190): GATEWAY_INTERFACE: CGI/1.1 admin(5190): REMOTE_PORT: 33351 admin(5190): HTTP_ACCEPT_LANGUAGE: en-us admin(5190): HTTP_ACCEPT_ENCODING: gzip, deflate Mar 02 07:36:48 2007 mailmanctl(5284): PID unreadable in: /var/run/mailman/mailman.pid Mar 02 07:36:48 2007 mailmanctl(5284): [Errno 2] No such file or directory: '/var/run/mailman/mailman.pid' Mar 02 07:36:48 2007 mailmanctl(5284): Is qrunner even running? Mar 02 07:36:50 2007 (5290) Uncaught runner exception: language Mar 02 07:36:50 2007 (5290) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 161, in _onefile lang = mlist.getMemberLanguage(sender) File "/var/lib/mailman/Mailman/OldStyleMemberships.py", line 116, in getMemberLanguage lang = self.__mlist.language.get( File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ raise AttributeError, name AttributeError: language ---------------------------------------- SNIP--------------------------------------------------------------------- Mar 02 07:37:14 2007 (5311) SHUNTING: 1008297783.149177+211c1bb30212c20dd5eb5087684a8ae9e272e80e Mar 02 07:37:25 2007 admin(5327): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(5327): [----- Mailman Version: 2.1.5 -----] admin(5327): [----- Traceback ------] admin(5327): Traceback (most recent call last): admin(5327): File "/var/lib/mailman/scripts/driver", line 110, in run_main admin(5327): main() admin(5327): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 42, in main admin(5327): listinfo_overview() admin(5327): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 88, in listinfo_overview admin(5327): if mlist.advertised: admin(5327): File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ admin(5327): raise AttributeError, name admin(5327): AttributeError: advertised admin(5327): [----- Python Information -----] admin(5327): sys.version = 2.3.5 (#2, Oct 16 2006, 19:19:48) [GCC 3.3.5 (Debian 1:3.3.5-13)] admin(5327): sys.executable = /usr/bin/python admin(5327): sys.prefix = /usr admin(5327): sys.exec_prefix = /usr admin(5327): sys.path = /usr admin(5327): sys.platform = linux2 admin(5327): [----- Environment Variables -----] admin(5327): SERVER_SOFTWARE: Apache/1.3.33 (Debian GNU/Linux) PHP/4.3.10-18 mod_ssl/2.8.22 OpenSSL/0.9.7e admin(5327): SCRIPT_NAME: /mailman/listinfo admin(5327): SERVER_SIGNATURE: <ADDRESS>Apache/1.3.33 Server at wa9als.com Port 443</ADDRESS> admin(5327): admin(5327): REQUEST_METHOD: GET admin(5327): SERVER_PROTOCOL: HTTP/1.1 admin(5327): QUERY_STRING: admin(5327): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) admin(5327): HTTP_CONNECTION: Keep-Alive admin(5327): SERVER_NAME: wa9als.com admin(5327): REMOTE_ADDR: 64.105.150.50 admin(5327): SERVER_PORT: 443 admin(5327): SERVER_ADDR: 64.105.150.51 admin(5327): DOCUMENT_ROOT: /home/wa9als/www/ admin(5327): PYTHONPATH: /var/lib/mailman admin(5327): SCRIPT_FILENAME: /var/lib/mailman/cgi-bin//listinfo admin(5327): SERVER_ADMIN: john@wa9als.com admin(5327): HTTP_HOST: wa9als.com admin(5327): HTTPS: on admin(5327): REQUEST_URI: /mailman/listinfo admin(5327): HTTP_ACCEPT: */* admin(5327): nokeepalive: 1 admin(5327): GATEWAY_INTERFACE: CGI/1.1 admin(5327): REMOTE_PORT: 32889 admin(5327): HTTP_ACCEPT_LANGUAGE: en-us admin(5327): ssl_unclean_shutdown: 1 admin(5327): HTTP_ACCEPT_ENCODING: gzip, deflate Mar 02 07:37:28 2007 (5311) Uncaught runner exception: language Mar 02 07:37:28 2007 (5311) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 161, in _onefile lang = mlist.getMemberLanguage(sender) File "/var/lib/mailman/Mailman/OldStyleMemberships.py", line 116, in getMemberLanguage lang = self.__mlist.language.get( File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ raise AttributeError, name AttributeError: language Mar 02 07:37:28 2007 (5311) SHUNTING: 1008298314.179932+606e3627579e7c6452b0ba13fd944c61f7270b7d Mar 02 07:37:28 2007 (5311) Uncaught runner exception: language Mar 02 07:37:28 2007 (5311) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 161, in _onefile lang = mlist.getMemberLanguage(sender) File "/var/lib/mailman/Mailman/OldStyleMemberships.py", line 116, in getMemberLanguage lang = self.__mlist.language.get( File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ raise AttributeError, name AttributeError: language Mar 02 07:37:28 2007 (5311) SHUNTING: 1008300154.540808+655c3679244a683adab6b4042bb9b8fb837ac091 Mar 02 07:37:39 2007 (5311) Uncaught runner exception: language Mar 02 07:37:39 2007 (5311) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 161, in _onefile lang = mlist.getMemberLanguage(sender) File "/var/lib/mailman/Mailman/OldStyleMemberships.py", line 116, in getMemberLanguage lang = self.__mlist.language.get( File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ raise AttributeError, name AttributeError: language Mar 02 07:37:39 2007 (5311) SHUNTING: 1008301472.112578+b7dc21277ef8cadb2bc534bf5cafe2cfa0b49077 Mar 02 07:37:39 2007 (5311) Uncaught runner exception: language Mar 02 07:37:39 2007 (5311) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 161, in _onefile lang = mlist.getMemberLanguage(sender) File "/var/lib/mailman/Mailman/OldStyleMemberships.py", line 116, in getMemberLanguage lang = self.__mlist.language.get( File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ raise AttributeError, name AttributeError: language Mar 02 07:37:39 2007 (5311) SHUNTING: 1008302599.373763+372efc2078e05d9cb3068567343a2358bf061dc5 Mar 02 07:37:49 2007 (5311) Uncaught runner exception: (4, 'Interrupted system call') Mar 02 07:37:49 2007 (5311) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Handlers/SpamAssassin.py", line 76, in process score, symbols = check_message(mlist, str(msg)) File "/usr/lib/mailman/Mailman/Handlers/SpamAssassin.py", line 62, in check_message res = connection.check(spamd.SYMBOLS, message) File "/usr/lib/mailman/Mailman/Handlers/spamd.py", line 122, in check response = fp.readline() File "/usr/lib/python2.3/socket.py", line 338, in readline data = self._sock.recv(self._rbufsize) error: (4, 'Interrupted system call') Mar 02 07:37:49 2007 (5311) SHUNTING: 1008303067.2221119+3eb7cfce1e28cd1f4f8c7c6467d1a7c2974a9319
John Fleming wrote:
Never seen this before - When visiting mailman listinfo web page, I get:
Bug in Mailman version 2.1.5 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs.
- and my lists aren't working. Restarting qrunner or rebooting (!) don't help. Anything stand out to you in the error log below? pid file missing?? How would that happen? Any help for this newbie would be greatly appreciated! Thanks - John
It appears that the config.pck file for at least one list is corrupt.
Try running
bin/dumpdb lists/<listname>/config.pck
for all your lists. If you find one that looks like things are missing, try
bin/dumpdb -p lists/<listname>/config.pck.last
for that list. If the config.pck.last looks OK (it probably won't), you can do
cp lists/<listname>/config.pck.last lists/<listname>/config.pck
for that list. Otherwise, I hope you have a recent backup.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
----- Original Message ----- From: "Mark Sapiro" <msapiro@value.net> To: "John Fleming" <john@wa9als.com>; <mailman-users@python.org> Sent: Friday, March 02, 2007 11:15 AM Subject: Re: [Mailman-Users] Urgent newbie help - "Hit a bug" page
John Fleming wrote:
Never seen this before - When visiting mailman listinfo web page, I get:
Bug in Mailman version 2.1.5 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs.
- and my lists aren't working. Restarting qrunner or rebooting (!) don't help. Anything stand out to you in the error log below? pid file missing?? How would that happen? Any help for this newbie would be greatly appreciated! Thanks - John
It appears that the config.pck file for at least one list is corrupt.
Try running
bin/dumpdb lists/<listname>/config.pck
for all your lists. If you find one that looks like things are missing, try
bin/dumpdb -p lists/<listname>/config.pck.last
for that list. If the config.pck.last looks OK (it probably won't), you can do
cp lists/<listname>/config.pck.last lists/<listname>/config.pck
for that list. Otherwise, I hope you have a recent backup.
The .pck files are OK. My lists are working again after -another- qrunner restart and nothing else changed. However, there's still a problem. I can view any individual list's information via the usual web pages (www.domain.name/mailman/listinfo/<listname>), but I get the "We hit a bug" page when I try to view the lists -overview- page for any of my domains. Here's the error log entry for when I try. Does anyone see what's wrong? This used to work, and I haven't changed anything in my configuration. (Mailman 2.1.5 Debian Stable) Thanks - John Mar 02 21:35:33 2007 admin(18864): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(18864): [----- Mailman Version: 2.1.5 -----] admin(18864): [----- Traceback ------] admin(18864): Traceback (most recent call last): admin(18864): File "/var/lib/mailman/scripts/driver", line 110, in run_main admin(18864): main() admin(18864): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 42, in main admin(18864): listinfo_overview() admin(18864): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 88, in listinfo_overview admin(18864): if mlist.advertised: admin(18864): File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ admin(18864): raise AttributeError, name admin(18864): AttributeError: advertised admin(18864): [----- Python Information -----] admin(18864): sys.version = 2.3.5 (#2, Oct 16 2006, 19:19:48) [GCC 3.3.5 (Debian 1:3.3.5-13)] admin(18864): sys.executable = /usr/bin/python admin(18864): sys.prefix = /usr admin(18864): sys.exec_prefix = /usr admin(18864): sys.path = /usr admin(18864): sys.platform = linux2 admin(18864): [----- Environment Variables -----] admin(18864): SERVER_SOFTWARE: Apache/1.3.33 (Debian GNU/Linux) PHP/4.3.10-18 mod_ssl/2.8.22 OpenSSL/0.9.7e admin(18864): SCRIPT_NAME: /mailman/listinfo admin(18864): SERVER_SIGNATURE: <ADDRESS>Apache/1.3.33 Server at wa9als.com Port 443</ADDRESS> admin(18864): admin(18864): REQUEST_METHOD: GET admin(18864): SERVER_PROTOCOL: HTTP/1.1 admin(18864): QUERY_STRING: admin(18864): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) admin(18864): HTTP_CONNECTION: Keep-Alive admin(18864): SERVER_NAME: wa9als.com admin(18864): REMOTE_ADDR: 64.105.150.50 admin(18864): SERVER_PORT: 443 admin(18864): SERVER_ADDR: 64.105.150.51 admin(18864): DOCUMENT_ROOT: /home/wa9als/www/ admin(18864): PYTHONPATH: /var/lib/mailman admin(18864): SCRIPT_FILENAME: /var/lib/mailman/cgi-bin//listinfo admin(18864): SERVER_ADMIN: john@wa9als.com admin(18864): HTTP_HOST: wa9als.com admin(18864): HTTPS: on admin(18864): REQUEST_URI: /mailman/listinfo admin(18864): HTTP_ACCEPT: */* admin(18864): nokeepalive: 1 admin(18864): GATEWAY_INTERFACE: CGI/1.1 admin(18864): REMOTE_PORT: 33765 admin(18864): HTTP_ACCEPT_LANGUAGE: en-us admin(18864): ssl_unclean_shutdown: 1 admin(18864): HTTP_ACCEPT_ENCODING: gzip, deflate and just before the above (when I wasn't even home), I see: Mar 02 21:06:00 2007 admin(18250): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(18250): [----- Mailman Version: 2.1.5 -----] admin(18250): [----- Traceback ------] admin(18250): Traceback (most recent call last): admin(18250): File "/var/lib/mailman/scripts/driver", line 110, in run_main admin(18250): main() admin(18250): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 42, in main admin(18250): listinfo_overview() admin(18250): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 88, in listinfo_overview admin(18250): if mlist.advertised: admin(18250): File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ admin(18250): raise AttributeError, name admin(18250): AttributeError: advertised admin(18250): [----- Python Information -----] admin(18250): sys.version = 2.3.5 (#2, Oct 16 2006, 19:19:48) [GCC 3.3.5 (Debian 1:3.3.5-13)] admin(18250): sys.executable = /usr/bin/python admin(18250): sys.prefix = /usr admin(18250): sys.exec_prefix = /usr admin(18250): sys.path = /usr admin(18250): sys.platform = linux2 admin(18250): [----- Environment Variables -----] admin(18250): SERVER_SOFTWARE: Apache/1.3.33 (Debian GNU/Linux) PHP/4.3.10-18 mod_ssl/2.8.22 OpenSSL/0.9.7e admin(18250): SCRIPT_NAME: /mailman/listinfo admin(18250): SERVER_SIGNATURE: <ADDRESS>Apache/1.3.33 Server at wa9als.com Port 80</ADDRESS> admin(18250): admin(18250): REQUEST_METHOD: GET admin(18250): SERVER_PROTOCOL: HTTP/1.1 admin(18250): QUERY_STRING: admin(18250): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) admin(18250): HTTP_CONNECTION: Keep-Alive admin(18250): SERVER_NAME: wa9als.com admin(18250): REMOTE_ADDR: 64.105.150.50 admin(18250): SERVER_PORT: 80 admin(18250): SERVER_ADDR: 64.105.150.51 admin(18250): DOCUMENT_ROOT: /home/wa9als/www/ admin(18250): PYTHONPATH: /var/lib/mailman admin(18250): SCRIPT_FILENAME: /var/lib/mailman/cgi-bin//listinfo admin(18250): SERVER_ADMIN: john@wa9als.com admin(18250): HTTP_HOST: wa9als.com admin(18250): REQUEST_URI: /mailman/listinfo admin(18250): HTTP_ACCEPT: */* admin(18250): GATEWAY_INTERFACE: CGI/1.1 admin(18250): REMOTE_PORT: 33340 admin(18250): HTTP_ACCEPT_LANGUAGE: en-us admin(18250): HTTP_ACCEPT_ENCODING: gzip, deflate
Quoting John Fleming <john@wa9als.com>:
----- Original Message ----- From: "Mark Sapiro" <msapiro@value.net> To: "John Fleming" <john@wa9als.com>; <mailman-users@python.org> Sent: Friday, March 02, 2007 11:15 AM Subject: Re: [Mailman-Users] Urgent newbie help - "Hit a bug" page
John Fleming wrote:
Never seen this before - When visiting mailman listinfo web page, I get:
Bug in Mailman version 2.1.5 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs.
- and my lists aren't working. Restarting qrunner or rebooting (!) don't help. Anything stand out to you in the error log below? pid file missing?? How would that happen? Any help for this newbie would be greatly appreciated! Thanks - John
It appears that the config.pck file for at least one list is corrupt.
Try running
bin/dumpdb lists/<listname>/config.pck
for all your lists. If you find one that looks like things are missing, try
bin/dumpdb -p lists/<listname>/config.pck.last
for that list. If the config.pck.last looks OK (it probably won't), you can do
cp lists/<listname>/config.pck.last lists/<listname>/config.pck
for that list. Otherwise, I hope you have a recent backup.
The .pck files are OK. My lists are working again after -another- qrunner restart and nothing else changed. However, there's still a problem. I can view any individual list's information via the usual web pages (www.domain.name/mailman/listinfo/<listname>), but I get the "We hit a bug" page when I try to view the lists -overview- page for any of my domains. Here's the error log entry for when I try. Does anyone see what's wrong? This used to work, and I haven't changed anything in my configuration. (Mailman 2.1.5 Debian Stable) Thanks - John
Mar 02 21:35:33 2007 admin(18864): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(18864): [----- Mailman Version: 2.1.5 -----] admin(18864): [----- Traceback ------] admin(18864): Traceback (most recent call last): admin(18864): File "/var/lib/mailman/scripts/driver", line 110, in run_main admin(18864): main() admin(18864): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 42, in main admin(18864): listinfo_overview() admin(18864): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 88, in listinfo_overview admin(18864): if mlist.advertised: admin(18864): File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ admin(18864): raise AttributeError, name admin(18864): AttributeError: advertised admin(18864): [----- Python Information -----] admin(18864): sys.version = 2.3.5 (#2, Oct 16 2006, 19:19:48) [GCC 3.3.5 (Debian 1:3.3.5-13)] admin(18864): sys.executable = /usr/bin/python admin(18864): sys.prefix = /usr admin(18864): sys.exec_prefix = /usr admin(18864): sys.path = /usr admin(18864): sys.platform = linux2 admin(18864): [----- Environment Variables -----] admin(18864): SERVER_SOFTWARE: Apache/1.3.33 (Debian GNU/Linux) PHP/4.3.10-18 mod_ssl/2.8.22 OpenSSL/0.9.7e admin(18864): SCRIPT_NAME: /mailman/listinfo admin(18864): SERVER_SIGNATURE: <ADDRESS>Apache/1.3.33 Server at wa9als.com Port 443</ADDRESS> admin(18864): admin(18864): REQUEST_METHOD: GET admin(18864): SERVER_PROTOCOL: HTTP/1.1 admin(18864): QUERY_STRING: admin(18864): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) admin(18864): HTTP_CONNECTION: Keep-Alive admin(18864): SERVER_NAME: wa9als.com admin(18864): REMOTE_ADDR: 64.105.150.50 admin(18864): SERVER_PORT: 443 admin(18864): SERVER_ADDR: 64.105.150.51 admin(18864): DOCUMENT_ROOT: /home/wa9als/www/ admin(18864): PYTHONPATH: /var/lib/mailman admin(18864): SCRIPT_FILENAME: /var/lib/mailman/cgi-bin//listinfo admin(18864): SERVER_ADMIN: john@wa9als.com admin(18864): HTTP_HOST: wa9als.com admin(18864): HTTPS: on admin(18864): REQUEST_URI: /mailman/listinfo admin(18864): HTTP_ACCEPT: */* admin(18864): nokeepalive: 1 admin(18864): GATEWAY_INTERFACE: CGI/1.1 admin(18864): REMOTE_PORT: 33765 admin(18864): HTTP_ACCEPT_LANGUAGE: en-us admin(18864): ssl_unclean_shutdown: 1 admin(18864): HTTP_ACCEPT_ENCODING: gzip, deflate
and just before the above (when I wasn't even home), I see:
Mar 02 21:06:00 2007 admin(18250): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(18250): [----- Mailman Version: 2.1.5 -----] admin(18250): [----- Traceback ------] admin(18250): Traceback (most recent call last): admin(18250): File "/var/lib/mailman/scripts/driver", line 110, in run_main admin(18250): main() admin(18250): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 42, in main admin(18250): listinfo_overview() admin(18250): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 88, in listinfo_overview admin(18250): if mlist.advertised: admin(18250): File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ admin(18250): raise AttributeError, name admin(18250): AttributeError: advertised admin(18250): [----- Python Information -----] admin(18250): sys.version = 2.3.5 (#2, Oct 16 2006, 19:19:48) [GCC 3.3.5 (Debian 1:3.3.5-13)] admin(18250): sys.executable = /usr/bin/python admin(18250): sys.prefix = /usr admin(18250): sys.exec_prefix = /usr admin(18250): sys.path = /usr admin(18250): sys.platform = linux2 admin(18250): [----- Environment Variables -----] admin(18250): SERVER_SOFTWARE: Apache/1.3.33 (Debian GNU/Linux) PHP/4.3.10-18 mod_ssl/2.8.22 OpenSSL/0.9.7e admin(18250): SCRIPT_NAME: /mailman/listinfo admin(18250): SERVER_SIGNATURE: <ADDRESS>Apache/1.3.33 Server at wa9als.com Port 80</ADDRESS> admin(18250): admin(18250): REQUEST_METHOD: GET admin(18250): SERVER_PROTOCOL: HTTP/1.1 admin(18250): QUERY_STRING: admin(18250): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) admin(18250): HTTP_CONNECTION: Keep-Alive admin(18250): SERVER_NAME: wa9als.com admin(18250): REMOTE_ADDR: 64.105.150.50 admin(18250): SERVER_PORT: 80 admin(18250): SERVER_ADDR: 64.105.150.51 admin(18250): DOCUMENT_ROOT: /home/wa9als/www/ admin(18250): PYTHONPATH: /var/lib/mailman admin(18250): SCRIPT_FILENAME: /var/lib/mailman/cgi-bin//listinfo admin(18250): SERVER_ADMIN: john@wa9als.com admin(18250): HTTP_HOST: wa9als.com admin(18250): REQUEST_URI: /mailman/listinfo admin(18250): HTTP_ACCEPT: */* admin(18250): GATEWAY_INTERFACE: CGI/1.1 admin(18250): REMOTE_PORT: 33340 admin(18250): HTTP_ACCEPT_LANGUAGE: en-us admin(18250): HTTP_ACCEPT_ENCODING: gzip, deflate
------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/dhottinger%40harrisonbu...
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Does mailman own those directory's? I seem to remember seeing a similiar issue on the list. -- Dwayne Hottinger Network Administrator Harrisonburg City Public Schools
----- Original Message ----- From: <dhottinger@harrisonburg.k12.va.us> To: <mailman-users@python.org> Sent: Friday, March 02, 2007 10:04 PM Subject: Re: [Mailman-Users] Urgent newbie help - "Hit a bug" page
Quoting John Fleming <john@wa9als.com>:
----- Original Message ----- From: "Mark Sapiro" <msapiro@value.net> To: "John Fleming" <john@wa9als.com>; <mailman-users@python.org> Sent: Friday, March 02, 2007 11:15 AM Subject: Re: [Mailman-Users] Urgent newbie help - "Hit a bug" page
John Fleming wrote:
Never seen this before - When visiting mailman listinfo web page, I get:
Bug in Mailman version 2.1.5 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs.
- and my lists aren't working. Restarting qrunner or rebooting (!) don't help. Anything stand out to you in the error log below? pid file missing?? How would that happen? Any help for this newbie would be greatly appreciated! Thanks - John
It appears that the config.pck file for at least one list is corrupt.
Try running
bin/dumpdb lists/<listname>/config.pck
for all your lists. If you find one that looks like things are missing, try
bin/dumpdb -p lists/<listname>/config.pck.last
for that list. If the config.pck.last looks OK (it probably won't), you can do
cp lists/<listname>/config.pck.last lists/<listname>/config.pck
for that list. Otherwise, I hope you have a recent backup.
The .pck files are OK. My lists are working again after -another- qrunner restart and nothing else changed. However, there's still a problem. I can view any individual list's information via the usual web pages (www.domain.name/mailman/listinfo/<listname>), but I get the "We hit a bug" page when I try to view the lists -overview- page for any of my domains. Here's the error log entry for when I try. Does anyone see what's wrong? This used to work, and I haven't changed anything in my configuration. (Mailman 2.1.5 Debian Stable) Thanks - John
Mar 02 21:35:33 2007 admin(18864): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(18864): [----- Mailman Version: 2.1.5 -----] admin(18864): [----- Traceback ------] admin(18864): Traceback (most recent call last): admin(18864): File "/var/lib/mailman/scripts/driver", line 110, in run_main admin(18864): main() admin(18864): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 42, in main admin(18864): listinfo_overview() admin(18864): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 88, in listinfo_overview admin(18864): if mlist.advertised: admin(18864): File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ admin(18864): raise AttributeError, name admin(18864): AttributeError: advertised admin(18864): [----- Python Information -----] admin(18864): sys.version = 2.3.5 (#2, Oct 16 2006, 19:19:48) [GCC 3.3.5 (Debian 1:3.3.5-13)] admin(18864): sys.executable = /usr/bin/python admin(18864): sys.prefix = /usr admin(18864): sys.exec_prefix = /usr admin(18864): sys.path = /usr admin(18864): sys.platform = linux2 admin(18864): [----- Environment Variables -----] admin(18864): SERVER_SOFTWARE: Apache/1.3.33 (Debian GNU/Linux) PHP/4.3.10-18 mod_ssl/2.8.22 OpenSSL/0.9.7e admin(18864): SCRIPT_NAME: /mailman/listinfo admin(18864): SERVER_SIGNATURE: <ADDRESS>Apache/1.3.33 Server at wa9als.com Port 443</ADDRESS> admin(18864): admin(18864): REQUEST_METHOD: GET admin(18864): SERVER_PROTOCOL: HTTP/1.1 admin(18864): QUERY_STRING: admin(18864): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) admin(18864): HTTP_CONNECTION: Keep-Alive admin(18864): SERVER_NAME: wa9als.com admin(18864): REMOTE_ADDR: 64.105.150.50 admin(18864): SERVER_PORT: 443 admin(18864): SERVER_ADDR: 64.105.150.51 admin(18864): DOCUMENT_ROOT: /home/wa9als/www/ admin(18864): PYTHONPATH: /var/lib/mailman admin(18864): SCRIPT_FILENAME: /var/lib/mailman/cgi-bin//listinfo admin(18864): SERVER_ADMIN: john@wa9als.com admin(18864): HTTP_HOST: wa9als.com admin(18864): HTTPS: on admin(18864): REQUEST_URI: /mailman/listinfo admin(18864): HTTP_ACCEPT: */* admin(18864): nokeepalive: 1 admin(18864): GATEWAY_INTERFACE: CGI/1.1 admin(18864): REMOTE_PORT: 33765 admin(18864): HTTP_ACCEPT_LANGUAGE: en-us admin(18864): ssl_unclean_shutdown: 1 admin(18864): HTTP_ACCEPT_ENCODING: gzip, deflate
and just before the above (when I wasn't even home), I see:
Mar 02 21:06:00 2007 admin(18250): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(18250): [----- Mailman Version: 2.1.5 -----] admin(18250): [----- Traceback ------] admin(18250): Traceback (most recent call last): admin(18250): File "/var/lib/mailman/scripts/driver", line 110, in run_main admin(18250): main() admin(18250): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 42, in main admin(18250): listinfo_overview() admin(18250): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 88, in listinfo_overview admin(18250): if mlist.advertised: admin(18250): File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ admin(18250): raise AttributeError, name admin(18250): AttributeError: advertised admin(18250): [----- Python Information -----] admin(18250): sys.version = 2.3.5 (#2, Oct 16 2006, 19:19:48) [GCC 3.3.5 (Debian 1:3.3.5-13)] admin(18250): sys.executable = /usr/bin/python admin(18250): sys.prefix = /usr admin(18250): sys.exec_prefix = /usr admin(18250): sys.path = /usr admin(18250): sys.platform = linux2 admin(18250): [----- Environment Variables -----] admin(18250): SERVER_SOFTWARE: Apache/1.3.33 (Debian GNU/Linux) PHP/4.3.10-18 mod_ssl/2.8.22 OpenSSL/0.9.7e admin(18250): SCRIPT_NAME: /mailman/listinfo admin(18250): SERVER_SIGNATURE: <ADDRESS>Apache/1.3.33 Server at wa9als.com Port 80</ADDRESS> admin(18250): admin(18250): REQUEST_METHOD: GET admin(18250): SERVER_PROTOCOL: HTTP/1.1 admin(18250): QUERY_STRING: admin(18250): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) admin(18250): HTTP_CONNECTION: Keep-Alive admin(18250): SERVER_NAME: wa9als.com admin(18250): REMOTE_ADDR: 64.105.150.50 admin(18250): SERVER_PORT: 80 admin(18250): SERVER_ADDR: 64.105.150.51 admin(18250): DOCUMENT_ROOT: /home/wa9als/www/ admin(18250): PYTHONPATH: /var/lib/mailman admin(18250): SCRIPT_FILENAME: /var/lib/mailman/cgi-bin//listinfo admin(18250): SERVER_ADMIN: john@wa9als.com admin(18250): HTTP_HOST: wa9als.com admin(18250): REQUEST_URI: /mailman/listinfo admin(18250): HTTP_ACCEPT: */* admin(18250): GATEWAY_INTERFACE: CGI/1.1 admin(18250): REMOTE_PORT: 33340 admin(18250): HTTP_ACCEPT_LANGUAGE: en-us admin(18250): HTTP_ACCEPT_ENCODING: gzip, deflate
------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/dhottinger%40harrisonbu...
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Does mailman own those directory's? I seem to remember seeing a similiar issue on the list.
"list" does.
John Fleming wrote:
The .pck files are OK. My lists are working again after -another- qrunner restart and nothing else changed. However, there's still a problem. I can view any individual list's information via the usual web pages (www.domain.name/mailman/listinfo/<listname>), but I get the "We hit a bug" page when I try to view the lists -overview- page for any of my domains. Here's the error log entry for when I try. Does anyone see what's wrong? This used to work, and I haven't changed anything in my configuration. (Mailman 2.1.5 Debian Stable) Thanks - John
Mar 02 21:35:33 2007 admin(18864): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(18864): [----- Mailman Version: 2.1.5 -----] admin(18864): [----- Traceback ------] admin(18864): Traceback (most recent call last): admin(18864): File "/var/lib/mailman/scripts/driver", line 110, in run_main admin(18864): main() admin(18864): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 42, in main admin(18864): listinfo_overview() admin(18864): File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 88, in listinfo_overview admin(18864): if mlist.advertised: admin(18864): File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ admin(18864): raise AttributeError, name admin(18864): AttributeError: advertised
You have one list whose saved state in config.pck does not have an 'advertised' attribute. Try the following shell script #! /bin/sh for list in `/path/to/bin/list_lists --bare` do echo ---------------------------------- echo list: $list /path/to/bin/dumpdb /path/to/lists/$list/config.pck | grep advertised echo ----------------------------------- done -- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro wrote:
Try the following shell script
#! /bin/sh for list in
/path/to/bin/list_lists --bare
do echo ---------------------------------- echo list: $list /path/to/bin/dumpdb /path/to/lists/$list/config.pck | grep advertised echo ----------------------------------- done
BTW, this will only identify the problem list. If the only thing wrong with it is the missing advertised attribute, you can fix it with withlist.
bin/withlist -l listname ... ...
m.advertised = 1 m.Save()
...
The last input is control-D (eof). If the list should not be advertised, then set m.advertised = 0.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
----- Original Message ----- From: "Mark Sapiro" <msapiro@value.net> To: "John Fleming" <john@wa9als.com>; <mailman-users@python.org> Sent: Friday, March 02, 2007 10:17 PM Subject: Re: [Mailman-Users] Urgent newbie help - "Hit a bug" page
Mark Sapiro wrote:
Try the following shell script
#! /bin/sh for list in
/path/to/bin/list_lists --bare
do echo ---------------------------------- echo list: $list /path/to/bin/dumpdb /path/to/lists/$list/config.pck | grep advertised echo ----------------------------------- doneBTW, this will only identify the problem list. If the only thing wrong with it is the missing advertised attribute, you can fix it with withlist.
bin/withlist -l listname ... ...
m.advertised = 1 m.Save()
...
The last input is control-D (eof). If the list should not be advertised, then set m.advertised = 0.
- I must be doing something wrong - Running that script only gives me:
Luke:/var/lib/mailman# ./johntest <----- the script sh-2.05b#
There are other atribute errors in the log - I see name and language, to name 2. (I haven't changed anything, so why are the atributes missing anyway?)
Luke:/var/lib/mailman/bin# ./withlist -l sked Loading list sked (locked) The variable `m' is the sked MailList instance
Unlocking (but not saving) list: sked Finalizing Luke:/var/lib/mailman/bin#
John Fleming wrote:
- I must be doing something wrong - Running that script only gives me:
Luke:/var/lib/mailman# ./johntest <----- the script sh-2.05b#
Yes. something is wrong because apparently, bin/sh is trying to read its input from the terminal instead of the script. What is the exact contents of johntest? What if you run
bin/sh ./johntest
instead?
- There are other atribute errors in the log - I see name and language, to name 2. (I haven't changed anything, so why are the atributes missing anyway?)
With any luck, it will only be one bad list. Once we identify which one, we can wory about fixing it.
I have no idea how it got broken. Did you have a system crash? power failure? some similar event?
- Luke:/var/lib/mailman/bin# ./withlist -l sked Loading list sked (locked) The variable `m' is the sked MailList instance
Unlocking (but not saving) list: sked Finalizing Luke:/var/lib/mailman/bin#
Before we start trying to do things with withlist, we need to identify the list that has the problem. Once we figure that out, you can for example do bin/dumpdb of that list's config.pck and compare it to bin/dumpdb of some other list's config.pck and get an idea of how badly it's messed up.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
----- Original Message ----- From: "Mark Sapiro" <msapiro@value.net> To: "John Fleming" <john@wa9als.com>; <mailman-users@python.org> Sent: Friday, March 02, 2007 11:11 PM Subject: Re: [Mailman-Users] Urgent newbie help - "Hit a bug" page
John Fleming wrote:
- I must be doing something wrong - Running that script only gives me:
Luke:/var/lib/mailman# ./johntest <----- the script sh-2.05b#
Yes. something is wrong because apparently, bin/sh is trying to read its input from the terminal instead of the script. What is the exact contents of johntest? What if you run
bin/sh ./johntest
instead?
Same thing as before. Here's the script:
Luke:/var/lib/mailman# cat johntest
! /bin/sh
for list in /var/lib/mailman/bin/list_lists --bare
do echo ----------------------------------
echo list: $list
/var/lib/mailman/bin/dumpdb /var/lib/mailman/lists/$list/config.pck | grep
advertised
echo -----------------------------------
doneLuke:/var/lib/mailman#
I don't know what I'm missing about running this script. Looking through the .pck files manually, they all seem to have the attributes real_name, language, and advertised - things that appeared in the error log. Some are advertised and some are not, but they all have that entry.
I have no idea how it got broken. Did you have a system crash? power failure? some similar event?
No, really. Server on UPS. There could have been a brief burp, but UPS -should've- protected me from that.
I received an email from a list member that a list wasn't working. I restarted qrunner to no avail, rebooted the server to no avail, and then restarted qrunner again and then the lists all started working again. The "We hit a bug" webpage problem persisted throughout.
Thanks for your patience - really. If I resort to my month-old backup, should I just replace the /lists directory? - John
John Fleming wrote:
Same thing as before. Here's the script:
Luke:/var/lib/mailman# cat johntest ! /bin/sh
This line needs to begin with a '#'
#! /bin/sh
for list in
/var/lib/mailman/bin/list_lists --bare
do echo ---------------------------------- echo list: $list /var/lib/mailman/bin/dumpdb /var/lib/mailman/lists/$list/config.pck | grep advertised echo ----------------------------------- doneLuke:/var/lib/mailman#
And there should be a newline after 'done'
I don't know what I'm missing about running this script. Looking through the .pck files manually, they all seem to have the attributes real_name, language, and advertised - things that appeared in the error log. Some are advertised and some are not, but they all have that entry.
Maybe there's a list you're not looking at. Does 'bin/list_lists' or 'ls -l /var/mailman/lists/' show anything you're not looking at?
I have no idea how it got broken. Did you have a system crash? power failure? some similar event?
No, really. Server on UPS. There could have been a brief burp, but UPS -should've- protected me from that.
I received an email from a list member that a list wasn't working. I restarted qrunner to no avail, rebooted the server to no avail, and then
Was Mailman running when you rebooted? Also, is it possible you had multiple instances of Mailman running when you rebooted so that a shutdown script if any didn't stop them all? See <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.068.htp>
- not for the problem, but for the solution.
Do ps auxww | egrep 'p[y]thon' or ps -fAww | egrep 'p[y]thon' or however you might spell it on your system to see that only one mailmanctl process and one of each of eight qrunner processes are running.
restarted qrunner again and then the lists all started working again. The "We hit a bug" webpage problem persisted throughout.
Thanks for your patience - really. If I resort to my month-old backup, should I just replace the /lists directory? - John
There is probably only one bad list, so no, don't replace the directory. Find the bad list first and then perhaps replace its list/listname directory or, if possible, use the config.pck.last or fix the config.pck.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
----- Original Message ----- From: "Mark Sapiro" <msapiro@value.net> To: "John Fleming" <john@wa9als.com>; <mailman-users@python.org> Sent: Saturday, March 03, 2007 9:43 AM Subject: Re: [Mailman-Users] Urgent newbie help - "Hit a bug" page
John Fleming wrote:
Same thing as before. Here's the script:
Luke:/var/lib/mailman# cat johntest ! /bin/sh
This line needs to begin with a '#'
#! /bin/sh
Duh - thanks.
The output I get now I think is the same as in the error log:
Luke:/var/lib/mailman# ./johntest Traceback (most recent call last): File "/var/lib/mailman/bin/list_lists", line 122, in ? main() File "/var/lib/mailman/bin/list_lists", line 102, in main longest = max(len(mlist.real_name), longest) File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ raise AttributeError, name AttributeError: real_name Luke:/var/lib/mailman#
- but I don't see any list-specific info!
And, here's the result of bin/list_lists: (same as above)
Maybe there's a list you're not looking at. Does 'bin/list_lists' or 'ls -l /var/mailman/lists/' show anything you're not looking at?
list_lists gives me the same error:
Luke:/var/lib/mailman/bin# ./list_lists Traceback (most recent call last): File "./list_lists", line 122, in ? main() File "./list_lists", line 102, in main longest = max(len(mlist.real_name), longest) File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ raise AttributeError, name AttributeError: real_name Luke:/var/lib/mailman/bin#
There were a couple of lists I hadn't looked at (getting tedious to do it manually) because they hadn't been used for a year or more. However, they also look OK to me. (They are not corrupted files, and the real_name values are correct, and nothing else seems amiss to me.)
We're still not getting the expected results from the script though...??
Was Mailman running when you rebooted?
The first thing I did was restart mailman, and I got the initial message "qrunner not running", so no, it had stopped. It restarted without further error, but the web problem was still there and the lists apparently were not working. Same thing after the reboot. But then after another qrunner restart, then I started receiving a backlog of messages from various lists (plural).
Also, is it possible you had
multiple instances of Mailman running when you rebooted so that a shutdown script if any didn't stop them all? See <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.068.htp>
- not for the problem, but for the solution.
Do ps auxww | egrep 'p[y]thon' or ps -fAww | egrep 'p[y]thon' or however you might spell it on your system to see that only one mailmanctl process and one of each of eight qrunner processes are running.
Yup:
Luke:/var/lib/mailman# ps auxww | egrep 'p[y]thon' list 11070 0.0 0.5 7792 5416 ? Ss Mar02 0:00 /usr/bin/python /usr/lib/mailman/bin/mailmanctl start list 11086 0.0 0.5 7592 5288 ? S Mar02 0:00 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s list 11087 0.0 0.6 8188 6284 ? S Mar02 0:00 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s list 11088 0.0 0.5 7620 5300 ? S Mar02 0:00 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s list 11089 0.0 0.9 11900 9800 ? S Mar02 0:03 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s list 11090 0.0 0.5 7600 5328 ? S Mar02 0:00 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s list 11091 0.0 0.6 8280 6320 ? S Mar02 0:01 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s list 11092 0.0 0.5 8264 6192 ? S Mar02 0:00 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s list 11093 0.0 0.5 7508 5288 ? S Mar02 0:00 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s Luke:/var/lib/mailman#
There is probably only one bad list, so no, don't replace the directory. Find the bad list first and then perhaps replace its list/listname directory or, if possible, use the config.pck.last or fix the config.pck.
OK - Comments on the script that is not giving list-specific info?
And, I assume we're still on the same page about the problem: The list overview web page gives an error when trying to view all of the advertised lists on -ANY- of my domains (all hosted on the same server) e.g. www.one.domain/mailman/. (As you know, if there are no advertised lists on a domain, we should get a nice web page stating that fact - or the advertised lists etc.) If I ask about a -specific- list www.one.domain/mailman/listinfo/<listname>, I get the expected web page without error.
- John
John Fleming wrote:
list_lists gives me the same error:
Luke:/var/lib/mailman/bin# ./list_lists Traceback (most recent call last): File "./list_lists", line 122, in ? main() File "./list_lists", line 102, in main longest = max(len(mlist.real_name), longest) File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ raise AttributeError, name AttributeError: real_name Luke:/var/lib/mailman/bin#
I might have anticipated that, but oh well.
Replace the line
for list in /var/lib/mailman/bin/list_lists --bare
with
for list in ls /var/lib/mailman/lists
<snip>
OK - Comments on the script that is not giving list-specific info?
bin/list_lists runs into the same problem so the script can't run as it was.
And, I assume we're still on the same page about the problem: The list overview web page gives an error when trying to view all of the advertised lists on -ANY- of my domains (all hosted on the same server) e.g. www.one.domain/mailman/. (As you know, if there are no advertised lists on a domain, we should get a nice web page stating that fact - or the advertised lists etc.) If I ask about a -specific- list www.one.domain/mailman/listinfo/<listname>, I get the expected web page without error.
Right, but the first thing the listinfo overview does is look at every list to figure out which of those lists are advertised and in the current domain. In the process of looking at every list, it hits one without an advertised attribute.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
----- Original Message ----- From: "Mark Sapiro" <msapiro@value.net> To: "John Fleming" <john@wa9als.com>; <mailman-users@python.org> Sent: Saturday, March 03, 2007 10:45 AM Subject: Re: [Mailman-Users] Urgent newbie help - "Hit a bug" page
Replace the line
for list in
/var/lib/mailman/bin/list_lists --bare
with
for list in
ls /var/lib/mailman/lists
<snip>
OK, finally, that gives the expected output (below) - Only it just lists all of my lists (only 12) with their expected advertised attributes, some 0 and some 1. No errors about any of them being missing. I also ran it grepping for "real_name" and also got the expected output for all 12 lists. This doesn't surprise me because I knew from looking manually that they all had the "advertised" and "real_name" attributes. I'm also not too excited that simply restoring backup .pck files are going to fix the problem at this point...?
Luke:/var/lib/mailman# ./johntest
list: 40days 'advertised': 1,
list: adboard 'advertised': 1,
list: communications 'advertised': 1,
list: flemings 'advertised': 0,
<snip> Luke:/var/lib/mailman#
John Fleming wrote:
OK, finally, that gives the expected output (below) - Only it just lists all of my lists (only 12) with their expected advertised attributes, some 0 and some 1. No errors about any of them being missing. I also ran it grepping for "real_name" and also got the expected output for all 12 lists.
Try the following:
Make a copy of bin/list_lists in the bin/ directory. Say
cp bin/list_lists bin/my_list_lists
Edit this my_list_lists file - find
mlists = []
longest = 0
for n in names:
mlist = MailList.MailList(n, lock=0)
if advertised and not mlist.advertised:
continue
if vhost and mm_cfg.VIRTUAL_HOST_OVERVIEW and \
vhost.find(mlist.web_page_url) == -1 and \
mlist.web_page_url.find(vhost) == -1:
continue
mlists.append(mlist)
longest = max(len(mlist.real_name), longest)
and add the line ' print n' so it becomes
mlists = []
longest = 0
for n in names:
print n
mlist = MailList.MailList(n, lock=0)
if advertised and not mlist.advertised:
continue
if vhost and mm_cfg.VIRTUAL_HOST_OVERVIEW and \
vhost.find(mlist.web_page_url) == -1 and \
mlist.web_page_url.find(vhost) == -1:
continue
mlists.append(mlist)
longest = max(len(mlist.real_name), longest)
Make sure that 'print' is indented exactly 8 spaces. Then run bin/my_list_lists.
This should print list names one by one until it throws the exception and prints the traceback. The last name printed has a problem. Temporarily move this list aside
mv /var/lib/mailman/thislist /somewhere/outside/mailman/thislist
and then run bin/my_list_lists again to see if there are any problems. If not, you've identified the one problem list. There is something wrong with this list's config.pck. There is something mysterious if various software says this list doesn't have an 'advertised' or 'real_name' attribute, yet bin/dumpdb says it does.
OTOH, maybe bin/my_list_lists fails on the first list and then when you move that list aside, it fails on the next one and so on. This would incriminate the software somehow and not a list.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
----- Original Message ----- From: "Mark Sapiro" <msapiro@value.net>
Try the following:
and add the line ' print n' so it becomes
mlists = [] longest = 0 for n in names: print n mlist = MailList.MailList(n, lock=0) if advertised and not mlist.advertised: continue if vhost and mm_cfg.VIRTUAL_HOST_OVERVIEW and
vhost.find(mlist.web_page_url) == -1 and
mlist.web_page_url.find(vhost) == -1: continue mlists.append(mlist) longest = max(len(mlist.real_name), longest)Make sure that 'print' is indented exactly 8 spaces. Then run bin/my_list_lists.
This should print list names one by one until it throws the exception and prints the traceback. The last name printed has a problem. Temporarily move this list aside
mv /var/lib/mailman/thislist /somewhere/outside/mailman/thislist
and then run bin/my_list_lists again to see if there are any problems. If not, you've identified the one problem list. There is something wrong with this list's config.pck. There is something mysterious if various software says this list doesn't have an 'advertised' or 'real_name' attribute, yet bin/dumpdb says it does.
OTOH, maybe bin/my_list_lists fails on the first list and then when you move that list aside, it fails on the next one and so on. This would incriminate the software somehow and not a list.
BINGO! The results listed several lists without error, and then there was the attribute error for real_name. The preceeding list was the mailman list! So with appropriate backups, I renamed the mailman list's config.pck.last file to config.pck and ran mylist_lists again, and it ran without error, listing all of my lists! And guess what, the list overview web page works as expected now!
Luke:/var/lib/mailman/bin# ./mylist_lists <listname> <listname> <listname> <listname> mailman Traceback (most recent call last): File "./mylist_lists", line 123, in ? main() File "./mylist_lists", line 103, in main longest = max(len(mlist.real_name), longest) File "/var/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ raise AttributeError, name AttributeError: real_name Luke:/var/lib/mailman/bin#
Do you agree that there was something VERY subtle about what was wrong with it? Here's a snippet from the original config.pck:
'preferred_language': 'en',
'private_roster': 1,
'real_name': 'Mailman',
'reject_these_nonmembers': [],
'reply_goes_to_list': 0,
The real_name -looks- OK to a text editor, no?
Here's how it looks now:
'preferred_language': 'en',
'private_roster': 1,
'real_name': 'Mailman',
'reject_these_nonmembers': [],
'reply_goes_to_list': 0,
Running diff adds to the confusion, and it's getting difficult to explain.
If I diff the present (working) config.pck (the renamed config.pck.last file) and config-orig.pck (the problem file), there is NO DIFFERENCE. However, if I diff config-orig.pck (problem file) and config.pck.last.orig (the original pck.last file), there IS a difference!! So it seems that simply renaming the "same" (according to diff) file fixed the problem?! Some very subtle binary difference not detectable in the text output from dumpdb??
Luke:/var/lib/mailman/lists/mailman# diff config.pck config-orig.pck Luke:/var/lib/mailman/lists/mailman#
Luke:/var/lib/mailman/lists/mailman# diff config-orig.pck config.pck.last.orig Binary files config-orig.pck and config.pck.last.orig differ
============================================== A special THANK YOU to Mark Shapiro for his patient and detailed help on this problem. Hopefully something in this thread has helped someone else now or in the future! - John
John Fleming wrote:
BINGO! The results listed several lists without error, and then there was the attribute error for real_name. The preceeding list was the mailman list! So with appropriate backups, I renamed the mailman list's config.pck.last file to config.pck and ran mylist_lists again, and it ran without error, listing all of my lists! And guess what, the list overview web page works as expected now!
That's great! I'm glad it's now working again.
Do you agree that there was something VERY subtle about what was wrong with it? Here's a snippet from the original config.pck:
'preferred_language': 'en', 'private_roster': 1, 'real_name': 'Mailman', 'reject_these_nonmembers': [], 'reply_goes_to_list': 0,
The real_name -looks- OK to a text editor, no?
Yes, it looks fine.
Here's how it looks now:
'preferred_language': 'en', 'private_roster': 1, 'real_name': 'Mailman', 'reject_these_nonmembers': [], 'reply_goes_to_list': 0,
And yes, this looks the same. One thing I thought of - are both of these excerpts from something identified by bin/dumpdb as 'object 1' in the file. i.e. directly below the lines
[----- start pickle file -----] <----- start object 1 ----->
with no intervening
<----- start object 2 ----->
Running diff adds to the confusion, and it's getting difficult to explain.
If I diff the present (working) config.pck (the renamed config.pck.last file) and config-orig.pck (the problem file), there is NO DIFFERENCE.
Very strange indeed. Of course, every time Mailman saves a list, it goes through a complex dance, the result of which is rotating the existing config.pck to config.pck.last and saving the new config.pck, but with more safety than just doing that directly.
However, if I diff config-orig.pck (problem file) and config.pck.last.orig (the original pck.last file), there IS a difference!!
Have the timestamps changed? maybe Mailman Saved the list in the mean time. However, that would not explain why diff says that config-orig.pck, and the current config.pck are the same, yet one works and the other didn't. That is the real mystery, and I have no answer for that.
So it seems that simply renaming the "same" (according to diff) file fixed the problem?! Some very subtle binary difference not detectable in the text output from dumpdb??
Still, diff 'should' detect a difference. Are the files the same length? What does
cmp config.pck config-orig.pck
say?
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
----- Original Message ----- From: "Mark Sapiro" <msapiro@value.net>
And yes, this looks the same. One thing I thought of - are both of these excerpts from something identified by bin/dumpdb as 'object 1' in the file. i.e. directly below the lines
[----- start pickle file -----] <----- start object 1 ----->
with no intervening
<----- start object 2 ----->
-YES-
Running diff adds to the confusion, and it's getting difficult to explain.
If I diff the present (working) config.pck (the renamed config.pck.last file) and config-orig.pck (the problem file), there is NO DIFFERENCE.
Have the timestamps changed? maybe Mailman Saved the list in the mean time. However, that would not explain why diff says that config-orig.pck, and the current config.pck are the same, yet one works and the other didn't. That is the real mystery, and I have no answer for that.
So it seems that simply renaming the "same" (according to diff) file fixed the problem?! Some very subtle binary difference not detectable in the text output from dumpdb??
Still, diff 'should' detect a difference. Are the files the same length? What does
cmp config.pck config-orig.pck
Luke:/var/lib/mailman/lists/mailman# cmp config.pck config-orig.pck config.pck config-orig.pck differ: char 46, line 2 Luke:/var/lib/mailman/lists/mailman#
Line 2 in the dumpdb output does not have 46 characters, so I assume this refers to the raw file??
Now look at this:
Luke:/var/lib/mailman/lists/mailman# cmp config-orig.pck config.pck.last.orig config-orig.pck config.pck.last.orig differ: char 46, line 2 Luke:/var/lib/mailman/lists/mailman#
So the first and third cmp results above are consistent and show the same difference.
***** And if you're not already going crazy, this will do it:
Earlier I sent you this diff result:
Luke:/var/lib/mailman/lists/mailman# diff config.pck config-orig.pck Luke:/var/lib/mailman/lists/mailman#
But now when I run it, I get:
Luke:/var/lib/mailman/lists/mailman# diff config.pck config-orig.pck Binary files config.pck and config-orig.pck differ Luke:/var/lib/mailman/lists/mailman#
So I think we've finally beaten the horse to death and I can barely keep it straight anymore! These are all cut and paste results, so it's not just my memory!
I don't under stand why they diff'ed the same this morning and not now!
Anyway, we know something was wrong with config.pck and using the config.pck.last file fixed it.
- John
participants (3)
-
dhottingerï¼ harrisonburg.k12.va.us
-
John Fleming
-
Mark Sapiro