'wallace not start'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kroupware
Subject:    wallace not start
From:       ladas () seznam ! cz
Date:       2024-04-03 11:43:31
Message-ID: 23457066.6Emhk5qWAg () zbook
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

Hi everybody,

since this morning cca 2:00 wallace at our server stop to work. After service restart \
                I get only usable message:
*wallace.service: main process exited, code=exited, status=2/INVALIDARGUMENT*

I checked configuration at other running server and did not find any difference. Can \
somebody give me an advice, where to start to dig? Or is it possible to go over \
wallace at all and deliver the message without check? We use email gateway so it is \
not theoretically necessary. Thank you very much for any advice.

Kolab16 runs at CentOS7, last updates installed

--
Greetings, ladas

[Attachment #5 (unknown)]

<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>Hi \
everybody, since this morning \
cca 2:00 wallace at our server stop to work. After service restart I get only usable \
message: wallace.service: main process exited, code=exited, \
status=2/INVALIDARGUMENT I checked \
configuration at other running server and did not find any difference. Can somebody \
give me an advice, where to start to dig? Or is it possible \
to go over wallace at all and deliver the message without check? We use email gateway \
so it is not theoretically necessary. Thank you very \
much for any advice. Kolab16 runs at \
CentOS7, last updates installed -- Greetings, \
ladas </body>
</html>

_______________________________________________
users mailing list
users@lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users

[prev in list] [next in list] [prev in thread] [next in thread] 