[midPoint] Postgresql errors. Normal?

[Chris Woods]

Hi Pascal,

thanks for the tip. Just trying to through a process of elimination trying 
to find out why my midPoint instances appear to randomly freeze - which in 
turn causes docker to restart the container due to the health check failing.

Regards,
Chris

Am 20. Mai 2021 18:29:29 schrieb Pascal PÉRICHON via midPoint 
<midpoint at lists.evolveum.com>:
> Hi,
> We had exactly the same errors when a vacuum task was manipulating datas in 
> postgreSql (https://www.postgresql.org/docs/11/sql-vacuum.html) in the same 
> time that midpoint was importing or reconciliating midpoint users.
> We solve the problem when we modify the crontab for that particular 
> postgresql script : it runs now only in the night when midpoint is sleeping
> Hope that could help
> Regards
> Le 20/05/2021 à 15:44, Chris Woods via midPoint a écrit :
>> Hi all,
>>
>> just wondering if anyone else has come across these error messages in their 
>> postgres logs:
>>
>>
>>
>> 2021-05-20 13:39:10.901 UTC [1537] ERROR:  could not serialize access due 
>> to concurrent update
>>
>>
>>
>> 2021-05-20 13:39:10.901 UTC [1537] STATEMENT:  update m_object set 
>> createChannel=$1, createTimestamp=$2, creatorRef_relation=$3, 
>> creatorRef_targetOid=$4, creatorRef_targetType=$5, fullObject=$6, 
>> lifecycleState=$7, modifierRef_relation=$8, modifierRef_targetOid=$9, 
>> modifierRef_targetType=$10, modifyChannel=$11, modifyTimestamp=$12, 
>> name_norm=$13, name_orig=$14, objectTypeClass=$15, tenantRef_relation=$16, 
>> tenantRef_targetOid=$17, tenantRef_targetType=$18, version=$19 where oid=$20
>>
>>
>>
>> 2021-05-20 13:40:19.775 UTC [1605] ERROR:  could not serialize access due 
>> to concurrent update
>>
>>
>>
>> 2021-05-20 13:40:19.775 UTC [1605] STATEMENT:  update m_object set 
>> createChannel=$1, createTimestamp=$2, creatorRef_relation=$3, 
>> creatorRef_targetOid=$4, creatorRef_targetType=$5, fullObject=$6, 
>> lifecycleState=$7, modifierRef_relation=$8, modifierRef_targetOid=$9, 
>> modifierRef_targetType=$10, modifyChannel=$11, modifyTimestamp=$12, 
>> name_norm=$13, name_orig=$14, objectTypeClass=$15, tenantRef_relation=$16, 
>> tenantRef_targetOid=$17, tenantRef_targetType=$18, version=$19 where oid=$20
>>
>>
>>
>> 2021-05-20 13:41:26.803 UTC [1673] ERROR:  could not serialize access due 
>> to concurrent update
>>
>>
>>
>> 2021-05-20 13:41:26.803 UTC [1673] STATEMENT:  update m_object set 
>> createChannel=$1, createTimestamp=$2, creatorRef_relation=$3, 
>> creatorRef_targetOid=$4, creatorRef_targetType=$5, fullObject=$6, 
>> lifecycleState=$7, modifierRef_relation=$8, modifierRef_targetOid=$9, 
>> modifierRef_targetType=$10, modifyChannel=$11, modifyTimestamp=$12, 
>> name_norm=$13, name_orig=$14, objectTypeClass=$15, tenantRef_relation=$16, 
>> tenantRef_targetOid=$17, tenantRef_targetType=$18, version=$19 where oid=$20
>>
>>
>>
>> 2021-05-20 13:41:26.870 UTC [1676] ERROR:  could not serialize access due 
>> to concurrent update
>>
>>
>>
>> 2021-05-20 13:41:26.870 UTC [1676] STATEMENT:  update m_object set 
>> createChannel=$1, createTimestamp=$2, creatorRef_relation=$3, 
>> creatorRef_targetOid=$4, creatorRef_targetType=$5, fullObject=$6, 
>> lifecycleState=$7, modifierRef_relation=$8, modifierRef_targetOid=$9, 
>> modifierRef_targetType=$10, modifyChannel=$11, modifyTimestamp=$12, 
>> name_norm=$13, name_orig=$14, objectTypeClass=$15, tenantRef_relation=$16, 
>> tenantRef_targetOid=$17, tenantRef_targetType=$18, version=$19 where oid=$20
>>
>>
>>
>> 2021-05-20 13:41:26.928 UTC [1676] ERROR:  could not serialize access due 
>> to concurrent update
>>
>>
>>
>> 2021-05-20 13:41:26.928 UTC [1676] STATEMENT:  update m_object set 
>> createChannel=$1, createTimestamp=$2, creatorRef_relation=$3, 
>> creatorRef_targetOid=$4, creatorRef_targetType=$5, fullObject=$6, 
>> lifecycleState=$7, modifierRef_relation=$8, modifierRef_targetOid=$9, 
>> modifierRef_targetType=$10, modifyChannel=$11, modifyTimestamp=$12, 
>> name_norm=$13, name_orig=$14, objectTypeClass=$15, tenantRef_relation=$16, 
>> tenantRef_targetOid=$17, tenantRef_targetType=$18, version=$19 where oid=$20
>>
>>
>>
>> and whether they should be of concern or not J
>>
>>
>>
>> Thanks in advance,
>>
>> Chris.
>>
>>
>>
>> CHRIS WOODS
>>
>> Identity Management
>>
>> Information and Business Technology
>>
>>
>>
>> Rohde & Schwarz GmbH & Co. KG
>>
>> Mühldofstraße 15| 81671 München
>>
>> Telefon: +49 89 4129 15735
>>
>> Internet: https://www.rohde-schwarz.com
>>
>>
>>
>>
>>
>> _______________________________________________
>> midPoint mailing list
>> midPoint at lists.evolveum.com
>> https://lists.evolveum.com/mailman/listinfo/midpoint
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> https://lists.evolveum.com/mailman/listinfo/midpoint

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20210522/ee1b9efd/attachment-0001.htm>