second week in a row…
and, i think second friday in a row…
i’d guess a friday noon (somewhere) cron is bad little boy.
DenverD wrote:
>
> second week in a row…
> and, i think second friday in a row…
> i’d guess a friday noon (somewhere) cron is bad little boy.
>
>
What’s Up exactly.
Maybe something was down briefly ?
Carl Fletcher wrote:
> What’s Up exactly.
> Maybe something was down briefly ?
the http to nntp to http software failed again this friday…was down
for several hours, again…it is back up now…
–
Enjoy Packman’s benefits? Show your appreciation by donating at
http://se.unixheads.org/?donate
DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]
On Fri, 09 Jul 2010 20:35:02 +0000, DenverD wrote:
> Carl Fletcher wrote:
>
>> What’s Up exactly.
>> Maybe something was down briefly ?
>
> the http to nntp to http software failed again this friday…was down
> for several hours, again…it is back up now…
When you see this happen, a specific message showing the issue would be
useful - that gives us something to look at. 
Jim
–
Jim Henderson
openSUSE Forums Administrator
Just tested…working fine from what I can tell.
–
Kim - 7/9/2010 3:00:15 PM
Jim Henderson wrote:
> When you see this happen, a specific message showing the issue would be
> useful - that gives us something to look at.
please tell me what can be more specific than the nntp<>http mechanism
was not working? like last week:
http://forums.opensuse.org/showthread.php?t=441333
i reported it here and via
http://en.opensuse.org/FAIL#forums.opensuse.org but, couldn’t find
your beeper number…
obviously, someone fixed it…
–
Enjoy Packman’s benefits? Show your appreciation by donating at
http://se.unixheads.org/?donate
DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]
On Fri, 09 Jul 2010 21:14:43 +0000, DenverD wrote:
> Jim Henderson wrote:
>
>> When you see this happen, a specific message showing the issue would be
>> useful - that gives us something to look at.
>
> please tell me what can be more specific than the nntp<>http mechanism
> was not working? like last week:
> http://forums.opensuse.org/showthread.php?t=441333
>
> i reported it here and via
> http://en.opensuse.org/FAIL#forums.opensuse.org but, couldn’t find your
> beeper number…
>
> obviously, someone fixed it…
A specific message at a time when you’re not seeing it go through - from
the NNTP side a message ID header would help, from the web side, a URL to
a thread that hasn’t passed through the gateway.
As Kim indicated, he tested it and it worked fine for him; I saw problems
in my tests a couple hours ago, but then lost my 'net connection (ISP
problems I’ve been fighting for a week), and when I came back it was
working.
So if it was stuck, it kicked loose. Looks like nobody “fixed” it, so
when it happens if we can find out quickly that it’s not working and have
specific messages to look at, that should help us track it down.
Jim
–
Jim Henderson
openSUSE Forums Administrator