Bug#894855: [Pkg-mailman-hackers] Bug#894855: Bug#894855: Bug#894855: bind(): No such file or directory [core/socket.c line 230]
Le vendredi 06 avril 2018 à 13:19:31+0200, Pierre-Elliott Bécue a écrit : > Le vendredi 06 avril 2018 à 12:34:44+0200, Pierre-Elliott Bécue a écrit : > > Hi, > > > > Thanks for submitting this bug. > > > > Le mercredi 04 avril 2018 à 14:51:21-0700, Purism Sysadmins a écrit : > > > Package: mailman3-web > > > Version: 0+20170523-13~bpo9+1 > > > Severity: important > > > > > > Dear Maintainer, > > > > > > When I tried to install mailman3-full I got this: > > > > > > ``` > > > Apr 04 12:36:10 lists systemd[1]: mailman3-web.service: Main process > > > exited, code=exited, status=1/FAILURE > > > Apr 04 12:36:10 lists systemd[1]: Failed to start Mailman3-web uWSGI > > > service. > > > Apr 04 12:36:10 lists systemd[1]: mailman3-web.service: Unit entered > > > failed state. > > > Apr 04 12:36:10 lists systemd[1]: mailman3-web.service: Failed with > > > result 'exit-code'. > > > dpkg: error processing package mailman3-web (--configure): > > > subprocess installed post-installation script returned error exit status > > > 1 > > > dpkg: dependency problems prevent configuration of mailman3-full: > > > mailman3-full depends on mailman3-web; however: > > > Package mailman3-web is not configured yet. > > > > > > dpkg: error processing package mailman3-full (--configure): > > > dependency problems - leaving unconfigured > > > Processing triggers for libc-bin (2.24-11+deb9u3) ... > > > Processing triggers for systemd (232-25+deb9u3) ... > > > Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.5-2+deb9u2) ... > > > Errors were encountered while processing: > > > mailman3-web > > > mailman3-full > > > E: Sub-process /usr/bin/dpkg returned an error code (1) > > > W: Operation was interrupted before it could finish > > > ``` > > > > > > Checking in the logs (/var/log/mailman3/web/mailman-web.log) I got this: > > > > > > ``` > > > *** Starting uWSGI 2.0.14-debian (64bit) on [Wed Apr 4 12:36:10 2018] *** > > > compiled with version: 6.3.0 20170516 on 17 March 2018 15:41:47 > > > os: Linux-4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) > > > nodename: announcements > > > machine: x86_64 > > > clock source: unix > > > pcre jit disabled > > > detected number of CPU cores: 1 > > > current working directory: / > > > detected binary path: /usr/bin/uwsgi-core > > > setgid() to 33 > > > setuid() to 33 > > > chdir() to /usr/share/mailman3-web > > > your processes number limit is 7931 > > > your memory page size is 4096 bytes > > > detected max file descriptor number: 1024 > > > lock engine: pthread robust mutexes > > > thunder lock: disabled (you can enable it with --thunder-lock) > > > bind(): No such file or directory [core/socket.c line 230] > > > ``` > > > > > > My workaround was this: > > > > > > ``` > > > mkdir /run/mailman3/web/ > > > chown www-data:www-data /run/mailman3/web/ > > > ``` > > > > Well, this one is reccurrent. > > > > I really understood that the presence of > > /usr/lib/tmpfiles.d/mailman3-web.conf is supposed to be enough for systemd > > users. > > > > I'll work on it (mostly, ask for advice) and we'll try to find a definitive > > solution. > > Thanks to wRAR (Andrey Rahmatullin), I think I have a proper explaination. > > Apparently, this bug is most likely due to debhelper's snippets integration > in postinst/prerm scripts. It has been reported in[1,2] and fixed in > debhelper 11.1[3], but dh 11.1.X entered the backports only recently[4] > > Until we rebuild/upload the packages again, there's most likely nothing we > can do. I'll discuss with Jonas about speeding up the next upload in order > to have proper postinst/prerm files. > > [1] https://bugs.debian.org/814285 > [2] https://bugs.debian.org/885998 > [3] > https://salsa.debian.org/debian/debhelper/blob/648c357c09d109f8b802fe3dd1091b734aa45271/debian/changelog#L64 > [4] > https://tracker.debian.org/news/945655/accepted-debhelper-1116bpo91-source-into-stretch-backports/ I'm currently uploading a new release of -suite into unstable. As soon as it's in the archive, I'll make a proper backport that will close this bug. Cheers, -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for one's principles than to live up to them. signature.asc Description: PGP signature
Bug#894855: [Pkg-mailman-hackers] Bug#894855: Bug#894855: bind(): No such file or directory [core/socket.c line 230]
Le vendredi 06 avril 2018 à 12:34:44+0200, Pierre-Elliott Bécue a écrit : > Hi, > > Thanks for submitting this bug. > > Le mercredi 04 avril 2018 à 14:51:21-0700, Purism Sysadmins a écrit : > > Package: mailman3-web > > Version: 0+20170523-13~bpo9+1 > > Severity: important > > > > Dear Maintainer, > > > > When I tried to install mailman3-full I got this: > > > > ``` > > Apr 04 12:36:10 lists systemd[1]: mailman3-web.service: Main process > > exited, code=exited, status=1/FAILURE > > Apr 04 12:36:10 lists systemd[1]: Failed to start Mailman3-web uWSGI > > service. > > Apr 04 12:36:10 lists systemd[1]: mailman3-web.service: Unit entered failed > > state. > > Apr 04 12:36:10 lists systemd[1]: mailman3-web.service: Failed with result > > 'exit-code'. > > dpkg: error processing package mailman3-web (--configure): > > subprocess installed post-installation script returned error exit status 1 > > dpkg: dependency problems prevent configuration of mailman3-full: > > mailman3-full depends on mailman3-web; however: > > Package mailman3-web is not configured yet. > > > > dpkg: error processing package mailman3-full (--configure): > > dependency problems - leaving unconfigured > > Processing triggers for libc-bin (2.24-11+deb9u3) ... > > Processing triggers for systemd (232-25+deb9u3) ... > > Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.5-2+deb9u2) ... > > Errors were encountered while processing: > > mailman3-web > > mailman3-full > > E: Sub-process /usr/bin/dpkg returned an error code (1) > > W: Operation was interrupted before it could finish > > ``` > > > > Checking in the logs (/var/log/mailman3/web/mailman-web.log) I got this: > > > > ``` > > *** Starting uWSGI 2.0.14-debian (64bit) on [Wed Apr 4 12:36:10 2018] *** > > compiled with version: 6.3.0 20170516 on 17 March 2018 15:41:47 > > os: Linux-4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) > > nodename: announcements > > machine: x86_64 > > clock source: unix > > pcre jit disabled > > detected number of CPU cores: 1 > > current working directory: / > > detected binary path: /usr/bin/uwsgi-core > > setgid() to 33 > > setuid() to 33 > > chdir() to /usr/share/mailman3-web > > your processes number limit is 7931 > > your memory page size is 4096 bytes > > detected max file descriptor number: 1024 > > lock engine: pthread robust mutexes > > thunder lock: disabled (you can enable it with --thunder-lock) > > bind(): No such file or directory [core/socket.c line 230] > > ``` > > > > My workaround was this: > > > > ``` > > mkdir /run/mailman3/web/ > > chown www-data:www-data /run/mailman3/web/ > > ``` > > Well, this one is reccurrent. > > I really understood that the presence of > /usr/lib/tmpfiles.d/mailman3-web.conf is supposed to be enough for systemd > users. > > I'll work on it (mostly, ask for advice) and we'll try to find a definitive > solution. Thanks to wRAR (Andrey Rahmatullin), I think I have a proper explaination. Apparently, this bug is most likely due to debhelper's snippets integration in postinst/prerm scripts. It has been reported in[1,2] and fixed in debhelper 11.1[3], but dh 11.1.X entered the backports only recently[4] Until we rebuild/upload the packages again, there's most likely nothing we can do. I'll discuss with Jonas about speeding up the next upload in order to have proper postinst/prerm files. [1] https://bugs.debian.org/814285 [2] https://bugs.debian.org/885998 [3] https://salsa.debian.org/debian/debhelper/blob/648c357c09d109f8b802fe3dd1091b734aa45271/debian/changelog#L64 [4] https://tracker.debian.org/news/945655/accepted-debhelper-1116bpo91-source-into-stretch-backports/ -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for one's principles than to live up to them.
Bug#894855: [Pkg-mailman-hackers] Bug#894855: bind(): No such file or directory [core/socket.c line 230]
Hi, Thanks for submitting this bug. Le mercredi 04 avril 2018 à 14:51:21-0700, Purism Sysadmins a écrit : > Package: mailman3-web > Version: 0+20170523-13~bpo9+1 > Severity: important > > Dear Maintainer, > > When I tried to install mailman3-full I got this: > > ``` > Apr 04 12:36:10 lists systemd[1]: mailman3-web.service: Main process exited, > code=exited, status=1/FAILURE > Apr 04 12:36:10 lists systemd[1]: Failed to start Mailman3-web uWSGI service. > Apr 04 12:36:10 lists systemd[1]: mailman3-web.service: Unit entered failed > state. > Apr 04 12:36:10 lists systemd[1]: mailman3-web.service: Failed with result > 'exit-code'. > dpkg: error processing package mailman3-web (--configure): > subprocess installed post-installation script returned error exit status 1 > dpkg: dependency problems prevent configuration of mailman3-full: > mailman3-full depends on mailman3-web; however: > Package mailman3-web is not configured yet. > > dpkg: error processing package mailman3-full (--configure): > dependency problems - leaving unconfigured > Processing triggers for libc-bin (2.24-11+deb9u3) ... > Processing triggers for systemd (232-25+deb9u3) ... > Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.5-2+deb9u2) ... > Errors were encountered while processing: > mailman3-web > mailman3-full > E: Sub-process /usr/bin/dpkg returned an error code (1) > W: Operation was interrupted before it could finish > ``` > > Checking in the logs (/var/log/mailman3/web/mailman-web.log) I got this: > > ``` > *** Starting uWSGI 2.0.14-debian (64bit) on [Wed Apr 4 12:36:10 2018] *** > compiled with version: 6.3.0 20170516 on 17 March 2018 15:41:47 > os: Linux-4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) > nodename: announcements > machine: x86_64 > clock source: unix > pcre jit disabled > detected number of CPU cores: 1 > current working directory: / > detected binary path: /usr/bin/uwsgi-core > setgid() to 33 > setuid() to 33 > chdir() to /usr/share/mailman3-web > your processes number limit is 7931 > your memory page size is 4096 bytes > detected max file descriptor number: 1024 > lock engine: pthread robust mutexes > thunder lock: disabled (you can enable it with --thunder-lock) > bind(): No such file or directory [core/socket.c line 230] > ``` > > My workaround was this: > > ``` > mkdir /run/mailman3/web/ > chown www-data:www-data /run/mailman3/web/ > ``` Well, this one is reccurrent. I really understood that the presence of /usr/lib/tmpfiles.d/mailman3-web.conf is supposed to be enough for systemd users. I'll work on it (mostly, ask for advice) and we'll try to find a definitive solution. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for one's principles than to live up to them.
Bug#894855: bind(): No such file or directory [core/socket.c line 230]
Package: mailman3-web Version: 0+20170523-13~bpo9+1 Severity: important Dear Maintainer, When I tried to install mailman3-full I got this: ``` Apr 04 12:36:10 lists systemd[1]: mailman3-web.service: Main process exited, code=exited, status=1/FAILURE Apr 04 12:36:10 lists systemd[1]: Failed to start Mailman3-web uWSGI service. Apr 04 12:36:10 lists systemd[1]: mailman3-web.service: Unit entered failed state. Apr 04 12:36:10 lists systemd[1]: mailman3-web.service: Failed with result 'exit-code'. dpkg: error processing package mailman3-web (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of mailman3-full: mailman3-full depends on mailman3-web; however: Package mailman3-web is not configured yet. dpkg: error processing package mailman3-full (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.24-11+deb9u3) ... Processing triggers for systemd (232-25+deb9u3) ... Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.5-2+deb9u2) ... Errors were encountered while processing: mailman3-web mailman3-full E: Sub-process /usr/bin/dpkg returned an error code (1) W: Operation was interrupted before it could finish ``` Checking in the logs (/var/log/mailman3/web/mailman-web.log) I got this: ``` *** Starting uWSGI 2.0.14-debian (64bit) on [Wed Apr 4 12:36:10 2018] *** compiled with version: 6.3.0 20170516 on 17 March 2018 15:41:47 os: Linux-4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) nodename: announcements machine: x86_64 clock source: unix pcre jit disabled detected number of CPU cores: 1 current working directory: / detected binary path: /usr/bin/uwsgi-core setgid() to 33 setuid() to 33 chdir() to /usr/share/mailman3-web your processes number limit is 7931 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) bind(): No such file or directory [core/socket.c line 230] ``` My workaround was this: ``` mkdir /run/mailman3/web/ chown www-data:www-data /run/mailman3/web/ ``` Regards, Theodotos Andreou Purism Sysadmin -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mailman3-web depends on: ii dbconfig-sqlite3 2.0.9~bpo9+1 ii debconf [debconf-2.0] 1.5.61 ii lsb-base 9.20161125 ii node-less 1.6.3~dfsg-2 ii python2.7.13-2 ii python-django-hyperkitty 1.1.4-4~bpo9+2 ii python-django-postorius 1.1.2-3~bpo9+2 ii python-psycopg2 2.6.2-1 ii python-whoosh 2.7.0-2 ii ruby-sass 3.4.23-1 ii ucf 3.0036 ii uwsgi 2.0.14+20161117-3+deb9u2 ii uwsgi-plugin-python 2.0.14+20161117-3+deb9u2 Versions of packages mailman3-web recommends: ii libapache2-mod-proxy-uwsgi 2.0.14+20161117-3+deb9u2 Versions of packages mailman3-web suggests: pn postgresql | default-mysql-server | virtual-mysql-server -- debconf information: mailman3-web/superuser-password: (password omitted) mailman3-web/app-password-confirm: (password omitted) mailman3-web/password-confirm: (password omitted) mailman3-web/internal/skip-preseed: false mailman3-web/purge: false mailman3-web/upgrade-error: abort mailman3-web/db/dbname: mailman3web.db mailman3-web/emailname: localhost.local mailman3-web/django-site: lists.example.com mailman3-web/install-error: abort mailman3-web/superuser-name: admin mailman3-web/passwords-do-not-match: * mailman3-web/database-type: sqlite3 mailman3-web/superuser-mail: root@localhost mailman3-web/dbconfig-remove: true mailman3-web/internal/reconfiguring: false mailman3-web/configure-webserver: none mailman3-web/db/basepath: /var/lib/mailman3/web * mailman3-web/dbconfig-install: true mailman3-web/restart-webserver: true mailman3-web/remove-error: abort mailman3-web/dbconfig-upgrade: true mailman3-web/nginx-choice: mailman3-web/missing-db-package-error: abort mailman3-web/upgrade-backup: true mailman3-web/dbconfig-reinstall: false
