ATTN: Guy Middleton

[James S MacKinnon <jmack@Phys.UAlberta.Ca>]

Here's what I got when I sent you a reply.
You may want to check your deliver script !

At any rate, what I had to say is in the body of this
forwarded message.

Cheers,
--
James S. MacKinnon             Office: P-139 Avahd-Bhatia Physics Lab
Computing/Networking           Voice : (403) 492-8226
Department of Physics
University of Alberta          email : jmack@phys.ualberta.ca
Edmonton, Canada T6G 2N5       bitnet: jmack@triumfcl  jsm1@ualtamts

---------- Forwarded message ----------
Date: Sun, 22 Aug 1993 18:54:34 -0600
From: The Post Office <postmaster@barrow.uwaterloo.ca>
To: jmack@Phys.UAlberta.Ca
Subject: Delivery problems with your mail

A copy of your message is being returned to you due to difficulties
encountered while attempting to deliver your mail.

The following errors occurred during message delivery processing:


<local - "|/software/deliver/bin/deliver gamiddle" 102>: expired after 3 hours, problem was: cannot fdopen(9)

----------  Original Message  ----------
external
rcvdfrom tshimshan.phys.ualberta.ca ([129.128.7.76])
with SMTP
from <jmack@Phys.UAlberta.Ca>
to <gamiddle@barrow.uwaterloo.ca>
Received: by Phys.UAlberta.Ca id <43398>; Sun, 22 Aug 1993 14:16:09 -0600
Date: Sun, 22 Aug 1993 14:06:33 -0600
From: James S MacKinnon <jmack@Phys.UAlberta.Ca>
Subject: Re: does anybody understand mailq debug output?
To: Guy Middleton <gamiddle@barrow.uwaterloo.ca>
In-Reply-To: <93Aug22.004226edt.106098@barrow.uwaterloo.ca>
Message-ID: <Pine.3.07.9308221431.A1707-b100000@tshimshan>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Just looking at the output suggests that the vertex info is a history
of the messages life in the queue, i.e. if it's been re-cycled on hold
and channel fifo history of a particular vertex.

Try running the scheduler in verbose mode. There are some hints in the
code in agenda.c which offer more output for the vertex structures
(essentially what you are seeing when mailq spits out debug output)
that would go into the scheduler log.

It might be that the mailq binary is hanging on your alpha, rather than
the queue itself. I checked your mailq from my machine and got:

121 relay# date
Sun Aug 22 14:10:07 MDT 1993
122 relay# mailq -svd barrow.uwaterloo.ca
[barrow.uwaterloo.ca]
0 entries in router queue: idle
0 entries in scheduler queue: idle
version zmailer 1.0
Vertices:
5368898056:     106096  1; 88
5368898568:     106097  1; 90   #[exit status 1] (retry in 1m44s, expires in 7h25m38s)
Channels:
ph:     >5368898568
local:  >5368898056
Hosts:
-:      >5368898056>5368898568
123 relay#


(which means that the output doesn't hang). You could also try querying another
zmailer site to see if it's just mailq.c that's giving you troubles(i.e. try
relay.phys.ualberta.ca )

Cheers,

James S. MacKinnon             Office: P-139 Avahd-Bhatia Physics Lab
Computing/Networking           Voice : (403) 492-8226
Department of Physics
University of Alberta          email : jmack@phys.ualberta.ca
Edmonton, Canada T6G 2N5       bitnet: jmack@triumfcl  jsm1@ualtamts