[tickets] [opensaf:tickets] #638 node cannot join AMF cluster after restart

2017-08-28 Thread A V Mahesh (AVM) via Opensaf-tickets
- **assigned_to**: A V Mahesh (AVM) --> nobody - **Blocker**: --> False - **Milestone**: 5.17.08 --> future --- ** [tickets:#638] node cannot join AMF cluster after restart** **Status:** accepted **Milestone:** future **Created:** Fri Nov 22, 2013 02:54 PM UTC by Hans Feldt **Last

[tickets] [opensaf:tickets] #638 node cannot join AMF cluster after restart

2015-11-02 Thread Anders Widell
- **Milestone**: 4.5.2 --> 4.6.2 --- ** [tickets:#638] node cannot join AMF cluster after restart** **Status:** accepted **Milestone:** 4.6.2 **Created:** Fri Nov 22, 2013 02:54 PM UTC by Hans Feldt **Last Updated:** Wed Jul 15, 2015 01:47 PM UTC **Owner:** A V Mahesh (AVM) OpenSAF 4.2.2

[tickets] [opensaf:tickets] #638 node cannot join AMF cluster after restart

2015-07-15 Thread Anders Bjornerstedt
- **Milestone**: future -- 4.5.2 --- ** [tickets:#638] node cannot join AMF cluster after restart** **Status:** accepted **Milestone:** 4.5.2 **Created:** Fri Nov 22, 2013 02:54 PM UTC by Hans Feldt **Last Updated:** Thu Jan 16, 2014 05:00 AM UTC **Owner:** A V Mahesh (AVM) OpenSAF 4.2.2

Re: [tickets] [opensaf:tickets] #638 node cannot join AMF cluster after restart

2014-01-16 Thread Anders Bjornerstedt
Just one question, ticket #637 is referred to below amfd cannot use imm during... That ticket was fixed and patches pushed at the end of November 2013. I assume then that the changeset 4634 for this fix on 4.2 are not included in the OpenSAFire release used here. /AndersBj A V Mahesh (AVM)

Re: [tickets] [opensaf:tickets] #638 node cannot join AMF cluster after restart

2014-01-16 Thread Anders Bjornerstedt
My mistake, now I see that this is an old ticket. /AndersBj Anders Bjornerstedt wrote: Just one question, ticket #637 is referred to below amfd cannot use imm during... That ticket was fixed and patches pushed at the end of November 2013. I assume then that the changeset 4634 for this fix

[tickets] [opensaf:tickets] #638 node cannot join AMF cluster after restart

2014-01-15 Thread A V Mahesh (AVM)
- **assigned_to**: Hans Feldt -- A V Mahesh (AVM) --- ** [tickets:#638] node cannot join AMF cluster after restart** **Status:** accepted **Created:** Fri Nov 22, 2013 02:54 PM UTC by Hans Feldt **Last Updated:** Tue Jan 14, 2014 08:47 AM UTC **Owner:** A V Mahesh (AVM) OpenSAF 4.2.2

[tickets] [opensaf:tickets] #638 node cannot join AMF cluster after restart

2014-01-15 Thread A V Mahesh (AVM)
--- ** [tickets:#638] node cannot join AMF cluster after restart** **Status:** accepted **Created:** Fri Nov 22, 2013 02:54 PM UTC by Hans Feldt **Last Updated:** Thu Jan 16, 2014 03:14 AM UTC **Owner:** A V Mahesh (AVM) OpenSAF 4.2.2 changeset 3796, 79 extra patches System: RHEL based, 2

[tickets] [opensaf:tickets] #638 node cannot join AMF cluster after restart

2014-01-15 Thread Sirisha Alla
I have seen a similar behavior in #708. The standby controller did not join the AMF cluster saying invalid nodeid --- ** [tickets:#638] node cannot join AMF cluster after restart** **Status:** accepted **Created:** Fri Nov 22, 2013 02:54 PM UTC by Hans Feldt **Last Updated:** Thu Jan 16, 2014

[tickets] [opensaf:tickets] #638 node cannot join AMF cluster after restart

2014-01-14 Thread Hans Feldt
MDS does not setup a maximum socket receive buffer size and thus relies on the system default. On the system where this problem occurred the system default was set to 64KiB. When the rmem_default value was increased to 229376 (as in RHEL 6.4, ubuntu13.10 has 212992) the problem disappeared. So

[tickets] [opensaf:tickets] #638 node cannot join AMF cluster after restart

2013-11-22 Thread Hans Feldt
--- ** [tickets:#638] node cannot join AMF cluster after restart** **Status:** unassigned **Created:** Fri Nov 22, 2013 02:54 PM UTC by Hans Feldt **Last Updated:** Fri Nov 22, 2013 02:54 PM UTC **Owner:** nobody OpenSAF 4.2.2 changeset 3796, 79 extra patches System: RHEL based, 2 node

[tickets] [opensaf:tickets] #638 node cannot join AMF cluster after restart

2013-11-22 Thread Hans Feldt
some traces: Nov 21 18:13:20.869969 osafamfd [6712:avd_ndfsm.c:0059] TR invalid node ID (2020f) Nov 21 18:13:40.891557 osafamfd [6712:avd_ndfsm.c:0059] TR invalid node ID (2020f) Nov 21 18:14:00.905991 osafamfd [6712:avd_ndfsm.c:0059] TR invalid node ID (2020f) Nov 21 18:14:20.920477 osafamfd