You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by David Crossley <cr...@apache.org> on 2004/09/01 11:25:14 UTC
Re: Jira moved
Would Forrest people please stop using the Jira until
this problem is solved. (See below.)
Nicola Ken, it seems that thosechanges that you made
this evening had no effect, e.g. you changed the
"Fix for version" from 0.6 to 0.7 for FOR-235
yet the Issue tracker still says 0.6 ...
http://issues.cocoondev.org/jira/secure/ViewIssue.jspa?key=FOR-235
(Somehow i dropped the Cc for forrest-dev for the previous
mail below.)
--David
David Crossley wrote:
> Steven Noels wrote:
> > Hi folks,
> >
> > I pulled the DNS switch and issues.cocoondev.org should shortly be
> > resolving to its new home, with a new version of Jira underneath.
> > Content, projects and users have been migrated as well.
> >
> > I've been exploring whether this was a good occasion to finally
> > transition Forrest to the ASF Jira instance, but unfortunately Jira
> > only allows a full system dump and restore currently. Maybe that will
> > change with v3 - dunnow.
> >
> > There might be an issue with forwarding of issues to the mailing lists
> > (as in: I still have to figure out how that should be done).
> >
> > As always: please LMK if you bump into any problems.
>
> I don't see any difference yet - the bottom of the page
> still reports the old Jira version number.
>
> There is something strange happening. We seem to have lost
> some recent Issue Comments. Here are some clues ...
>
> In the past, the notification emails used ...
> ----
> View the issue:
> http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-245
> ----
>
> Recently there are occasional notification emails that use ...
> ----
> View the issue:
> http://issues.cocoondev.org//browse/FOR-245
> ----
> which is a broken URL.
>
> These notifications came to me personally, because i was the
> creator of the issue. However they did not come through to the
> forrest-dev list. Probably Steven's comment above about mail config.
>
> Also that Comment is not listed in the Issue tracker ...
> http://issues.cocoondev.org/jira/secure/ViewIssue.jspa?key=FOR-245
> There should be a recent one from Charles Palmer, before
> my test comment.
>
> Is it possible that some notifications are coming from the
> new Jira instance, while others come from the old Jira?
>
> --David
Re: No mail delivery from issues.cocoondev.org -> apache.org (was:Re:
Jira moved)
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
--On Wednesday, September 1, 2004 1:41 PM +0200 Steven Noels
<st...@outerthought.org> wrote:
> Maybe something happens on the receiving end - we should check with
> infrastructure then. Could be something with these new SPF records (which I
> haven't set up on my site yet).
To be perfectly clear, if we reject your email due to SPF records, you *will*
get a bounce back and a pointer to a URL description where you can find more
information.
So, if you see a '250 queued' or whatnot, then if it isn't being delivered,
ezmlm is the culprit not qmail. As Noel mentioned, ezmlm will often silently
discard messages or hold them for moderation without notification. -- justin
Re: No mail delivery from issues.cocoondev.org -> apache.org (was:Re: Jira moved)
Posted by Steven Noels <st...@outerthought.org>.
On 01 Sep 2004, at 18:06, Noel J. Bergman wrote:
> Steven,
>
> One other possibility. You said that you just upgraded JIRA? There
> is a
> problem with JIRA that Jeff Turner kept having to fix on nagoya
> because they
> hadn't fixed it at Atlassian. They keep sticking a Precedence: Bulk
> header
> in the message. We discard all such messages.
Oh - brilliant. I just checked and of course I don't have that magical
patch installed. :-/
BTW, these mails are passed on fine by Mailman to the lists I host
myself on cocoondev.org - apparently Mailman ignores these headers
happily. Another ezmlm quirk?
Slightly off-topic, I have to recycle Jira 2.6.1 every 8 hours since it
runs out of file handles - even though my box is configured to hand out
plenty of them. We used to have this saying in my previous company:
"looks good, but no function".
:-(
(never mind, and thanks Noel for your tips)
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source Java & XML An Orixo Member
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org
[solved] Re: No mail delivery from issues.cocoondev.org -> apache.org (was:Re: Jira moved)
Posted by Steven Noels <st...@outerthought.org>.
On 01 Sep 2004, at 18:06, Noel J. Bergman wrote:
> Steven,
>
> One other possibility. You said that you just upgraded JIRA? There
> is a
> problem with JIRA that Jeff Turner kept having to fix on nagoya
> because they
> hadn't fixed it at Atlassian. They keep sticking a Precedence: Bulk
> header
> in the message. We discard all such messages.
FYI: I received a patched version of the mail library from Jeff and
installed it on my server, and mails are now delivered correctly to
list recipients. Thanks Noel for your analysis, and thanks Jeff for
providing me with a patch. I'd suggest to drop that header in the
forthcoming 3.0 version. ;-)
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source Java & XML An Orixo Member
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org
Re: No mail delivery from issues.cocoondev.org -> apache.org
(was:Re: Jira moved)
Posted by David Crossley <cr...@apache.org>.
Steven Noels wrote:
> Noel J. Bergman wrote:
> >...They keep sticking a Precedence: Bulk
> > header in the message. We discard all such messages.
>
> ACK - that should be it. Tnx!
Whether it was that or the forrest-dev mailing list config
that Noel mentioned, it is fixed now thanks.
--
David Crossley
RE: No mail delivery from issues.cocoondev.org -> apache.org (was:Re: Jira moved)
Posted by "Noel J. Bergman" <no...@devtech.com>.
Steven,
One other possibility. You said that you just upgraded JIRA? There is a
problem with JIRA that Jeff Turner kept having to fix on nagoya because they
hadn't fixed it at Atlassian. They keep sticking a Precedence: Bulk header
in the message. We discard all such messages.
--- Noel
RE: No mail delivery from issues.cocoondev.org -> apache.org (was:Re: Jira moved)
Posted by "Noel J. Bergman" <no...@devtech.com>.
At a guess, the problem was that dev@forrest.apache.org was that the list
moderators had decided that they didn't want to deal with spam (which is why
we have list moderators in the first place), so they asked for moderation to
be turned off and we (foolishly, in my view) did so. It appears that list
moderation was turned off almost two years ago, but I have fixed the list
configuration.
Try again.
--- Noel
Re: No mail delivery from issues.cocoondev.org -> apache.org (was:Re: Jira moved)
Posted by Steven Noels <st...@outerthought.org>.
On 01 Sep 2004, at 14:28, David Crossley wrote:
> Steven Noels wrote:
>> David Crossley wrote:
>>
>>> But they are not appearing. See
>>> http://marc.theaimsgroup.com/?l=forrest-dev&r=1&b=200409
>>> There are notifications there from me today, but not the
>>> more recent ones from Nicola Ken.
>
> For Infrastructure, some background. The notifications from the
> new Jira at Cocoondev.org are not being received at dev@forrest.a.o
> Those few from me today are because i managed to erroneously
> use the old Jira at cocoondev.org
>
> I just did another test from the new Jira and they are not being
> received at Apache or not leaving cocoondev.org
They *are* leaving the new Jira server, I think they are queued on
hermes, but they aren't delivered to ezmlm apparently.
Sep 1 06:30:07 strider postfix/smtp[29259]: 95BC6160102:
to=<de...@forrest.apache.org>, relay=mail.apache.org[209.237.227.199],
delay=6, status=sent (250 Queued!
<20...@mail.outerthought.net>)
Sep 1 06:36:28 strider postfix/smtp[29474]: 27469160102:
to=<de...@forrest.apache.org>, relay=mail.apache.org[209.237.227.199],
delay=1, status=sent (250 Queued!
<20...@mail.outerthought.net>)
(these are some mails sent from locally on the server - and arrive fine
on the lists)
Sep 1 06:54:25 strider postfix/smtp[29989]: BDDB7160102:
to=<de...@forrest.apache.org>, relay=mail.apache.org[209.237.227.199],
delay=3, status=sent (250 Queued!
<23...@strider.outerthought.net>)
Sep 1 07:21:52 strider postfix/smtp[30829]: CB908160104:
to=<de...@forrest.apache.org>, relay=mail.apache.org[209.237.227.199],
delay=4, status=sent (250 Queued!
<33...@strider.outerthought.net>)
(these are Jira mails - they don't arrive on the list)
Could you please parse mail logs on your side and tell us what's going
wrong?
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source Java & XML An Orixo Member
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org
Re: No mail delivery from issues.cocoondev.org -> apache.org
(was:Re: Jira moved)
Posted by David Crossley <cr...@apache.org>.
Steven Noels wrote:
> David Crossley wrote:
>
> > But they are not appearing. See
> > http://marc.theaimsgroup.com/?l=forrest-dev&r=1&b=200409
> > There are notifications there from me today, but not the
> > more recent ones from Nicola Ken.
For Infrastructure, some background. The notifications from the
new Jira at Cocoondev.org are not being received at dev@forrest.a.o
Those few from me today are because i managed to erroneously
use the old Jira at cocoondev.org
I just did another test from the new Jira and they are not being
received at Apache or not leaving cocoondev.org
--
David Crossley
No mail delivery from issues.cocoondev.org -> apache.org (was:Re: Jira moved)
Posted by Steven Noels <st...@outerthought.org>.
On 01 Sep 2004, at 12:29, David Crossley wrote:
> But they are not appearing. See
> http://marc.theaimsgroup.com/?l=forrest-dev&r=1&b=200409
> There are notifications there from me today, but not the
> more recent ones from Nicola Ken.
strider:~# cat /var/log/mail.info | grep "to=<de...@forrest.apache.org>"
| wc -l
30
issues *are* being sent from the new server IIUC, but maybe they aren't
received on apache.org
HELO cocoondev.org
250 mail.outerthought.net
mail from: issues@cocoondev.org
250 Ok
rcpt to: dev@forrest.apache.org
250 Ok
data
354 End data with <CR><LF>.<CR><LF>
To: dev@forrest.apache.org
From: issues@cocoondev.org
Subject: testing mail delivery from new cd.org to a.org
this is just a quick test to check mail handling from the new server to
apache.org
please disregard and sorry for the noise
.
250 Ok: queued as 45486160101
results in my mail queue as:
Sep 1 06:36:27 strider postfix/qmgr[9834]: 45486160101:
from=<is...@cocoondev.org>, size=536, nrcpt=1 (queue active)
Sep 1 06:36:27 strider postfix/smtpd[29473]: connect from
localhost[127.0.0.1]
Sep 1 06:36:27 strider postfix/smtpd[29473]: 27469160102:
client=localhost[127.0.0.1]
Sep 1 06:36:27 strider postfix/cleanup[29469]: 27469160102:
message-id=<20...@mail.outerthought.net>
Sep 1 06:36:27 strider postfix/smtpd[29473]: disconnect from
localhost[127.0.0.1]
Sep 1 06:36:27 strider amavis[27773]: (27773-02) Passed,
<is...@cocoondev.org> -> <de...@forrest.apache.org>, Message-ID:
<20...@mail.outerthought.net>, Hits: 4.004
Sep 1 06:36:27 strider postfix/qmgr[9834]: 27469160102:
from=<is...@cocoondev.org>, size=1017, nrcpt=1 (queue active)
Sep 1 06:36:27 strider postfix/smtp[29470]: 45486160101:
to=<de...@forrest.apache.org>, relay=127.0.0.1[127.0.0.1], delay=91,
status=sent (250 2.6.0 Ok, id=27773-02, from MTA: 250 Ok: queued as
27469160102)
Sep 1 06:36:27 strider postfix/qmgr[9834]: 45486160101: removed
Sep 1 06:36:28 strider postfix/smtp[29474]: 27469160102:
to=<de...@forrest.apache.org>, relay=mail.apache.org[209.237.227.199],
delay=1, status=sent (250 Queued!
<20...@mail.outerthought.net>)
Sep 1 06:36:28 strider postfix/qmgr[9834]: 27469160102: removed
(the trip through localhost is amavisd for checking spam & viruses)
Maybe something happens on the receiving end - we should check with
infrastructure then. Could be something with these new SPF records
(which I haven't set up on my site yet).
I'm at loss ATM.
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source Java & XML An Orixo Member
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org
Re: Jira moved
Posted by David Crossley <cr...@apache.org>.
Steven Noels wrote:
> David Crossley wrote:
>
> >> I don't see any difference yet - the bottom of the page
> >> still reports the old Jira version number.
>
> Funny. It should read "Professional Edition, Version: 2.6.1-#65".
>
> stevenn [~] $ dig issues.cocoondev.org ANY
>
> ; <<>> DiG 9.2.2 <<>> issues.cocoondev.org ANY
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56471
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;issues.cocoondev.org. IN ANY
>
> ;; ANSWER SECTION:
> issues.cocoondev.org. 1800 IN A 67.19.2.50
>
> I suspect your DNS is stale - are you caching lookups somewhere locally?
I get the same answer from my desktop with 'dig'.
The web browser tells me it is going to issues.cocoondev.org
but when i use 'ngrep' to watch the outgoing network interface
i see it is going to "cocoondev.org=65.77.211.32"!
Switched web browsers and it worked properly!
> >> There is something strange happening. We seem to have lost
> >> some recent Issue Comments. Here are some clues ...
> >>
> >> In the past, the notification emails used ...
> >> ----
> >> View the issue:
> >> http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-245
> >> ----
> >>
> >> Recently there are occasional notification emails that use ...
> >> ----
> >> View the issue:
> >> http://issues.cocoondev.org//browse/FOR-245
> >> ----
> >> which is a broken URL.
>
> Works for me, though.
>
> >> These notifications came to me personally, because i was the
> >> creator of the issue. However they did not come through to the
> >> forrest-dev list. Probably Steven's comment above about mail config.
>
> That should be solved since Monday - notification mails are now being
> sent From: issues@cocoondev.org To: dev@forrest.apache.org
But they are not appearing. See
http://marc.theaimsgroup.com/?l=forrest-dev&r=1&b=200409
There are notifications there from me today, but not the
more recent ones from Nicola Ken.
> >> Also that Comment is not listed in the Issue tracker ...
> >> http://issues.cocoondev.org/jira/secure/ViewIssue.jspa?key=FOR-245
> >> There should be a recent one from Charles Palmer, before
> >> my test comment.
> >>
> >> Is it possible that some notifications are coming from the
> >> new Jira instance, while others come from the old Jira?
>
> I'm thinking DNS caching isn't helping us here. What if I switch off
> the instance on the old server so that we are sure nobody is using that
> one anymore?
I think so. I have already been using it over the last few days.
So i suppose all those changes can be retrieved and manually
re-entered. Can you disable edit rather than switch off?
--
David Crossley
Re: Jira moved
Posted by Antonio Gallardo <ag...@agssa.net>.
Steven Noels dijo:
> On 01 Sep 2004, at 11:25, David Crossley wrote:
>
>>> I don't see any difference yet - the bottom of the page
>>> still reports the old Jira version number.
>
> Funny. It should read "Professional Edition, Version: 2.6.1-#65".
Perhaps a matter of time. I already saw the above label down at:
http://issues.cocoondev.org/secure/Dashboard.jspa
(hope this help).
Best Regards,
Antonio Gallardo
Re: Jira moved
Posted by Steven Noels <st...@outerthought.org>.
On 01 Sep 2004, at 11:25, David Crossley wrote:
>> I don't see any difference yet - the bottom of the page
>> still reports the old Jira version number.
Funny. It should read "Professional Edition, Version: 2.6.1-#65".
stevenn [~] $ dig issues.cocoondev.org ANY
; <<>> DiG 9.2.2 <<>> issues.cocoondev.org ANY
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56471
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0
;; QUESTION SECTION:
;issues.cocoondev.org. IN ANY
;; ANSWER SECTION:
issues.cocoondev.org. 1800 IN A 67.19.2.50
I suspect your DNS is stale - are you caching lookups somewhere locally?
>> There is something strange happening. We seem to have lost
>> some recent Issue Comments. Here are some clues ...
>>
>> In the past, the notification emails used ...
>> ----
>> View the issue:
>> http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-245
>> ----
>>
>> Recently there are occasional notification emails that use ...
>> ----
>> View the issue:
>> http://issues.cocoondev.org//browse/FOR-245
>> ----
>> which is a broken URL.
Works for me, though.
>> These notifications came to me personally, because i was the
>> creator of the issue. However they did not come through to the
>> forrest-dev list. Probably Steven's comment above about mail config.
That should be solved since Monday - notification mails are now being
sent From: issues@cocoondev.org To: dev@forrest.apache.org
>> Also that Comment is not listed in the Issue tracker ...
>> http://issues.cocoondev.org/jira/secure/ViewIssue.jspa?key=FOR-245
>> There should be a recent one from Charles Palmer, before
>> my test comment.
>>
>> Is it possible that some notifications are coming from the
>> new Jira instance, while others come from the old Jira?
I'm thinking DNS caching isn't helping us here. What if I switch off
the instance on the old server so that we are sure nobody is using that
one anymore?
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source Java & XML An Orixo Member
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org