(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
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
Broken in jessie-backports.
should depend on dovecot-abi-2.2.abiv26
instead of dovecot-abi-2.2.abiv24
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
This problem exists now in the actual stable release: debian stretch.
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
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 effecte
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
I can confirm this.
Same problem with my ejabberd server (on debian testing).
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
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
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
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
> >
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]
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
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 =
The problem exists even after a reboot.
If i run
grep postfix -r /etc/mailman3/
i get nothing back.
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
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",
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,
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
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
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
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 t
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
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
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
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
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
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
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,
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
32 matches
Mail list logo
