Bug 7047

Summary:	spamassassin service doesn't start, /var/run/spamd is not created
Product:	Mageia	Reporter:	Olav Vitters <olav>
Component:	RPM Packages	Assignee:	Remco Rijnders <remco>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	mageia
Version:	Cauldron
Target Milestone:	Mageia 3
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	spamassassin-3.3.2-10.mga3.src.rpm	CVE:
Status comment:

Description Olav Vitters 2012-08-13 23:53:57 CEST

Aug 13 22:38:27 bkor spamd[1912]: Aug 13 22:38:27.856 [1912] warn: server socket setup failed, retry 9: spamd: directory for /var/run/spamd/spamd.socket does not exist, exiting
Aug 13 22:38:28 bkor spamd[1912]: Aug 13 22:38:28.857 [1912] error: spamd: directory for /var/run/spamd/spamd.socket does not exist, exiting
Aug 13 22:38:28 bkor spamd[1912]: spamd: directory for /var/run/spamd/spamd.socket does not exist, exiting
Aug 13 22:38:28 bkor systemd[1]: spamassassin.service: control process exited, code=exited status=255
Aug 13 22:38:28 bkor systemd[1]: Unit spamassassin.service entered failed state.


lack of setting up /var/run/spamd

Manuel Hiebel 2012-08-14 00:07:31 CEST

Assignee: bugsquad => remco
Target Milestone: --- => Mageia 3

Remco Rijnders 2012-08-14 04:25:40 CEST

Status: NEW => ASSIGNED

Remco Rijnders 2012-08-14 04:57:25 CEST

CC: (none) => mageia

Comment 1 Remco Rijnders 2012-08-14 05:02:07 CEST

@colin

I see the same as Olav does on my Cauldron box. However, in the .spec file for this package I do have 
install -d %{buildroot}/var/run/spamd

Furthermore, this spamd directory does show up under /var/run.runmove~/, but not under /var/run/ . Could this in any way be related to the big /usr move?

Comment 2 Colin Guthrie 2012-08-14 10:17:34 CEST

Yes it's 100% usrmove related. It needs tmpfiles.d now. I've been lazy so have not fixed up all the packages yet. I'll hopefully do a "spurt" soon.

Comment 3 Remco Rijnders 2012-08-14 10:23:20 CEST

@coling,

Thanks for that. I had not seen this package listed as needing fixing up. Is this anything simple I can do? If it was on the mailinglist, a message ID on how / what to fix will hopefully suffice for me to fix this (and perhaps lend a hand with other packages needing a fix). :-)

Comment 4 Colin Guthrie 2012-08-14 10:32:30 CEST

Should be fixed now (not tested just updated and submitted so please let me know). Feel free to check the commit. It's basically a matter of adding a tmpfiles.d file which ensures folders etc. are correctly created on fresh boot.

Some suggested improvements: 
 1. Make spamd socket activated such that it can be started automatically when something needs it (assuming this is supported internally - might need some modifications to accept the socket - worth checking fedora).
 2. Why is spamd run as root? Seems like a bad idea to me. We should run it as a less privileged user.

Comment 5 Remco Rijnders 2012-08-14 21:28:07 CEST

Thanks Colin, fix confirmed. I'll look at your suggestions later. As for #2, I guess this is because it wants to bind to port 783 (privileged port) by default.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED