Still weird that this starts happening now, when this issue is supposed to be remedied, and not earlier, when it wasn't. We really need that "permit overlapping publications" solution I have been preaching about.
Br ///jon > -----Original Message----- > From: Rune Torgersen [mailto:ru...@innovsys.com] > Sent: Friday, 18 March, 2016 10:25 > To: 'Erik Hugne' > Cc: tipc-discussion@lists.sourceforge.net > Subject: Re: [tipc-discussion] tipc nametable update problem > > Yes I have. > There are quite a few at the same time like this: > > Mar 17 20:08:58 restarttv kernel: Dropping name table update (0) of > {1853110816, > 1952998688, 1801810542} from <1.1.1> key=1633905523 > Mar 17 20:08:58 restarttv kernel: Dropping name table update (0) of > {542000723, > 544613732, 544437616} from <1.1.1> key=167800175 > Mar 17 20:08:58 restarttv kernel: Dropping name table update (0) of > {544239474, > 1953325424, 543582572} from <1.1.1> key=1930035237 > Mar 17 20:08:58 restarttv kernel: Dropping name table update (0) of > {1933189232, > 1869771885, 1634738291} from <1.1.1> key=1768843040 > Mar 17 20:08:58 restarttv kernel: Dropping name table update (0) of > {1717660012, > 1701054976, 628308512} from <1.1.1> key=1869881446 > Mar 17 20:08:58 restarttv kernel: Dropping name table update (0) of {16397, > 1073741824, 16397} from <1.1.1> key=29285 > Mar 17 20:08:58 restarttv kernel: Dropping name table update (0) of > {1633943667, > 1752134260, 544367969} from <1.1.1> key=1679834144 > Mar 17 20:08:58 restarttv kernel: Dropping name table update (0) of > {1869771808, > 2003986804, 1698300018} from <1.1.1> key=4294915584 > Mar 17 20:08:58 restarttv kernel: Dropping name table update (0) of > {1073741824, > 65279, 4294902016} from <1.1.1> key=1073741824 > Mar 17 20:08:58 restarttv kernel: Dropping name table update (0) of {65279, > 4294901760, 59154} from <1.1.1> key=65023 > > > From: Erik Hugne [mailto:erik.hu...@gmail.com] > Sent: Friday, March 18, 2016 1:48 AM > To: Rune Torgersen > Cc: tipc-discussion@lists.sourceforge.net > Subject: Re: [tipc-discussion] tipc nametable update problem > > > Hi Rune. > When the problem occurs, have you seen any traces like "tipc: Dropping name > table update...." ? > > //E > On Mar 18, 2016 02:11, "Rune Torgersen" > <ru...@innovsys.com<mailto:ru...@innovsys.com>> wrote: > More info. > The failing ports are all opened as TIPC_ZONE_SCOPE. > Addresses of the two computers are 1.1.1 and 1.1.2. > > If I change the open param to TIPC_CLUSTER_SCOPE, the nametable seems to > update correctly. > > > -----Original Message----- > From: Rune Torgersen > [mailto:ru...@innovsys.com<mailto:ru...@innovsys.com>] > Sent: Thursday, March 17, 2016 7:06 PM > To: 'tipc-discussion@lists.sourceforge.net<mailto:tipc- > discuss...@lists.sourceforge.net>' > Subject: [tipc-discussion] tipc nametable update problem > > Hi. > > The product I work on uses TIPC for communication between different > computers on a network. We've actually been using older version (1.7.7 and > older > ) for nearly 10 years. > > On a new product, we're using the latest Ubuntu server (16.04, still in beta) > using > kernel 4.4.0. > > On several occasions now, after boot, programs that open TIPC sockets during > the boot process, have ports that does not show in the nametable on the other > computer. This of course causes the programs to not being able to talk. > If we restart the program, reopening the TIPC port, then it shows up on both > sides. > > > I know this is somewhat sparse info, but I am not sure where to start to look > at > this. > > One piece of info that might be useful, is that we kind of require the old > interface > naming on our interfaces, so we have turned off systemd's ethernet naming > scheme, and use udev to name the devices. > > This should be done well before we initializer the tipc driver module and > give it a > netid and address and enable the bearer links. > > ------------------------------------------------------------------------------ > Transform Data into Opportunity. > Accelerate data analysis in your applications with > Intel Data Analytics Acceleration Library. > Click to learn more. > http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 > _______________________________________________ > tipc-discussion mailing list > tipc-discussion@lists.sourceforge.net<mailto:tipc- > discuss...@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/tipc-discussion > > ------------------------------------------------------------------------------ > Transform Data into Opportunity. > Accelerate data analysis in your applications with > Intel Data Analytics Acceleration Library. > Click to learn more. > http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 > _______________________________________________ > tipc-discussion mailing list > tipc-discussion@lists.sourceforge.net<mailto:tipc- > discuss...@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/tipc-discussion > ------------------------------------------------------------------------------ > Transform Data into Opportunity. > Accelerate data analysis in your applications with > Intel Data Analytics Acceleration Library. > Click to learn more. > http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 > _______________________________________________ > tipc-discussion mailing list > tipc-discussion@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tipc-discussion ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 _______________________________________________ tipc-discussion mailing list tipc-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tipc-discussion
