djigzo accepts all emails but did not deliver anyone.
in the syslog i find entries like this:
"......lost connection with 127.0.0.1[127.0.0.1] while receiving the initial
server greeting"
and later in the syslog many entries
"connect to 127.0.0.1 .... connection refused"
i tried to open http-management interface, but i got this error message:
(See attached file: check.htm)
has someone an idea what has happend and what can we do to prevent this
behavior?
Zitat von Andreas Schubert <schubert(a)transline.de>:
hello,
yesterday we had a strange behavior.
djigzo accepts all emails but did not deliver anyone.
in the syslog i find entries like this:
"......lost connection with 127.0.0.1[127.0.0.1] while receiving the initial
server greeting"
and later in the syslog many entries
"connect to 127.0.0.1 .... connection refused"
i tried to open http-management interface, but i got this error message:
(See attached file: check.htm)
has someone an idea what has happend and what can we do to prevent this
behavior?
I guess one needs the /var/log/djigzo.log to tell what is going on....
Somehow the Java Virtual Machine got stuck which normally should not
happen (perhaps a JVM bug?).
Java wrapper which is used to start Djigzo 'injects' a Java process into
the JVM and periodically checks whether the JVM still responds. Java
wrapper itself is a Linux application (written in C). It detected that
the JVM was no longer responding and tried to restart the JVM. Somehow
Java wrapper was unable to restart Djigzo.
JVM appears hung: Timed out waiting for signal from JVM.
JVM did not exit on request, terminated
JVM exited in response to signal SIGKILL (9).
Unable to start a JVM
<-- Wrapper Stopped
--> Wrapper Started as Console
You test that the wrapper process restarts Djigzo after an unexpected
exit by killing the Djigzo java process (using killl -9)
If I explicitly kill the Djigzo Java process Djigzo is automatically
restarted by the wrapper process. djigzo.log after killing the Djigzo
process:
JVM exited unexpectedly.
JVM exited in response to signal SIGKILL (9).
Launching a JVM...
In your case the Java wrapper was unable to restart Djigzo so it seems
that there were problems with your Linux system. The big question is
what kind of problems.
Is there anything relevant in syslog or kernel.log?
Kind regards,
Martijn Brinkers
Andreas Schubert wrote:
ยทยทยท
hello,
yesterday we had a strange behavior.
djigzo accepts all emails but did not deliver anyone.
in the syslog i find entries like this:
"......lost connection with 127.0.0.1[127.0.0.1] while receiving the initial
server greeting"
and later in the syslog many entries
"connect to 127.0.0.1 .... connection refused"
i tried to open http-management interface, but i got this error message:
(See attached file: check.htm)
has someone an idea what has happend and what can we do to prevent this
behavior?