Bug 1772303 - uwsgi service fails to start after install
Summary: uwsgi service fails to start after install
Keywords:
Status: CLOSED DUPLICATE of bug 1687403
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: uwsgi
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jorge Gallegos
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-14 04:08 UTC by Jon Dufresne
Modified: 2019-11-14 04:10 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-11-14 04:10:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jon Dufresne 2019-11-14 04:08:23 UTC
Description of problem:

After installing uwsgi, the default systemd configuration fails to start.


Version-Release number of selected component (if applicable):

uwsgi-2.0.17.1-2.el7.x86_64


How reproducible:

100%


Steps to Reproduce:
1. yum install uwsgi
2. systemctl start uwsgi


Actual results:

uwsgi.service is in a failed state.

The logs in /var/log/messages show:

[uWSGI] getting INI configuration from /etc/uwsgi.ini
setting capability setgid [6]
setting capability setuid [7]
*** Starting uWSGI 2.0.17.1 (64bit) on [Wed Nov 13 23:00:08 2019] ***
compiled with version: 4.8.5 20150623 (Red Hat 4.8.5-36) on 08 March 2019 03:58:40
os: Linux-3.10.0-957.12.2.el7.x86_64 #1 SMP Tue May 14 21:24:32 UTC 2019
nodename: web
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 1
current working directory: /
writing pidfile to /run/uwsgi/uwsgi.pid
open("/run/uwsgi/uwsgi.pid"): No such file or directory [core/utils.c line 3613]



Expected results:

uwsgi.service starts no problem.


Additional info:

The directory /run/uwsgi does not exist. Perhaps it should be created with the systemd RuntimeDirectory= features.

https://www.freedesktop.org/software/systemd/man/systemd.exec.html#RuntimeDirectory=

Comment 1 Jon Dufresne 2019-11-14 04:10:25 UTC

*** This bug has been marked as a duplicate of bug 1687403 ***


Note You need to log in before you can comment on or make changes to this bug.