Linux Counter

[Alex Potter]

I've been getting these:

Final-Recipient: rfc822; machine-***@gimel.counter.li.org
Original-Recipient: rfc822;machine-***@counter.li.org
Action: delayed
Status: 4.3.0
Diagnostic-Code: x-unix; temporary failure
Will-Retry-Until: Thu, 17 Mar 2011 01:53:04 +0100 (CET)

Which, ultimately, end in failure, for a couple of months. Does anyone
know whether they have stopped accepting updates?

[Kevin Safford]

On Mon, 14 Mar 2011 13:16:35 +0000, Alex Potter wrote:

I just tried adding an email address, and got a 'this page is trying to
redirect in a way that will never complete' message. I allowed cookies,
so they might well be having problems.

[Alex Potter]

Post by Kevin Safford
I just tried adding an email address, and got a 'this page is trying to
redirect in a way that will never complete' message. I allowed cookies,
so they might well be having problems.

Thanks. Not just me, then.

[Kevin Safford]

Post by Alex Potter
Thanks. Not just me, then.

No, I think it must be something more general. Their home page
(http://counter.li.org/) has this message on it:

"The Linux Users Groups WorldWide site is down due to machine failure"

[Alex Potter]

Post by Kevin Safford
"The Linux Users Groups WorldWide site is down due to machine failure"

I saw that, and thought that it probably didn't apply to the counter, as
everything else works for me on the counter site - I just get "temporary
failure" DSNs when machine-update runs.

[Kevin Safford]

Post by Alex Potter

Post by Kevin Safford
"The Linux Users Groups WorldWide site is down due to machine failure"

I saw that, and thought that it probably didn't apply to the counter, as
everything else works for me on the counter site - I just get "temporary
failure" DSNs when machine-update runs.

Ah, I understand now; apologies.

I registered as a Linux user ages ago, but didn't register my machines.
I've just registered one. The initial 'machine-update -m' command worked
OK (well, no errors, anyway). Manually running the cron job also gave no
errors.

(Updates to my email address had also got through, despite the redirect
problems.)