Environment
- App Control Linux Agent (formerly CB Protection): 7.2.4 and higher
- RHEL: All Supported Versions
Symptoms
- Installing the Linux agent, it is succeeds but the agent then subsequently fails to start
- b9daemon fails to start with following errors:
Starting the Bit9 Daemon
Job for b9daemon.service failed because the control process exited with error code. See "systemctl status b9daemon.service" and "journalctl -xe" for details.
Nov 02 14:28:32 Server01 systemd[1]: Starting LSB: Start daemon at boot time...
Nov 02 14:28:33 Server01 b9daemon[4026]: Checking b9k_7241501 Driver
Nov 02 14:28:33 Server01 b9daemon[4026]: Looking if modules file is updated
Nov 02 14:28:33 Server01 b9daemon[4026]: kernel/lib/b9k_7241501.ko: kernel/lib/cbproxy_cbp_724041817.ko
Nov 02 14:28:33 Server01 messages[4058]: b9daemon : Failed to create rc lock file
Nov 02 14:28:33 Server01 b9daemon[4026]: Starting b9daemon: [FAILED]
Nov 02 14:28:33 Server01 systemd[1]: b9daemon.service: control process exited, code=exited status=1
Nov 02 14:28:33 Server01 systemd[1]: Failed to start LSB: Start daemon at boot time.
Nov 02 14:28:33 Server01 systemd[1]: Unit b9daemon.service entered failed state.
Nov 02 14:28:33 Server01 systemd[1]: b9daemon.service failed.
Cause
- Tracing shows issue is caused by failure to write lock file to /var/lock/subsys/ directory on file system because that directory does not exist
- Some AWS template builds of Red Hat have been noted to omit this folder by default
Resolution
- Create the subsys folder with root permissions so the lock file can be created:
As root user
# mkdir /var/lock/subsys
# ls -l /var/lock/
drwxr-xr-x. 2 root root 80 Nov 7 14:34 subsys
- Restart the b9daemon
# systemctl restart b9daemon.service
# systemctl status b9daemon.service
Additional Notes
Issue may also be observed if required permissions are missing from folder
Related Content
