Mailman-users search results for query "Cannot connect to SMTP server localhost on port 25"
mailman-users@mailman3.org- 42 messages
Re: Uncaught runner exception
by Wolfgang Bock
Thanks Mark!
I changed the outgoing.py per cut&paste because I didnt know, whow th patch a python file ... But succeeded:
/var/log/mailman3/mailman.log
Apr 08 19:08:10 2020 (9234) Master started
Apr 08 19:08:12 2020 (9241) bounces runner started.
Apr 08 19:08:12 2020 (9263) virgin runner started.
Apr 08 19:08:12 2020 (9259) out runner started.
Apr 08 19:08:12 2020 (9255) lmtp runner started.
Apr 08 19:08:12 2020 (9259) Cannot connect to SMTP server localhost on port 25
[Errno 13] Permission denied: '/var/lib/mailman3/cache/7d/c6/7dc6d1a99a5ecf2b2241d6d0958a2bc704e32238150e5cc273f6779b124bd04f'
Apr 08 19:08:12 2020 (9237) archive runner started.
....
Checked the ownership ....
ls -la:
/var/lib/mailman3/cache
drwxrwx--- 3 root root 4096 Nov 9 22:27 61
drwxrwx--- 3 root root 4096 Feb 3 17:37 6c
drwxrwx--- 3 root root 4096 Nov 12 11:59 71
drwxrwx--- 3 root root 4096 Nov 6 12:01 72
drwxrwx--- 3 root root 4096 Feb 5 21:52 7d
drwxrwx--- 3 root root 4096 Feb 5 23:05 8b
drwxrwx--- 3 root root 4096 Nov 12 23:41 94
drwxrwx--- 3 root root 4096 Nov 7 08:31 ae
drwxrwx--- 3 root root 4096 Nov 12 23:40 fa
/var/log/mailman3/mailman.log
....
Apr 08 19:08:19 2020 (9259) Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration
self._process_one_file(msg, msgdata)
File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file
keepqueued = self._dispose(mlist, msg, msgdata)
File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 93, in _dispose
self._func(mlist, msg, msgdata)
File "/usr/lib/python3/dist-packages/mailman/mta/deliver.py", line 86, in deliver
refused = agent.deliver(mlist, msg, msgdata)
File "/usr/lib/python3/dist-packages/mailman/mta/bulk.py", line 100, in deliver
self.decorate(mlist, msg, msgdata)
File "/usr/lib/python3/dist-packages/mailman/mta/decorating.py", line 32, in decorate
decorator.process(mlist, msg, msgdata)
File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 264, in process
process(mlist, msg, msgdata)
File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 73, in process
for archiver in IListArchiverSet(mlist).archivers:
File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line 135, in __call__
adapter = self.__adapt__(obj)
File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line 151, in __adapt__
adapter = hook(self, obj)
File "/usr/lib/python3/dist-packages/zope/component/_api.py", line 156, in adapter_hook
return sitemanager.queryAdapter(object, interface, name, default)
File "/usr/lib/python3/dist-packages/zope/interface/registry.py", line 348, in queryAdapter
return self.adapters.queryAdapter(object, interface, name, default)
File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line 353, in queryAdapter
return self.adapter_hook(provided, object, name, default)
File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line 363, in adapter_hook
result = factory(object)
File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper
return function(args[0], config.db.store, *args[1:], **kws)
File "/usr/lib/python3/dist-packages/mailman/model/mailinglist.py", line 600, in __init__
for archiver in config.archivers:
File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 260, in archivers
archiver = call_name(class_path)
File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 70, in call_name
return named_callable(*args, **kws)
File "/usr/lib/python3/dist-packages/mailman/archiving/mhonarc.py", line 46, in __init__
config.archiver.mhonarc.configuration)
File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 335, in external_configuration
cfg_path = str(expand_path(resources, path))
File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 80, in expand_path
cfg_path = resources.enter_context(path(package, resource + '.cfg'))
File "/usr/lib/python3.7/contextlib.py", line 426, in enter_context
result = _cm_type.__enter__(cm)
File "/usr/lib/python3.7/contextlib.py", line 112, in __enter__
return next(self.gen)
File "/usr/lib/python3.7/importlib/resources.py", line 188, in path
yield Path(reader.resource_path(resource))
File "<frozen importlib._bootstrap_external>", line 932, in resource_path
File "<frozen importlib._bootstrap_external>", line 941, in is_resource
File "<frozen importlib._bootstrap_external>", line 95, in _path_isfile
File "<frozen importlib._bootstrap_external>", line 87, in _path_is_mode_type
File "<frozen importlib._bootstrap_external>", line 81, in _path_stat
File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 114, in signal_handler
raise RunnerInterrupt
mailman.interfaces.runner.RunnerInterrupt
Apr 08 19:08:19 2020 (9259) SHUNTING: 1586365699.6492867+798bd45a31fb2b8d5fd24a481a3cf95710994bf7
Apr 08 19:08:19 2020 (9259) out runner exiting.
Apr 08 19:08:19 2020 (9234) Master watcher caught SIGTERM. Exiting.
Apr 08 19:08:19 2020 (9234) Master stopped
Changed the ownership for /var/lib/mailman3/cache to list:list and from that point my lists are responding.
Same problem occurs before fort he list-directory, which I corrected some days ago.
Is the ownship misconfiguration a coincidence or did I made a mistake somewhere??
Thanks for your assistance!
Regards Wolfgang
-----Ursprüngliche Nachricht-----
Von: Mark Sapiro <mark(a)msapiro.net>
Gesendet: Mittwoch, 8. April 2020 00:23
An: MM3 Users <mailman-users(a)mailman3.org>
Betreff: [MM3-users] Re: Uncaught runner exception
On 4/7/20 2:40 PM, Wolfgang Bock via Mailman-users wrote:
> Yes,
I assume that means
telnet localhost 25
succeeds. Try the attached patch to mailman/runners/outgoing.py. It should log more about the actual exception.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
5 years, 5 months
Re: Importing config and archives only partially succeeded?
by Eric Broens
`mailman qfile` on the 5 pck files that were in the /out directory looked OK, although I am not sure if I should have looked at something specific.
The bak file disappeared as soon as I stopped mailman. When I started mailman again the name of the bak file had changed, and it changed every time I listed the directory.After stopping and starting mailman once more it didn't appear anymore.
There are also 6 files in the shunt directory. I don't know what this directory is used for.
For now I have disabled the hourly jobs.I will rebuild the search index for each mailinglist separately since the update_index was apparently killed before it finished.
Best Regards,Eric
On Sunday, December 13, 2020, 06:18:21 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote:
On 12/13/20 7:11 AM, Eric Broens via Mailman-users wrote:
> Hi Mark,
> 1.Regarding the repeated access of /archives/api/mailman/urls seems to be related to mailman not being able to open port 25.
> This is weird because other mails have been distributed.
> The mailman log shows:Dec 12 22:16:48 2020 (1471) ACCEPT: < message id >
> Dec 12 22:16:52 2020 (1474) Cannot connect to SMTP server localhost on port 25
That message is in response to a socket.error exception in attempted
delivery. It is logged only once until there is a successful delivery,
but the message keeps being retried.
> webserver logs:<host > - - [12/Dec/2020:22:16:50 +0100] "GET /archives/api/mailman/urls ?mlist=...&key=*** HTTP/1.1" 200 64 "-" "python-requests/2.25.0"
> <host > - - [12/Dec/2020:22:16:52 +0100] "GET /archives/api/mailman/urls?mlist=...&msgid=< message id >&key=*** HTTP/1.1" 200 105 "-" "python-requests/2.25.0"
> This last entry is repeated forever (until I stop the mailserver for a few minutes, but later on this happens again for other mails too).
Those GETs are part of normal message processing. As I said, they result
from core handlers asking HyperKitty for the URL at which the message
will be archived so they can add that URL to the Archived-At: header and
maybe to a message header or footer.
Presumably the one that keeps repeating is the one message/message-id
that is throwing the socket.error and being continuously retried.
I would stop Mailman and move that one .pck or .bak file out of
Mailman's var/queue/out/ directory and then start mailman. You can then
examine the queue entry with `mailman qfile` and maybe see what the
issue is.
> 2..Regarding the mails on the archive page, for most of the lists it is solved now. So probably one of the periodic jobs fixed that.The mailinglist which showed 0 participants 0 subscribers, does show now 0 participants 66 discussions.I have checked the member tables, and the members for this mailinglist are included there.
OK.
> 3.What I notice now too is that the hourly runjobs tasks don't seem to finish.I would have to check what they exactly do. Can I somehow activate logging for these?
> mailman 300042 300016 1 08:00 ? 00:09:18 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 302158 302149 2 09:00 ? 00:09:10 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 304513 304506 2 10:00 ? 00:09:38 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 308631 308620 3 11:00 ? 00:09:29 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 312847 312832 3 12:00 ? 00:09:15 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 317343 317332 4 13:00 ? 00:09:20 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 320079 320072 7 14:00 ? 00:09:08 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 322618 322610 13 15:00 ? 00:08:54 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 325205 325198 84 16:00 ? 00:06:56 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings
/opt/mailman/venv/bin/django-admin runjobs --list
will show you what the jobs are. The hourly jobs are
new_lists_from_mailman, thread_starting_email and update_index. The one
running long is almost certainly update_index. I would stop running the
hourly jobs until you have successfully updated the search index for all
lists.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
_______________________________________________
Mailman-users mailing list -- mailman-users(a)mailman3.org
To unsubscribe send an email to mailman-users-leave(a)mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
4 years, 9 months