Re: [MooseFS-Users] HEADS UP! Fallout from change of init script names.

[Aleksander W. <ale...@mo...>]

Hi.
We would like to explain that we unified names of installation packages
and init scripts names from 2.0.60 version.
All information about name changing was mentioned on our website:
https://moosefs.com/download.html
Also our documentation contains information about new sysv and systemd
naming: https://moosefs.com/Content/Downloads/MooseFS-2-0-60-User-Manual.pdf

So during installation or update  to version 2.0.6x and above, system
will not transfer old init script state because for him it's not the
same package.

Best regards
Aleksander Wieliczko
Technical Support Engineer
MooseFS.com <moosefs.com>

On 08.06.2015 08:04, Tom Ivar Helbekkmo wrote:
> We had a bit of a surprise the other day.  We've been running MooseFS
> Pro version 2.0.43 on RHEL 6, and upgraded to 2.0.62.  Everything went
> smoothly, of course -- until there was a restart of one of the servers,
> and the mfs services didn't start at boot.
>
> It turns out that the init scripts have changed names, and the upgrade
> does not duplicate the state of the old ones onto the new.  A manual
> 'chkconfig --add' and 'chkconfig on' is needed for each of them.
>
> -tih