how to get issue tracker access?

Robert A Basch rbasch at MIT.EDU
Tue Aug 7 20:00:05 EDT 2012

I just checked a test SP here that is auto-updating, and found that shibd was
not running, and the symlinks in /etc/rc?.d/ were gone.  The /etc/init.d/shibd
script itself was properly updated.

I haven't investigated further, so this is just a guess, but I noticed that the
package name changed, to shibboleth-sp -- maybe the uninstall scriptlet from
the old package was invoked and removed the service?


On Aug 7, 2012, at 7:40 PM, Cantor, Scott wrote:

> On 8/7/12 7:15 PM, "Cantor, Scott" <cantor.2 at> wrote:
>> On 8/7/12 6:49 PM, "Jeff Long" <long at> wrote:
>>> Thanks for the answer, but that's too much (local) bureaucracy to get
>>> through. Before I read through all of the ProtectNetwork ToS does
>>> anyone care to comment on whether or not the automatic yum update of
>>> shibboleth-2.4.3 to shibboleth-2.5.0 on RHEL systems worked correctly?
>> It has in my testing.
> Just updated the SP. The init script was fine (it's dated
> now, which it should be). What broke, and I half expected it to, is that
> it can't always get the process restarted. It works at times, but not
> others, mainly I think when it's a complex configuration that takes time
> to shut down or start up. It starts fine afterwards, so possibly inserting
> a delay might work, I'll have to look at it as part of some other cleanup.
> The rest of the glitches were some problems with dependency rules I'm
> planning to fix, but they don't break anything and they don't apply if a
> full yum update is done.
> But fair warning I suppose is that I'm probably going to regenerate them
> again to fix those dependency glitches, so if you're having an issue, best
> we find out what it is, or I'd suggest blocking the repo for automatic
> updating.
> -- Scott
> --
> To unsubscribe from this list send an email to users-unsubscribe at

More information about the users mailing list