Archive for October, 2010

OpenSAF 4.0 Troubleshooting

October 28, 2010

Here is list of problems and solutions when bringing up OpenSAF 4.0

DISCARDING IMPLEMENTER

Upon startup do you get the following errors in /var/log/messages and then OpenSAF quits?

Oct 28 18:35:19 my-laptop osafimmnd[32053]: Create implementer:
Oct 28 18:35:19 my-laptop osafimmnd[32053]: Implementer 3 disconnected. Marking it as doomed
Oct 28 18:35:19 my-laptop osafimmnd[32053]: DISCARDING IMPLEMENTER 3 (safPlmService)
Oct 28 18:35:34 my-laptop opensafd[31997]: Starting the PLMD service
Oct 28 18:35:34 my-laptop osafimmnd[32053]: Create implementer:
Oct 28 18:35:34 my-laptop osafimmnd[32053]: Implementer 4 disconnected. Marking it as doomed
Oct 28 18:35:34 my-laptop osafimmnd[32053]: DISCARDING IMPLEMENTER 4 (safPlmService)
Oct 28 18:35:49 my-laptop opensafd[31997]: Starting the PLMD service
Oct 28 18:35:49 my-laptop osafimmnd[32053]: Create implementer:
Oct 28 18:35:49 my-laptop osafimmnd[32053]: Implementer 5 disconnected. Marking it as doomed
Oct 28 18:35:49 my-laptop osafimmnd[32053]: DISCARDING IMPLEMENTER 5 (safPlmService)
Oct 28 18:35:49 my-laptop osafimmnd[32053]: Implementer 1 disconnected. Marking it as doomed
Oct 28 18:35:49 my-laptop osafimmnd[32053]: DISCARDING IMPLEMENTER 1 (OpenSAFDtsvService)
Oct 28 18:35:49 my-laptop osafimmnd[32053]: Director Service in NOACTIVE state
Oct 28 18:35:49 my-laptop osafrded[32018]: Connection closed by client (orderly shutdown)
Oct 28 18:35:49 my-laptop osafimmnd[32053]: Director Service is down
Oct 28 18:35:49 my-laptop osafrded[32018]: Connection closed by client (orderly shutdown)
Oct 28 18:35:49 my-laptop osafrded[32018]: Connection closed by client (orderly shutdown)
Oct 28 18:35:49 my-laptop kernel: [14221.183751] TIPC: Disabling bearer
Oct 28 18:35:49 my-laptop kernel: [14221.183762] TIPC: Left network mode
Oct 28 18:35:49 my-laptop kernel: [14221.199712] NET: Unregistered protocol family 30
Oct 28 18:35:49 my-laptop kernel: [14221.199718] TIPC: Deactivated

Answer

You do not have a machine that has “platform management” or you do not have openhpi correctly installed. Platform management is the ability for the system to detect hardware issues like temperature alarms or component failures. It is optional. Reconfigure, rebuild, and reinstall OpenSAF, but disable plm in the configure step as follows:

./configure –disable-ais-plm

Startup seems to work without error and then quits

Answer 1

Make sure that the node name as defined in /etc/opensaf/node_name is one of the nodes defined in your imm.xml file. By default it fills this file with the linux nodename during installation.

Answer 2

Make sure that your node name (/etc/opensaf/node_name) and slot number (/etc/opensaf/slot_id) is unique in the cluster.