Your message dated Sat, 22 Sep 2018 19:24:04 +0200
with message-id <[email protected]>
and subject line Re: bind(): Permission denied [core/socket.c line 185]
has caused the Debian Bug report #729523,
regarding bind(): Permission denied [core/socket.c line 185]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
729523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729523
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: uwsgi
Version: 1.9.17.1-5
Severity: important
Dear Maintainer,
When trying to start uwsgi with /etc/init.d/uwsgi start
it fails and gives the error
bind(): Permission denied [core/socket.c line 185]
This can be fixed by adding
chown-socket = www-data
to /usr/share/uwsgi/conf/default.ini
The socket owner can be specified in other places, but it seems it should
have a default.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages uwsgi depends on:
ii initscripts 2.88dsf-43
ii lsb-base 4.1+Debian12
ii uwsgi-core 1.9.17.1-5
Versions of packages uwsgi recommends:
ii sqlite3 3.8.1-1
uwsgi suggests no packages.
-- Configuration Files:
/etc/uwsgi/apps-available/README [Errno 2] No such file or directory:
u'/etc/uwsgi/apps-available/README'
/etc/uwsgi/apps-enabled/README [Errno 2] No such file or directory:
u'/etc/uwsgi/apps-enabled/README'
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.0.15-11
Hi,
This bug is believed fixed by correctly double-escaping (which for grep
has same effect as using extended regexp syntax, but not e.g. for sed).
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
--- End Message ---