SQLGrey itself will not be updated during the upgrade towards Jessie, however the change to Systemd will result in a stub automatically created by Systemd around the original init. The problem I encountered was, that SQLGrey would start before my database (MySQL). Hence you receive something like the following in /var/log/syslog

sqlgrey: dbaccess: can't connect to DB: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock’

The problem here is, that the generated stub is not obeying the init scripts dependencies and not having any Systemd ones, hence the services are starting in a “wild” order.

So what is the solution

We need to create at least the SQLGrey unit file and add the dependency into it. Create /etc/systemd/system/sqlgrey.service and add:

Description=SQLgrey Postfix Grey-listing Policy service
After=syslog.target network.target mysql.service
ExecStart=/usr/sbin/sqlgrey -d

Note the mysql.service in the After line. This is the needed dependency.

As you might have noticed, there is no mysql.service unit file existing, as the package maintainers have deprioritized to create one (there are two bugs #765425 and #742900.

However you can reference the stubs as well. If you need to adapt this for other services: To find the name of the stub you can use systemd-analyze blame. It gives you a list of the services started. Details you can get with systemctl, e.g. systemctl status mysql.service. The details will tell you in the Loaded line if it is a real unit file or just a init script stub.



1 comment

Dont forget, like I did, to enable the service! systemctl enable sqlgrey.service

Please Note: By submitting your comment your browser will send the values of the form fields (and the typical browsing meta data) to the API of Staticman. If you don't want to connect to a third party, you should E-Mail me.