headers
J.A. Terranson | 1 Dec 2008 04:00

List "disappears" now.


So, we've gone from disappearing 'space" to a disappearing list!

The machine in question has no disappearing space, but after running
flawlessly for 6/7 months, the "lists" page only shows 3 out of the four
active lists (there's 2 admins, but I'm the only one who would do
anything other than approve messages).

at http://lists.domain.com/mailman/listinfo/
I see

	list2	Description
	list3	Description
	list4	Description

--> list1 is *gone*, yet is is fully operational and carrying heavy
traffic.  i can reach list1 directly at

http://lists.domain.com/mailman/listinfo/list1

On the file systems, everything *seems* OK (I ran perm_chk to be sure):

[root <at> lists /usr/spv/mailman]# ls -al lists
total 14
drwxrwsr-x   7 root     mailman  512 Jul  1 12:57 .
drwxrwsr-x  19 mailman  mailman  512 Nov 27 14:47 ..
drwxrwsr-x   3 apache   mailman  512 Nov 30 20:34 list1
drwxrwsr-x   3 apache   mailman  512 Nov 30 18:35 list2
drwxrwsr-x   2 root     mailman  512 Nov 30 00:10 mailman
drwxrwsr-x   3 apache   mailman  512 Nov 30 20:48 list3
(Continue reading)

Permalink | Reply | 4 comments |
headers
Mark Sapiro | 1 Dec 2008 04:08
Favicon

Re: List "disappears" now.

J.A. Terranson wrote:
>
>So, we've gone from disappearing 'space" to a disappearing list!

And what is the status of disappearing 'space"?

>The machine in question has no disappearing space, but after running
>flawlessly for 6/7 months, the "lists" page only shows 3 out of the four
>active lists (there's 2 admins, but I'm the only one who would do
>anything other than approve messages).

See the FAQ at <http://wiki.list.org/x/6oA9>

--

-- 
Mark Sapiro <mark <at> msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
Permalink | Reply | 3 comments |
headers
Mark Sapiro | 1 Dec 2008 04:12
Favicon

Re: List "disappears" now.

Mark Sapiro wrote:
>
>And what is the status of disappearing 'space"?

Having not read far enough down in your post.

>(BTW, the box with the disappearing space looks like logfiles - not done
>there yet, but I'm 90% certain it's rotation)

--

-- 
Mark Sapiro <mark <at> msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
Permalink | Reply | 0 comments |
headers
J.A. Terranson | 1 Dec 2008 04:41

Re: List "disappears" now.


On Sun, 30 Nov 2008, Mark Sapiro wrote:

> See the FAQ at <http://wiki.list.org/x/6oA9>

What, besides clicking the web interface, would cause this to flip?  2
people have the password.  I haven't been there since I set this up months
ago, and I checked with the other admin, and she says shes only approved
postings, and is afraid of the rest of the UI (I believe that BTW-she's
just *terrified* of the ui).

I though about this and then dismissed it - improperly it would seem
(blushing), as I should be the only one to touch it.

Thanks for allowing me to be a genuine schmuck :-)  I both appreciate the
help, and the self-inflicted reminder to check the obvious even if its
impossible.

Nevertheless, just for me, was there another way?

//Alif

--

-- 
Yours,
J.A. Terranson
sysadmin_at_mfn.org
0xpgp_key_mgmt_is_broken-dont_bother

"Never belong to any party, always oppose privileged classes and public
plunderers, never lack sympathy with the poor, always remain devoted to
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mark Sapiro | 1 Dec 2008 05:12
Favicon

Re: List "disappears" now.

J.A. Terranson
>
>Nevertheless, just for me, was there another way?

List attributes like advertised can be changed via the web admin ui and
via command line tools, e.g. bin/config_list and bin/withlist.

They can also be inadvertently changed by restoring old backups of the
lists/LISTNAME/config.pck file, but that doesn't seem to be much of a
possibility here.

There is one other rare possibility. If the list was originally created
as a Mailman 2.0 list and migrated to 2.1, the migration converted the
2.0 lists/LISTNAME/config.db file to an "equivalent
lists/LISTNAME/config.pck, but it left the lists/LISTNAME/config.db
file in place. You should remove these files or move them aside. The
reason is if somehow hboth the lists/LISTNAME/config.pck and
lists/LISTNAME/config.pck.last files should become corrupt and
unreadable, Mailman will fall back to the now ancient
lists/LISTNAME/config.db if there is one. It is also not likely that
this was the reason either.

As far as I know, no other Mailman process changes these attributes.

--

-- 
Mark Sapiro <mark <at> msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
Permalink | Reply | 0 comments |
headers
Richard Hartmann | 1 Dec 2008 10:21
Picon
Gravatar

Strange error with Mailman 2.1.9

Hi all,

I have this in my error log:

