Bogdan,

For what it's worth, these changes have not affected my inability to connect
to the siptrace db more often than not.  Still the same error 2003 as
before.


- Jeff



On 4/7/09 11:35 AM, "Bogdan-Andrei Iancu" <bog...@voice-system.ro> wrote:

> Hi Brett,
> 
> more fixes for the DB part were done today (couple of hours ago). Please
> see if those will fix your problem. If not, try to get a backtrace from
> the core files.
> 
> Thanks and regards,
> Bogdan
> 
> Brett Nemeroff wrote:
>> Bogdan,
>> For what it's worth, I've updated to latest 1_5 tonight (about 20
>> minutes ago) and I still am having problems. Full out crashes as well.
>> 
>> I rewrote my queries so I'd have a bunch of little (select * from acc
>> where callid=X) kinds of queries. Of course, there is a lot of DB
>> activity while this happens. Crashes start to happen within seconds of
>> the DB activity ramping up.
>> 
>> For grins, I slowed my queries down to ensure I only did one query per
>> second (in my database, not opensips).. after about 15-20 queries
>> (different each time really) opensips would just crash.
>> 
>> I have acc and sip_trace loaded up, sip_trace isn't active for these
>> calls. Also potentially relevant, my acc table is an InnoDB table.
>> 
>> Now if I slowed my call volume to 1CPS and keep the queries at 1 QPS,
>> it seemed to be happier, but still crashes eventually.
>> 
>> -Brett
>> 
>> 
>> 
>> On Mon, Apr 6, 2009 at 11:27 AM, Bogdan-Andrei Iancu
>> <bog...@voice-system.ro <mailto:bog...@voice-system.ro>> wrote:
>> 
>>     Hi Brett,
>> 
>>     it looks like the DB connections are dropped and reconnect is
>>     taking place (this are the errors about). But to find out the real
>>     cause, I can enable some more logs to spot the reason for
>>     re-connect...
>> 
>>     I will do it later as right now I'm in the middle of some DB
>>     debugging and I'm afraid of mixing different patches and what goes
>>     on SVN :)
>> 
>>     Regards,
>>     Bogdan
>> 
>>     Brett Nemeroff wrote:
>> 
>>         Hi All,
>>         So I'm doing some load testing with sipp on my opensips 1.5
>>         system. I just checked out (like 2 hours ago, the 1.5 branch
>>         from SVN).  Everything works just fine, until I run some
>>         rating scripts on my database (perl scripts accessing the
>>         mysql db directly). While my scripts are running, I see the
>>         UAS in sipp retransmitting the 200 OKs and the following gets
>>         printed to the syslog:
>>         http://www.pastebin.ca/1381169
>> 
>>         As soon as my perl script is done, the 200OKs stop
>>         retransmitting...
>>         My PERL script isn't doing anything terribly unusual, however,
>>         it is performing the queries inside of a transaction,
>>         including a "SELECT/DELETE * FROM acc WHERE " kind of clause.
>> 
>>         Any ideas as to what is causing this? I'm afraid I may be
>>         losing call records..
>> 
>>         -Brett
>> 
>>         
>> ------------------------------------------------------------------------
>> 
>>         _______________________________________________
>>         Users mailing list
>>         Users@lists.opensips.org <mailto:Users@lists.opensips.org>
>>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>          
>> 
>> 
>> 
> 
> 
> _______________________________________________
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to