Paolo Lucente <pa...@pmacct.net> wrote: Hi Paolo,
> * The SEGV appears to be in a pthread_getspecific() call while the MySQL > plugin does not do any pthread-related call. Also a simple inet_ntoa() > should not do that. Did you by any chance compile the package with the > --enable-threads option? I don't think so but it's worth asking. Tested once, but used only more CPU-Time, so thrown away ;) Currently runnig: ./configure --enable-mysql --enable-ipv6 --prefix=/usr/ --with-pcap-libs=/usr/local/lib/ --with-pcap-includes=/usr/local/src/libpcap-0.9.8.20081128 --enable-64bit --enable-debug > * Within the debugger i can see the following line: "Core was generated > by `pmacctd: SQL Plugin -- DB Writer (urgent)". An urgent DB Writer can > be triggered for two reasons - both related to the SQL cache: 1) memory > is finished so it tries to purge the content of the cache to the DB in > order to make room to further traffic or 2) the SQL cache size is too > small for the traffic footprint. The value is expressed in cache entries, > defaults to 32771 and can be tuned via the 'sql_cache_entries' config > directive. Can you let me know about this point? It's the default, so increasing sql_cache_entries might help? I'll set it to 262168, should bee enough to prevent it to be the error. > * Falling into an urgent DB writer and having the 'sql_dont_try_update' > directive set to true can generate the duplicate SQL key message. The > strange thing about it is that the key is reported truncated in the > middle of an IP address '[...]-84.38.64.216-79.221.203.'. I actually > can't think at anything which can originate this behaviour. Looks like a fixed legth trukation, while testing I'd thrown out the agent and tos-field, and after that the ip fits completly in the error. > * Few days ago we received on this list a report from another user by > which 'sql_multi_values' was causing a crash. Just to be sure, do you > mind commenting this out and see if it helps? I try everything ;) But that Changes seems to solve the Problem, although without sql_multi_values the db-Server is a more loaded (and the table longer locked). regards Johannes _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
