You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We see a lot of the following errors in our postgres logs. Some times they come multiple times per our and some times it's some hours between.
2024-05-08 11:03:31.239 UTC [3800318] [10.1.0.193(42088)] peertube@peertube_prod ERROR: duplicate key value violates unique constraint "actor_url"
2024-05-08 11:03:31.239 UTC [3800318] [10.1.0.193(42088)] peertube@peertube_prod DETAIL: Key (url)=(https://REMOTE_INSTANCE/accounts/peertube) already exists.
2024-05-08 11:03:31.239 UTC [3800318] [10.1.0.193(42088)] peertube@peertube_prod STATEMENT: UPDATE "actor" SET "type"=$1,"preferredUsername"=$2,"url"=$3,"publicKey"=$4,"followingCount"=$5,"inboxUrl"=$6,"outboxUrl"=$7,"followersUrl"=$8,"followingUrl"=$9,"remoteCreatedAt"=$10,"updatedAt"=$11 WHERE "id" = $12
The REMOTE_INSTANCE variable is a Peertube instance who's following ours, and that instance is running Peertube 6.0.4. Some of the errors is logged at the same timestamp as when activity-pub-refresher job has been ran (succesfully). These jobs has a payload that looks like:
Are you able to check in your database the current url of the row "id" = $12? I suspect the remote instance updated its URL, that you already have in your database.
When I check the current url it's the same URL as the one it's trying to update with. I checked if there's any other rows with the same url, but it's just one. Sounds weird. I'm getting the id from this log statement
Describe the current behavior
We see a lot of the following errors in our postgres logs. Some times they come multiple times per our and some times it's some hours between.
The REMOTE_INSTANCE variable is a Peertube instance who's following ours, and that instance is running Peertube 6.0.4. Some of the errors is logged at the same timestamp as when
activity-pub-refresher
job has been ran (succesfully). These jobs has a payload that looks like:Steps to reproduce
Describe the expected behavior
No response
Additional information
PeerTube instance:
Browser name, version and platforms on which you could reproduce the bug:
Link to browser console log if relevant:
Link to server log if relevant (
journalctl
or/var/www/peertube/storage/logs/
):The text was updated successfully, but these errors were encountered: