I don't have a parser for the logs but looking through the raw data I do
see the 500 results going out to the Second Life requests. I don't know
why my external tester is not getting them but it is obviously an
indication of where to start looking.
My knowledge of the MYSQL internal operations is minimal.
Could randomly occurring, rapid (simultaneous) requests be causing file
locking or is there only one thread at a time using the data access?
If there is file locking, would this cause 500 error responses to
blocked requests or do they just wait?
Would duplicate data files and splitting requests between them help?
(Most of the data is static).
On 10/6/2011 3:05 AM, Edmund Edgar wrote:
> On 6 October 2011 15:26, AnnM...@SLFBI.com<AnnM...@slfbi.com> wrote:
>> **HOWEVER** tonight I wrote a test program running outside SL accessing the
>> same database once every 10 seconds and it is not getting any errors after
>> running a couple of hours.
>> Previously I've assumed the error 500 "internal server error" was
>> originating from my data base but with tonight's test I'm wondering if the
>> Second Life http handlers could be introducing the problem.
> Have you checked your server logs to see if your server is sending
> HTTP 500 responses?
>
_______________________________________________
Click here to unsubscribe or manage your list subscription:
https://lists.secondlife.com/cgi-bin/mailman/listinfo/secondlifescripters
Presumably you connect to a scripting language (like PHP) to access the
MySQL db. Check its error logs to find more specific errors, like db
connection timeouts, that might be behind the 500 status code.
> On 10/6/2011 3:05 AM, Edmund Edgar wrote:
> > On 6 October 2011 15:26, AnnM...@SLFBI.com<AnnM...@slfbi.com> wrote:
> >> **HOWEVER** tonight I wrote a test program running outside SL accessing the
> >> same database once every 10 seconds and it is not getting any errors after
> >> running a couple of hours.
> >> Previously I've assumed the error 500 "internal server error" was
> >> originating from my data base but with tonight's test I'm wondering if the
> >> Second Life http handlers could be introducing the problem.
> > Have you checked your server logs to see if your server is sending
> > HTTP 500 responses?
> >
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> https://lists.secondlife.com/cgi-bin/mailman/listinfo/secondlifescripters
Ima Mechanique
Check List
1) Check the documentation.
2) Drink coffee.
3) Check the documentation again, to see what I missed first time.
4) If I still can't solve it, ask if anyone else has the answer.
ima.mechanique(at)blueyonder.co.uk
I suspected it might be due to file locking when incoming queries
synchronized randomly and suddenly bombarded the data base with 100
queries in less than a second. It doesn't explain why that should occur
more from 6PM to Midnight unless the MYSQL engine is just running slower
under peak hour load.
95% of the queries access one data file that is "Read Frequently, write
rarely". The file is about 750K and about 2,000 records.
So I made two mirrors of the file which are accessed at random and kept
the original as a master copy. This reduced file locking time 50%.
Write functions are just applied to the master and periodically, or on
demand, the master is copied to the mirrors.
A simple solution that took 5 minutes to set up and so far it has been
running without a single http failure. It would be very easy to expand
to more mirrors later if needed but so far 2 data sources seems to be
working.
Ann-Marie Otoole.
Can't you move away from HDD and onto memory?
Read up on the MySQL 'MEMORY' engine for a temporary table that holds things more frequently accessed.Then copy to HDD infrequently.
- Nexii Malthus