Does anybody know what is up with openFATE?

Siminin · July 5, 2010, 8:17am

It hasn’t been working for a few days now. Yesterday there was a message that there is a problem with it and today i tried to access openFATE and it says “Service unavailable”. Does anyone know the reason:question:

caf4926 · July 5, 2010, 8:24am

No idea
You could email webmaster

featureadmin@suse.de

ab · July 5, 2010, 8:47am

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

Reported internally. Thanks for bringing it up. Feel free to do so the
first time you see this in the future.

Good luck.

On 07/05/2010 12:36 AM, Siminin wrote:
>
> It hasn’t been working for a few days now. Yesterday there was a message
> that there is a problem with it and today i tried to access openFATE and
> it says “Service unavailable”. Does anyone know the reason:question:
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJMMX+GAAoJEF+XTK08PnB5kywQAJ4vTRbzPUy2Hj34ICkXx/QH
qFIovEb4KVfjpC07kop3PKjvNEunpMSdT0TyFEnP972FS6UprPa5V8ufH6Ocxb7N
mKN3og9SAB4kk6k5eIl77FWVq+VuRY0DYun5AoKLs+qFW4WhsALOjUtDsqS0rH2P
w5Z2qWz/exPuugj2K11FY+g2VhgyJ5HfEP1oZr5Cp3WzcsZS5B4+lIJZM9gpHVY3
3ME9GChybpqM+c8bL4uFX580ruFsMtXkLjiYXtLnWXuJ7W4DHhJwC6Gtzvdhj/ek
BameHFwr6QYXeYl5fyPG34OuDmog3P8raFoWsl7K/ewW1Q4qrkhZdoglZQPPONCD
dgJUEuoHnXzzPL0hxwS0ZqsQFie1pNOcmYjtnL7c3bGF2X2PXd6SK+qDH0uGTSVx
cLyL4C6wjSPFLUEDSiG05d+0ugfP8PZmsHkNsAo4ZVrTtiR1AZcUSnlyDJK8icAq
T+kiLuWassRREIsQtFDTMDDxlxoMnVJg4wqj3yiOrfvCZF6CUZ9Orn5CqbOWWxRu
Ls6wHTynhXDD5DFriYDarcFX5UuzhoO/Y7a6W/YyWYh651eVhuWrjc6qd+5UgDAh
pDhlFzfF7LjEBBtqryJtM1jcL7KeyeouaQFqUE6/VwUur9goFmKiGn15mIhCM8bv
2GKHHOkhQ0n9Igq97jAa
=PLkG
-----END PGP SIGNATURE-----

user · July 5, 2010, 10:19am

And you are wrong … Internal (ACS) IS&T ist not responsible for any OpenSUSE system! You need to contact
webmaster@opensuse.org
admin@opensuse.org

caf4926 · July 5, 2010, 11:35am

I did this already

DenverD · July 5, 2010, 11:52am

mhoppe1 wrote:
> And you are wrong … Internal (ACS) IS&T ist not responsible for any
> OpenSUSE system!

ok, i bite: who/where is “Internal (ACS) IS&T” ?

DenverD · July 5, 2010, 12:40pm

Siminin wrote:
> It hasn’t been working for a few days now.

https://features.opensuse.org/ seems to be working now

hendersj · July 8, 2010, 12:40am

On Mon, 05 Jul 2010 09:52:48 +0000, DenverD wrote:

> mhoppe1 wrote:
>> And you are wrong … Internal (ACS) IS&T ist not responsible for any
>> OpenSUSE system!
>
> ok, i bite: who/where is “Internal (ACS) IS&T” ?

It’s Novell’s IS&T department.

Jim

–
Jim Henderson
openSUSE Forums Administrator

DenverD · July 8, 2010, 8:58am

Jim Henderson wrote:
>> ok, i bite: who/where is “Internal (ACS) IS&T” ?
>
> It’s Novell’s IS&T department.

