Working on a different bugreport, I ran into the following when installing spamassassin (current cauldron SVN, built on a mga4 box): [root@silvertown remmy (master)]# systemctl status httpd.service httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled) Active: failed (Result: exit-code) since zo 2014-08-17 15:30:32 CEST; 1h 15min ago Main PID: 16895 (code=exited, status=1/FAILURE) Status: "Total requests: 6482; Current requests/sec: 0; Current traffic: 0 B/sec" CGroup: /system.slice/httpd.service aug 17 15:30:32 silvertown.webconquest.com httpd[16895]: AH00526: Syntax error on line 21 of /etc/httpd/conf/sites.d/spamd.conf: aug 17 15:30:32 silvertown.webconquest.com httpd[16895]: SADebug can't be used in vhost, see bug #4963\n aug 17 15:30:32 silvertown.webconquest.com systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE aug 17 15:30:32 silvertown.webconquest.com systemd[1]: Failed to start The Apache HTTP Server. aug 17 15:30:32 silvertown.webconquest.com systemd[1]: Unit httpd.service entered failed state. I'm not yet sure if this is the result of a local configuration change I made, or if this is an issue affecting other users.
Works here. I just installed spamassassin-spamd-3.3.2-21.mga4.x86_64.rpm and started it. Here is my output: # systemctl status httpd.service httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled) Active: active (running) since Sun 2014-08-17 10:29:59 MST; 1s ago Process: 18345 ExecStop=/usr/bin/kill -WINCH ${MAINPID} (code=exited, status=0/SUCCESS) Main PID: 18352 (httpd) Status: "Processing requests..." CGroup: /system.slice/httpd.service ââ18352 /usr/sbin/httpd -DFOREGROUND ââ18353 /usr/sbin/nss_pcache 32769 off /etc/pki/nss/apache-mod_nss ââ18356 /usr/sbin/httpd -DFOREGROUND ââ18358 /usr/sbin/httpd -DFOREGROUND ââ18359 /usr/sbin/httpd -DFOREGROUND ââ18360 /usr/sbin/httpd -DFOREGROUND ââ18361 /usr/sbin/httpd -DFOREGROUND Aug 17 10:29:59 aargau.btspuhler.com systemd[1]: Started The Apache HTTP Server. [root@aargau ~]# systemctl status spamd spamd.service - Spamassassin daemon Loaded: loaded (/usr/lib/systemd/system/spamd.service; enabled) Active: active (running) since Sun 2014-08-17 10:29:22 MST; 46s ago Process: 18311 ExecStart=/usr/bin/spamd --pidfile /run/spamd.pid $SPAMDOPTIONS (code=exited, status=0/SUCCESS) Main PID: 18313 (/usr/bin/spamd ) CGroup: /system.slice/spamd.service ââ18313 /usr/bin/spamd --pidfile /run/spamd.pid -d -c -m5 -H --syslog=/var/log/spamassassin/spamd.log --socketpath=/run/spamd/... ââ18317 spamd child ââ18318 spamd child Aug 17 10:29:22 aargau.btspuhler.com systemd[1]: Started Spamassassin daemon. But also: # less /etc/httpd/conf/sites.d/spamd.conf /etc/httpd/conf/sites.d/spamd.conf: No such file or directory Maybe your config file is wrong?
Whiteboard: (none) => Need more info
CC: guillomovitch => (none)
Assignee: bugsquad => remco
Keywords: (none) => NEEDINFOWhiteboard: Need more info => (none)
Probably a local config issue.
Status: NEW => RESOLVEDResolution: (none) => INVALID
Reopened (and assigned to self). The problem is specifically in the perl-Mail-SpamAssassin-Spamd-3.3.2-21.mga4 package. I haven't tested on current Cauldron yet which has 3.4.0.
Status: RESOLVED => REOPENEDVersion: Cauldron => 4Resolution: INVALID => (none)Source RPM: (none) => perl-Mail-SpamAssassin-Spamd-3.3.2-21.mga4.x86_64.rpm
Remco: I just checkde this again. all is fine here. You must have something wrong in your config. See attachment Again, I do not have a /etc/httpd/conf/sites.d/spamd.conf file No spamd.conf at all. Same on current cauldron. BTW, what are you using spamd for? I think there is hardly any app that require or use it?
Created attachment 6644 [details] start of spamd/httpd
I get the problem when installing perl-Mail-SpamAssassin-Spamd-3.3.2 I'll have a look.
Hi Thomas, Thanks for looking into this / helping with this. Commenting out the offending lines from spamd.conf, I run into a different problem which I've reported upstream. See https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7197 for this. I am a bit puzzled by upstream's reply that this (second problem) should only be possible with mod_perl 2.0.9 in combination with apache 2.4 while we have 2.0.7. As listed maintainer for spamassassin, I had this package installed locally. I myself don't have an actual use case for it and thus can do without, but think the package should ideally be fixed. As no one else stumbled onto this bug, I think real world use of this package is very limited indeed.
Keywords: NEEDINFO => (none)URL: (none) => https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7197
Remco: Since you just run into this by accident, I suggest to make this package obsolete. I don't see Fedora providing it. Maybe nobody ever used it. I don't really see how it's being used.
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Why don't we make perl-Mail-SpamAssassin-Spamd Obsolete as proposed. I would know why we need it. As far as ( can see, there is no dependency problem The maintainer is mgarepo maintdb get spamassassin remmy
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: REOPENED => RESOLVEDResolution: (none) => OLD