We are running opensaf 4.4.0, on a HP chassis. We are facing a payload blade 
(slot-8) have opensaf startup problem.

Here is the relevant part of the syslog:

Jan  4 12:44:20 BHA-IND-MUM-MALAD-CAE-8 kernel: [660527.561238] tipc: Activated 
(version 2.0.1.2)
Jan  4 12:44:20 BHA-IND-MUM-MALAD-CAE-8 kernel: [660527.561327] NET: Registered 
protocol family 30
Jan  4 12:44:20 BHA-IND-MUM-MALAD-CAE-8 kernel: [660527.561444] tipc: Started 
in single node mode
Jan  4 12:44:20 BHA-IND-MUM-MALAD-CAE-8 kernel: [660527.563034] tipc: Started 
in network mode
Jan  4 12:44:20 BHA-IND-MUM-MALAD-CAE-8 kernel: [660527.563037] tipc: Own node 
address <1.1.129>, network identity 1234
Jan  4 12:44:20 BHA-IND-MUM-MALAD-CAE-8 kernel: [660527.565229] tipc: Enabled 
bearer <eth:bond0>, discovery domain <1.1.0>, priority 10
Jan  4 12:44:20 BHA-IND-MUM-MALAD-CAE-8 osafimmnd[65304]: Started
Jan  4 12:44:20 BHA-IND-MUM-MALAD-CAE-8 kernel: [660528.240310] IPMI Watchdog: 
response: Error d5 on cmd 22

Jan  4 12:52:20 BHA-IND-MUM-MALAD-CAE-8 opensafd[65278]: ER Timed-out for 
response from IMMND
Jan  4 12:52:20 BHA-IND-MUM-MALAD-CAE-8 opensafd[65278]: ER
Jan  4 12:52:20 BHA-IND-MUM-MALAD-CAE-8 opensafd[65278]: ER Going for recovery
Jan  4 12:52:20 BHA-IND-MUM-MALAD-CAE-8 opensafd[65278]: ER Trying To RESPAWN 
/usr/lib/opensaf/clc-cli/osaf-immnd attempt #1
Jan  4 12:52:20 BHA-IND-MUM-MALAD-CAE-8 opensafd[65278]: ER Sending SIGKILL to 
IMMND, pid=65297
Jan  4 12:52:20 BHA-IND-MUM-MALAD-CAE-8 osafimmnd[65304]: exiting for shutdown

Anybody can suggest how to fin dout what the problem is? Other payload blade 
did not have the same problem.

Thanks.

Kang-sen

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-users mailing list
Opensaf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-users

Reply via email to