Hide Forgot
Description of problem: sympa-httpd's wwsympa is failed to start because it contains -u nginx option. Use nginx doesn't exist Version-Release number of selected component (if applicable): sympa-httpd-6.2.56-1.fc32.x86_64 How reproducible: 100% Steps to Reproduce: 1. install sympa-httpd and start wwsympa Actual results: Jun 11 10:52:14 sympa.example.com systemd[1]: Starting WWSympa - Web interface for Sympa mailing list manager... Jun 11 10:52:14 sympa.example.com spawn-fcgi[24144]: spawn-fcgi: can't find user name nginx Expected results: Additional info: ]# systemctl cat wwsympa.service # /usr/lib/systemd/system/wwsympa.service [Unit] Description=WWSympa - Web interface for Sympa mailing list manager After=syslog.target sympa.service [Service] Type=forking PIDFile=/run/sympa/wwsympa.pid ExecStart=/usr/bin/spawn-fcgi -F $FCGI_CHILDREN \ -P /run/sympa/wwsympa.pid \ -s /run/sympa/wwsympa.socket \ -u $FCGI_USER -g $FCGI_GROUP $FCGI_OPTS -- \ /usr/libexec/sympa/wwsympa.fcgi Environment="FCGI_CHILDREN=5" Environment="FCGI_USER=sympa" Environment="FCGI_GROUP=sympa" Environment="FCGI_OPTS=-M 0600 -U nginx" <<<< HERE EnvironmentFile=-/etc/sysconfig/sympa Restart=always [Install] WantedBy=multi-user.target
This needs to be configured in /etc/sysconfig/sympa, as hinted by the "EnvironmentFile=-/etc/sysconfig/sympa" just below the one you pointed out.
Just a note, I'm working to get rid off of spawn-fcgi in favor of systemd managed sockets. This will make this work out of the box, without that tweak.
(In reply to Xavier Bachelot from comment #1) > This needs to be configured in /etc/sysconfig/sympa, as hinted by the > "EnvironmentFile=-/etc/sysconfig/sympa" just below the one you pointed out. I see. Thank you. However nginx user should not be mentioned in -httpd package.
nginx user is not mentioned in -httpd package. The unit file is from the main package.
(In reply to Xavier Bachelot from comment #4) > nginx user is not mentioned in -httpd package. > The unit file is from the main package. rpm doesn't think so :) [root@localhost sympa]# rpm -ql sympa-httpd /etc/httpd/conf.d/sympa.conf /usr/lib/systemd/system/sympasoap.service /usr/lib/systemd/system/wwsympa.service << !!!! [root@localhost sympa]# rpm -qf /usr/lib/systemd/system/wwsympa.service sympa-httpd-6.2.56-1.fc32.x86_64 [root@localhost sympa]# cat /usr/lib/systemd/system/wwsympa.service [Unit] Description=WWSympa - Web interface for Sympa mailing list manager After=syslog.target sympa.service [Service] Type=forking PIDFile=/run/sympa/wwsympa.pid ExecStart=/usr/bin/spawn-fcgi -F $FCGI_CHILDREN \ -P /run/sympa/wwsympa.pid \ -s /run/sympa/wwsympa.socket \ -u $FCGI_USER -g $FCGI_GROUP $FCGI_OPTS -- \ /usr/libexec/sympa/wwsympa.fcgi Environment="FCGI_CHILDREN=5" Environment="FCGI_USER=sympa" Environment="FCGI_GROUP=sympa" Environment="FCGI_OPTS=-M 0600 -U nginx" EnvironmentFile=-/etc/sysconfig/sympa Restart=always [Install] WantedBy=multi-user.target
Right you are, sorry :-) However, the same unit files for wwsympa and sympasoap are distributed in all of -nginx, -httpd, -lighttpd. I can't think of any other way to do this. Beside finishing up the work to make use of systemd sockets, which will replace the need to tweak /etc/sysconfig/sympa by an unit file override from the webserver sub-packages.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
FEDORA-2022-a243247a14 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a243247a14
FEDORA-EPEL-2022-70627a704c has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-70627a704c
FEDORA-2022-b9fb2e828a has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b9fb2e828a
FEDORA-2022-fdfd82227a has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-fdfd82227a
FEDORA-EPEL-2022-70627a704c has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-70627a704c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-a243247a14 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-a243247a14` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a243247a14 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-b9fb2e828a has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-b9fb2e828a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b9fb2e828a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-fdfd82227a has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-fdfd82227a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-fdfd82227a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-b9fb2e828a has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-a243247a14 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-fdfd82227a has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-70627a704c has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.