Programs from 'nut' package are configured and compiled to use 'nogroup' group id. There is no such group and 'service nut start' fails due to this. Michal michal
It's compiled with --with-uid=`id -u nobody` --with-gid=`id -g nobody` i think, you have wrong id for nobody.
# rpm -qf /usr/bin/bestups nut-0.44.1-5 # strings /usr/bin/bestups | grep nog nogroup and a daemon complaints on a startup about missing 'nogroup' gid. It is quite possible that a configuration and/or compilation of the whole thing is buggy but this what this report was about.
it's fixed in nut-0.44.3-1.