Re: [Mailman-Users] We're sorry, we hit a bug!

2015-01-10 Thread Steve Matzura
Well, on a new implementation, I'm getting the same thing in 2.18-1.
What'd you do to fix it on your end?

On Tue, 1 Jul 2014 17:33:19 +0200, you wrote:

Mark Sapiro m...@msapiro.net wrote:


 The above message indicates the traceback was written to some 'error' log,
 just not the one you're looking at.
 
 You can always edit (temporarily) Mailman's scripts/driver and at line 33
 change
 
 STEALTH_MODE = 1
 
 to
 
 STEALTH_MODE = 0
 
 and that will allow the traceback and other diagnostic info to be displayed
 instead of the We're sorry, we hit a bug! message.
 
 
  Would like to show some logging, but it simply is not there.
 
 
 It was successfully written to an 'error' log somewhere or the We're sorry,
 we hit a bug! message would say:
 
 Mailman experienced a very low level failure and could not even generate a
 useful traceback for you.  Please report this to the Mailman administrator at
 this site.
 

Thanks Mark, the page is showing that the log location was not writeable, must
be the bug.

Resetting the LOG_DIR to default saved me.

Apologies for the noise.
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] 18-1 Bug with Empty error logfile

2015-01-10 Thread Steve Matzura
I just brought up a new 2.1.18-1 installation and am geting the we're
sorry but we encountered a bug page on theadmin interface.
/var/log/mail/error is 0-length. Should I turn stealth mode off to get
more info possibly?
 
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Tend to pending moderator requests error when logging in

2015-01-10 Thread Brian Carpenter
It is very important that your hosting provider reviews the mailman error
log to see what is causing that error. In my experience it is usually a
permission issue and those are easily fixed. cPanel (which I believe is your
platform, provides scripts that will correct permission problems on
individual lists. Your hosting provider should be able to easily do this for
you. If not send me a private message to inquire more about moving to a host
that gladly supports mailman (that would be us).


Brian Carpenter
Owner

www.mailmanhost.com
www.emwd.com

E: br...@emwd.com
www.emwd.com

 



 -Original Message-
 From: Mailman-Users [mailto:mailman-users-
 bounces+brian=emwd@python.org] On Behalf Of Jim Black
 Sent: Saturday, January 10, 2015 10:15 AM
 To: mailman-users@python.org
 Subject: [Mailman-Users] Tend to pending moderator requests error when
 logging in
 
 Does anyone know how to solve this error problem when clicking on the link
 to
 
 Tend to pending moderator requests
 
 resulting in the error message:
 
 Bug in Mailman version 2.1.18-1
 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.
 
 
 My hosting provider cannot get me the log files, so hopefully there will
be
 others who encountered this problem too.
 
 --
 Mailman-Users mailing list Mailman-Users@python.org
 https://mail.python.org/mailman/listinfo/mailman-users
 Mailman FAQ: http://wiki.list.org/x/AgA3
 Security Policy: http://wiki.list.org/x/QIA9
 Searchable Archives: http://www.mail-archive.com/mailman-
 users%40python.org/
 Unsubscribe: https://mail.python.org/mailman/options/mailman-
 users/brian%40emwd.com

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] 18-1 Bug with Empty error logfile

2015-01-10 Thread Steve Matzura
Yes!Found and fixed three permissions errors. Then I logged in as
asministrator and turned up another perms error, but this time it was
logged to /var/log/mail/error so I was able to find and fix it.
/etc/mailman/adm.pw was +644 owner=root group=roott. check_perms
changed it to group=mailman as it should be. All good now, and of
course, many thanks. It's always the little things.

On Sat, 10 Jan 2015 10:04:43 -0800, you wrote:

On 01/10/2015 07:01 AM, Steve Matzura wrote:
 I just brought up a new 2.1.18-1 installation and am geting the we're
 sorry but we encountered a bug page on theadmin interface.
 /var/log/mail/error is 0-length. Should I turn stealth mode off to get
 more info possibly?


First, try running Mailman's

bin/check_perms -f

as root and see if it fixes permissions on the log directory/files.

Once permissions are fixed, your bug may go away. If not and if there
is still no error log entry, try turning off stealth mode.
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] Tend to pending moderator requests error when logging in

2015-01-10 Thread Jim Black
Does anyone know how to solve this error problem when clicking on the link to 

Tend to pending moderator requests 

resulting in the error message:

Bug in Mailman version 2.1.18-1 
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. 


My hosting provider cannot get me the log files, so hopefully there will be 
others who encountered this problem too.  
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] We're sorry, we hit a bug!

2015-01-10 Thread Mark Sapiro
On 01/10/2015 06:53 AM, Steve Matzura wrote:
 Well, on a new implementation, I'm getting the same thing in 2.18-1.
 What'd you do to fix it on your end?


I think that one was a permissions error. As Mr. Wagenaar reported, he
had overridden the LOG_DIR setting and it pointed to an unwritable location.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Tend to pending moderator requests error when logging in

2015-01-10 Thread Mark Sapiro
On 01/10/2015 07:14 AM, Jim Black wrote:
 Does anyone know how to solve this error problem when clicking on the link to 
 
 Tend to pending moderator requests 
 
 resulting in the error message:
 
 Bug in Mailman version 2.1.18-1 


See my comments in your bug report at
https://bugs.launchpad.net/mailman/+bug/1409292

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] 18-1 Bug with Empty error logfile

2015-01-10 Thread Mark Sapiro
On 01/10/2015 07:01 AM, Steve Matzura wrote:
 I just brought up a new 2.1.18-1 installation and am geting the we're
 sorry but we encountered a bug page on theadmin interface.
 /var/log/mail/error is 0-length. Should I turn stealth mode off to get
 more info possibly?


First, try running Mailman's

bin/check_perms -f

as root and see if it fixes permissions on the log directory/files.

Once permissions are fixed, your bug may go away. If not and if there
is still no error log entry, try turning off stealth mode.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Migration Problem

2015-01-10 Thread Mark Sapiro
On 01/08/2015 04:35 PM, Dennis Putnam wrote:

 I do have the patch files, but I question if they are directly
 compatible with this version so I haven't tried that yet.


Usually when applying patches from a prior version, there are at most
only minor line number offsets. Occasionally there are more serious
conflicts that have to be resolved by hand, but this is normally not
difficult if you understand what the patch is doing.

The only way to know is to apply the patches and see the results. if the
patch command doesn't complain, that patch is good. if it complains only
about line # offsets, it's almost certainly still good, and you can diff
the .orig file the patch command makes with the new file to get a new
patch with correct line numbers. If it complains about failed hunks, you
have to manually examine the .rej file to see the problems and figure
out how to fix them. Often the changed code is good, but the patch fails
because one of the adjacent lines changed.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org