Re: [MRBS-general] Duplicate and conflicting entries

[Edward S. <lbs...@us...>]

Still working on it.  my colleagues found the problem recurred, so the 
ownership/permissions was not the problem after all. :)
He is now operating well over my knowledge level of database detail - 
saying he found a number of deadlocks on the INNODB log, such as

    /MySQL thread id 829, query id 299852 localhost root//
    //Trx read view will not see trx with id >= 0 6922831, sees < 0
    6824953//
    //---TRANSACTION 0 6922560, ACTIVE 922 sec, process no 12779, OS
    thread id 139823936894720//
    //1 lock struct(s), heap size 368, 0 row lock(s), undo log entries 1//
    ////
    //MySQL thread id 843, query id 299828 localhost root//
    //Trx read view will not see trx with id >= 0 6922561, sees < 0
    6824953//
    //---TRANSACTION 0 6825030, ACTIVE 65456 sec, process no 12779, OS
    thread id 139824074053376//
    //1 lock struct(s), heap size 368, 0 row lock(s), undo log entries 6/

Cache flushing and buffering settings are now being tweaked :(

-Ed

p.s. Campbell, just FYI in case you are wondering why you do not see 
these messages in your ma...@ca... account, they are 
being bounced back to me with a spam warning :

<<< 550-ATLAS(2503): 143.89.13.11 is blacklisted and not authenticated. Please
<<< 550-request delisting via the following link:
<<< 550 Blacklisted by Webfusion for high spam volumes.
554 5.0.0 Service unavailable



On 26/09/2012 4:46 PM, Campbell Morrison wrote:
> OK thanks, that sounds promising.   However I would expect that if your MySQL user didn't have sufficient permissions MRBS should fail with some kind of message in the error log.   Look forward to hearing the results.
>
> Campbell
>
>
>
>
>
> From: Edward Spodick [mailto:lbs...@us...]
> Sent: 26 September 2012 08:04
> To: ma...@ca...; General purpose list (support/developers/users)
> Cc: Campbell Morrison; Edward Spodick
> Subject: Re: [MRBS-general] Duplicate and conflicting entries
>
> The problem only appears with bookings made after the upgrade.  All testing with Vanilla and non-vanilla showed no problem, but the volume of testing is far less than the actual booking volume in production.
>
> However - my colleague thinks he has identified the issue, and we are now rolling out a fix to see if the problem stops.
>
> The good news is that if he is correct, then the problem may have nothing directly to do with the MRBS codebase.  He believes the problem is in the MySQL server itself, and the fix being tried out both reduces/eliminates caching on the database (potential ouch) and switching to root for the MySQL login from MRBS with some adjusted permissions (we were using a less powerful user previously).
>
> I will let you know the results...
>
> -Edward
>
>
> On 25/09/2012 2:48 PM, Campbell Morrison wrote:
> Did you change the resolution and/or the day start at the same time as upgrading to 1.4.8?    If so, that could explain some, though not all, of the apparently conflicting entries.   For example, if you previously had a resolution of 15 mins and a start on the hour and then changed the resolution to 30 mins, two bookings, one ending at quarter past and one starting at quarter past would show up in the same slot.
>
> Does the problem only show up with bookings made before the upgrade, or do you get the problem with bookings made since the upgrade?
>
> Have you tried testing with a vanilla 1.4.8 to see if it's the modifications that are causing the problem?
>
>
> Campbell
>
>
>
> From: Edward Spodick [mailto:lbs...@us...]
> Sent: 25 September 2012 04:14
> To: mrb...@li...
> Cc: Edward Spodick
> Subject: [MRBS-general] Duplicate and conflicting entries
>
> We're using version 1.4.8 with a few modifications.  We just rolled it out to replace our much older version, and it is getting very heavy use - hundreds of bookings being made per day.
>
> Unfortunately, we are getting reports of duplicate bookings, and conflicting bookings being made, and I am seeing them in the interface - with the plus sign i a booking slot with 2 competing entries.  In most cases both entries are by the same person.  In some cases, one of the entries has an invalid id when clicked upon.  And in some cases, the time periods are by 2 different users, overlapping (e.g. one from 6-9pm, another from 7-9pm for the same room on the same date).  And in a few cases 3 different users have booked the same time slots.  None of this happened in testing, of course. :)
>
> We have disabled MySQL caching in the hope that would help, but so far the problem continues.  I have not yet discovered a pattern and am really puzzled how the system could permit this.  We do not have tentative bookings enabled, and the default setting is confirmed.  We do not require bookings to be approved.  We do not use private bookings.
>
> Does anyone have any suggestions?  Thanks.
>
> -Edward Spodick, HKUST Library, Hong Kong
>    lbs...@us...
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> mrbs-general mailing list
> mrb...@li...
> https://lists.sourceforge.net/lists/listinfo/mrbs-general
> Want to unsubscribe: mailto:mrb...@li...?subject=unsubscribe