Re: Usenet Gateway down.... for two weeks

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

AndrewSN is reporting no -hackers messages to usenet since 02/04. I
have confirmed with Google groups:

http://groups.google.com/group/pgsql.hackers/topics?lnk=srg

Although Google groups is receiving messages for -general.

Joshua D. Drake

- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHu2lkATb/zqfZUUQRAjRpAJ9B9OEraV/Fqo1+isTF8vF+ZAtIlgCeNoEM
gE6sRuTCEW+sC21Mrfwun/8=
=NUmX
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Looking into it ... odd thing is we used to have a mirror news gateway out of
France, which should have gave us the redundancy that even if the primary were
having gateway issues, the secondary would have still been feeding articles ...
will look into both sides ...

- --On Tuesday, February 19, 2008 15:42:28 -0800 "Joshua D. Drake"
<jd(at)commandprompt(dot)com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> AndrewSN is reporting no -hackers messages to usenet since 02/04. I
> have confirmed with Google groups:
>
> http://groups.google.com/group/pgsql.hackers/topics?lnk=srg
>
> Although Google groups is receiving messages for -general.
>
> Joshua D. Drake
>
> - --
> The PostgreSQL Company since 1997: http://www.commandprompt.com/
> PostgreSQL Community Conference: http://www.postgresqlconference.org/
> Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
> PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFHu2lkATb/zqfZUUQRAjRpAJ9B9OEraV/Fqo1+isTF8vF+ZAtIlgCeNoEM
> gE6sRuTCEW+sC21Mrfwun/8=
> =NUmX
> -----END PGP SIGNATURE-----
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster

- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy(at)hub(dot)org MSN . scrappy(at)hub(dot)org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFHu4Tb4QvfyHIvDvMRArGPAJsHq9gtc1gEpmZnmDv2cvXAPHGzKwCgpLmT
SBjbUZgq0L9t7AUZOeSJUPg=
=p1ZF
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 19 Feb 2008 21:39:39 -0400
"Marc G. Fournier" <scrappy(at)hub(dot)org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Looking into it ... odd thing is we used to have a mirror news
> gateway out of France, which should have gave us the redundancy that
> even if the primary were having gateway issues, the secondary would
> have still been feeding articles ... will look into both sides ...

Is there any kind of test we could put in place to make sure this
doesn't happen again? I mean I can't remember a single day in the last
5 years that hackers didn't get at least one message.

Joshua D. Drake

- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHu4fkATb/zqfZUUQRAhv4AJ0c+4hgSGsxgtuwdVhB9Sqr8DijUQCfcexE
FQlQ6Tbc4LFMoiRT8Qz0jJY=
=OhTi
-----END PGP SIGNATURE-----

Joshua D. Drake wrote:
> On Tue, 19 Feb 2008 21:39:39 -0400 "Marc G. Fournier"
> <scrappy(at)hub(dot)org> wrote:
>
> > Looking into it ... odd thing is we used to have a mirror news
> > gateway out of France, which should have gave us the redundancy that
> > even if the primary were having gateway issues, the secondary would
> > have still been feeding articles ... will look into both sides ...
>
> Is there any kind of test we could put in place to make sure this
> doesn't happen again?

Agreed. Expecting to know about breakage just because someone complains
is no way to run a service.

> I mean I can't remember a single day in the last
> 5 years that hackers didn't get at least one message.

Well, in all likelyhood that would be a pretty unremarkable day, so if
it existed it wouldn't be a surprise that you wouldn't remember it.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Is there any kind of test we could put in place to make sure this
> doesn't happen again? I mean I can't remember a single day in the last
> 5 years that hackers didn't get at least one message.

The only thing think of is to do something like:

# telnet localhost nntp
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
200 news.hub.org InterNetNews NNRP server INN 2.4.3 ready (posting ok).
GROUP pgsql.hackers
211 48254 37 48358 pgsql.hackers

Now, that said, not sure what the numbers mean ... 48358 is the latest, and 37
is the oldest article number based on the active file ... not sure what the
211/48254 are though ...

The problem is that 38358 will increment if a posting comes in from the
Internet itself, so you can't just check for that to increase, you'd have to
take a look at the Path in the header of the article itself, and look for:

Path: news.hub.org!postgresql.org!pgsql-hackers-owner+m114209

which translates as news.hub.org received from postgresql.org ...

- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy(at)hub(dot)org MSN . scrappy(at)hub(dot)org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFHu4ty4QvfyHIvDvMRAh/OAJ42XW8a+Cy3U2IDzs/Q/K1gklyqigCgznuQ
0i/BDIf9NlBH4hIfvJ0sFz0=
=n9N7
-----END PGP SIGNATURE-----

On Tue, Feb 19, 2008 at 10:07:46PM -0400, Marc G. Fournier wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> > Is there any kind of test we could put in place to make sure this
> > doesn't happen again? I mean I can't remember a single day in the last
> > 5 years that hackers didn't get at least one message.
>
> The only thing think of is to do something like:
>
> # telnet localhost nntp
> Trying ::1...
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> 200 news.hub.org InterNetNews NNRP server INN 2.4.3 ready (posting ok).
> GROUP pgsql.hackers
> 211 48254 37 48358 pgsql.hackers
>
> Now, that said, not sure what the numbers mean ... 48358 is the latest, and 37
> is the oldest article number based on the active file ... not sure what the
> 211/48254 are though ...

211 = response code
48254 = *estimated* number of articles in group
37 = low watermark (first article)
48358 = high watermark (last article)

//Magnus