Chris Wilson <ch...@aptivate.org> wrote: Hi Chris,
> >> Paolo, this looks weird to me. pthread_getspecific() should not crash, > >> that makes me think that the heap has been trashed (stack looks > >> generally OK as the backtrace is OK). Perhaps a Valgrind is in order? > >> Any static or fixed-size buffers in the mysql plugin that might be > >> busted? > > > > No Valgrind instaled. > > You can probably apt-get install valgrind and run pmacctd through it. Well, I'd need some help with them. >> I cleared the database, and observed what happend: >> Apr 13 17:18:19 server1 pmacctd[12394]: INFO ( default/core ): Start logging >> ... >> Apr 13 17:18:19 server1 pmacctd[12394]: OK ( default/core ): link type is: 1 >> Apr 13 17:20:01 server1 pmacctd[12419]: ERROR ( default/mysql ): Duplicate >> entry >> '0-00:1b:8f:61:55:c9-00:1c:c0:ab:8a:48-0-91.22.172.35-84.38.74.24' for key 1 >> Apr 13 17:20:01 server1 kernel: pmacctd[12419]: segfault at 3827208c ip >> 00000000f7c599ca sp 00000000ffde7894 error 4 in >> libpthread-2.3.6.so[f7c51000+e000] > > As this crash is so early, perhaps the thread isn't initialised properly? Well, the first update (into the complet empty table) was successfull, and I think that has used the same kid of thread. Perhaps Paolo has a good Idee where to digg further. regards Johannes _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
