Questions installing from source #1920
Labels
Comments
|
Hi @raba34 , |
|
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 [1] ,
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 [2], or unsubscribe
[3].
You are receiving this because you were mentioned.Message ID:
***@***.***>
Links:
------
[1] https://github.com/raba34
[2]
#1920 (comment)
[3]
https://github.com/notifications/unsubscribe-auth/ABGRSMHYVO52M2OHR7RBWYT2IUZLNAVCNFSM6AAAAABUPA5RQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRXG4ZTGNRZGY
--=_94b2fe42d42c8f2ed750333ea9b9203f
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3DUTF-8" /></head><body style=3D'font-size: 10pt; font-family: Verdana,Gen=
eva,sans-serif'>
<p>Hi IKEDA,</p>
<p>I will list several steps below. At the bottom you can see the error mes=
sage “Failed with result ‘service-start-limit-hit’.&rdquo=
; Maybe this is important.</p>
<p>Best regards,</p>
<p>Ralph</p>
<p><br /></p>
<p>Step 1: Start of wwsympa.socket: "systemctl start wwsympa.socket"</p>
<p>No reaction in bash</p>
<p>------------------------------------------------------------------------=
-------------------------------------------------------------</p>
<p>Step 2: "systemctl status wwsympa.socket"</p>
<p>Reaction in bash:</p>
<div><span> wwsympa.socket - Sympa web interface socket</span></div>
<div><span> Loaded: loaded (/usr/lib/systemd/system/wwsy=
mpa.socket; disabled; preset: enabled)</span></div>
<div><span> Drop-In: /etc/systemd/system/wwsympa.socket.d</spa=
n></div>
<div><span> =E2=94=94=E2=94=
=80override.conf</span></div>
<div><span> Active: active (listening) since Thu 2025-01=
-02 15:23:26 CET; 1min 52s ago</span></div>
<div><span> Triggers: =E2=97=8F wwsympa.service</span></div>
<div><span> Listen: /usr/local/var/run/sympa/wwsympa.soc=
ket (Stream)</span></div>
<div><span> Tasks: 0 (limit: 9431)</span></div>
<div><span> Memory: 0B (peak: 256.0K)</span></div>
<div><span> CPU: 1ms</span></div>
<div><span> CGroup: /system.slice/wwsympa.socket</span><=
/div>
<div><span> </span></div>
<div><span>Jan 02 15:23:26 sympa.schule.de systemd[1]: Starting wwsympa.soc=
ket - Sympa web interface socket...</span></div>
<div><span>Jan 02 15:23:26 sympa.schule.de systemd[1]: Listening on wwsympa=
=2Esocket - Sympa web interface socket.</span></div>
<div> </div>
<div><span>----------------------------------------------------------------=
----------------------------------------------------------------------</spa=
n></div>
<div> </div>
<div><span>Step 3: </span><span>Call of "https://sympa.schule.de/symp=
a"</span></div>
<div> </div>
<div><span><span>Reaction in browser: "Service Unavailable"</span></span></=
div>
<div> </div>
<div><span><span>Reaction in apache2/error.log:</span></span></div>
<div> </div>
<div><span><span>[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<br=
/>[Thu Jan 02 15:04:37.351397 2025] [proxy_fcgi:error] [pid 142205] (104)C=
onnection reset by peer: [client 91.52.3.22:52237] AH01075: Error dispatchi=
ng request to :<br /></span></span></div>
<div> </div>
<div><span><span>----------------------------------------------------------=
---------------------------------------------------------------------------=
-</span></span></div>
<div> </div>
<div><span><span>Step 4: "systemctl status wwsympa.socket"</span></span></d=
iv>
<div> </div>
<div>
<div><span>× wwsympa.socket - Sympa web interface socket</span></div>
<div><span> Loaded: loaded (/usr/lib/systemd/system/wwsy=
mpa.socket; disabled; preset: enabled)</span></div>
<div><span> Drop-In: /etc/systemd/system/wwsympa.socket.d</spa=
n></div>
<div><span> =E2=94=94=E2=94=
=80override.conf</span></div>
<div><span> Active: failed (Result: service-start-limit-=
hit) since Thu 2025-01-02 15:33:55 CET; 4s ago</span></div>
<div><span> Duration: 10min 28.933s</span></div>
<div><span> Triggers: =E2=97=8F wwsympa.service</span></div>
<div><span> Listen: /usr/local/var/run/sympa/wwsympa.soc=
ket (Stream)</span></div>
<div><span> CPU: 1ms</span></div>
<div><span> </span></div>
<div><span>Jan 02 15:23:26 sympa.schule.de systemd[1]: Starting wwsympa.soc=
ket - Sympa web interface socket...</span></div>
<div><span>Jan 02 15:23:26 sympa.schule.de systemd[1]: Listening on wwsympa=
=2Esocket - Sympa web interface socket.</span></div>
<div><span>Jan 02 15:33:55 sympa.schule.de systemd[1]: wwsympa.socket: Fail=
ed with result 'service-start-limit-hit'.</span></div>
<div> </div>
<div><span>----------------------------------------------------------------=
---------------------------------------------------------------------</span=
</div>
<p><br /></p>
</div>
<p id=3D"reply-intro">Am 02.01.2025 13:55, schrieb IKEDA Soji:</p>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0">
<div id=3D"replybody1">
<p><br /></p>
<p dir=3D"auto">Hi <a class=3D"v1user-mention v1notranslate" href=3D"https:=
//github.com/raba34" target=3D"_blank" rel=3D"noopener ***@***.***<=
/a> ,<br />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: (e=
ntire copy the configuration file), and then runa command 'bar uu oo', ..."=
, and I saw baz is not boo but foo.</p>
<p style=3D"font-size: small; -webkit-text-size-adjust: none; color: #666;"=
—<br />Reply to this email directly, <a href=3D"https://github.com/s=
ympa-community/sympa/issues/1920#issuecomment-2567733696" target=3D"_blank"=
rel=3D"noopener noreferrer">view it on GitHub</a>, or <a href=3D"https://g=
ithub.com/notifications/unsubscribe-auth/ABGRSMHYVO52M2OHR7RBWYT2IUZLNAVCNF=
SM6AAAAABUPA5RQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRXG4ZTGNRZGY" t=
arget=3D"_blank" rel=3D"noopener noreferrer">unsubscribe</a>.<br />You are =
receiving this because you were mentioned.<img src=3D"https://github.com/no=
tifications/beacon/ABGRSMCATBDWPDRC4W2TDID2IUZLNA5CNFSM6AAAAABUPA5RQGWGG33N=
NVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUZBSA4A.gif" width=3D=
"1" height=3D"1" /><span style=3D"color: transparent; font-size: 0; display=
: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height:=
0; max-width: 0; max-height: 0; mso-hide: all;">Message ID: <span><symp=
a-community/sympa/issues/1920/2567733696</span><span>@</span><span>github</=
span><span>.</span><span>com></span></span></p>
</div>
</blockquote>
<p><br /></p>
</body></html>
…--=_94b2fe42d42c8f2ed750333ea9b9203f--
|
|
@raba34 I think you need to check the sympa log files to determine what is going on with WWSympa. |
|
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 [1] 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 [2], or unsubscribe
[3].
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@raba34 It is odd that you see no entries in the sympa log. Where is your sympa log located and which permissions has the file? |
|
Fundamentally, it is difficult to know where you went wrong without knowing everything you did during the installation process. I think the better way to be sure is to delete everything you installed and then start the installation process over again, following the instructions in the documentation and recording every operation you perform. |
|
@raba34 Set log_level to at least 1 to get log entries. |
|
Hi Stefan,
first of all: "sympa test syslog" only brings an entry in sympa.log if
the file is open for the world to write.
Incidentally, I do not have /etc/syslog, only /etc/rsyslog.
But even if the log file is open, I get no entry for my problem.
Unfortunately, I can't find a way to increase the log level either. The
option "-d" or "--debug" mentioned in the manual does not work. Like any
other unavailable option, this leads to the initially incomprehensible
error message "Unknown option at /usr/local/sbin/sympa line 185". If you
look at the file, this is the way out if every case distinction does not
lead to the goal and there is no "d" there.
How do I enable debugging?
We use here
Ubuntu 24.04.1 LTS (GNU/Linux 6.8.0-51-generic x86_64)
Best regards,
Ralph
Am 02.01.2025 20:56, schrieb Stefan Hornburg (Racke):
@raba34 [1] It is odd that you see no entries in the sympa log.
Where is your sympa log located and which permissions has the file?
Which Linux distribution + release do you use?
--
Reply to this email directly, view it on GitHub [2], or unsubscribe
[3].
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hello,
two PERL modules were missing, namely "libmime-lite-html-perl" and
"libdatetime-format-mail-perl".
I found this out by starting "/usr/local/lib/sympa/cgi/wwsympa.fcgi"
directly and then received meaningful error messages.
But this was not mentioned anywhere in the instructions.
Let's see what other problems I encounter now.
Best regards,
Ralph
Am 03.01.2025 13:15, schrieb IKEDA Soji:
@raba34 [1]
Fundamentally, it is difficult to know where you went wrong without
knowing everything you did during the installation process.
I think the better way to be sure is to delete everything you installed
and then start the installation process over again, following the
instructions in the documentation [2] and recording every operation you
perform.
--
Reply to this email directly, view it on GitHub [3], or unsubscribe
[4].
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@raba34 , See the description in the documentation. You may refer to the |
|
Hi Soji,
many thanks for the tip. I had overlooked this point in the manual.
I have carried out the steps described there and a few more modules have
been installed.
But now I have another problem. The command "systemctl start
sympa.service" fails because the unit "sympa.service" does not exist.
Where is this installation described?
Best regards,
Ralph
Am 06.01.2025 06:13, schrieb IKEDA Soji:
@raba34 [1] ,
See the description in the documentation [2]. You may refer to the
cpanfile file.
--
Reply to this email directly, view it on GitHub [3], or unsubscribe
[4].
You are receiving this because you were mentioned.Message ID:
***@***.***>
Links:
------
[1] https://github.com/raba34
[2]
https://www.sympa.community/manual/install/install-dependent-modules.html#using-package-management-tools
[3]
#1920 (comment)
[4]
https://github.com/notifications/unsubscribe-auth/ABGRSMCLWGD3GBYHJNEHPBL2JIGIHAVCNFSM6AAAAABUPA5RQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZSGI4TAMBZGI
|
|
Hi Soji
after some searching and a "make" I finally got symba.service and
installed it under systemd.
But this really seems to be missing from the documentation, doesn't it?
Best regards,
Ralph
Am 06.01.2025 12:42, schrieb Ralph Ballier:
Hi Soji,
many thanks for the tip. I had overlooked this point in the manual.
I have carried out the steps described there and a few more modules
have been installed.
But now I have another problem. The command "systemctl start
sympa.service" fails because the unit "sympa.service" does not exist.
Where is this installation described?
Best regards,
Ralph
Am 06.01.2025 06:13, schrieb IKEDA Soji:
> @raba34 [1] ,
>
> See the description in the documentation [2]. You may refer to the
> cpanfile file.
>
> --
> Reply to this email directly, view it on GitHub [3], or unsubscribe
> [4].
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
Links:
------
[1] https://github.com/raba34
[2]
https://www.sympa.community/manual/install/install-dependent-modules.html#using-package-management-tools
[3]
#1920 (comment)
[4]
https://github.com/notifications/unsubscribe-auth/ABGRSMCLWGD3GBYHJNEHPBL2JIGIHAVCNFSM6AAAAABUPA5RQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZSGI4TAMBZGI
|
It is difficult for us to know where you went wrong without knowing how you did 'some searching and a "make"', 'got symba.service' and 'installed it'. |
|
Hi Soji,
yes, I completely understand that. I just wanted to express that I
reached my goal this way.
I was simply asking where in the documentation the creation of
symba.service is described. I didn't find this place and only got to the
sympa-6.2.74/service directory via a search and created sympa.service
there via "make" and then integrated it into systemd without any
problems.
So far there is only one problem: After restarting the server, the
bulk.pl daemon is not started automatically. This means that outgoing
mail remains in the bulk/msg directory. I then have to call bulk.pl
manually. After that the mail transport works. What could be the reason
for this?
Greetings and many thanks for your help
Ralph
Am 07.01.2025 14:21, schrieb IKEDA Soji:
> after some searching and a "make" I finally got symba.service and
> installed it under systemd.
It is difficult for us to know where you went wrong without knowing how
you did 'some searching and a "make"', 'got symba.service' and
'installed it'.
--
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Please show how your sympa.service looks like: |
|
***@***.***:/var/log# systemctl cat sympa.service
# /etc/systemd/system/sympa.service
[Unit]
Description=Sympa mailing list manager
After=syslog.target
Wants=sympa-outgoing.service
Before=sympa-outgoing.service
Wants=sympa-archive.service
Before=sympa-archive.service
Wants=sympa-bounce.service
Before=sympa-bounce.service
Wants=sympa-task.service
Before=sympa-task.service
[Service]
Type=forking
PIDFile=/usr/local/var/run/sympa/sympa_msg.pid
ExecStartPre=/bin/mkdir -p /usr/local/var/run/sympa
ExecStartPre=/bin/chown sympa:sympa /usr/local/var/run/sympa
ExecStartPre=/usr/local/sbin/sympa check
ExecStart=/usr/local/sbin/sympa_msg.pl
[Install]
WantedBy=multi-user.target
# /etc/systemd/system/sympa.service.d/dependencies.conf
[Unit]
Requires=mysql.service
After=mysql.service
***@***.***:/var/log#
Am 07.01.2025 15:07, schrieb Stefan Hornburg (Racke):
Please show how your sympa.service looks like:
systemctl cat sympa.service
--
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
The document describes a variety of possible options. So you’d be better to explain what you actually did instead of simply saying “I read the document”, and someone might suggest correct (or at least better) way. For example: After reading this section of the document, could you please explain what you did, i.e. the command lines you typed etc.? |
|
I have set up the users and their rights as specified and then
./configure --enable-fhs --prefix=/usr/local --with-confdir=/etc/sympa
was executed.
Again my question: where is it written how to create sympa.service? Or
is it done automatically somewhere? For wwsympa.service and
wwsympa.socket, on the other hand, I can find detailed instructions.
Am 08.01.2025 04:01, schrieb IKEDA Soji:
I was simply asking where in the documentation the creation of
symba.service is described. I didn't find this place and only got to the
sympa-6.2.74/service directory via a search and created sympa.service
there via "make" and then integrated it into systemd without any
problems.
The document describes a variety of possible options. So you'd be better
to explain what you actually did instead of simply saying "I read the
document", and someone might suggest correct (or at least better) way.
For example: After reading this section of the document [1], could you
please explain what you did, i.e. the command lines you typed etc.?
…--
Reply to this email directly, view it on GitHub [2], or unsubscribe [3].
You are receiving this because you were mentioned.Message ID:
***@***.***>
Links:
------
[1]
https://www.sympa.community/manual/install/install-sympa-distribution-source.html#run-codeconfigurecode-script
[2]
#1920 (comment)
[3]
https://github.com/notifications/unsubscribe-auth/ABGRSMGVLJGCSQUPGIMUJ7D2JSIJ3AVCNFSM6AAAAABUPA5RQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZWGYYTEMJWGE
|
See the section described in above. In a subsection “Other useful options”, you will find what you need:
Now we know what you did, in other words what you didn’t, and we can finally answer your question. That’s why I’ve been asking “Please say what you actually did”. |
|
Hi IKEDA,
thank you for clarifying the facts.
But I have one more question: Why does this very important configuration
only appear under "Other useful options"? I assumed that the line
mentioned contains all the important elements and that this creates an
executable system. But if sympa.service is not created, nothing works.
Best regards,
Ralph
Am 09.01.2025 04:40, schrieb IKEDA Soji:
> ./configure --enable-fhs --prefix=/usr/local --with-confdir=/etc/sympa
> was executed.
See the section described in above [1]. In a subsection "Other useful
options", you will find what you need:
> * --without-initdir --with-unitsdir=/lib/systemd/system
>
> Installs Systemd unit files into specified directory.
Now we know what you did, in other words what you _didn't_, and we can
finally answer your question. That's why I've been asking "Please say
what you actually did".
--
Reply to this email directly, view it on GitHub [2], or unsubscribe
[3].
You are receiving this because you were mentioned.Message ID:
***@***.***>
Links:
------
[1]
https://www.sympa.community/manual/install/install-sympa-distribution-source.html#run-codeconfigurecode-script
[2]
#1920 (comment)
[3]
https://github.com/notifications/unsubscribe-auth/ABGRSMEZUQO3WL7GNF22GH32JXVSVAVCNFSM6AAAAABUPA5RQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZZGEYTSOBTGA
|
|
Not all operating systems adopt Systemd (and probably GNU/Linux-based). The fact is that the conditions that vary from environment to environment are described as broadly as possible. Your environment is not the only thing that matters. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
Sympa 6.2.72
Installation method
Installing from source
Expected behavior
After entering “https://sympa.schule.de/sympa”, the web interface should appear.
Actual behavior
After entering “https://sympa.schule.de/sympa” I see "Service Unavailable"
Steps to reproduce
This is is reproducible
Additional information
The Apache2 error log says:
[proxy:error] [pid 140889] (111)Connection refused: AH02454: FCGI: attempt to connect to Unix domain socket /usr/local/var/run/sympa/wwsympa.socket (*:80) failed
[proxy_fcgi:error] [pid 140889] [client 91.52.3.22:59260] AH01079: failed to make connection to backend: httpd-UDS
The text was updated successfully, but these errors were encountered: