rc script not executed on system boot

Hi,

I have a problem that one of my rc scripts which I have enabled in rc.conf is not executed on system boot.

It's about the rc script mfsmaster which is part of the MooseFS cluster file system.

I have in my rc.conf file:

Code:
mfsmaster_enable="YES"
mfsmetalogger_enable="YES"
mfschunkserver_enable="YES"

but mfsmaster is not started on system boot.

I can manually start /usr/local/etc/rc.d/mfsmaster though.

Any ideas what could be the reason, why it's not started on system boot?

Best regards,
rforberger
 
Look in /var/log/messages for clues why it failed to start during boot.
 
SirDice
Thanks for your reply.
When looking in /var/log/messages I see nothing from mfsmaster being started. The rc script just seems not executed on system boot.
 
Does it show up in rcorder /etc/rc.d/* /usr/local/etc/rc.d/*?

Yes, as per:

Code:
$ rcorder /etc/rc.d/* /usr/local/etc/rc.d/* | grep mfs
/usr/local/etc/rc.d/mfsmaster
/usr/local/etc/rc.d/mfsmetalogger
/usr/local/etc/rc.d/mfschunkserver

but it's not started on system boot.
 
I can manually start /usr/local/etc/rc.d/mfsmaster though.
You mean call it as root, thus it has the executable flag set? What does service mfsmaster start tell you? service -e|grep mfs
 
All the service(8) command does is start the appropriate /usr/local/etc/rc.d/ script. There is no difference between starting a service like this: server something start or /usr/local/etc/rc.d/something start. They both do the exact same thing.
 
Hi mjollnir ,
Yes, the executable flag is set on the rc script.
Code:
# ls -lah /usr/local/etc/rc.d/mfsmaster
-rwxr-xr-x  1 root  wheel   603B  6 Juli 13:04 /usr/local/etc/rc.d/mfsmaster

service mfmaster start will start the mfsmaster daemon as expected.

service -e | grep mfs only lists the mfschunkserver and mfsmetalogger though.

Code:
# service -e | grep mfs
/usr/local/etc/rc.d/mfsmetalogger
/usr/local/etc/rc.d/mfschunkserver
 
Then it's a typo. S/th like mfs_master_enable vs. mfsmaster_enable or mfsmaster_enabled with a superfluous "d".
 
Then it's a typo. S/th like mfs_master_enable vs. mfsmaster_enable or mfsmaster_enabled with a superfluous "d".

Well, my rc.conf seems correct:

Code:
# cat /etc/rc.conf | grep mfs
mfsmaster_enable="YES"
mfsmetalogger_enable="YES"
mfschunkserver_enable="YES"

Maybe any special character in rc.conf could cause the problem?
 
I removed the KEYWORD nostart from the script /usr/local/etc/rc.d/mfsmaster.

.... # KEYWORD: nostart shutdown ....

No idea, why this keyword is specified there.

Now the mfsmaster service will start on system boot.

Thanks for your help.
 
Looks like that port is maintained by the Moosefs upstream:

Earliest checkin I can find with the nostart keyword is this:

It's still there in Moosefs 3:

I'd file a bug on their Github project.
 
Back
Top