Stephan, I've installed NetBSD 6.0 + corosync from git + libqb from git (master). And yes, you are right. Corosync doesn't work. What is interesting, it doesn't work ONLY when in daemon mode. If you will run corosync -f (so no daemonize), it will work perfectly. Regards, Honza Stephan napsal(a): > Ok, I will sync the current git sources and build them later :) > > 2012/12/11 Angus Salkeld <asalkeld@xxxxxxxxxx>: >> On 11/12/12 12:26 +0100, Fabio M. Di Nitto wrote: >>> >>> On 12/11/2012 12:14 PM, Stephan wrote: >>>> >>>> Would you please tell me which version of libqb i should pick? >>> >>> >>> I used git master at the time. I don´t recall exactly to which release >>> it maps. >> >> >> Latest release is v0.14.3, but I'll release soon as there are a bunch >> of bugs that have been fixed. >> >> If you can test on master that would be great as I'll know that NetBSD >> works before releasing v0.14.4 (or we can fix before releasing). >> >> -Angus >> >> >>> >>> Fabio >>> >>>> >>>> Regards, >>>> >>>> Stephan >>>> >>>> 2012/12/10 Stephan <stephanwib@xxxxxxxxxxxxxx>: >>>>> >>>>> I just grabbed libqb 0.14.3, recompiled and reinstalled everything. >>>>> Unfortunately, these messages appear again. >>>>> >>>>> 2012/12/10 Fabio M. Di Nitto <fdinitto@xxxxxxxxxx>: >>>>>> >>>>>> On 12/10/2012 12:31 PM, Stephan wrote: >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> it might be a NetBSD related bug or something is interfering with its >>>>>>> pthread implementation. I found a 2.x release not compiling on NetBSD >>>>>>> some time ago, but you are right - the 2.1.0 release can be >>>>>>> successfully build. >>>>>>> >>>>>>> There is another issue - this happens when I start it: >>>>>>> >>>>>>> Dec 10 11:21:16 [21835] ctx4980gate2 corosync notice [TOTEM ] >>>>>>> Initializing transport (UDP/IP Multicast). >>>>>>> Dec 10 11:21:16 [21835] ctx4980gate2 corosync notice [TOTEM ] >>>>>>> Initializing transmit/receive security (NSS) crypto: none hash: none >>>>>>> Dec 10 11:21:16 [21835] ctx4980gate2 corosync error [QB ] >>>>>>> kevent(poll): Bad file descriptor (9) >>>>>>> Dec 10 11:21:16 [21835] ctx4980gate2 corosync warning [QB ] >>>>>>> fd->poll: Bad file descriptor (9) >>>>>>> Dec 10 11:21:16 [21835] ctx4980gate2 corosync error [QB ] >>>>>>> kevent(poll): Bad file descriptor (9) >>>>>>> Dec 10 11:21:16 [21835] ctx4980gate2 corosync warning [QB ] >>>>>>> fd->poll: Bad file descriptor (9) >>>>>>> Dec 10 11:21:16 [21835] ctx4980gate2 corosync error [QB ] >>>>>>> kevent(poll): Bad file descriptor (9) >>>>>>> Dec 10 11:21:16 [21835] ctx4980gate2 corosync warning [QB ] >>>>>>> fd->poll: Bad file descriptor (9) >>>>>>> Dec 10 11:21:16 [21835] ctx4980gate2 corosync error [QB ] >>>>>>> kevent(poll): Bad file descriptor (9) >>>>>>> Dec 10 11:21:16 [21835] ctx4980gate2 corosync warning [QB ] >>>>>>> fd->poll: Bad file descriptor (9) >>>>>>> Dec 10 11:21:16 [21835] ctx4980gate2 corosync error [QB ] >>>>>>> kevent(poll): Bad file descriptor (9) >>>>>>> Dec 10 11:21:16 [21835] ctx4980gate2 corosync warning [QB ] >>>>>>> fd->poll: Bad file descriptor (9) >>>>>>> Dec 10 11:21:16 [21835] ctx4980gate2 corosync error [QB ] >>>>>>> kevent(poll): Bad file descriptor (9) >>>>>>> Dec 10 11:21:16 [21835] ctx4980gate2 corosync warning [QB ] >>>>>>> fd->poll: Bad file descriptor (9) >>>>>>> Dec 10 11:21:16 [21835] ctx4980gate2 corosync error [QB ] >>>>>>> kevent(poll): Bad file descriptor (9) >>>>>>> >>>>>>> Ideas? >>>>>> >>>>>> >>>>>> grab the latest version of libqb. >>>>>> >>>>>> I recall we fixed this issue and libqb testsuite completes without >>>>>> problems. I was also able to run a NetBSD corosync cluster at the end >>>>>> of >>>>>> the day. >>>>>> >>>>>> Fabio >>>>>> >>>>>> _______________________________________________ >>>>>> discuss mailing list >>>>>> discuss@xxxxxxxxxxxx >>>>>> http://lists.corosync.org/mailman/listinfo/discuss >>>> >>>> _______________________________________________ >>>> discuss mailing list >>>> discuss@xxxxxxxxxxxx >>>> http://lists.corosync.org/mailman/listinfo/discuss >>>> >>> >>> _______________________________________________ >>> discuss mailing list >>> discuss@xxxxxxxxxxxx >>> http://lists.corosync.org/mailman/listinfo/discuss >> >> _______________________________________________ >> discuss mailing list >> discuss@xxxxxxxxxxxx >> http://lists.corosync.org/mailman/listinfo/discuss > > _______________________________________________ > discuss mailing list > discuss@xxxxxxxxxxxx > http://lists.corosync.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
