Bug#586419: tokyotyrant: daemon dies after receiving SIGABRT after random time of operating

2010-08-10 Thread bugreporter
On Wed, 23 Jun 2010 16:32:24 +0200, Örjan Persson ora...@fobie.net wrote: severity 586419 important thanks sorry for very long delay on our side - we could not deal with investigation of this problem we've not upgraded any important part of system running this service yet

Bug#586419: tokyotyrant: daemon dies after receiving SIGABRT after random time of operating

2010-08-10 Thread bugreporter
On Wed, 23 Jun 2010 16:32:24 +0200, Örjan Persson ora...@fobie.net wrote: severity 586419 important thanks u - possibly we have found the source of this problem as mentioned before, we use PHP API for Tyrant: http://mamasam.indefero.net/p/tyrant/ Inside this API there is method in

Bug#586419: tokyotyrant: daemon dies after receiving SIGABRT after random time of operating

2010-08-10 Thread bugreporter
OK - on very low level of communication. Here is example PHP script using API mentioned above: ?php ini_set('display_errors',1); error_reporting(E_ALL); include('./Tyrant.php'); $session=Tyrant::connect('10.0.4.13', '1999'); $data1=array( 'somedata', 'otherstuff',

Bug#586419: tokyotyrant: daemon dies after receiving SIGABRT after random time of operating

2010-06-23 Thread bugreporter
On Tue, 22 Jun 2010 21:39:33 +0200, Örjan Persson ora...@fobie.net wrote: o2o bug reporter (bugrepor...@one-2-one.pl) wrote: The problem is that after quite random time of operation (at least 30 minutes, usually few hours)- while daemon is not under heavy load (I would even say while it is

Bug#586419: tokyotyrant: daemon dies after receiving SIGABRT after random time of operating

2010-06-23 Thread Örjan Persson
severity 586419 important thanks bugrepor...@one-2-one.pl (bugrepor...@one-2-one.pl) wrote: Currently I also started session as you described and it is working fine for about 5 minutes now. It would be very helpful if you're able to tell exactly what's triggering this behaviour. :) Than

Bug#586419: tokyotyrant: daemon dies after receiving SIGABRT after random time of operating

2010-06-22 Thread Örjan Persson
o2o bug reporter (bugrepor...@one-2-one.pl) wrote: The problem is that after quite random time of operation (at least 30 minutes, usually few hours)- while daemon is not under heavy load (I would even say while it is almost not used) - it crashes, leaving it's PID file. Without using

Bug#586419: tokyotyrant: daemon dies after receiving SIGABRT after random time of operating

2010-06-19 Thread o2o bug reporter
Package: tokyotyrant Version: 1.1.40-4 Severity: grave Justification: renders package unusable There is tokyotyrant properly installed (using package system) taken from 'testing' branch while most of installed packages on host are 'stable'. $ cat /etc/default/tokyotyrant | egrep -v (^$|^#)