ahhh…so now i think i understand a little more clearly…if i put
together what you explain above, along with what mhoppe1 said
(“Internal (ACS) IS&T ist not responsible for any OpenSUSE system!”) i
can read between those lines that (as i suspected) we have no 24x7x365
sysAdmin on the hook to cover problems which pop up during “off
hours”, “weekends” or “holidays”…

a ‘fact’ i thought i had detected over a year ago when we were off the
air for long periods several instances until it became “office hours”
somewhere…

and, when i complained about the lack of (Novell) admin support i
was told we (openSUSE) do have around the clock coverage…and we
weren’t just waiting for an office-hours-worker to show up on Monday
morning (which seemed to happen several times)

so, i now assume the full coverage is not provided by Novell’s already
on duty IT after all, but by ???

[please don’t press me to cite that, but it is somewhere in
forum.support.information or forum.comments- from last year]

hendersj · July 8, 2010, 7:25pm

On Thu, 08 Jul 2010 06:58:53 +0000, DenverD wrote:

> Jim Henderson wrote:
>>> ok, i bite: who/where is “Internal (ACS) IS&T” ?
>>
>> It’s Novell’s IS&T department.
>
> ahhh…so now i think i understand a little more clearly…if i put
> together what you explain above, along with what mhoppe1 said (“Internal
> (ACS) IS&T ist not responsible for any OpenSUSE system!”) i can read
> between those lines that (as i suspected) we have no 24x7x365 sysAdmin
> on the hook to cover problems which pop up during “off hours”,
> “weekends” or “holidays”…
>
> a ‘fact’ i thought i had detected over a year ago when we were off the
> air for long periods several instances until it became “office hours”
> somewhere…
>
> and, when i complained about the lack of (Novell) admin support i was
> told we (openSUSE) do have around the clock coverage…and we weren’t
> just waiting for an office-hours-worker to show up on Monday morning
> (which seemed to happen several times)
>
> so, i now assume the full coverage is not provided by Novell’s already
> on duty IT after all, but by ???

Put simply, it’s much more complex than any here could imagine.
Seriously, I’ve tried explaining things that on the outside look like
they should be simple to people in the past, and ultimately, there’s no
easy way to explain it unless you know ALL of the internal details of how
the company operates. Yes, it should be simple. No, it isn’t. No, I
can’t adequately explain why it isn’t unless we get into a deep
discussion of how the company operates - and that’s not something I even
can do (since internal operations are - by their nature - company
confidential).

So don’t worry about it - let us worry about it.

Jim

Jim Henderson
openSUSE Forums Administrator

DenverD · July 8, 2010, 7:59pm

Jim Henderson wrote:
> So don’t worry about it - let us worry about it.

You have the conn!

(but, do the mods have a beeper number they can call to get the world
wide working again?)

–
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]

hendersj · July 8, 2010, 8:26pm

On Thu, 08 Jul 2010 17:59:53 +0000, DenverD wrote:

> Jim Henderson wrote:
>> So don’t worry about it - let us worry about it.
>
> You have the conn!
>
> (but, do the mods have a beeper number they can call to get the world
> wide working again?)

No, but if the forums go down, we generally do get it noticed relatively
quickly. Like I said, it’s much more complex than just having a beeper
number, there’s a whole ITIL-based reporting system we have to use
internally, unfortunately it sometimes takes a fair bit of time to find
the right person. We can’t just go to the person who has responsibility
to fix the system and ask them to fix it - we’re forced to follow very
specific procedures.

IMHO, there’s far too much red tape, but I don’t get to make the call, I
just have to use the system I’m handed (and work around it when I can -
and sometimes I can).

Jim

–
Jim Henderson
openSUSE Forums Administrator

DenverD · July 9, 2010, 9:21am

Jim Henderson wrote:
> unfortunately it sometimes takes a fair bit of time to find
> the right person. We can’t just go to the person who has responsibility
> to fix the system and ask them to fix it - we’re forced to follow very
> specific procedures.

