ClusterLabs / ClusterLabs/resource-agents
[FreeBSD] service resource agent not supported
- Dominant language
- Shell
- Stars
- 519
- Forks
- 608
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 7
Description
Configuring a resource, such as "service:hastd" does not work on BSD systems.
Pacemaker expects the RC script to be `/etc/init.d/hastd` instead of `/etc/rc.d/hastd`.
```
Jan 11 15:58:51 bsd1 lrmd[723]: warning: Cannot execute '/etc/init.d/hastd': No such file or directory (2)
Jan 11 15:58:51 bsd1 crmd[726]: error: Unable to retrieve meta-data for (null):heartbeat:hastd
Jan 11 15:58:51 bsd1 crmd[726]: error: No metadata for service::(null):hastd
Jan 11 15:58:51 bsd1 crmd[726]: error: Result of probe operation for hastd on bsd1: Not installed
```
The resource agent should use the `service` command or `/etc/rc.d`.
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the service resource agent and trace how it constructs the init-script path for a resource such as service:hastd. Compare the current `/etc/init.d` lookup with the FreeBSD `service` command and `/etc/rc.d`; done means FreeBSD service resources can be configured and probed without the `/etc/init.d` error shown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100