On Mon, Feb 15, 2010 at 1:12 PM, Adrian Chapela <[email protected]> wrote: > Hello, > > I have the same issue than Michael, but only on one machine...
Random thought, at what point during startup does corosync get started? Do the problems persist when you start corosync manually after boot? > > I have corosync 1.2, Pacemaker 1.0.7 and Debian 5.0. One of my two node > cluster machine can't start sometimes. The log: > > Feb 15 13:00:31 correo2 crmd: [2214]: info: init_ais_connection: > Creating connection to our AIS plugin > Feb 15 13:00:31 correo2 crmd: [2214]: info: init_ais_connection: > Connection to our AIS plugin (9) failed: Try again (6) > Feb 15 13:00:32 correo2 crmd: [2214]: info: init_ais_connection: > Creating connection to our AIS plugin > Feb 15 13:00:32 correo2 crmd: [2214]: info: init_ais_connection: > Connection to our AIS plugin (9) failed: Try again (6) > Feb 15 13:00:33 correo2 crmd: [2214]: info: init_ais_connection: > Creating connection to our AIS plugin > Feb 15 13:00:33 correo2 crmd: [2214]: info: init_ais_connection: > Connection to our AIS plugin (9) failed: Try again (6) > Feb 15 13:00:34 correo2 crmd: [2214]: info: init_ais_connection: > Creating connection to our AIS plugin > Feb 15 13:00:34 correo2 crmd: [2214]: info: init_ais_connection: > Connection to our AIS plugin (9) failed: Try again (6) > Feb 15 13:00:35 correo2 crmd: [2214]: info: init_ais_connection: > Creating connection to our AIS plugin > Feb 15 13:00:35 correo2 crmd: [2214]: info: init_ais_connection: > Connection to our AIS plugin (9) failed: Try again (6) > Feb 15 13:00:36 correo2 crmd: [2214]: info: init_ais_connection: > Creating connection to our AIS plugin > Feb 15 13:00:36 correo2 crmd: [2214]: info: init_ais_connection: > Connection to our AIS plugin (9) failed: Try again (6) > Feb 15 13:00:37 correo2 crmd: [2214]: info: init_ais_connection: > Creating connection to our AIS plugin > Feb 15 13:00:37 correo2 crmd: [2214]: info: init_ais_connection: > Connection to our AIS plugin (9) failed: Try again (6) > Feb 15 13:00:38 correo2 crmd: [2214]: info: init_ais_connection: > Creating connection to our AIS plugin > Feb 15 13:00:38 correo2 crmd: [2214]: info: init_ais_connection: > Connection to our AIS plugin (9) failed: Try again (6) > Feb 15 13:00:39 correo2 crmd: [2214]: info: init_ais_connection: > Creating connection to our AIS plugin > Feb 15 13:00:39 correo2 crmd: [2214]: info: init_ais_connection: > Connection to our AIS plugin (9) failed: Try again (6) > Feb 15 13:00:40 correo2 crmd: [2214]: info: init_ais_connection: > Creating connection to our AIS plugin > Feb 15 13:00:40 correo2 crmd: [2214]: info: init_ais_connection: > Connection to our AIS plugin (9) failed: Try again (6) > Feb 15 13:00:41 correo2 crmd: [2214]: info: init_ais_connection: > Creating connection to our AIS plugin > Feb 15 13:00:41 correo2 crmd: [2214]: info: init_ais_connection: > Connection to our AIS plugin (9) failed: Try again (6) > Feb 15 13:00:41 correo2 crmd: [2214]: ERROR: init_ais_connection: Retry > count exceeded > Feb 15 13:00:41 correo2 crmd: [2214]: ERROR: do_log: FSA: Input I_ERROR > from do_ha_control() received in state S_RECOVERY > Feb 15 13:00:41 correo2 crmd: [2214]: info: do_dc_release: DC role released > Feb 15 13:00:41 correo2 crmd: [2214]: info: do_te_control: Transitioner > is now inactive > Feb 15 13:00:41 correo2 crmd: [2214]: ERROR: do_started: Start > cancelled... S_RECOVERY > Feb 15 13:00:41 correo2 crmd: [2214]: ERROR: do_log: FSA: Input > I_TERMINATE from do_recover() received in state S_RECOVERY > Feb 15 13:00:41 correo2 crmd: [2214]: info: do_state_transition: State > transition S_RECOVERY -> S_TERMINATE [ input=I_TERMINATE > cause=C_FSA_INTERNAL origin=do_recover ] > Feb 15 13:00:41 correo2 crmd: [2214]: info: do_lrm_control: Disconnected > from the LRM > Feb 15 13:00:41 correo2 crmd: [2214]: info: do_ha_control: Disconnected > from OpenAIS > Feb 15 13:00:41 correo2 crmd: [2214]: info: do_cib_control: > Disconnecting CIB > Feb 15 13:00:41 correo2 crmd: [2214]: info: do_exit: Performing A_EXIT_0 > - gracefully exiting the CRMd > Feb 15 13:00:41 correo2 crmd: [2214]: ERROR: do_exit: Could not recover > from internal error > Feb 15 13:00:41 correo2 crmd: [2214]: info: free_mem: Dropping > I_RELEASE_SUCCESS: [ state=S_TERMINATE cause=C_FSA_INTERNAL > origin=do_dc_release ] > Feb 15 13:00:41 correo2 crmd: [2214]: info: free_mem: Dropping > I_TERMINATE: [ state=S_TERMINATE cause=C_FSA_INTERNAL origin=do_stop ] > Feb 15 13:00:41 correo2 crmd: [2214]: info: do_exit: [crmd] stopped (2) > > For me is strange because sometimes it is running OK. > > Regards... > > El 03/02/10 14:07, Michael Schwartzkopff escribió: >> Am Mittwoch, 27. Januar 2010 07:32:56 schrieb Steven Dake: >> >>> try that with corosync-cfgtool -s >>> >>> I had a look at confdb and it doesn't tell me what I need to know. >>> >>> Regards >>> -steve >>> >> (...) >> >> >>> 1) stating corosync with pacemaker configured: >>> # corosync-cfgtool -s >>> Printing ring status. >>> Local node ID 36773292 >>> RING ID 0 >>> id = 172.29.49.2 >>> status = ring 0 active with no faults >>> >>> 2) unload pacemaker >>> # corosync-cfgtool -u pacemaker >>> Unloading service 'pacemaker' version '0' >>> linux-h3m0:~ # corosync-cfgtool -s >>> Printing ring status. >>> Could not initialize corosync configuration API error 6 >>> linux-h3m0:~ # >>> >>> 3) Load pacemaker doesn't work: >>> # corosync-cfgtool -l pacemaker >>> Loading service 'pacemaker' version '0' >>> Could not initialize corosync configuration API error 6 >>> >> >> > > _______________________________________________ > Openais mailing list > [email protected] > https://lists.linux-foundation.org/mailman/listinfo/openais > _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
