Bug#1037264: cksum crashes intermittently with "Illegal instruction" on some Xen DomU
Hi! I have this issue with cron-apt: 8< /etc/cron.daily/apt-compat: Illegal instruction R: /etc/cron.daily/apt-compat: 44: arithmetic expression: expecting primary: " % 32767 " run-parts: /etc/cron.daily/apt-compat exited with return code 2 >8 A change in the config file of the domU did solve this problem (not really a solution to the problem but maybe a useful hint): old domU.cfg: kernel = '/usr/lib/grub-xen/grub-x86_64-xen.bin' extra = 'elevator=noop' new domU.cfg: type= 'pvh' kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin' extra = 'elevator=noop' And i get a different output from `cpuid -1` for these configs. Markus
Bug#1032868: sendxmpp: Stopped working after dist-upgrade to bookworm
same issue here after upgrade bullseye -> bookworm Debian bookworm My XMPP-server is running ejabberd 23.01-1~bpo11+1 echo 'test' | sendxmpp -t -a /etc/ssl/certs/ -u -j -p -s "test1" gives same output as OP posted. from apt history: 2023-04-04 dist-upgrade libnet-xmpp-perl:amd64 (1.05-1, 1.05-1.1) libxml2:amd64 (2.9.4+dfsg1-7+deb10u5, 2.9.10+dfsg-6.7+deb11u3) 2023-04-10 15:07:07 libnet-xmpp-perl:amd64 (1.05-1.1, 1.05-2) 2023-04-24 libxml2:amd64 (2.9.14+dfsg-1.1+b3, 2.9.14+dfsg-1.2) markus
Bug#1028638: Bug#1028413: gajim 1.6.1-2 crash
On Thu, 2023-01-26 at 14:36 +0100, Martin wrote: > could you please try out, if the problem is fixed with a patched > libproxy? > > $ echo deb https://deb.debian.org/debian/ experimental main \ > | sudo tee /etc/apt/sources.list.d/experimental.list > $ sudo apt update > $ sudo apt install -t experimental libproxy1v5 thx! yes. this solves the problem (tested on one of my laptops).
Bug#1028413: gajim 1.6.1-2 crash
Hi! I see the same on Debian testing with latest updates (2023-01-26) gajim 1.6.1-2 python3-nbxmpp 4.1.0-1
Bug#1017944: Another reproduction of #1017944
On Sun, 11 Sep 2022 15:55:00 -0700 Elliott Mitchell wrote: > ... another > potential workaround is to add: > > deb https://snapshot.debian.org/archive/debian/20220801T032804Z/ bullseye main > > To /etc/apt/sources.list, then *hold* the GRUB packages at 2.04-20. A more recent version (grub-xen-bin 2.06-3~deb10u1) which works is in buster: deb http://debian.anexia.at/debian/ buster contrib non-free main
Bug#933972: policyd-weight: using IPv6 broken in buster
Package: policyd-weight Version: 0.1.15.2-12 After dist-upgrade from stretch to buster: # service policyd-weight restart [] Restarting policyd-weight configuration (incl. cache): policyd- weightCan't locate object method "new" via package "IO::Socket::INET6" (perhaps you forgot to load "IO::Socket::INET6"?) at /usr/sbin/policyd- weight line 921. failed! Solution: File /usr/sbin/policyd-weight is not loading the module IO::Socket::INET6. around line 72 following should be inserted: use IO::Socket::INET6; Maybe th Markus
Bug#891937: [Pkg-mailman-hackers] Bug#891937: Bug#891937: mailman3-full install issues
On Thu, 2018-10-18 at 13:20 +0200, Pierre-Elliott Bécue wrote: > Le jeudi 18 octobre 2018 à 12:54:20+0200, Markus Gschwendt a écrit : > > On Thu, 2018-10-18 at 11:02 +0200, Pierre-Elliott Bécue wrote: > > > Le mardi 16 octobre 2018 à 14:39:38+0200, Markus Gschwendt a écrit : > > > > > > > > ... > > > What is a "huge memory footprint" when translated to numbers? > > > > I would say for a VM only running the list software with a few not too > > busy lists and exim light 128MB should sufficient. > > With a mailman-web-gui _not_ more than 250-500MB. > > You misunderstood my question. Sorry. You are right. I did not understand it that way. > How much RAM, according to your friend, does mailman3 use on his system? 700MB only for mailman3 See the Post of him (mailman-users list, Thursday, 13 September 2018 2:05 p.m.) https://lists.mailman3.org/archives/list/mailman-us...@mailman3.org/thr ead/5LZNBMEMYPZHW5XE7KMPUOAAECK3KP6D/ I had a short chat with him yesterday. He didn't answer the comment of Mark Sapiro because of lack of time at the moment. But in short: There is not such a thing like 'idle memory'. It is RSS, not virtual memory. And mailman3 releases the memory not before exiting. Myself i was not able to run exim4-light +mailman3 +web-gui packages on a VM below ~1.8GB RAM. My production mailserver exim4-heavy +mailman2 +mailman-web-gui +dovecot +spamassassin +clamav is running on 3GB RAM, where most of the memory is used by clamav+sa. Only ~50MB by mailman2. Markus
Bug#891937: [Pkg-mailman-hackers] Bug#891937: Bug#891937: mailman3-full install issues
On Thu, 2018-10-18 at 11:02 +0200, Pierre-Elliott Bécue wrote: > Le mardi 16 octobre 2018 à 14:39:38+0200, Markus Gschwendt a écrit : > > ... > What is a "huge memory footprint" when translated to numbers? I would say for a VM only running the list software with a few not too busy lists and exim light 128MB should sufficient. With a mailman-web-gui _not_ more than 250-500MB. Markus
Bug#891937: [Pkg-mailman-hackers] Bug#891937: mailman3-full install issues
Hi Jonas! On Mon, 2018-10-08 at 00:43 +0200, Jonas Meurer wrote: > Yes. At least with mailman3 3.1.1-8 > > Sorry to poke you again. Can you still reproduce it with latest mailman3 > 3.2 packages from Debian unstable? Did you try to do a fresh > installation of mailman3 in the meantime? No, but i'm very busy at the moment. I will try in about a month. A friend (who is running several small mailman2 servers) tried to install mailman3 without the Web-GUI and was very disappointed about the huge memory footprint for a mailman with only one list and a few members and doing nothing. This would be a reason to move away from mailman. Markus
Bug#891937: [Pkg-mailman-hackers] Bug#891937: mailman3-full install issues
On Wed, 2018-04-18 at 12:06 +0200, Jonas Meurer wrote:
> do you still encounter this problem?
Yes. At least with mailman3 3.1.1-8
> I bet there's something wrong on
> your side. Mailman3 works fine with Exim4 and if you configured it
> correctly, it certainly doesn't run the Postfix postmap command.
It's an install of the mailman3-Debian-Sid packages. Nothing else is on
that machine.
exim4: 4.90.1-5
nginx-light: 1.13.12-1
mailman3: 3.1.1-9
I just did upgrade from 3.1.1-8 to 3.1.1-9 and get this on restarting
mailman:
service mailman3 stopTraceback (most recent call last):
File "/usr/lib/mailman3/bin/master", line 11, in
load_entry_point('mailman==3.1.1', 'console_scripts', 'master')()
File "/usr/lib/python3/dist-packages/mailman/bin/master.py", line
528, in main
with open(config.PID_FILE, 'w') as fp:
PermissionError: [Errno 13] Permission denied:
'/run/mailman3/master.pid'
> If you still encounter this problem, please paste the output of the
> following commands:
>
> # mailman info
mailman info
GNU Mailman 3.1.1 (Between The Wheels)
Python 3.6.5rc1 (default, Mar 22 2018, 10:45:39)
[GCC 7.3.0]
config file: /etc/mailman3/mailman.cfg
db url: sqlite:var/lib/mailman3/data/mailman.db
devmode: DISABLED
REST root url: http://localhost:8001/3.1/
REST credentials: restadmin:x
> # mailman conf | grep -F "[mta]"
[mta] configuration: python:mailman.config.exim4
[mta] delivery_retry_period: 5d
[mta] incoming: mailman.mta.exim4.LMTP
[mta] lmtp_host: 127.0.0.1
[mta] lmtp_port: 8024
[mta] max_autoresponses_per_day: 10
[mta] max_delivery_threads: 0
[mta] max_recipients: 500
[mta] max_sessions_per_connection: 0
[mta] outgoing: mailman.mta.deliver.deliver
[mta] remove_dkim_headers: no
[mta] smtp_host: localhost
[mta] smtp_pass:
[mta] smtp_port: 25
[mta] smtp_user:
[mta] verp_confirm_format: $address+$cookie
[mta] verp_confirm_regexp:
^(.*<)?(?P[^+]+?)\+(?P[^@]+)@.*$
[mta] verp_confirmations: no
[mta] verp_delimiter: +
[mta] verp_delivery_interval: 0
[mta] verp_format: ${bounces}+${local}=${domain}
[mta] verp_personalized_deliveries: no
[mta] verp_probe_format: $bounces+$token@$domain
[mta] verp_probe_regexp: ^(?P[^+]+?)\+(?P[^@]+)@.*$
[mta] verp_probes: no
[mta] verp_regexp:
^(?P[^+]+?)\+(?P[^=]+)=(?P[^@]+)@.*$
> # cat /etc/mailman3/mailman.cfg
# Copyright (C) 2008-2017 by the Free Software Foundation, Inc.
#
# This file is part of GNU Mailman.
#
# GNU Mailman is free software: you can redistribute it and/or modify
it under
# the terms of the GNU General Public License as published by the Free
# Software Foundation, either version 3 of the License, or (at your
option)
# any later version.
#
# GNU Mailman is distributed in the hope that it will be useful, but
WITHOUT
# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
# FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
for
# more details.
#
# You should have received a copy of the GNU General Public License
along with
# GNU Mailman. If not, see for details.
[mailman]
# This address is the "site owner" address. Certain messages which
must be
# delivered to a human, but which can't be delivered to a list owner
(e.g. a
# bounce from a list owner), will be sent to this address. It should
point to
# a human.
site_owner: x...@example.com
# This is the local-part of an email address used in the From field
whenever a
# message comes from some entity to which there is no natural reply
recipient.
# Mailman will append '@' and the host name of the list involved. This
# address must not bounce and it must not point to a Mailman process.
noreply_address: noreply
# The default language for this server.
default_language: en
# Membership tests for posting purposes are usually performed by
looking at a
# set of headers, passing the test if any of their values match a
member of
# the list. Headers are checked in the order given in this
variable. The
# value From_ means to use the envelope sender. Field names are case
# insensitive. This is a space separate list of headers.
sender_headers: from from_ reply-to sender
# Mail command processor will ignore mail command lines after
designated max.
email_commands_max_lines: 10
# Default length of time a pending request is live before it is evicted
from
# the pending database.
pending_request_life: 3d
# How long should files be saved before they are evicted from the
cache?
cache_life: 7d
# A callable to run with no arguments early in the initialization
process.
# This runs before database initialization.
pre_hook:
# A callable to run with no arguments late in the initialization
process.
# This runs after adapters are initialized.
post_hook:
# Which paths.* file system layout to use.
# You should not change this variab
Bug#891937: [Pkg-mailman-hackers] Bug#891937: mailman3-full install issues
On Thu, 2018-03-29 at 17:57 +0200, Jonas Meurer wrote: > > > ... > > File "/usr/lib/python2.7/smtplib.py", line 292, in _get_socket > > return socket.create_connection((host, port), timeout) > > > File "/usr/lib/python2.7/socket.py", line 575, in create_connection > > raise err > > error: [Errno 111] Connection refused > ... my fault. don't know why it worked from command line. exim could not bind to an unconfigured IPv6 address. but again the postfix issue on an exim install during adding a list: RuntimeError: command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_lmtp, 127, Key has expired command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_domains, 127, Key has expired Mar 29 16:11:38 2018 (8096) 127.0.0.1 - - "POST /3.0/lists HTTP/1.1" 500 59 Mar 29 16:12:02 2018 (8096) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 294 Mar 29 16:12:02 2018 (8096) 127.0.0.1 - - "GET /3.0/domains/mm3a.runout.at HTTP/1.1" 200 189 Mar 29 16:12:02 2018 (8096) 127.0.0.1 - - "GET /3.0/domains/mm3a.runout.at HTTP/1.1" 200 189 Mar 29 16:12:02 2018 (8096) 127.0.0.1 - - "GET /3.0/domains/mm3a.runout.at HTTP/1.1" 200 189 Mar 29 16:12:02 2018 (8096) command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_lmtp, 127, Key has expired Mar 29 16:12:02 2018 (8096) command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_domains, 127, Key has expired Mar 29 16:12:02 2018 (8096) REST request handler error: Traceback (most recent call last): File "/usr/lib/python3.6/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python3/dist- packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ File "falcon/api.py", line 189, in falcon.api.API.__call__ File "/usr/lib/python3/dist-packages/mailman/rest/lists.py", line 245, in on_post mlist = create_list(**validator(request)) File "/usr/lib/python3/dist-packages/mailman/app/lifecycle.py", line 100, in create_list call_name(config.mta.incoming).create(mlist) File "/usr/lib/python3/dist-packages/mailman/mta/postfix.py", line 66, in create self.regenerate() File "/usr/lib/python3/dist-packages/mailman/mta/postfix.py", line 103, in regenerate raise RuntimeError(NL.join(errors)) RuntimeError: command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_lmtp, 127, Key has expired command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_domains, 127, Key has expired Mar 29 16:12:02 2018 (8096) 127.0.0.1 - - "POST /3.0/lists HTTP/1.1" 500 59
Bug#891937: [Pkg-mailman-hackers] Bug#891937: mailman3-full install issues
Maybe this bug should be renamed to something more generic. I don't want to open a new bug for everything i run into on debugging the install process until it's stable. I just tried again with the latest sid repo. Mail/SMTP from commandline does work (eg `mail -v -s test root`) 8< [mta] incoming: mailman.mta.exim4.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: localhost smtp_port: 25 smtp_user: smtp_pass: lmtp_host: 127.0.0.1 lmtp_port: 8024 configuration: python:mailman.config.exim4 >8 Now i get until the WebUI-Login page. After entering User/PW i get following in /var/log/mailman3/web/mailman.log: 8< ERROR 2018-03-29 15:13:29,516 12710 django.request Internal Server Error: /accounts/login/ Traceback (most recent call last): File "/usr/lib/python2.7/dist- packages/django/core/handlers/exception.py", line 41, in inner response = get_response(request) File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py", line 187, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python2.7/dist-packages/django/views/generic/base.py", line 68, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/django/utils/decorators.py", line 67, in _wrapper return bound_func(*args, **kwargs) File "/usr/lib/python2.7/dist- packages/django/views/decorators/debug.py", line 76, in sensitive_post_parameters_wrapper return view(request, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/django/utils/decorators.py", line 63, in bound_func return func.__get__(self, type(self))(*args2, **kwargs2) File "/usr/lib/python2.7/dist-packages/allauth/account/views.py", line 137, in dispatch return super(LoginView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/allauth/account/views.py", line 80, in dispatch **kwargs) File "/usr/lib/python2.7/dist-packages/django/views/generic/base.py", line 88, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/allauth/account/views.py", line 103, in post response = self.form_valid(form) File "/usr/lib/python2.7/dist-packages/allauth/account/views.py", line 150, in form_valid return form.login(self.request, redirect_url=success_url) File "/usr/lib/python2.7/dist-packages/allauth/account/forms.py", line 197, in login redirect_url=redirect_url) File "/usr/lib/python2.7/dist-packages/allauth/account/utils.py", line 146, in perform_login send_email_confirmation(request, user, signup=signup) File "/usr/lib/python2.7/dist-packages/allauth/account/utils.py", line 314, in send_email_confirmation signup=signup) File "/usr/lib/python2.7/dist-packages/allauth/account/models.py", line 60, in send_confirmation confirmation.send(request, signup=signup) File "/usr/lib/python2.7/dist-packages/allauth/account/models.py", line 166, in send get_adapter(request).send_confirmation_mail(request, self, signup) File "/usr/lib/python2.7/dist-packages/allauth/account/adapter.py", line 444, in send_confirmation_mail ctx) File "/usr/lib/python2.7/dist-packages/allauth/account/adapter.py", line 137, in send_mail msg.send() File "/usr/lib/python2.7/dist-packages/django/core/mail/message.py", line 348, in send return self.get_connection(fail_silently).send_messages([self]) File "/usr/lib/python2.7/dist- packages/django/core/mail/backends/smtp.py", line 104, in send_messages new_conn_created = self.open() File "/usr/lib/python2.7/dist- packages/django/core/mail/backends/smtp.py", line 64, in open self.connection = self.connection_class(self.host, self.port, **connection_params) File "/usr/lib/python2.7/smtplib.py", line 256, in __init__ (code, msg) = self.connect(host, port) File "/usr/lib/python2.7/smtplib.py", line 317, in connect self.sock = self._get_socket(host, port, self.timeout) File "/usr/lib/python2.7/smtplib.py", line 292, in _get_socket return socket.create_connection((host, port), timeout) File "/usr/lib/python2.7/socket.py", line 575, in create_connection raise err error: [Errno 111] Connection refused ERROR 2018-03-29 15:13:29,516 12710 django.request Internal Server Error: /accounts/login/ Traceback (most recent call last): File "/usr/lib/python2.7/dist- packages/django/core/handlers/exception.py", line 41, in inner response = get_response(request) File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/usr/lib/python2.7/dist-packages/django/core/hand
Bug#891937: [Pkg-mailman-hackers] Bug#891937: mailman3-suite: Hyperkitty tries to connect postgres on system using sqlite
Sorry for the late Answer. I had lots of work last week.
I tried again but got stuck on restarting 'mailman-web'.
There is a '/var/run/mailman3/web/ directory which is empty and the log
reports a different directory for the pid file:
writing pidfile to /run/mailman3-web/mailman3-web.pid
open("/run/mailman3-web/mailman3-web.pid"): No such file or directory
[core/utils.c line 3590]
Markus
Bug#891881: [Pkg-mailman-hackers] Bug#891881: mailman3-suite: On system using exim (no postfix install) the list create script tries to create postfix aliases
After further debugging and discussion i bring this back here because i think it is related to the debian packages. Summary: I figured out that a restart/stop-start of mailman3-suite and mailman3- core does not stop mailman. 'service mailman3-suite stop' kills only the uwsgi processes (not mailman) this is why the changed config is not active for the webUI after stop- start mailman in this way. a 'mailman stop' and 'mailman start' seems to work Details: https://gitlab.com/mailman/mailman/issues/455
Bug#892427: mailman3-suite: Wrong permission on /var/lib/mailman3/suite/static/CACHE
Package: mailman3 (sid) Version: 3.1.1 System: debian stretch The directory is created with ownership root:root Fix: chown www-data:www-data /var/lib/mailman3/suite/static/CACHE ii mailman3 0+20170523- 11all Full Mailman3 mailing list management suite (metapackage) ii mailman3-core3.1.1- 4 all Mailing list management system ii mailman3-suite 0+20170523- 11all Django project integrating Mailman3 Postorius and HyperKitty ii python-django-mailman3 1.1.0- 3 all Django library to help interaction with Mailman3 (Python 2 version) ii python-mailmanclient 3.1.1- 4 all Python bindings for Mailman3 REST API (Python 2 version) ii python3-mailman-hyperkitty 1.1.0- 1 all Mailman3 plugin to archive emails with HyperKitty
Bug#891937: mailman3-suite: Hyperkitty tries to connect postgres on system using sqlite
cat /etc/mailman3/mailman3-suite.py
# This file is imported by the Mailman Suite. It is used to override
# the default settings from /usr/share/mailman3-suite/settings.py.
# SECURITY WARNING: keep the secret key used in production secret!
SECRET_KEY = '5S/5OIURrBJcaoB3xFK+lorJ+Rnb1GdTN3jVx9RGwKJZkjDz'
ADMINS = (
('Mailman Suite Admin', 'root@localhost'),
)
# Hosts/domain names that are valid for this site; required if DEBUG is
False
# See https://docs.djangoproject.com/en/1.8/ref/settings/#allowed-hosts
# Set to '*' per default in the Deian package to allow all hostnames.
Mailman3
# is meant to run behind a webserver reverse proxy anyway.
ALLOWED_HOSTS = [
#"localhost", # Archiving API from Mailman, keep it.
# "lists.your-domain.org",
# Add here all production URLs you may have.
'*'
]
# Mailman API credentials
MAILMAN_REST_API_URL = 'http://localhost:8001'
MAILMAN_REST_API_USER = 'restadmin'
MAILMAN_REST_API_PASS = 'x'
MAILMAN_ARCHIVER_KEY = 'x'
MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1')
# Application definition
INSTALLED_APPS = (
'hyperkitty',
'postorius',
'django_mailman3',
# Uncomment the next line to enable the admin:
'django.contrib.admin',
# Uncomment the next line to enable admin documentation:
# 'django.contrib.admindocs',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.sites',
'django.contrib.messages',
'django.contrib.staticfiles',
'rest_framework',
'django_gravatar',
'paintstore',
'compressor',
'haystack',
'django_extensions',
'django_q',
'allauth',
'allauth.account',
'allauth.socialaccount',
#'django_mailman3.lib.auth.fedora',
#'allauth.socialaccount.providers.openid',
#'allauth.socialaccount.providers.github',
#'allauth.socialaccount.providers.gitlab',
#'allauth.socialaccount.providers.google',
#'allauth.socialaccount.providers.facebook',
#'allauth.socialaccount.providers.twitter',
#'allauth.socialaccount.providers.stackexchange',
)
# Database
# https://docs.djangoproject.com/en/1.8/ref/settings/#databases
DATABASES = {
'default': {
# Use 'sqlite3', 'postgresql_psycopg2', 'mysql', 'sqlite3' or
'oracle'.
'ENGINE': 'django.db.backends.sqlite3',
#'ENGINE': 'django.db.backends.postgresql_psycopg2',
#'ENGINE': 'django.db.backends.mysql',
# DB name or path to database file if using sqlite3.
'NAME': '/var/lib/mailman3/web/mailman3suite.db.db',
# The following settings are not used with sqlite3:
'USER': '',
'PASSWORD': '',
# HOST: empty for localhost through domain sockets or
'127.0.0.1' for
# localhost through TCP.
'HOST': '',
# PORT: set to empty string for default.
'PORT': '',
# OPTIONS: Extra parameters to use when connecting to the
database.
'OPTIONS': {
# Set sql_mode to 'STRICT_TRANS_TABLES' for MySQL. See
# https://docs.djangoproject.com/en/1.11/ref/
# databases/#setting-sql-mode
#'init_command': "SET sql_mode='STRICT_TRANS_TABLES'",
},
}
}
# If you're behind a proxy, use the X-Forwarded-Host header
# See https://docs.djangoproject.com/en/1.8/ref/settings/#use-x-forward
ed-host
USE_X_FORWARDED_HOST = True
# And if your proxy does your SSL encoding for you, set
SECURE_PROXY_SSL_HEADER
# https://docs.djangoproject.com/en/1.8/ref/settings/#secure-proxy-ssl-
header
SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')
SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_SCHEME', 'https')
# Other security settings
# SECURE_SSL_REDIRECT = True
# If you set SECURE_SSL_REDIRECT to True, make sure the
SECURE_REDIRECT_EXEMPT
# contains at least this line:
# SECURE_REDIRECT_EXEMPT = [
# "archives/api/mailman/.*", # Request from Mailman.
# ]
# SESSION_COOKIE_SECURE = True
# SECURE_CONTENT_TYPE_NOSNIFF = True
# SECURE_BROWSER_XSS_FILTER = True
# CSRF_COOKIE_SECURE = True
# CSRF_COOKIE_HTTPONLY = True
# X_FRAME_OPTIONS = 'DENY'
# Internationalization
# https://docs.djangoproject.com/en/1.8/topics/i18n/
LANGUAGE_CODE = 'en-us'
TIME_ZONE = 'UTC'
USE_I18N = True
USE_L10N = True
USE_TZ = True
# Set default domain for email addresses.
EMAILNAME = 'x.xx'
# If you enable internal authentication, this is the address that the
emails
# will appear to be coming from. Make sure you set a valid domain name,
# otherwise the emails may get rejected.
# https://docs.djangoproject.com/en/1.8/ref/settings/#default-from-emai
l
# DEFAULT_FROM_EMAIL = "mailing-li...@you-domain.org"
DEFAULT_FROM_EMAIL = 'postorius@{}'.format(EMAILNAME)
# If you enable email reporting for error messages, this is where those
emails
# will appear to be coming from. Make sure you set a valid domain name,
# otherwise the emails may get rejected.
# https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SERVE
R_EMAI
Bug#891881: mailman3-suite: On system using exim (no postfix install) the list create script tries to create postfix aliases
The problem exists even after a reboot. If i run grep postfix -r /etc/mailman3/ i get nothing back.
Bug#891937: mailman3-suite: Hyperkitty tries to connect postgres on system using sqlite
Same/similar issue with the cron daily script: ... OperationalError: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? ERROR OCCURED IN DAILY JOB: daily_cleanup (APP: django_extensions) START TRACEBACK: END TRACEBACK ERROR OCCURED IN DAILY JOB: orphan_emails (APP: hyperkitty) START TRACEBACK: END TRACEBACK ERROR OCCURED IN DAILY JOB: recent_threads_cache (APP: hyperkitty) START TRACEBACK: END TRACEBACK ERROR OCCURED IN DAILY JOB: sync_mailman (APP: hyperkitty) START TRACEBACK: END TRACEBACK
Bug#891937: mailman3-suite: Hyperkitty tries to connect postgres on system using sqlite
Package: mailman3 Version: 3.1.1 System: debian stretch-backports Fresh install with sqlite as DB. Hyperkitty tries to connect postgres on system using sqlite. Postgres is not installed on this system. Mail from (hourly) cronjob: Traceback (most recent call last): File "/usr/lib/python2.7/dist- packages/django_extensions/management/commands/runjobs.py", line 34, in runjobs job().execute() File "/usr/lib/python2.7/dist- packages/hyperkitty/jobs/thread_starting_email.py", line 39, in execute starting_email__isnull=True).all(): File "/usr/lib/python2.7/dist-packages/django/db/models/query.py", line 250, in __iter__ self._fetch_all() File "/usr/lib/python2.7/dist-packages/django/db/models/query.py", line 1118, in _fetch_all self._result_cache = list(self._iterable_class(self)) File "/usr/lib/python2.7/dist-packages/django/db/models/query.py", line 53, in __iter__ results = compiler.execute_sql(chunked_fetch=self.chunked_fetch) File "/usr/lib/python2.7/dist- packages/django/db/models/sql/compiler.py", line 887, in execute_sql cursor = self.connection.cursor() File "/usr/lib/python2.7/dist- packages/django/db/backends/base/base.py", line 254, in cursor return self._cursor() File "/usr/lib/python2.7/dist- packages/django/db/backends/base/base.py", line 229, in _cursor self.ensure_connection() File "/usr/lib/python2.7/dist- packages/django/db/backends/base/base.py", line 213, in ensure_connection self.connect() File "/usr/lib/python2.7/dist-packages/django/db/utils.py", line 94, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/usr/lib/python2.7/dist- packages/django/db/backends/base/base.py", line 213, in ensure_connection self.connect() File "/usr/lib/python2.7/dist- packages/django/db/backends/base/base.py", line 189, in connect self.connection = self.get_new_connection(conn_params) File "/usr/lib/python2.7/dist- packages/django/db/backends/postgresql/base.py", line 176, in get_new_connection connection = Database.connect(**conn_params) File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 164, in connect conn = _connect(dsn, connection_factory=connection_factory, async=async) OperationalError: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? ERROR OCCURED IN HOURLY JOB: thread_starting_email (APP: hyperkitty) START TRACEBACK: END TRACEBACK
Bug#891881: [Pkg-mailman-hackers] Bug#891881: mailman3-suite: On system using exim (no postfix install) the list create script tries to create postfix aliases
Sorry, i forgot to mention that i have already following MTA config in /etc/mailman3/mailman.cfg [mta] incoming: mailman.mta.exim4.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: localhost smtp_host: localhost lmtp_port: 8024 smtp_port: 25 configuration: python:mailman.config.exim4 And of course an exim is running on the same machine.
Bug#891703: DB user isn't read from setting_local (mailman3-suite.py in /etc)
I'm not sure if this is the same bug.
I get following in the logs:
```
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-
packages/django/core/handlers/exception.py", line 41, in inner
response = get_response(request)
File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py",
line 249, in _legacy_get_response
response = self._get_response(request)
File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py",
line 187, in _get_response
response = self.process_exception_by_middleware(e, request)
File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py",
line 185, in _get_response
response = wrapped_callback(request, *callback_args,
**callback_kwargs)
File "/usr/lib/python2.7/dist-packages/django/views/generic/base.py",
line 68, in view
return self.dispatch(request, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/django/utils/decorators.py",
line 67, in _wrapper
return bound_func(*args, **kwargs)
File "/usr/lib/python2.7/dist-
packages/django/views/decorators/debug.py", line 76, in
sensitive_post_parameters_wrapper
return view(request, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/django/utils/decorators.py",
line 63, in bound_func
return func.__get__(self, type(self))(*args2, **kwargs2)
File "/usr/lib/python2.7/dist-packages/allauth/account/views.py",
line 137, in dispatch
return super(LoginView, self).dispatch(request, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/allauth/account/views.py",
line 80, in dispatch
**kwargs)
File "/usr/lib/python2.7/dist-packages/django/views/generic/base.py",
line 88, in dispatch
return handler(request, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/allauth/account/views.py",
line 103, in post
response = self.form_valid(form)
File "/usr/lib/python2.7/dist-packages/allauth/account/views.py",
line 150, in form_valid
return form.login(self.request, redirect_url=success_url)
File "/usr/lib/python2.7/dist-packages/allauth/account/forms.py",
line 197, in login
redirect_url=redirect_url)
File "/usr/lib/python2.7/dist-packages/allauth/account/utils.py",
line 146, in perform_login
send_email_confirmation(request, user, signup=signup)
File "/usr/lib/python2.7/dist-packages/allauth/account/utils.py",
line 323, in send_email_confirmation
confirm=True)
File "/usr/lib/python2.7/dist-packages/allauth/account/managers.py",
line 15, in add_email
user=user, email__iexact=email, defaults={"email": email}
File "/usr/lib/python2.7/dist-packages/django/db/models/manager.py",
line 85, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/django/db/models/query.py",
line 466, in get_or_create
return self._create_object_from_params(lookup, params)
File "/usr/lib/python2.7/dist-packages/django/db/models/query.py",
line 498, in _create_object_from_params
obj = self.create(**params)
File "/usr/lib/python2.7/dist-packages/django/db/models/query.py",
line 394, in create
obj.save(force_insert=True, using=self.db)
File "/usr/lib/python2.7/dist-packages/django/db/models/base.py",
line 808, in save
force_update=force_update, update_fields=update_fields)
File "/usr/lib/python2.7/dist-packages/django/db/models/base.py",
line 838, in save_base
updated = self._save_table(raw, cls, force_insert, force_update,
using, update_fields)
File "/usr/lib/python2.7/dist-packages/django/db/models/base.py",
line 924, in _save_table
result = self._do_insert(cls._base_manager, using, fields,
update_pk, raw)
File "/usr/lib/python2.7/dist-packages/django/db/models/base.py",
line 963, in _do_insert
using=using, raw=raw)
File "/usr/lib/python2.7/dist-packages/django/db/models/manager.py",
line 85, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/django/db/models/query.py",
line 1076, in _insert
return query.get_compiler(using=using).execute_sql(return_id)
File "/usr/lib/python2.7/dist-
packages/django/db/models/sql/compiler.py", line 1112, in execute_sql
cursor.execute(sql, params)
File "/usr/lib/python2.7/dist-packages/django/db/backends/utils.py",
line 64, in execute
return self.cursor.execute(sql, params)
File "/usr/lib/python2.7/dist-packages/django/db/utils.py", line 94,
in __exit__
six.reraise(dj_exc_type, dj_exc_value, traceback)
File "/usr/lib/python2.7/dist-packages/django/db/backends/utils.py",
line 64, in execute
return self.cursor.execute(sql, params)
File "/usr/lib/python2.7/dist-
packages/django/db/backends/sqlite3/base.py", line 328, in execute
return Database.Cursor.execute(self, query, params)
OperationalError: attempt to write a readonly database
```
after changing the owner of the database the error disappears:
chown www-data:www-data /var/lib/mailman3/web/mailman3suite.db.db
as a sidenote:
there are 2 .db fi
Bug#891881: mailman3-suite: On system using exim (no postfix install) the list create script tries to create postfix aliases
Package: mailman3 Version: 3.1.1 System: debian stretch-backports This is a system with exim4 as local mailserver On creating a new mailinglist i get following error in the logs: ``` File "/usr/lib/python3.5/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python3/dist- packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ (falcon/api.c:2571) File "falcon/api.py", line 189, in falcon.api.API.__call__ (falcon/api.c:2190) File "/usr/lib/python3/dist-packages/mailman/rest/lists.py", line 245, in on_post mlist = create_list(**validator(request)) File "/usr/lib/python3/dist-packages/mailman/app/lifecycle.py", line 100, in create_list call_name(config.mta.incoming).create(mlist) File "/usr/lib/python3/dist-packages/mailman/mta/postfix.py", line 66, in create self.regenerate() File "/usr/lib/python3/dist-packages/mailman/mta/postfix.py", line 103, in regenerate raise RuntimeError(NL.join(errors)) RuntimeError: command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_lmtp, 127, Key has expired command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_domains, 127, Key has expired Mar 01 21:34:02 2018 (11537) 127.0.0.1 - - "POST /3.0/lists HTTP/1.1" 500 59 ``` This means that it tries to create postfix aliases but postfix is not installed. /usr/sbin/postmap does not exist. A workaround is to create that file (empty) with execute permissions. A proper fix would be that /usr/lib/python3/dist-packages/mailman/mta/postfix.py will not be called in the first place.
Bug#891849: Cron errors, permission denied: '/var/log/mailman3/mailman-suite.log'
i tried to fix this with chown list:list /var/log/mailman3/mailman-suite.log but then other parts break: ``` Traceback (most recent call last): File "manage.py", line 10, in execute_from_command_line(sys.argv) File "/usr/lib/python2.7/dist- packages/django/core/management/__init__.py", line 364, in execute_from_command_line utility.execute() File "/usr/lib/python2.7/dist- packages/django/core/management/__init__.py", line 338, in execute django.setup() File "/usr/lib/python2.7/dist-packages/django/__init__.py", line 22, in setup configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) File "/usr/lib/python2.7/dist-packages/django/utils/log.py", line 75, in configure_logging logging_config_func(logging_settings) File "/usr/lib/python2.7/logging/config.py", line 794, in dictConfig dictConfigClass(config).configure() File "/usr/lib/python2.7/logging/config.py", line 576, in configure '%r: %s' % (name, e)) ValueError: Unable to configure handler 'file': [Errno 13] Permission denied: '/var/log/mailman3/mailman-suite.log' ``` I think that 2 different users try to write to that logfile. A workaround (i don't like) is to give o+rw permission to that file. Mainlman 3.1.1 from stretch-backports
Bug#854210: libnet-xmpp-perl: sendxmpp can't send message to hangouts (work fine for 1.02-5)
On Tue, 2017-06-27 at 23:08 +0200, gregor herrmann wrote: > On Tue, 27 Jun 2017 21:06:20 +0200, Salvatore Bonaccorso wrote: > ... > > Maybe I miss something obvious, but IMHO the bug should 1/ be > > reassigned to sendxmpp itself. Then the question is if sendxmpp > > should > > be patches actually (if so it might need to depend on > > ca-certificates), or "just" document when > > -tls-ca-path="/etc/ssl/certs" needs to be passed. If people don't like to use SSL (which i would consider as a bad idea these days) they also don't want a dependency on ca-certificates. So it should be a 'reccomended package'. But if ca-certificates is installed, it would be nice to have tls-ca- path="/etc/ssl/certs" set as default. Otherwise it will not be used anyways. If the -t flag is used and no certs are found, there should be a error message which suggests the installation of the ca-certificates package or to set a proper path to manually deployed certs. ... > Ack, AFAICS Net::XMPP fixed a bug (ignoring the path to the certs) > and this triggered the necessity for sendxmpp to set it (by the user > or in the code). I'd like to have the default set in Net::XMPP debian package to have it available in several applications which use this library. Maybe in sendxmpp too. > -- At the other end of the chain XML::Stream is just > a general-purpose low-level library, and changes there look like the > wrong place to me. ACK. this would be too low-level. Markus
Bug#854210: libnet-xmpp-perl: sendxmpp can't send message to hangouts (work fine for 1.02-5)
On Mon, 2017-06-26 at 19:23 +0200, gregor herrmann wrote: > On Mon, 26 Jun 2017 00:36:27 +0200, Markus Gschwendt wrote: > > Could you please also tell us if my interpretation of your message re > ejabberd from my last mail was correct? yes. in my opinion ejabberd is not effected. the cause of the problem is on the local side of perl/sendxmpp configuration. ejabberd was just the remote side in my case like google chat in the original report. > -#-#-#-# > > > > Another question: you marked this bug as "affects: sendxmpp > > > ejabberd". The former is obvious but why the latter? I don't > > > think > > > that ejabberd uses XML::Stream or Net::XMPP … > > > > This information was provided by Markus Gschwendt here: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854210#10 > > Right but I'm reading the message as "It also happens when I use > sendxmpp to send a message to a server running ejabberd [and not only > some google server as in the original bug report]". Cc'ing Markus for > clarification. > > #-#-#-#- > Markus
Bug#854210: libnet-xmpp-perl: sendxmpp can't send message to hangouts (work fine for 1.02-5)
On Sun, 2017-06-25 at 23:40 +0200, gregor herrmann wrote: > On Sun, 25 Jun 2017 14:52:54 -0300, Eriberto Mota wrote: > ... > - the idea to make this all easier for users by setting a sane > default in either sendxmpp or libxml-stream-perl; > +1 I'd like to have the path to the certs as default. Maybe both packages should have a default value. > ... Markus
Bug#825562: dovecot-imapd: service fail to start at boot time
This is a problem after upgrading to 'stretch' which is the 'stable' release now. Dovecot starts before the network is up. i used a modified fix from RH: https://bugzilla.redhat.com/show_bug.cgi?id=1309946 What works for me in debian stretch: create file /etc/systemd/system/dovecot.service with the content ~~ .include /lib/systemd/system/dovecot.service [Unit] After=network-online.target ~~
Bug#854210: libnet-xmpp-perl: sendxmpp can't send message
This problem exists now in the actual stable release: debian stretch.
Bug#854210: libnet-xmpp-perl: sendxmpp can't send message
I can confirm this. Same problem with my ejabberd server (on debian testing).
Bug#831561: Needs rebuild for dovecot 2.2.26
Broken in jessie-backports. should depend on dovecot-abi-2.2.abiv26 instead of dovecot-abi-2.2.abiv24
Bug#836587: confirm this bug
I will confirm this bug after a normal upgrade via `apt-get update && apt-get upgrade`. Workbench opens but crashes on opening a DB after asking for the password. Linux 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18) x86_64 GNU/Linux Debian GNU/Linux stretch
Bug#789770: linux-image-3.16.0-4-amd64: Dell R310 server (Xen 4.4 Dom0) periodically crashing after upgrade to Jessie from Wheezy
Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Control Registers (rev 05) ff:05.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Address Registers (rev 05) ff:05.2 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Rank Registers (rev 05) ff:05.3 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Thermal Control Registers (rev 05) ff:06.0 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Control Registers (rev 05) ff:06.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Address Registers (rev 05) ff:06.2 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Rank Registers (rev 05) ff:06.3 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Thermal Control Registers (rev 05) Markus Gschwendt