Nov 27 09:53:19 2008 post(18252): Traceback (most recent call last):
post(18252):   File "/usr/lib/mailman/scripts/post", line 69, in ?
post(18252):      main()
post(18252):   File "/usr/lib/mailman/scripts/post", line 64, in main
post(18252):      tolist=1, _plaintext=1)
post(18252):   File "/usr/lib/mailman/Mailman/Queue/Switchboard.py",
line 137, in enqueue
post(18252):      os.fsync(fp.fileno())
post(18252): OSError :  [Errno 5] Input/output error
post(19319):   File "/usr/lib/mailman/scripts/post", line 64, in main
post(19319):      tolist=1, _plaintext=1)
post(19319):   File "/usr/lib/mailman/Mailman/Queue/Switchboard.py",
line 137, in enqueue
post(19319):      os.fsync(fp.fileno())
post(19319): OSError :  [Errno 5] Input/output error
Nov 28 11:49:40 2008 post(927): Traceback (most recent call last):
post(927):   File "/usr/lib/mailman/scripts/post", line 69, in ?
post(927):      main()
post(927):   File "/usr/lib/mailman/scripts/post", line 64, in main
post(927):      tolist=1, _plaintext=1)
post(927):   File "/usr/lib/mailman/Mailman/Queue/Switchboard.py",
line 137, in enqueue
post(927):      os.fsync(fp.fileno())
post(927): OSError :  [Errno 5] Input/output error

And my in looks like:
(Continue reading)

Permalink | Reply | 11 comments |
headers
Richard Hartmann | 1 Dec 2008 11:14
Picon
Gravatar

Re: Strange error with Mailman 2.1.9

Further info:

Restarting mailman gives me

# /etc/init.d/mailman restart
Shutting down mailman

                                                      done
rm: cannot remove `/var/lib/mailman/locks/*': No such file or directory
Starting mailmanrm: cannot remove `/var/lib/mailman/locks/*': No such
file or directory
 # ls -l /var/lib/mailman/locks/
total 8
-rw-rw-r--  2 mailman mailman 49 Dec  2  2008 master-qrunner
-rw-rw-r--  2 mailman mailman 49 Dec  2  2008 master-qrunner.plesk1.6444
#

I tried stopping mailman, moving the messages to shunt/, starting Mailman again
and then running bin/unshunt, but that does not work, either. Neither does this
produce any new log output.

Any and all ideas appreciated..
Richard
Permalink | Reply | 10 comments |
headers
Richard Hartmann | 1 Dec 2008 11:50
Picon
Gravatar

Re: Strange error with Mailman 2.1.9

Even more info (should have stated that in the first email):

This is a NFS share. So it might 'just' be a crappy net connection.

Any thoughts about this patch which I plan to apply locally?
Beware evil GMail linebreaks..

--- /usr/lib/mailman/Mailman/Queue/Switchboard.py.orig  2008-12-01
11:46:31.524425955 +0100
+++ /usr/lib/mailman/Mailman/Queue/Switchboard.py       2008-12-01
11:48:39.676765175 +0100
 <at>  <at>  -134,7 +134,19  <at>  <at> 
                 fp.write(msgsave)
                 cPickle.dump(data, fp, protocol)
                 fp.flush()
-                os.fsync(fp.fileno())
+                # os.fsync(fp.fileno())
+                # Sometimes, the sync to our NFS share fails. This retries
+                # nine times and then gives up -- RichiH 081201
+                for trial in xrange(10):
+                    try:
+                        os.fsync(fp.fileno())
+                    except OSError, e:
+                        if trial == 9 or e.errno != errno.EIO:
+                            raise
+                        time.sleep(1)
+                        continue
+                    else:
+                        break
             finally:
(Continue reading)

Permalink | Reply | 1 comment |
headers
J.A. Terranson | 1 Dec 2008 15:14

Re: Strange error with Mailman 2.1.9


On Mon, 1 Dec 2008, Richard Hartmann wrote:

> Restarting mailman gives me
>
> # /etc/init.d/mailman restart
> Shutting down mailman
>
>                                                       done
> rm: cannot remove `/var/lib/mailman/locks/*': No such file or directory
> Starting mailmanrm: cannot remove `/var/lib/mailman/locks/*': No such
> file or directory

try this:

	./mailmanctl stop
	./mailmanctl --stale-lock-cleanup start

--

-- 
Yours,
J.A. Terranson
sysadmin_at_mfn.org
0xpgp_key_mgmt_is_broken-dont_bother

"Never belong to any party, always oppose privileged classes and public
plunderers, never lack sympathy with the poor, always remain devoted to
the public welfare, never be satisfied with merely printing news, always
be drastically independent, never be afraid to attack wrong, whether by
predatory plutocracy or predatory poverty."
(Continue reading)

Permalink | Reply | 1 comment |
headers
Richard Hartmann | 1 Dec 2008 17:27
Picon
Gravatar

Re: Strange error with Mailman 2.1.9

On Mon, Dec 1, 2008 at 15:14, J.A. Terranson <measl <at> mfn.org> wrote:

> try this:
>
>        ./mailmanctl stop
>        ./mailmanctl --stale-lock-cleanup start

Nope, the warnings are still there. I don't really care about those, though.
My main concern is to make Mailman reliably relay list mail.

Thanks though!
Rihcard
Permalink | Reply | 0 comments |

Gmane