it was not my thought that the world widely distributed forum
moderators (who one might expect to be the first able to note the
problem and report it) would not have to “find the right person” (in
Utah/Germany/wherever) to fix the problem, instead just ring
(text/SMS/email) the right phone (blackberry, HTC, palmtop, whatever)
to get the process started…

that 24x7x365 answered device (blackberry/etc) might be anywhere on
earth that is constantly attended abd only must relay a message to
you/Ken or whoever IS the point inside the company/community who is
both qualified and responsible to walk the complicated corporation
fence lines to support this Community (before Monday morning rolls
around in Utah/wherever)…

that inside the company/community fence walker would not have to
always be the same individual, as long as whoever has the conn at any
given time has the ability to find and roust “the right person”…

pretty simple command/control/communications planning and world wide
community support commitment. (a dead giveaway of lack of same is
consistently fixing friday night cron problems mid-day on utah-monday.)

–
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]

hendersj · July 10, 2010, 7:12am

On Fri, 09 Jul 2010 07:21:00 +0000, DenverD wrote:

> pretty simple command/control/communications planning and world wide
> community support commitment. (a dead giveaway of lack of same is
> consistently fixing friday night cron problems mid-day on utah-monday.)

Like I said, it looks like it should be simpler than it is. It
probably could be simpler than it is. It isn’t simpler than it is, so
we deal with it the best way we can.

I know exactly how you feel, because I felt the same way 8 years ago
before I joined Novell. I looked (for example) at stupid bugs in NetWare
where it would report negative disk space free, and would think “that’s
an easy fix - change from using signed ints/longs to unsigned ints/longs,
problem solved”. It’s not that simple, and I learned that very quickly.
And then I tried to explain it to people who aren’t internal - and they
reacted exactly the same way you are. I learned it’s futile to try to
explain why things are the way they are, because until you’re on the
inside, nothing makes any sense. Even on the inside, some things don’t
make a lot of sense, to be honest.

The same goes for the infrastructure maintenance. Whatever you think the
infrastructure maintenance team looks like or what their procedures
should be, I can guarantee you that they’re not. So just keep
reporting outages to us and we’ll do what we can to get them taken care
of - and instead of speculating on what you seem to think is a personal
vendetta that Novell’s IS&T department has against you, let’s just stick
to the facts, OK?

Jim

Jim Henderson
openSUSE Forums Administrator

DenverD · July 10, 2010, 7:52am

Jim Henderson wrote:
> So just keep reporting outages to us

yes, reporting to “us” is all that is required…

the problem i’m trying to get across is that that “us” has a monday to
friday day job in utah, and may or may not learn of a friday night
problem until they read the message on monday…

if there is a message waiting to be read…because trying to pass
that failure message via nntp or http is problematic if either/neither
system is passing messages…

its like: i can’t email you (or ‘us’) to let you know that your filter
is bouncing my emails…

–
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]

hendersj · July 10, 2010, 6:26pm

On Sat, 10 Jul 2010 05:52:29 +0000, DenverD wrote:

> Jim Henderson wrote:
>> So just keep reporting outages to us
>
> yes, reporting to “us” is all that is required…
>
> the problem i’m trying to get across is that that “us” has a monday to
> friday day job in utah, and may or may not learn of a friday night
> problem until they read the message on monday…
>
> if there is a message waiting to be read…because trying to pass that
> failure message via nntp or http is problematic if either/neither system
> is passing messages…
>
> its like: i can’t email you (or ‘us’) to let you know that your filter
> is bouncing my emails…

Now I know you have my personal e-mail address, and when I say “us”, I
mean “the forum staff”. When the NNTP gateway is down, PM still works on
the web interface as well.

As you can see, I’m here today; unless I’m personally out of range of any
sort of connectivity, I check my e-mail several times a day. I think
you’ll find that most of the staff is here.

Jim

–
Jim Henderson
openSUSE Forums Administrator