R3.2 setup_all of centos74 cluster failed unable to start supervisor-database
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.2 |
New
|
High
|
Unassigned | |||
Trunk |
New
|
High
|
Unassigned |
Bug Description
For R3.2 of centos74 cluster, setup_all fails unable to start supervisor-
[root@server3 utils]# service supervisor-database status
● supervisor-
Loaded: loaded (/etc/rc.
Active: active (exited) since Thu 2018-05-17 20:09:20 UTC; 1h 30min ago
Docs: man:systemd-
Process: 12135 ExecStart=
May 17 20:08:59 server3 systemd[1]: Starting SYSV: Supervisord instance for Contrail Database Package...
May 17 20:08:59 server3 supervisor-
May 17 20:08:59 server3 supervisor-
May 17 20:08:59 server3 supervisor-
May 17 20:09:20 server3 systemd[1]: Started SYSV: Supervisord instance for Contrail Database Package.
Hint: Some lines were ellipsized, use -l to show in full.
[root@server3 utils]# echo $?
3
[root@server3 utils]#
Arvind V. debugged the issue and found in 3.2, database packages for rpm don’t create user kafka as part of the post install.
For recovery, we can issue the following:
1) “adduser kafka”
2) chown -R kafka /tmp/kafka-logs
3) chown -R kafka /var/log/kafka
4) restart supervisor