The mailing list for listmasters using Sympa

[Ralph Ballier <address@concealed>]

Hi Stefan,

there are no entries in the sympa.log.

But in the syslog I found the following lines after trying to access the website.

This also explains the message “service-start-limit-hit”. After five unsuccessful attempts to start, it was given up. Now I just need to know what is meant by “status=2/INVALIDARGUMENT”.

Ralph

2025-01-02T17:14:41.703806+01:00 sympa systemd[1]: Started wwsympa.service - WWSympa - Web interface for Sympa mailing list manager (service).
2025-01-02T17:14:41.860097+01:00 sympa systemd[1]: wwsympa.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
2025-01-02T17:14:41.860257+01:00 sympa systemd[1]: wwsympa.service: Failed with result 'exit-code'.
2025-01-02T17:14:42.100815+01:00 sympa systemd[1]: wwsympa.service: Scheduled restart job, restart counter is at 1.
2025-01-02T17:14:42.115370+01:00 sympa systemd[1]: Started wwsympa.service - WWSympa - Web interface for Sympa mailing list manager (service).
2025-01-02T17:14:42.271417+01:00 sympa systemd[1]: wwsympa.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
2025-01-02T17:14:42.271553+01:00 sympa systemd[1]: wwsympa.service: Failed with result 'exit-code'.
2025-01-02T17:14:42.600854+01:00 sympa systemd[1]: wwsympa.service: Scheduled restart job, restart counter is at 2.
2025-01-02T17:14:42.610255+01:00 sympa systemd[1]: Started wwsympa.service - WWSympa - Web interface for Sympa mailing list manager (service).
2025-01-02T17:14:42.762242+01:00 sympa systemd[1]: wwsympa.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
2025-01-02T17:14:42.762355+01:00 sympa systemd[1]: wwsympa.service: Failed with result 'exit-code'.
2025-01-02T17:14:42.980970+01:00 sympa postfix/smtpd[151764]: connect from unknown[80.94.95.235]
2025-01-02T17:14:43.100772+01:00 sympa systemd[1]: wwsympa.service: Scheduled restart job, restart counter is at 3.
2025-01-02T17:14:43.115286+01:00 sympa systemd[1]: Started wwsympa.service - WWSympa - Web interface for Sympa mailing list manager (service).
2025-01-02T17:14:43.268945+01:00 sympa systemd[1]: wwsympa.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
2025-01-02T17:14:43.269175+01:00 sympa systemd[1]: wwsympa.service: Failed with result 'exit-code'.
2025-01-02T17:14:43.600779+01:00 sympa systemd[1]: wwsympa.service: Scheduled restart job, restart counter is at 4.
2025-01-02T17:14:43.610244+01:00 sympa systemd[1]: Started wwsympa.service - WWSympa - Web interface for Sympa mailing list manager (service).
2025-01-02T17:14:43.763764+01:00 sympa systemd[1]: wwsympa.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
2025-01-02T17:14:43.763895+01:00 sympa systemd[1]: wwsympa.service: Failed with result 'exit-code'.
2025-01-02T17:14:44.101045+01:00 sympa systemd[1]: wwsympa.service: Scheduled restart job, restart counter is at 5.
2025-01-02T17:14:44.101257+01:00 sympa systemd[1]: wwsympa.service: Start request repeated too quickly.
2025-01-02T17:14:44.101328+01:00 sympa systemd[1]: wwsympa.service: Failed with result 'exit-code'.
2025-01-02T17:14:44.101387+01:00 sympa systemd[1]: Failed to start wwsympa.service - WWSympa - Web interface for Sympa mailing list manager (service).
2025-01-02T17:14:44.101578+01:00 sympa systemd[1]: wwsympa.socket: Failed with result 'service-start-limit-hit'.

Am 02.01.2025 17:04, schrieb Stefan Hornburg (Racke):

@raba34 I think you need to check the sympa log files to determine what is going on with WWSympa.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: <sympa-community/sympa/issues/1920/2568006664@github.com>