View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004190SOGoBackend Generalpublic2017-06-07 20:532023-02-20 09:16
Reportermodir Assigned Tosebastien  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Platform[Server] LinuxOSRHEL/CentOSOS Version7
Product Version3.2.9 
Fixed in Version5.8.1 
Summary0004190: entry '{DAV:}XXX' already exists in DAV permissions table
Description

Since I restarted the sogod process my logs get flooded with those three messages:

Jun 07 22:48:16 sogod [45065]: [WARN] <0x0x7fdafc637a40[SOGoWebDAVAclManager]> entry '{DAV:}write' already exists in DAV permissions table
Jun 07 22:48:16 sogod [45065]: [WARN] <0x0x7fdafc637a40[SOGoWebDAVAclManager]> entry '{DAV:}write-properties' already exists in DAV permissions table
Jun 07 22:48:16 sogod [45065]: [WARN] <0x0x7fdafc637a40[SOGoWebDAVAclManager]> entry '{DAV:}write-content' already exists in DAV permissions table

What do I have to do now. It would be great if the message is a little bit clearer on what I need to do now. Did a DB upgrade script behave badly or why are those entries already there.

TagsNo tags attached.

Activities

Christian Mack

Christian Mack

2017-06-19 08:18

developer   ~0011986

That are warnings only.
Those are normal.
They only state, that some DAV client is setting ACLs, which are already set for that entry.
modir

modir

2022-12-12 16:21

reporter   ~0016486

If this is normal then it would be better if this is a INFO message and not a WARN. And then we can close this issue.
sebastien

sebastien

2023-02-20 09:16

administrator   ~0016664

https://github.com/Alinto/sogo/commit/1964ef03581947056807649fd46fa0d9a95f998e

Issue History

Date Modified Username Field Change
2017-06-07 20:53 modir New Issue
2017-06-19 08:18 Christian Mack Note Added: 0011986
2022-12-12 16:21 modir Note Added: 0016486
2023-02-20 09:16 sebastien Note Added: 0016664
2023-02-20 09:16 sebastien Assigned To => sebastien
2023-02-20 09:16 sebastien Status new => resolved
2023-02-20 09:16 sebastien Resolution open => fixed
2023-02-20 09:16 sebastien Fixed in Version => 5.8.1