[MDEV-20241] CONNECT engine JDBC error HY000 Got error 122 'Out of range valblock index value' from CONNECT Created: 2019-08-02  Updated: 2019-09-17

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - Connect
Affects Version/s: 10.3.16
Fix Version/s: 10.3

Type: Bug Priority: Major
Reporter: Robert Dyas Assignee: Olivier Bertrand
Resolution: Unresolved Votes: 0
Labels: None
Environment:

centos7


Attachments: Text File rc_neg3.log     Text File valblock-error-aug-22.log    

 Description   

We frequently get this error from connect, but not 100% of the time. Sometimes it will run fine 9 out of 10 times, then fail with this message.

HY000 Got error 122 'Out of range valblock index value' from CONNECT

I've included the output of the log file in case this helps (there are two valblock errors below with 100 lines before and after each for context... please let me know if you need more or less to help diagnose):

Jul 30 06:00:00 di-mariadb-test1 mysqld: cdp(29).Name=Tags cp=(nil)
Jul 30 06:00:00 di-mariadb-test1 mysqld: New BLOCK: size=144 g=0x7f640c5ca6b0 p=(nil)
Jul 30 06:00:00 di-mariadb-test1 mysqld: SubAlloc in 0x7f63fffff010 size=144 used=19296 free=67089568
Jul 30 06:00:00 di-mariadb-test1 mysqld: Done memp=0x7f6400003b70 used=19440 free=67089424
Jul 30 06:00:00 di-mariadb-test1 mysqld: making new JDBCCOL C29 Tags at 0x7f6400003b70
Jul 30 06:00:00 di-mariadb-test1 mysqld: colp=0x7f6400003b70
Jul 30 06:00:00 di-mariadb-test1 mysqld: ColDB: am=102 colname=FulfillmentStatus tabname=Orders num=0
Jul 30 06:00:00 di-mariadb-test1 mysqld: cdp(30).Name=FulfillmentStatus cp=(nil)
Jul 30 06:00:00 di-mariadb-test1 mysqld: New BLOCK: size=144 g=0x7f640c5ca6b0 p=(nil)
Jul 30 06:00:00 di-mariadb-test1 mysqld: SubAlloc in 0x7f63fffff010 size=144 used=19440 free=67089424
Jul 30 06:00:00 di-mariadb-test1 mysqld: Done memp=0x7f6400003c00 used=19584 free=67089280
Jul 30 06:00:00 di-mariadb-test1 mysqld: making new JDBCCOL C30 FulfillmentStatus at 0x7f6400003c00
Jul 30 06:00:00 di-mariadb-test1 mysqld: colp=0x7f6400003c00
Jul 30 06:00:00 di-mariadb-test1 mysqld: ColDB: am=102 colname=FinancialStatus tabname=Orders num=0
Jul 30 06:00:00 di-mariadb-test1 mysqld: cdp(31).Name=FinancialStatus cp=(nil)
Jul 30 06:00:00 di-mariadb-test1 mysqld: New BLOCK: size=144 g=0x7f640c5ca6b0 p=(nil)
Jul 30 06:00:00 di-mariadb-test1 mysqld: SubAlloc in 0x7f63fffff010 size=144 used=19584 free=67089280
Jul 30 06:00:00 di-mariadb-test1 mysqld: Done memp=0x7f6400003c90 used=19728 free=67089136
Jul 30 06:00:00 di-mariadb-test1 mysqld: making new JDBCCOL C31 FinancialStatus at 0x7f6400003c90
Jul 30 06:00:00 di-mariadb-test1 mysqld: colp=0x7f6400003c90
Jul 30 06:00:00 di-mariadb-test1 mysqld: ColDB: am=102 colname=DiscountCodes tabname=Orders num=0
Jul 30 06:00:00 di-mariadb-test1 mysqld: cdp(32).Name=DiscountCodes cp=(nil)
Jul 30 06:00:00 di-mariadb-test1 mysqld: New BLOCK: size=144 g=0x7f640c5ca6b0 p=(nil)
Jul 30 06:00:00 di-mariadb-test1 mysqld: SubAlloc in 0x7f63fffff010 size=144 used=19728 free=67089136
Jul 30 06:00:00 di-mariadb-test1 mysqld: Done memp=0x7f6400003d20 used=19872 free=67088992
Jul 30 06:00:00 di-mariadb-test1 mysqld: making new JDBCCOL C32 DiscountCodes at 0x7f6400003d20
Jul 30 06:00:00 di-mariadb-test1 mysqld: colp=0x7f6400003d20
Jul 30 06:00:00 di-mariadb-test1 mysqld: ColDB: am=102 colname=ShippingAddressFirstName tabname=Orders num=0
Jul 30 06:00:00 di-mariadb-test1 mysqld: cdp(56).Name=ShippingAddressFirstName cp=(nil)
Jul 30 06:00:00 di-mariadb-test1 mysqld: New BLOCK: size=144 g=0x7f640c5ca6b0 p=(nil)
Jul 30 06:00:00 di-mariadb-test1 mysqld: SubAlloc in 0x7f63fffff010 size=144 used=19872 free=67088992
Jul 30 06:00:00 di-mariadb-test1 mysqld: Done memp=0x7f6400003db0 used=20016 free=67088848
Jul 30 06:00:00 di-mariadb-test1 mysqld: making new JDBCCOL C56 ShippingAddressFirstName at 0x7f6400003db0
Jul 30 06:00:00 di-mariadb-test1 mysqld: colp=0x7f6400003db0
Jul 30 06:00:00 di-mariadb-test1 mysqld: ColDB: am=102 colname=ShippingAddressLastName tabname=Orders num=0
Jul 30 06:00:00 di-mariadb-test1 mysqld: cdp(57).Name=ShippingAddressLastName cp=(nil)
Jul 30 06:00:00 di-mariadb-test1 mysqld: New BLOCK: size=144 g=0x7f640c5ca6b0 p=(nil)
Jul 30 06:00:00 di-mariadb-test1 mysqld: SubAlloc in 0x7f63fffff010 size=144 used=20016 free=67088848
Jul 30 06:00:00 di-mariadb-test1 mysqld: Done memp=0x7f6400003e40 used=20160 free=67088704
Jul 30 06:00:00 di-mariadb-test1 mysqld: making new JDBCCOL C57 ShippingAddressLastName at 0x7f6400003e40
Jul 30 06:00:00 di-mariadb-test1 mysqld: colp=0x7f6400003e40
Jul 30 06:00:00 di-mariadb-test1 mysqld: ColDB: am=102 colname=ShippingAddressAddress1 tabname=Orders num=0
Jul 30 06:00:00 di-mariadb-test1 mysqld: cdp(58).Name=ShippingAddressAddress1 cp=(nil)
Jul 30 06:00:00 di-mariadb-test1 mysqld: New BLOCK: size=144 g=0x7f640c5ca6b0 p=(nil)
Jul 30 06:00:00 di-mariadb-test1 mysqld: SubAlloc in 0x7f63fffff010 size=144 used=20160 free=67088704
Jul 30 06:00:00 di-mariadb-test1 mysqld: Done memp=0x7f6400003ed0 used=20304 free=67088560



 Comments   
Comment by Robert Dyas [ 2019-08-22 ]

Hi Olivier - did you ever make that change to the logging for 10.3.17 so that we might be better able to track down this error?

Comment by Robert Dyas [ 2019-08-22 ]

Also, here is some new output from
sudo cat /var/log/messages-20190818 | grep "valblock" -C 25
let me know if you need more context lines before and after.
File attached. valblock-error-aug-22.log

This was collected with
connect_xtrace=1023

Comment by Olivier Bertrand [ 2019-08-23 ]

Not yet. It will be made in the next release.

Looking at the attached file, the error occurs when reading a column. However, there are many column types. So I would need at least the CREATE TABLE to try to guess what could have happened.

Comment by Robert Dyas [ 2019-08-23 ]

Here are the CREATE TABLE statements:

CREATE TABLE Orders ( `Id` BIGINT , 
`Number` BIGINT ,
`CustomerId` BIGINT ,
`CustomerFirstName` VARCHAR(255) ,
`CustomerLastName` VARCHAR(255) ,
`Currency` VARCHAR(255) ,
`Email` VARCHAR(255) ,
`Name` VARCHAR(255) ,
`TotalDiscounts` DOUBLE ,
`TotalOrderItemsPrice` DOUBLE ,
`TotalPrice` DOUBLE ,
`SubtotalPrice` DOUBLE ,
`TotalTax` DOUBLE ,
`TotalWeight` BIGINT ,
`BrowserIp` VARCHAR(255) ,
`BuyerAcceptsMarketing` BOOLEAN ,
`CancelReason` VARCHAR(255) ,
`CartToken` VARCHAR(255) ,
`OrderStatusUrl` VARCHAR(255) ,
`Token` VARCHAR(255) ,
`TaxesIncluded` BOOLEAN ,
`SourceName` VARCHAR(255) ,
`ReferringSite` VARCHAR(255) ,
`ProcessingMethod` VARCHAR(255) ,
`Phone` VARCHAR(255) ,
`Note` VARCHAR(255) ,
`LocationId` BIGINT ,
`LandingSite` VARCHAR(255) ,
`Tags` VARCHAR(255) ,
`FulfillmentStatus` VARCHAR(255) ,
`FinancialStatus` VARCHAR(255) ,
`DiscountCodes` VARCHAR(255) ,
`CustomerLocale` VARCHAR(255) ,
`InvoiceSentAt` DATETIME ,
`InvoiceUrl` VARCHAR(255) ,
`TaxExempt` BOOLEAN ,
`LineAggregate` VARCHAR(255) ,
`TaxAggregate` VARCHAR(255) ,
`TransactionAggregate` VARCHAR(255) ,
`BillingAddressFirstName` VARCHAR(255) ,
`BillingAddressLastName` VARCHAR(255) ,
`BillingAddressAddress1` VARCHAR(255) ,
`BillingAddressAddress2` VARCHAR(255) ,
`BillingAddressPhone` VARCHAR(255) ,
`BillingAddressCity` VARCHAR(255) ,
`BillingAddressCompany` VARCHAR(255) ,
`BillingAddressZip` VARCHAR(255) ,
`BillingAddressProvince` VARCHAR(255) ,
`BillingAddressCountry` VARCHAR(255) ,
`BillingAddressLatitude` DOUBLE ,
`BillingAddressLongitude` DOUBLE ,
`BillingAddressName` VARCHAR(255) ,
`BillingAddressCountryCode` VARCHAR(255) ,
`BillingAddressProvinceCode` VARCHAR(255) ,
`BillingAddressDefault` BOOLEAN ,
`ShippingAddressFirstName` VARCHAR(255) ,
`ShippingAddressLastName` VARCHAR(255) ,
`ShippingAddressAddress1` VARCHAR(255) ,
`ShippingAddressAddress2` VARCHAR(255) ,
`ShippingAddressPhone` VARCHAR(255) ,
`ShippingAddressCity` VARCHAR(255) ,
`ShippingAddressCompany` VARCHAR(255) ,
`ShippingAddressZip` VARCHAR(255) ,
`ShippingAddressProvince` VARCHAR(255) ,
`ShippingAddressCountry` VARCHAR(255) ,
`ShippingAddressLatitude` DOUBLE ,
`ShippingAddressLongitude` DOUBLE ,
`ShippingAddressName` VARCHAR(255) ,
`ShippingAddressCountryCode` VARCHAR(255) ,
`ShippingAddressProvinceCode` VARCHAR(255) ,
`ShippingAddressDefault` BOOLEAN ,
`AppliedDiscountTitle` VARCHAR(255) ,
`AppliedDiscountDescription` VARCHAR(255) ,
`AppliedDiscountValue` DOUBLE ,
`AppliedDiscountValueType` VARCHAR(255) ,
`AppliedDiscountAmount` DOUBLE ,
`ProcessedAt` DATETIME ,
`CreatedAt` DATETIME ,
`ClosedAt` DATETIME ,
`CancelledAt` DATETIME ,
`UpdatedAt` DATETIME ,
`SendReceipt` BOOLEAN ,
`SendFulfillmentReceipt` BOOLEAN ,
`InventoryBehaviour` VARCHAR(255) ,
`Operation` VARCHAR(255)  )  ENGINE=CONNECT TABLE_TYPE=JDBC  BLOCK_SIZE=100  TABNAME='Orders'  QUOTED=1  
CONNECTION='ds73f4ec8272e55900021bd20461649a16' OPTION_LIST='Memory=2' 
 
 
CREATE TABLE OrdersItems ( `ItemId` BIGINT , 
`OrderId` BIGINT ,
`OrderUpdatedAt` DATETIME ,
`ProductId` BIGINT ,
`ItemVariantId` BIGINT ,
`ItemTitle` VARCHAR(255) ,
`Name` VARCHAR(255) ,
`ItemQuantity` BIGINT ,
`ItemPrice` DOUBLE ,
`ItemGrams` BIGINT ,
`SKU` VARCHAR(255) ,
`VariantTitle` VARCHAR(255) ,
`Properties` VARCHAR(255) ,
`Vendor` VARCHAR(255) ,
`FulFillmentsService` VARCHAR(255) ,
`RequiresShipping` BOOLEAN ,
`Taxable` BOOLEAN ,
`GiftCard` BOOLEAN ,
`FulfillableQuantity` BIGINT ,
`TotalDiscount` DOUBLE ,
`FulfillmentStatus` VARCHAR(255) ,
`AppliedDiscountTitle` VARCHAR(255) ,
`AppliedDiscountDescription` VARCHAR(255) ,
`AppliedDiscountValue` DOUBLE ,
`AppliedDiscountValueType` VARCHAR(255) ,
`AppliedDiscountAmount` DOUBLE  )  ENGINE=CONNECT TABLE_TYPE=JDBC  BLOCK_SIZE=100  TABNAME='OrdersItems'  QUOTED=1  
CONNECTION='ds73f4ec8272e55900021bd20461649a16' OPTION_LIST='Memory=2' 

Comment by Olivier Bertrand [ 2019-08-23 ]

I did not check it yet, but I found something that could explain these errors occuring apparently randomly. Perhaps you sometimes receive a value bigger than 255 bytes and CONNECT won't recognize this as such explaining why a better and more accurate message is not return.
Could you check that increasing the column sizes makes the errors not happening anymore?

Comment by Robert Dyas [ 2019-08-23 ]

I can't easily check with increased column size as this is production even with the errors and it only happens occasionally EVEN WITH the exact same data. i.e. I can run this once on the data and it will fail, then i can run it again on the exact same data and it will work, then fail, etc... it might run 20 times and then fail, or it might run 1 time and then fail once, then run once, etc - no discernible pattern.

The only things I can think of (stabbing in the dark) is:

  1. if connect tries to allocate memory and the system is low on memory and has to free resources b4 allocation at the OS level, maybe this is the issue (i.e. a call to allocate x bytes returns null because the malloc fails... i.e. malloc is on sometimes returning a null pointer and this isn't checked for)
  2. the jdbc driver connect is relying on is doing something dirty - like skipping a column on occasion - and connect isn't checking for that ugly edge case

Those are just wild speculation. But because its random - even with the same data set - leads me to believe memory allocation could be the problem..

Comment by Olivier Bertrand [ 2019-08-24 ]

Connect doesn't allocate memory. It just sub-allocate some when needed and because this is done in a clean pool, failures can't happen randoml with the same data.
The only way a computer can repond differently with the same data, except for multithreading that is not done by Connect for JDBC tables, is hardware failure, which I doubt is the case here.
Remains the possibility that the remote server doesn't return the same data each time called even with the same queries. This can be checked only by debugging or by adding more tracing. I will add more tracing but this means the server being updated or recompiled with new source files.

Comment by Olivier Bertrand [ 2019-08-24 ]

Meanwhile, can you repeat your tests with connect_xtrace set to 2. This may help to see on which column the error occurs.

Comment by Robert Dyas [ 2019-08-24 ]

I've just changed it to connect_xtrace to 2 (was 1023).
As soon as I get a failure I'll post it here.

The memory issue... if you free memory and then accidentally use a pointer to the free'ed memory it can behave in a seemingly random way... when the memory is free'ed the OS doesn't free it and it is not reinitialized until it is overwritten... so in many cases using a pointer to recently free'ed memory will work, but under certain circumstances (if the OS happens to free it immediately) it will be a bogus reference. Usually this results in a seg fault, which we don't have it seems... again just guessing. I haven't coded in C since the 1990s.

Comment by Olivier Bertrand [ 2019-08-24 ]

As I said, I don't allocate memory. Just sub-allocating in a big pool. Nothing is ever freed. On each query, the pool is reset as empty and sub-allocating is done as before.

Comment by Robert Dyas [ 2019-08-28 ]

More info here and a similar "random" error... not sure if this sheds any light on valblock error. Log attached. rc_neg3.log

Comment by Robert Dyas [ 2019-08-28 ]

Trying log file again. rc_neg3.log

Comment by Olivier Bertrand [ 2019-08-28 ]

This same error OpenTable: Cannot get result size rc=-3 is the one where the message explaining why is lost. I have fixed it, but we must wait to the next release.

Comment by Robert Dyas [ 2019-09-14 ]

I now have 10.3.18 installed to capture the additional info.
What should I set connect_xtrace to? 1023 ? some other value?

Comment by Olivier Bertrand [ 2019-09-14 ]

Sorry but, I don't know why, my fix has disappeared.
However, setting connect_xtrace to 1 should give us more information.

Comment by Robert Dyas [ 2019-09-15 ]

rc=-3 error below with connect_xtrace at 2

Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: FulfillmentStatus status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: FinancialStatus status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: DiscountCodes status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressFirstName status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressLastName status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressAddress1 status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressAddress2 status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressPhone status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressCity status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressZip status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressCountryCode status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressProvinceCode status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ProcessedAt status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: CreatedAt status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: CancelledAt status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: UpdatedAt status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Maps: read=F0813C85 write=00000000 vcol=00000000 defr=F0813C85 defw=00000000
Sep 15 00:04:25 di-mariadb-test1 mysqld: FormatValue: ptm=0x7fbc9c0b88a0 len=20
Sep 15 00:04:25 di-mariadb-test1 mysqld: strftime: n=19 buf=2019-04-29 23:08:59
Sep 15 00:04:25 di-mariadb-test1 mysqld: FormatValue: ptm=0x7fbc9c0b88a0 len=20
Sep 15 00:04:25 di-mariadb-test1 mysqld: strftime: n=19 buf=2019-04-29 23:08:59
Sep 15 00:04:25 di-mariadb-test1 mysqld: FormatValue: ptm=0x7fbc9c0b88a0 len=20
Sep 15 00:04:25 di-mariadb-test1 mysqld: strftime: n=19 buf=2019-04-29 23:09:03
Sep 15 00:04:25 di-mariadb-test1 mysqld: JDBC ReadDB: R2389 Mode=10
Sep 15 00:04:25 di-mariadb-test1 mysqld: Read: Rbuf=1 rc=0
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: Id status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: CustomerId status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: Name status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: TotalPrice status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: setting double: '63.6' -> 63.600000
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: SubtotalPrice status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: setting double: '63.6' -> 63.600000
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: TotalTax status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: setting double: '3.6' -> 3.600000
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: TotalWeight status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: CancelReason status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ProcessingMethod status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: Tags status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: FulfillmentStatus status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: FinancialStatus status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: DiscountCodes status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressFirstName status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressLastName status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressAddress1 status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressAddress2 status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressPhone status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressCity status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressZip status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressCountryCode status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressProvinceCode status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ProcessedAt status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: CreatedAt status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: CancelledAt status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: UpdatedAt status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Maps: read=F0813C85 write=00000000 vcol=00000000 defr=F0813C85 defw=00000000
Sep 15 00:04:25 di-mariadb-test1 mysqld: FormatValue: ptm=0x7fbc9c0b88a0 len=20
Sep 15 00:04:25 di-mariadb-test1 mysqld: strftime: n=19 buf=2019-04-29 23:03:52
Sep 15 00:04:25 di-mariadb-test1 mysqld: FormatValue: ptm=0x7fbc9c0b88a0 len=20
Sep 15 00:04:25 di-mariadb-test1 mysqld: strftime: n=19 buf=2019-04-29 23:03:52
Sep 15 00:04:25 di-mariadb-test1 mysqld: FormatValue: ptm=0x7fbc9c0b88a0 len=20
Sep 15 00:04:25 di-mariadb-test1 mysqld: strftime: n=19 buf=2019-04-29 23:03:59
Sep 15 00:04:25 di-mariadb-test1 mysqld: JDBC ReadDB: R2389 Mode=10
Sep 15 00:04:25 di-mariadb-test1 mysqld: Read: Rbuf=1 rc=0
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: Id status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: CustomerId status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: Name status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: TotalPrice status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: setting double: '95' -> 95.000000
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: SubtotalPrice status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: setting double: '95' -> 95.000000
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: TotalTax status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: setting double: '0' -> 0.000000
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: TotalWeight status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: CancelReason status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ProcessingMethod status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: Tags status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: FulfillmentStatus status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: FinancialStatus status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: DiscountCodes status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressFirstName status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressLastName status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressAddress1 status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressAddress2 status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressPhone status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressCity status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressZip status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressCountryCode status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ShippingAddressProvinceCode status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: ProcessedAt status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: CreatedAt status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: CancelledAt status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Col Eval: UpdatedAt status=0002
Sep 15 00:04:25 di-mariadb-test1 mysqld: Maps: read=F0813C85 write=00000000 vcol=00000000 defr=F0813C85 defw=00000000
Sep 15 00:04:25 di-mariadb-test1 mysqld: FormatValue: ptm=0x7fbc9c0b88a0 len=20
Sep 15 00:04:25 di-mariadb-test1 mysqld: strftime: n=19 buf=2019-04-29 22:58:46
Sep 15 00:04:25 di-mariadb-test1 mysqld: FormatValue: ptm=0x7fbc9c0b88a0 len=20
Sep 15 00:04:25 di-mariadb-test1 mysqld: strftime: n=19 buf=2019-04-29 22:58:46
Sep 15 00:04:25 di-mariadb-test1 mysqld: FormatValue: ptm=0x7fbc9c0b88a0 len=20
Sep 15 00:04:25 di-mariadb-test1 mysqld: strftime: n=19 buf=2019-04-29 22:58:50
Sep 15 00:05:43 di-mariadb-test1 journal: Suppressed 114218 messages from /system.slice/mariadb.service
Sep 15 00:05:43 di-mariadb-test1 mysqld: OpenTable: Get result size:  (rc=-3)
Sep 15 00:09:51 di-mariadb-test1 mysqld: 2019-09-15  0:09:51 1266 [Warning] Access denied for user 'root'@'85.93.20.91' (using password: YES)
Sep 15 00:13:33 di-mariadb-test1 systemd: Removed slice User Slice of root.
Sep 15 00:18:56 di-mariadb-test1 mysqld: 2019-09-15  0:18:56 1268 [Warning] Access denied for user 'root'@'85.93.20.91' (using password: YES)
Sep 15 00:19:00 di-mariadb-test1 mysqld: 2019-09-15  0:19:00 1269 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:19:01 di-mariadb-test1 mysqld: 2019-09-15  0:19:01 1270 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:19:01 di-mariadb-test1 mysqld: 2019-09-15  0:19:01 1271 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:19:01 di-mariadb-test1 mysqld: 2019-09-15  0:19:01 1272 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:19:01 di-mariadb-test1 mysqld: 2019-09-15  0:19:01 1273 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:19:01 di-mariadb-test1 mysqld: 2019-09-15  0:19:01 1274 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:19:02 di-mariadb-test1 mysqld: 2019-09-15  0:19:02 1275 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:19:03 di-mariadb-test1 mysqld: 2019-09-15  0:19:03 1276 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:19:03 di-mariadb-test1 mysqld: 2019-09-15  0:19:03 1277 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:19:03 di-mariadb-test1 mysqld: 2019-09-15  0:19:03 1278 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:28:01 di-mariadb-test1 mysqld: 2019-09-15  0:28:01 1279 [Warning] Access denied for user 'root'@'85.93.20.91' (using password: YES)
Sep 15 00:34:00 di-mariadb-test1 mysqld: 2019-09-15  0:34:00 1280 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:34:01 di-mariadb-test1 mysqld: 2019-09-15  0:34:01 1281 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:34:01 di-mariadb-test1 mysqld: 2019-09-15  0:34:01 1282 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:34:01 di-mariadb-test1 mysqld: 2019-09-15  0:34:01 1283 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:34:01 di-mariadb-test1 mysqld: 2019-09-15  0:34:01 1284 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:34:02 di-mariadb-test1 mysqld: 2019-09-15  0:34:02 1285 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:34:02 di-mariadb-test1 mysqld: 2019-09-15  0:34:02 1286 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:34:03 di-mariadb-test1 mysqld: 2019-09-15  0:34:03 1287 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:34:03 di-mariadb-test1 mysqld: 2019-09-15  0:34:03 1288 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:34:03 di-mariadb-test1 mysqld: 2019-09-15  0:34:03 1289 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:44:26 di-mariadb-test1 mysqld: 2019-09-15  0:44:26 1290 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:44:27 di-mariadb-test1 mysqld: 2019-09-15  0:44:27 1291 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:44:27 di-mariadb-test1 mysqld: 2019-09-15  0:44:27 1292 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:46:21 di-mariadb-test1 mysqld: 2019-09-15  0:46:21 1293 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:46:21 di-mariadb-test1 mysqld: 2019-09-15  0:46:21 1294 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:46:22 di-mariadb-test1 mysqld: 2019-09-15  0:46:22 1295 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:46:49 di-mariadb-test1 mysqld: 2019-09-15  0:46:49 1296 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:46:50 di-mariadb-test1 mysqld: 2019-09-15  0:46:50 1297 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:46:50 di-mariadb-test1 mysqld: 2019-09-15  0:46:50 1298 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:47:31 di-mariadb-test1 mysqld: 2019-09-15  0:47:31 1299 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:47:31 di-mariadb-test1 mysqld: 2019-09-15  0:47:31 1300 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:47:37 di-mariadb-test1 mysqld: 2019-09-15  0:47:37 1301 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:47:37 di-mariadb-test1 mysqld: 2019-09-15  0:47:37 1302 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:47:37 di-mariadb-test1 mysqld: 2019-09-15  0:47:37 1303 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:49:00 di-mariadb-test1 mysqld: 2019-09-15  0:49:00 1304 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:49:00 di-mariadb-test1 mysqld: 2019-09-15  0:49:00 1305 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:49:01 di-mariadb-test1 mysqld: 2019-09-15  0:49:01 1306 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:49:01 di-mariadb-test1 mysqld: 2019-09-15  0:49:01 1307 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:49:01 di-mariadb-test1 mysqld: 2019-09-15  0:49:01 1308 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:49:01 di-mariadb-test1 mysqld: 2019-09-15  0:49:01 1309 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:49:02 di-mariadb-test1 mysqld: 2019-09-15  0:49:02 1310 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:49:02 di-mariadb-test1 mysqld: 2019-09-15  0:49:02 1311 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:49:03 di-mariadb-test1 mysqld: 2019-09-15  0:49:03 1312 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 00:49:03 di-mariadb-test1 mysqld: 2019-09-15  0:49:03 1313 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:01:01 di-mariadb-test1 systemd: Created slice User Slice of root.
Sep 15 01:01:01 di-mariadb-test1 systemd: Started Session 14 of user root.
Sep 15 01:01:41 di-mariadb-test1 systemd: Removed slice User Slice of root.
Sep 15 01:04:00 di-mariadb-test1 mysqld: 2019-09-15  1:04:00 1314 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:04:00 di-mariadb-test1 mysqld: 2019-09-15  1:04:00 1315 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:04:01 di-mariadb-test1 mysqld: 2019-09-15  1:04:01 1316 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:04:01 di-mariadb-test1 mysqld: 2019-09-15  1:04:01 1317 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:04:01 di-mariadb-test1 mysqld: 2019-09-15  1:04:01 1318 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:04:01 di-mariadb-test1 mysqld: 2019-09-15  1:04:01 1319 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:04:02 di-mariadb-test1 mysqld: 2019-09-15  1:04:02 1320 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:04:02 di-mariadb-test1 mysqld: 2019-09-15  1:04:02 1321 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:04:03 di-mariadb-test1 mysqld: 2019-09-15  1:04:03 1322 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:04:03 di-mariadb-test1 mysqld: 2019-09-15  1:04:03 1323 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:19:00 di-mariadb-test1 mysqld: 2019-09-15  1:19:00 1324 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:19:00 di-mariadb-test1 mysqld: 2019-09-15  1:19:00 1325 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:19:01 di-mariadb-test1 mysqld: 2019-09-15  1:19:01 1326 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:19:01 di-mariadb-test1 mysqld: 2019-09-15  1:19:01 1327 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:19:01 di-mariadb-test1 mysqld: 2019-09-15  1:19:01 1328 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:19:01 di-mariadb-test1 mysqld: 2019-09-15  1:19:01 1329 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:19:02 di-mariadb-test1 mysqld: 2019-09-15  1:19:02 1330 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:19:02 di-mariadb-test1 mysqld: 2019-09-15  1:19:02 1331 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:19:03 di-mariadb-test1 mysqld: 2019-09-15  1:19:03 1332 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:19:03 di-mariadb-test1 mysqld: 2019-09-15  1:19:03 1333 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:22:38 di-mariadb-test1 mysqld: 2019-09-15  1:22:38 1334 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:22:38 di-mariadb-test1 mysqld: 2019-09-15  1:22:38 1335 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:22:39 di-mariadb-test1 mysqld: 2019-09-15  1:22:39 1336 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:23:17 di-mariadb-test1 mysqld: 2019-09-15  1:23:17 1337 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:23:18 di-mariadb-test1 mysqld: 2019-09-15  1:23:18 1338 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:23:28 di-mariadb-test1 mysqld: 2019-09-15  1:23:28 1339 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:23:28 di-mariadb-test1 mysqld: 2019-09-15  1:23:28 1340 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:24:04 di-mariadb-test1 mysqld: 2019-09-15  1:24:04 1341 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:24:04 di-mariadb-test1 mysqld: 2019-09-15  1:24:04 1342 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:34:00 di-mariadb-test1 mysqld: 2019-09-15  1:34:00 1343 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:34:00 di-mariadb-test1 mysqld: 2019-09-15  1:34:00 1344 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:34:01 di-mariadb-test1 mysqld: 2019-09-15  1:34:01 1345 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:34:01 di-mariadb-test1 mysqld: 2019-09-15  1:34:01 1346 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:34:01 di-mariadb-test1 mysqld: 2019-09-15  1:34:01 1347 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:34:01 di-mariadb-test1 mysqld: 2019-09-15  1:34:01 1348 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:34:02 di-mariadb-test1 mysqld: 2019-09-15  1:34:02 1349 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:34:02 di-mariadb-test1 mysqld: 2019-09-15  1:34:02 1350 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:34:03 di-mariadb-test1 mysqld: 2019-09-15  1:34:03 1351 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:34:03 di-mariadb-test1 mysqld: 2019-09-15  1:34:03 1352 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:49:00 di-mariadb-test1 mysqld: 2019-09-15  1:49:00 1353 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:49:00 di-mariadb-test1 mysqld: 2019-09-15  1:49:00 1354 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:49:01 di-mariadb-test1 mysqld: 2019-09-15  1:49:01 1355 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:49:01 di-mariadb-test1 mysqld: 2019-09-15  1:49:01 1356 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:49:01 di-mariadb-test1 mysqld: 2019-09-15  1:49:01 1357 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:49:01 di-mariadb-test1 mysqld: 2019-09-15  1:49:01 1358 [Warning] IP address '107.178.237.19' has been resolved to the host name '19.237.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:49:02 di-mariadb-test1 mysqld: 2019-09-15  1:49:02 1359 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:49:02 di-mariadb-test1 mysqld: 2019-09-15  1:49:02 1360 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:49:03 di-mariadb-test1 mysqld: 2019-09-15  1:49:03 1361 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.
Sep 15 01:49:03 di-mariadb-test1 mysqld: 2019-09-15  1:49:03 1362 [Warning] IP address '107.178.200.226' has been resolved to the host name '226.200.178.107.gae.googleusercontent.com', which resembles IPv4-address itself.

Comment by Olivier Bertrand [ 2019-09-15 ]

Incidentally, my fix if there (I was thinking about ODBC) but doesn't show anything. Possible causes are a buffer overflow when retrieving date values or a throw not correctly handled.
Could you please repeat the test with connect_xtrace=3?

Comment by Robert Dyas [ 2019-09-16 ]

New valblock error below with connect_xtrace 3.

Sep 16 18:24:59 di-mariadb-test1 mysqld: Table JDBC made
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: tdp=0x7f9d5800f3b0
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdb=0x7f9d5800f3b0 type=JDBC
Sep 16 18:24:59 di-mariadb-test1 mysqld: Going to get table...
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdbp=0x7f9d58014520 name=fbi_ladings amtype=102
Sep 16 18:24:59 di-mariadb-test1 mysqld: 0x5555fdc3e550 In info: flag=212 valid_info=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: XTAB: making new TABLE sfa_Account (null)
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDB: name=sfa_Account
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: name=sfa_Account am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: MakeTableDesc: name=sfa_Account schema=<null> am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: server: ds6792bd034e5d4c1a00db7a685dc48ab6 Tabname: AccountTable JDBC made
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: tdp=0x7f9d58014700
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdb=0x7f9d58014700 type=JDBC
Sep 16 18:24:59 di-mariadb-test1 mysqld: Going to get table...
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdbp=0x7f9d58018688 name=sfa_Account amtype=102
Sep 16 18:24:59 di-mariadb-test1 mysqld: 0x5555fdc62a50 In info: flag=212 valid_info=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: XTAB: making new TABLE MS_pets (null)
Sep 16 18:24:59 di-mariadb-test1 mysqld: DB: name=sfc_Contact mode=0 cat=0x7f9de80858f0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: tabp=0x7f9d88177508
Sep 16 18:24:59 di-mariadb-test1 mysqld: Returning tdbp=0x7f9d8817b1b0 mode=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: name=shopLC_Orders mode=0 cat=0x7f9de80858f0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: tabp=0x7f9d8817b348
Sep 16 18:24:59 di-mariadb-test1 mysqld: Returning tdbp=0x7f9d88180478 mode=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: name=parasql_connect_tables mode=0 cat=0x7f9de80858f0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: tabp=0x7f9d88180610
Sep 16 18:24:59 di-mariadb-test1 mysqld: Returning tdbp=0x7f9d88181e90 mode=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: name=jira_Epics mode=0 cat=0x7f9de80858f0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: tabp=0x7f9d88181fb8
Sep 16 18:24:59 di-mariadb-test1 mysqld: Returning tdbp=0x7f9d881838e0 mode=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntCheckDB: dbuserp=0x7f9d98164e20
Sep 16 18:24:59 di-mariadb-test1 mysqld: cat=0x7f9d98164ec0 oldhandler=(nil) newhandler=0x5555fed34e80
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: name=Orders mode=10 cat=0x7f9d98164ec0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: tabp=0x7f9d8bfff038
Sep 16 18:24:59 di-mariadb-test1 mysqld: Returning tdbp=0x7f9d8c003340 mode=10
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntOpenTable: tdbp=0x7f9d8c003340 mode=10
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column Id
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column CustomerId
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column Name
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column TotalPrice
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column SubtotalPrice
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column TotalTax
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column TotalWeight
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column CancelReason
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ProcessingMethod
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column Tags
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column FulfillmentStatus
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column FinancialStatus
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column DiscountCodes
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ShippingAddressFirstName
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ShippingAddressLastName
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ShippingAddressAddress1
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ShippingAddressAddress2
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ShippingAddressPhone
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ShippingAddressCity
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ShippingAddressZip
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ShippingAddressCountryCode
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ShippingAddressProvinceCode
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ProcessedAt
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column CreatedAt
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column CancelledAt
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column UpdatedAt
Sep 16 18:24:59 di-mariadb-test1 mysqld: Opening table Orders in mode 10 tdbp=0x7f9d8c003340
Sep 16 18:24:59 di-mariadb-test1 mysqld: About to open the table: tdbp=0x7f9d8c003340
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntCloseTable: tdbp=0x7f9d8c003340 mode=10 nox=1 abort=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: Table Orders closed
Sep 16 18:24:59 di-mariadb-test1 mysqld: =====> Begin new query 155816
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntCheckDB: dbuserp=0x7f9d98164e20
Sep 16 18:24:59 di-mariadb-test1 mysqld: cat=0x7f9d98164ec0 oldhandler=0x5555fed34e80 newhandler=0x5555fec8d810
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: name=OrderItems mode=10 cat=0x7f9d98164ec0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: tabp=0x7f9d8bfff038
Sep 16 18:24:59 di-mariadb-test1 mysqld: Returning tdbp=0x7f9d8c0005f0 mode=10
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntOpenTable: tdbp=0x7f9d8c0005f0 mode=10
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ItemId
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column OrderId
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column OrderUpdatedAt
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ProductId
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ItemVariantId
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ItemTitle
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column Name
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ItemQuantity
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ItemPrice
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column ItemGrams
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column SKU
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column VariantTitle
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column Properties
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column Vendor
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column FulFillmentsService
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column RequiresShipping
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column Taxable
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column GiftCard
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column FulfillableQuantity
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column TotalDiscount
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column FulfillmentStatus
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column AppliedDiscountTitle
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column AppliedDiscountDescription
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column AppliedDiscountValue
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column AppliedDiscountValueType
Sep 16 18:24:59 di-mariadb-test1 mysqld: Allocating column AppliedDiscountAmount
Sep 16 18:24:59 di-mariadb-test1 mysqld: Opening table OrderItems in mode 10 tdbp=0x7f9d8c0005f0
Sep 16 18:24:59 di-mariadb-test1 mysqld: About to open the table: tdbp=0x7f9d8c0005f0
Sep 16 18:24:59 di-mariadb-test1 mysqld: Error 5 reading columns: Out of range valblock index value
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntCloseTable: tdbp=0x7f9d8c0005f0 mode=10 nox=1 abort=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: Table OrderItems closed
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: name=sfa_Contact mode=0 cat=0x7f9d90078ec0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: tabp=0x7f9d57fff028
Sep 16 18:24:59 di-mariadb-test1 mysqld: Returning tdbp=0x7f9d58002c88 mode=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: name=shopL_Customers mode=0 cat=0x7f9d90078ec0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: tabp=0x7f9d58002e20
Sep 16 18:24:59 di-mariadb-test1 mysqld: Returning tdbp=0x7f9d58004f10 mode=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: name=shopL_OrdersItems mode=0 cat=0x7f9d90078ec0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: tabp=0x7f9d580050a8
Sep 16 18:24:59 di-mariadb-test1 mysqld: Returning tdbp=0x7f9d58007770 mode=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: name=Orders2 mode=0 cat=0x7f9d90078ec0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: tabp=0x7f9d58007908
Sep 16 18:24:59 di-mariadb-test1 mysqld: Returning tdbp=0x7f9d5800c980 mode=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: name=OrdersItems2 mode=0 cat=0x7f9d90078ec0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: tabp=0x7f9d5800cb18
Sep 16 18:24:59 di-mariadb-test1 mysqld: Returning tdbp=0x7f9d5800f1d0 mode=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: name=fbi_ladings mode=0 cat=0x7f9d90078ec0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: tabp=0x7f9d5800f368
Sep 16 18:24:59 di-mariadb-test1 mysqld: Returning tdbp=0x7f9d58014520 mode=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: name=sfa_Account mode=0 cat=0x7f9d90078ec0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: tabp=0x7f9d580146b8
Sep 16 18:24:59 di-mariadb-test1 mysqld: Returning tdbp=0x7f9d58018688 mode=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: name=MS_pets mode=0 cat=0x7f9d90078ec0
Sep 16 18:24:59 di-mariadb-test1 mysqld: CntGetTDB: tabp=0x7GetTableDB: name=MS_pets
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: name=MS_pets am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: MakeTableDesc: name=MS_pets schema=<null> am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: server: ds1496357478163 Tabname: petsTable JDBC made
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: tdp=0x7f9d58018860
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdb=0x7f9d58018860 type=JDBC
Sep 16 18:24:59 di-mariadb-test1 mysqld: Going to get table...
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdbp=0x7f9d58019f00 name=MS_pets amtype=102
Sep 16 18:24:59 di-mariadb-test1 mysqld: 0x5555fdc69230 In info: flag=212 valid_info=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: XTAB: making new TABLE parasql_rmt_command (null)
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDB: name=parasql_rmt_command
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: name=parasql_rmt_command am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: MakeTableDesc: name=parasql_rmt_command schema=<null> am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: server: ds6792bd034e5d4c1a00db7a685dc48ab6 Tabname: parasql_rmt_commandTable JDBC made
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: tdp=0x7f9d5801a0e8
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdb=0x7f9d5801a0e8 type=JDBC
Sep 16 18:24:59 di-mariadb-test1 mysqld: Going to get table...
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdbp=0x7f9d5801b708 name=parasql_rmt_command amtype=101
Sep 16 18:24:59 di-mariadb-test1 mysqld: 0x5555fdc86760 In info: flag=212 valid_info=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: XTAB: making new TABLE fbi_contacts (null)
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDB: name=fbi_contacts
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: name=fbi_contacts am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: MakeTableDesc: name=fbi_contacts schema=<null> am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: Table JDBC made
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: tdp=0x7f9d5801b900
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdb=0x7f9d5801b900 type=JDBC
Sep 16 18:24:59 di-mariadb-test1 mysqld: Going to get table...
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdbp=0x7f9d5801e278 name=fbi_contacts amtype=102
Sep 16 18:24:59 di-mariadb-test1 mysqld: 0x5555fdcba590 In info: flag=212 valid_info=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: XTAB: making new TABLE MS_Clients (null)
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDB: name=MS_Clients
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: name=MS_Clients am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: MakeTableDesc: name=MS_Clients schema=<null> am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: server: ds1496357478163 Tabname: ClientsTable JDBC made
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: tdp=0x7f9d5801e458
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdb=0x7f9d5801e458 type=JDBC
Sep 16 18:24:59 di-mariadb-test1 mysqld: Going to get table...
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdbp=0x7f9d5801fc50 name=MS_Clients amtype=102
Sep 16 18:24:59 di-mariadb-test1 mysqld: 0x5555fdcc14b0 In info: flag=212 valid_info=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: XTAB: making new TABLE parasql_connect_columns (null)
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDB: name=parasql_connect_columns
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: name=parasql_connect_columns am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: MakeTableDesc: name=parasql_connect_columns schema=<null> am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: Table JDBC made
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: tdp=0x7f9d5801fe38
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdb=0x7f9d5801fe38 type=JDBC
Sep 16 18:24:59 di-mariadb-test1 mysqld: Going to get table...
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdbp=0x7f9d58021b38 name=parasql_connect_columns amtype=192
Sep 16 18:24:59 di-mariadb-test1 mysqld: 0x5555fdccb0b0 In info: flag=212 valid_info=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: XTAB: making new TABLE fbi_upload_documents (null)
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDB: name=fbi_upload_documents
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: name=fbi_upload_documents am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: MakeTableDesc: name=fbi_upload_documents schema=<null> am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: Table JDBC made
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: tdp=0x7f9d58021cb8
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdb=0x7f9d58021cb8 type=JDBC
Sep 16 18:24:59 di-mariadb-test1 mysqld: Going to get table...
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdbp=0x7f9d58023dc8 name=fbi_upload_documents amtype=102
Sep 16 18:24:59 di-mariadb-test1 mysqld: 0x5555fdcd34b0 In info: flag=212 valid_info=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: XTAB: making new TABLE fbi_lading_tasks (null)
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDB: name=fbi_lading_tasks
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: name=fbi_lading_tasks am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: MakeTableDesc: name=fbi_lading_tasks schema=<null> am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: Table JDBC made
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: tdp=0x7f9d58023fb0
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdb=0x7f9d58023fb0 type=JDBC
Sep 16 18:24:59 di-mariadb-test1 mysqld: Going to get table...
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdbp=0x7f9d58025ea8 name=fbi_lading_tasks amtype=102
Sep 16 18:24:59 di-mariadb-test1 mysqld: 0x5555fdce60f0 In info: flag=212 valid_info=0
Sep 16 18:24:59 di-mariadb-test1 mysqld: XTAB: making new TABLE jira_Issues (null)
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDB: name=jira_Issues
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: name=jira_Issues am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: MakeTableDesc: name=jira_Issues schema=<null> am=<null>
Sep 16 18:24:59 di-mariadb-test1 mysqld: server: dsea49d2006a10289d6aff37e8ac576fcc Tabname: IssuesTable JDBC made
Sep 16 18:24:59 di-mariadb-test1 mysqld: GetTableDesc: tdp=0x7f9d58026088
Sep 16 18:24:59 di-mariadb-test1 mysqld: tdb=0x7f9d58026088 type=JDBC

Comment by Olivier Bertrand [ 2019-09-17 ]

This is totally absurd. Once we get valblock index error, once rc=-3 error. Are these the same query? It is impossible for me to imagine what can happen looking at these extracts that are completely different. The only way to investigate this is for me to try to reproduce the error. For this I need to have your exact table definitions, the involved query and access to the remote database.

Generated at Thu Feb 08 08:57:57 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.