Sebastian Wolfgarten:
> Hi,
>
> I am uncertain as to what?s causing the DB to get locked - I am also running
> Roundcube (webmail) on the server, maybe that?s the reason. I will check the
> permission roundcube uses to access the db, I think it can be read-only which
> will hopefully fix the locking issue.
It certainly looks like a problem specific to your setup. The Postfix
sqlite client has been around since Postfix 2.8 and it has hardly
changed.
> As a feature request, would it maybe make sense to add a waiting
> period to be able to wait for the lock for 1-2 seconds and then
> retry with the database query?
The only lock that can prevent sqlite from reading is a write lock,
and there is nothing in Postfix that generate an sqlite write request.
Look at the file modification time. Did the file change recently?
Let's find out more about the error first. See John Fawcett's suggestion.
Wietse
>
> Kind regards
> Sebastian
>
> > Am 10.01.2018 um 21:15 schrieb Wietse Venema <wie...@porcupine.org>:
> >
> > Sebastian Wolfgarten:
> >> Dear all,
> >>
> >> I am running postfix 3.3 and recently migrated all my virtual
> >> domains from MySQL to Sqlite for performance reasons. So far,
> >> everything works fine however up to 5-8 times a day, I am seeing
> >> an error message in my mail.log saying that the Sqlite 3 database
> >> may be locked. Here is an example:
> >
> > So what is locking the database? The query as shown does not attempt
> > to modify the database. Note that the query fails immediately, there
> > is no attempt to wait for a lock to be released.
> >
> > Wietse
> >
> >> Jan 10 18:00:45 waldfest postfix/smtpd[88198]: 3D13F5076C7:
> >> client=spring-chicken-bi.twitter.com[199.16.156.174]
> > ...
> >> Jan 10 18:00:45 waldfest postfix/cleanup[88252]: fatal:
> >> dict_sqlite_lookup: /etc/postfix/sqlite_virtual_alias_maps.cf: SQL
> >> finalize failed for query 'SELECT goto FROM alias WHERE
> >> address='pre...@freizeitpark-erlebnis.de' AND active = '1'': database is
> >> locked?
>
>
