Using Cherokee webserver as a service was working well for me until a few days ago when OpenRC got updated to v0.11.5
There's a script running every 2 minutes (using cron) to check server sanity and restart it when needed - /etc/init.d/cherokee - with commands stop/restart/start and so on. Since this openRC update, I can run it manually (as root) BUT the script fails and adds this message:
* You are attempting to run an openrc service on a
* system which openrc did not boot.
* You may be inside a chroot or you may have used
* another initialization system to boot this system.
* In this situation, you will get unpredictable results!
* If you really want to do this, issue the following command:
* touch /lib64/rc/init.d/softlevel
* ERROR: cherokee failed to stop
* WARNING: cherokee has already been started
So should I do this touch or will it mess my system up even more as the version got upgraded?
Mind I didn't reboot the machine since then and am reluctant to do it as it's a production server and if openRC fails to load net.eth0 I'll be in big trouble
When I upgraded the package (using emerge), the only message I got was the one below but I don't know if that means the cherokee script is faulty:
* Messages for package sys-apps/openrc-0.11.5:
* Auto-adding 'swapfiles' service to your boot runlevel
* Auto-adding 'sysfs' service to your sysinit runlevel
* Auto-adding 'udev-mount' service to your sysinit runlevel
* Auto-adding 'tmpfiles.setup' service to your boot runlevel
* In this version of OpenRC, the loopback interface no longer
* satisfies the net virtual.
* If you have services now which do not start because of this,
* They can be fixed by adding rc_need="!net"
* to the /etc/conf.d/<servicename> file.
* You should also file a bug against the service asking that
* need net be dropped from the dependencies.
* The bug you file should block the following tracker:
* This version of OpenRC doesn't enable nfs mounts automatically any
* longer. In order to mount nfs file systems, you must use the
* nfsmount service from the nfs-utils package.
* See bug https://bugs.gentoo.org/show_bug.cgi?id=427996 for
* more information on this.
* You should now update all files in /etc, using etc-update
* or equivalent before restarting any services or this host.
* Please read the migration guide available at:
Please let me know how to resolve this issue. Thanks.
Please mind that after launching
things seem to work well but I need to know if things won't crash on a reboot and if launching it might have had another negative effect.
I needd to see your build log. This might be a dupe of #443996, but I
can't be sure based on what I see in this report.
Don't think I have any build log left as all got completed. Let me know if you want me to try any command to re-create a log.
1353657522: >>> emerge (2 of 4) sys-apps/openrc-0.11.5 to /
1353657522: === (2 of 4) Cleaning (sys-apps/openrc-0.11.5::/usr/portage/sys-apps/openrc/openrc-0.11.5.ebuild)
1353657522: === (2 of 4) Compiling/Merging (sys-apps/openrc-0.11.5::/usr/portage/sys-apps/openrc/openrc-0.11.5.ebuild)
1353657536: === (2 of 4) Merging (sys-apps/openrc-0.11.5::/usr/portage/sys-apps/openrc/openrc-0.11.5.ebuild)
1353657537: >>> AUTOCLEAN: sys-apps/openrc:0
1353657537: === Unmerging... (sys-apps/openrc-0.9.8.4)
1353657539: >>> unmerge success: sys-apps/openrc-0.9.8.4
1353657542: === (2 of 4) Post-Build Cleaning (sys-apps/openrc-0.11.5::/usr/portage/sys-apps/openrc/openrc-0.11.5.ebuild)
1353657542: ::: completed emerge (2 of 4) sys-apps/openrc-0.11.5 to /
OpenRC 0.11.6 was just put in the tree. Please upgrade to that and let
me know if you still have issues.
Please read my report here from 2012-11-25 07:49:55 UTC
I upgraded and will report if further issues arise.
(In reply to comment #3)
> Don't think I have any build log left as all got completed. Let me know if
> you want me to try any command to re-create a log.
What I want to find out is why $RC_SVCDIR is pointing to /lib64/rc/init.d instead of /run/openrc. This is where it should be pointing on Linux systems.
This is a Linux server correct?
Can you please post the output from:
emerge -pv openrc
In particular, I need to know whether pam is or is not in your use flags.
# emerge -pv openrc
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] sys-apps/openrc-0.11.8 USE="ncurses pam unicode -debug -newnet (-prefix) (-selinux) -static-libs" 0 kB
Total: 1 package (1 reinstall), Size of downloads: 0 kB