View Issue Details

IDProjectCategoryView StatusLast Update
0003027SOGoBackend Generalpublic2019-05-08 08:53
ReporterSigurd Holter Assigned Toludovic  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionnot fixable 
Platform[Server] LinuxOSRHEL/CentOSOS Version7
Summary0003027: Lock file broken
Description

I get the following repeatedly for cron run tasks :

/usr/sbin/sogo-ealarms-notify -p /etc/sogo/sieve.creds :

2014-12-14 18:16:01.268 sogo-ealarms-notify[20567] Warning ... someone broke our lock (/home/sogo/GNUstep/Defaults/.lck/.GNUstepDefaults.lck) ... and may have interfered with updating defaults data in file.

/usr/sbin/sogo-tool expire-sessions 60 :

2014-12-14 16:08:01.374 sogo-tool[17811] Warning ... someone broke our lock (/home/sogo/GNUstep/Defaults/.lck/.GNUstepDefaults.lck) ... and may have interfered with updating defaults data in file.

Google doesn't suggest anything regarding GNUstep lock files.

TagsNo tags attached.

Activities

Christian Mack

Christian Mack

2014-12-16 11:13

developer   ~0007840

There was another user with that problem on the user mailinglist.
See thread
http://www.mail-archive.com/users%40sogo.nu/msg19258.html

Sigurd Holter

Sigurd Holter

2014-12-17 11:47

reporter   ~0007863

Ok, changing the cron entry to :

/usr/sbin/sogo-ealarms-notify -p /etc/sogo/sieve.creds && /usr/sbin/sogo-tool expire-sessions 60

.. seems to have solved the Lock file problem.

But if sogo-ealarms-notify fails or returns FALSE the expire-sessions command will not run.
Not critical here, but there's room for improvement.

ludovic

ludovic

2014-12-17 18:29

administrator   ~0007865

The warning is in GNUstep.

It can also be safely ignored because neither of these tools nor sogod rewrite its defaults during runtime.

Issue History

Date Modified Username Field Change
2014-12-15 13:40 Sigurd Holter New Issue
2014-12-16 11:13 Christian Mack Note Added: 0007840
2014-12-17 11:47 Sigurd Holter Note Added: 0007863
2014-12-17 18:29 ludovic Note Added: 0007865
2014-12-17 18:29 ludovic Status new => resolved
2014-12-17 18:29 ludovic Resolution open => not fixable
2014-12-17 18:29 ludovic Assigned To => ludovic