ERROR is thrown by artifactory during DB statement

I see a lot of ERRORs being logged by Production Postgres DB related to Artifactory, it is cross region, I've provided 2 examples which look similar.

2020-04-27 07:00:50 UTC:192.168.130.219(59076):inditex_art@inditex_art:[12683]:ERROR: duplicate key value violates unique constraint "locks_pk"
2020-04-27 07:00:50 UTC:192.168.130.219(59076):inditex_art@inditex_art:[12683]:DETAIL: Key (category, lock_key)=(node-event-task-manager, node-npmjsorg-remote-cache/run-async/-/run-async-2.4.1.tgz) already exists.
2020-04-27 07:00:50 UTC:192.168.130.219(59076):inditex_art@inditex_art:[12683]:STATEMENT: insert into distributed_locks values($1,$2,$3,$4,$5,$6)

2020-04-27 05:01:46 UTC:192.168.191.29(42566):tr1_art@tr1_art:[88756]:ERROR: duplicate key value violates unique constraint "locks_pk"
2020-04-27 05:01:46 UTC:192.168.191.29(42566):tr1_art@tr1_art:[88756]:DETAIL: Key (category, lock_key)=(node-event-task-manager, libs-snapshot-local/com/thomsonreuters/anzpathway/cobalt-pathway-nz-comm/1.0.0-SNAPSHOT/cobalt-pathway-nz-comm-1.0.0-20180802.154603-28.pom) already exists.
2020-04-27 05:01:46 UTC:192.168.191.29(42566):tr1_art@tr1_art:[88756]:STATEMENT: insert into distributed_locks values($1,$2,$3,$4,$5,$6)

Please check and determine whether it should be handles or removed, as these production instances should not have an ERROR level log without being addressed accordingly