The mailing list for listmasters using Sympa

[Ralph Ballier <address@concealed>]

Hi IKEDA,

I will list several steps below. At the bottom you can see the error message “Failed with result ‘service-start-limit-hit’.” Maybe this is important.

Best regards,

Ralph

Step 1: Start of wwsympa.socket: "systemctl start wwsympa.socket"

No reaction in bash

-------------------------------------------------------------------------------------------------------------------------------------

Step 2:  "systemctl status wwsympa.socket"

Reaction in bash:

 wwsympa.socket - Sympa web interface socket

     Loaded: loaded (/usr/lib/systemd/system/wwsympa.socket; disabled; preset: enabled)

    Drop-In: /etc/systemd/system/wwsympa.socket.d

             └─override.conf

     Active: active (listening) since Thu 2025-01-02 15:23:26 CET; 1min 52s ago

   Triggers: ● wwsympa.service

     Listen: /usr/local/var/run/sympa/wwsympa.socket (Stream)

      Tasks: 0 (limit: 9431)

     Memory: 0B (peak: 256.0K)

        CPU: 1ms

     CGroup: /system.slice/wwsympa.socket

 

Jan 02 15:23:26 sympa.schule.de systemd[1]: Starting wwsympa.socket - Sympa web interface socket...

Jan 02 15:23:26 sympa.schule.de systemd[1]: Listening on wwsympa.socket - Sympa web interface socket.

 

--------------------------------------------------------------------------------------------------------------------------------------

 

Step 3:  Call of "https://sympa.schule.de/sympa"

 

Reaction in browser: "Service Unavailable"

 

Reaction in apache2/error.log:

 

[Thu Jan 02 15:04:37.351369 2025] [proxy_fcgi:error] [pid 142205] [client 91.52.3.22:52237] AH01067: Failed to read FastCGI header
[Thu Jan 02 15:04:37.351397 2025] [proxy_fcgi:error] [pid 142205] (104)Connection reset by peer: [client 91.52.3.22:52237] AH01075: Error dispatching request to :

 

--------------------------------------------------------------------------------------------------------------------------------------

 

Step 4: "systemctl status wwsympa.socket"

 

× wwsympa.socket - Sympa web interface socket

     Loaded: loaded (/usr/lib/systemd/system/wwsympa.socket; disabled; preset: enabled)

    Drop-In: /etc/systemd/system/wwsympa.socket.d

             └─override.conf

     Active: failed (Result: service-start-limit-hit) since Thu 2025-01-02 15:33:55 CET; 4s ago

   Duration: 10min 28.933s

   Triggers: ● wwsympa.service

     Listen: /usr/local/var/run/sympa/wwsympa.socket (Stream)

        CPU: 1ms

 

Jan 02 15:23:26 sympa.schule.de systemd[1]: Starting wwsympa.socket - Sympa web interface socket...

Jan 02 15:23:26 sympa.schule.de systemd[1]: Listening on wwsympa.socket - Sympa web interface socket.

Jan 02 15:33:55 sympa.schule.de systemd[1]: wwsympa.socket: Failed with result 'service-start-limit-hit'.

 

-------------------------------------------------------------------------------------------------------------------------------------

Am 02.01.2025 13:55, schrieb IKEDA Soji:

Hi @raba34 ,
Please describe the Steps to reproduce the problem, e.g. "I run a command 'foo ee aa', entered 'yes', edited a file 'foo.conf' as below: (entire copy the configuration file), and then runa command 'bar uu oo', ...", and I saw baz is not boo but foo.

—
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/2567733696@github.com>