31 May
2010
31 May
'10
11:24 a.m.
Hi!
We are using perdition 1.17.1 on Centos 5.3 x64.
I tried to use the CentOS repo for updating to 1.18 but that version
dies immediately after a imap4 connect with "Exit 11" -
as we are using ldap as database I thing that is related to that patch
http://hg.vergenet.net/perdition/perdition/rev/28264fe9e31b
so I tried to compile perdition 1.18 manually.
That fails with:
-DHAVE_CONFIG_H -I. -I.. -DPERDITION_LIBDIR=\"/opt/perdition180/lib\"
-DPERDITION_SYSCONFDIR=\"/opt/perdition180/etc/perdition\"
-DPERDITION_LOCALSTATEDIR=\"/opt/perdition180/var\" -I/usr/include
-g -O2 -MT perdition.o -MD -MP -MF .deps/perdition.Tpo -c -o perdition.o
perdition.c
perdition.c: In function »main«:
perdition.c:547: Warning: Zuweisung erzeugt Zeiger von Ganzzahl ohne
Typkonvertierung
perdition.c:712: Fehler: expected expression before »else«
perdition.c:950: Fehler: expected expression before »else«
perdition.c:998: Fehler: expected expression before »else«
make[3]: *** [perdition.o] Fehler 1
make[3]: Leaving directory `/root/perdition-1.18/perdition'
make[2]: *** [all-recursive] Fehler 1
make[2]: Leaving directory `/root/perdition-1.18/perdition'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/root/perdition-1.18'
make: *** [all] Fehler 2
Can somebody give me a hint please?
regards martin
1 Jun
1 Jun
6:17 a.m.
On Mon, May 31, 2010 at 01:24:41PM +0200, Martin Hochreiter wrote:
Hi!
We are using perdition 1.17.1 on Centos 5.3 x64.
I tried to use the CentOS repo for updating to 1.18 but that version
dies immediately after a imap4 connect with "Exit 11" -
as we are using ldap as database I thing that is related to that patch
http://hg.vergenet.net/perdition/perdition/rev/28264fe9e31b
so I tried to compile perdition 1.18 manually.
That fails with:
-DHAVE_CONFIG_H -I. -I.. -DPERDITION_LIBDIR=\"/opt/perdition180/lib\"
-DPERDITION_SYSCONFDIR=\"/opt/perdition180/etc/perdition\"
-DPERDITION_LOCALSTATEDIR=\"/opt/perdition180/var\" -I/usr/include
-g -O2 -MT perdition.o -MD -MP -MF .deps/perdition.Tpo -c -o perdition.o
perdition.c
perdition.c: In function »main«:
perdition.c:547: Warning: Zuweisung erzeugt Zeiger von Ganzzahl ohne
Typkonvertierung
perdition.c:712: Fehler: expected expression before »else«
perdition.c:950: Fehler: expected expression before »else«
perdition.c:998: Fehler: expected expression before »else«
make[3]: *** [perdition.o] Fehler 1
make[3]: Leaving directory `/root/perdition-1.18/perdition'
make[2]: *** [all-recursive] Fehler 1
make[2]: Leaving directory `/root/perdition-1.18/perdition'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/root/perdition-1.18'
make: *** [all] Fehler 2
Can somebody give me a hint please?
Strange. Are you sure that the source hasn't been mangled somehow?
How did you obtain the code?
6:31 a.m.
Am 2010-06-01 08:17, schrieb Simon Horman:
On Mon, May 31, 2010 at 01:24:41PM +0200, Martin
Hochreiter wrote:
Hello Simon!
Thank you for your reply!
Thats my source:
http://www.vergenet.net/linux/perdition/download/1.18/perdition-1.18.tar.gz
I tried the mentioned ldap patch and I got an error and I downloaded and
extracted the source
again and tried it without the ldap patch ... same problem.
May it be related to a CentOS 5.3 (64bit) problem?
Or - another solution for us ... do you plan to integrate the patch in
the CentOS RPMs?
(we use ldap as database and need the mailhost field ...)
regards
martin
Hi!
We are using perdition 1.17.1 on Centos 5.3 x64.
I tried to use the CentOS repo for updating to 1.18 but that version
dies immediately after a imap4 connect with "Exit 11" -
as we are using ldap as database I thing that is related to that patch
http://hg.vergenet.net/perdition/perdition/rev/28264fe9e31b
so I tried to compile perdition 1.18 manually.
That fails with:
-DHAVE_CONFIG_H -I. -I.. -DPERDITION_LIBDIR=\"/opt/perdition180/lib\"
-DPERDITION_SYSCONFDIR=\"/opt/perdition180/etc/perdition\"
-DPERDITION_LOCALSTATEDIR=\"/opt/perdition180/var\" -I/usr/include
-g -O2 -MT perdition.o -MD -MP -MF .deps/perdition.Tpo -c -o perdition.o
perdition.c
perdition.c: In function »main«:
perdition.c:547: Warning: Zuweisung erzeugt Zeiger von Ganzzahl ohne
Typkonvertierung
perdition.c:712: Fehler: expected expression before »else«
perdition.c:950: Fehler: expected expression before »else«
perdition.c:998: Fehler: expected expression before »else«
make[3]: *** [perdition.o] Fehler 1
make[3]: Leaving directory `/root/perdition-1.18/perdition'
make[2]: *** [all-recursive] Fehler 1
make[2]: Leaving directory `/root/perdition-1.18/perdition'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/root/perdition-1.18'
make: *** [all] Fehler 2
Can somebody give me a hint please?
Strange. Are you sure that the source hasn't been mangled somehow?
How did you obtain the code?
7:52 a.m.
On Tue, 2010-06-01 at 08:31 +0200, Martin Hochreiter wrote:
May it be related to a CentOS 5.3 (64bit) problem?
very unlikely. i tried a compile on RHEL 5.5 x86_64 and it worked right
away.
the codes lines throwing errors are if/else conditions with calls to
VANESSA_LOGGER_ERR, so nothing special there.
did you check the configure run for any errors? especially concerning
the vanessa libs?
hth,
tom.
--
Thomas "Duke" Hager duke(a)sigsegv.at
GPG: 1024D/D27F858C http://www.sigsegv.at/gpg/duke.gpg
=================================================================
"Never Underestimate the Power of Stupid People in Large Groups."
9:24 a.m.
Am 2010-06-01 09:52, schrieb Thomas Hager:
On Tue, 2010-06-01 at 08:31 +0200, Martin Hochreiter
wrote:
I can not see any - I have the configure and make output enclosed,
I am not a specialist in compiling so maybe you can tell me more ...
regards
martin
May it be related to a CentOS 5.3 (64bit)
problem?
very unlikely. i tried a compile on RHEL 5.5 x86_64 and it worked right
away.
the codes lines throwing errors are if/else conditions with calls to
VANESSA_LOGGER_ERR, so nothing special there.
did you check the configure run for any errors? especially concerning
the vanessa libs?
hth,
tom.
10:36 a.m.
On Tue, 2010-06-01 at 11:24 +0200, Martin Hochreiter wrote:
I can not see any - I have the configure and make
output enclosed,
I am not a specialist in compiling so maybe you can tell me more ...
unfortunately
not. as far as i can tell everything looks sane.
your best option now is to send your perdition.c to simon, as he
suggested.
tom.
--
Thomas "Duke" Hager duke(a)sigsegv.at
GPG: 1024D/D27F858C http://www.sigsegv.at/gpg/duke.gpg
=================================================================
"Never Underestimate the Power of Stupid People in Large Groups."
8:37 a.m.
On Tue, Jun 01, 2010 at 08:31:55AM +0200, Martin Hochreiter wrote:
Am 2010-06-01 08:17, schrieb Simon Horman:
Possibly. Could you send me a copy of your perdition.c file as
an attachment? Off-list is fine.
On Mon, May 31, 2010 at 01:24:41PM +0200, Martin
Hochreiter wrote:
Hello Simon!
Thank you for your reply!
Thats my source:
http://www.vergenet.net/linux/perdition/download/1.18/perdition-1.18.tar.gz
I tried the mentioned ldap patch and I got an error and I downloaded and
extracted the source
again and tried it without the ldap patch ... same problem.
May it be related to a CentOS 5.3 (64bit) problem? Hi!
We are using perdition 1.17.1 on Centos 5.3 x64.
I tried to use the CentOS repo for updating to 1.18 but that version
dies immediately after a imap4 connect with "Exit 11" -
as we are using ldap as database I thing that is related to that patch
http://hg.vergenet.net/perdition/perdition/rev/28264fe9e31b
so I tried to compile perdition 1.18 manually.
That fails with:
-DHAVE_CONFIG_H -I. -I.. -DPERDITION_LIBDIR=\"/opt/perdition180/lib\"
-DPERDITION_SYSCONFDIR=\"/opt/perdition180/etc/perdition\"
-DPERDITION_LOCALSTATEDIR=\"/opt/perdition180/var\" -I/usr/include
-g -O2 -MT perdition.o -MD -MP -MF .deps/perdition.Tpo -c -o perdition.o
perdition.c
perdition.c: In function »main«:
perdition.c:547: Warning: Zuweisung erzeugt Zeiger von Ganzzahl ohne
Typkonvertierung
perdition.c:712: Fehler: expected expression before »else«
perdition.c:950: Fehler: expected expression before »else«
perdition.c:998: Fehler: expected expression before »else«
make[3]: *** [perdition.o] Fehler 1
make[3]: Leaving directory `/root/perdition-1.18/perdition'
make[2]: *** [all-recursive] Fehler 1
make[2]: Leaving directory `/root/perdition-1.18/perdition'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/root/perdition-1.18'
make: *** [all] Fehler 2
Can somebody give me a hint please?
Strange. Are you sure that the source hasn't been mangled somehow?
How did you obtain the code?
Or - another solution for us ... do you plan to
integrate the patch in
the CentOS RPMs?
(we use ldap as database and need the mailhost field ...)
Yes, but it may be faster for you to sort the build problem out.
9:25 a.m.
Possibly. Could you send me a copy of your perdition.c
file as
an attachment? Off-list is fine.
Hi Simon,
please find the files enclosed
Thank you for your help!
regards
Martin
Or - another solution for us ... do you plan to
integrate the patch in
the CentOS RPMs?
(we use ldap as database and need the mailhost field ...)
Yes, but it may be faster for you to sort the build problem out.
2 Jun
2 Jun
5:09 a.m.
On Tue, Jun 01, 2010 at 11:25:23AM +0200, Martin Hochreiter wrote:
Thanks.
I suspect that your installation of vanessa_logger is not the latest
version and that some macros provided by it are causing the problem
that you are seeing. Could you try the following patch for perdition.c ?
It should fix the build-errors that you are seeing, but I'm not sure
that the result will run as expected.
Index: perdition/perdition/perdition.c
===================================================================
--- perdition.orig/perdition/perdition.c 2010-06-02 14:05:21.000000000 +0900
+++ perdition/perdition/perdition.c 2010-06-02 14:06:01.000000000 +0900
@@ -704,15 +704,16 @@ int main (int argc, char **argv, char **
token_flush();
if(status<0){
VANESSA_LOGGER_DEBUG("protocol->in_get_pw");
- if (io_get_err(client_io) == io_err_timeout)
+ if (io_get_err(client_io) == io_err_timeout) {
VANESSA_LOGGER_ERR_UNSAFE("Fatal Error: Timeout reading "
"authentication information from "
"client%s: Exiting child",
from_to_host_str);
- else
+ } else {
VANESSA_LOGGER_ERR_UNSAFE("Fatal Error reading authentication "
"information from client%s: "
"Exiting child", from_to_host_str);
+ }
perdition_exit_cleanly(-1);
}
else if(status == 1){
@@ -944,11 +945,12 @@ int main (int argc, char **argv, char **
}
else if(status<0){
VANESSA_LOGGER_DEBUG_UNSAFE("protocol->out_authenticate %d", status);
- if (io_get_err(client_io) == io_err_timeout)
+ if (io_get_err(client_io) == io_err_timeout) {
VANESSA_LOGGER_ERR("Fatal error: Timeout authenticating user. "
"Exiting child.");
- else
+ } else {
VANESSA_LOGGER_ERR("Fatal error authenticating user. Exiting child.");
+ }
perdition_exit_cleanly(-1);
}
@@ -992,11 +994,12 @@ int main (int argc, char **argv, char **
if(io_pipe(server_io, client_io, buffer, BUFFER_SIZE,
&bytes_written, &bytes_read, &auth_log)<0){
VANESSA_LOGGER_DEBUG("vanessa_socket_pipe");
- if (io_get_err(client_io) == io_err_timeout)
+ if (io_get_err(client_io) == io_err_timeout) {
VANESSA_LOGGER_ERR("Fatal error: Timeout piping data. "
"Exiting child.");
- else
+ } else {
VANESSA_LOGGER_ERR("Fatal error piping data. Exiting child.");
+ }
perdition_exit_cleanly(-1);
}
Possibly. Could you send me a copy of your
perdition.c file as
an attachment? Off-list is fine.
Hi Simon,
please find the files enclosed Or - another solution for us ... do you plan to
integrate the patch in
the CentOS RPMs?
(we use ldap as database and need the mailhost field ...)
Yes, but it may be faster
for you to sort the build problem out.
7:32 a.m.
Thanks.
I suspect that your installation of vanessa_logger is not the latest
version and that some macros provided by it are causing the problem
that you are seeing. Could you try the following patch for perdition.c ?
It should fix the build-errors that you are seeing, but I'm not sure
that the result will run as expected.
Index: perdition/perdition/perdition.c
===================================================================
--- perdition.orig/perdition/perdition.c 2010-06-02 14:05:21.000000000 +0900
+++ perdition/perdition/perdition.c 2010-06-02 14:06:01.000000000 +0900
@@ -704,15 +704,16 @@ int main (int argc, char **argv, char **
token_flush();
if(status<0){
VANESSA_LOGGER_DEBUG("protocol->in_get_pw");
- if (io_get_err(client_io) == io_err_timeout)
+ if (io_get_err(client_io) == io_err_timeout) {
VANESSA_LOGGER_ERR_UNSAFE("Fatal Error: Timeout reading "
"authentication information from "
"client%s: Exiting child",
from_to_host_str);
- else
+ } else {
VANESSA_LOGGER_ERR_UNSAFE("Fatal Error reading authentication "
"information from client%s: "
"Exiting child", from_to_host_str);
+ }
perdition_exit_cleanly(-1);
}
else if(status == 1){
@@ -944,11 +945,12 @@ int main (int argc, char **argv, char **
}
else if(status<0){
VANESSA_LOGGER_DEBUG_UNSAFE("protocol->out_authenticate %d",
status);
- if (io_get_err(client_io) == io_err_timeout)
+ if (io_get_err(client_io) == io_err_timeout) {
VANESSA_LOGGER_ERR("Fatal error: Timeout authenticating user. "
"Exiting child.");
- else
+ } else {
VANESSA_LOGGER_ERR("Fatal error authenticating user. Exiting
child.");
+ }
perdition_exit_cleanly(-1);
}
@@ -992,11 +994,12 @@ int main (int argc, char **argv, char **
if(io_pipe(server_io, client_io, buffer, BUFFER_SIZE,
&bytes_written,&bytes_read,&auth_log)<0){
VANESSA_LOGGER_DEBUG("vanessa_socket_pipe");
- if (io_get_err(client_io) == io_err_timeout)
+ if (io_get_err(client_io) == io_err_timeout) {
VANESSA_LOGGER_ERR("Fatal error: Timeout piping data. "
"Exiting child.");
- else
+ } else {
VANESSA_LOGGER_ERR("Fatal error piping data. Exiting child.");
+ }
perdition_exit_cleanly(-1);
}
Hello Simon!
Thank you for the patch - as this is a production enviroment with over
3000 users, I don't
want to try the patch when you are unsure if it is working :)
To get further into troubleshooting - that are the rpm libaries of
vanessa - i think the
configure script of perdition will use them and they should be the most
recent versions, or am I wrong?
libvanessa_socket1-0.0.10-2.1
libvanessa_logger0-0.0.8-18.1
libvanessa_adt0-0.0.8-6.1
I can compile the vanessa stuff myself (in an alternative /opt/
directory) but I don't know
how to tell the perdition configure script to use them and not the rpm
ones - so maybe
you can help me here. That would enable me to compile perdition and
vanessa completely from sources.
So far I compiled logger and adt but the vanessa_socket also dies with:
[root@mailgw vanessa_socket-0.0.10]# make
make all-recursive
make[1]: Entering directory `/root/perdition-1.18/vanessa_socket-0.0.10'
Making all in libvanessa_socket
make[2]: Entering directory
`/root/perdition-1.18/vanessa_socket-0.0.10/libvanessa_socket'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I.. -g -O2 -MT vanessa_socket_client.lo -MD -MP -MF
.deps/vanessa_socket_client.Tpo -c -o vanessa_socket_client.lo
vanessa_socket_client.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT
vanessa_socket_client.lo -MD -MP -MF .deps/vanessa_socket_client.Tpo -c
vanessa_socket_client.c -fPIC -DPIC -o .libs/vanessa_socket_client.o
vanessa_socket_client.c: In function »vanessa_socket_client_src_open«:
vanessa_socket_client.c:200: Fehler: expected expression before »else«
vanessa_socket_client.c:221: Fehler: expected expression before »else«
make[2]: *** [vanessa_socket_client.lo] Fehler 1
make[2]: Leaving directory
`/root/perdition-1.18/vanessa_socket-0.0.10/libvanessa_socket'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/root/perdition-1.18/vanessa_socket-0.0.10'
make: *** [all] Fehler 2
Thank you for your help!
regards
martin
8:30 a.m.
Thanks.
I suspect that your installation of vanessa_logger is not the latest
version and that some macros provided by it are causing the problem
that you are seeing. Could you try the following patch for perdition.c ?
It should fix the build-errors that you are seeing, but I'm not sure
that the result will run as expected.
Index: perdition/perdition/perdition.c
===================================================================
--- perdition.orig/perdition/perdition.c 2010-06-02 14:05:21.000000000
+0900
+++ perdition/perdition/perdition.c 2010-06-02 14:06:01.000000000 +0900
@@ -704,15 +704,16 @@ int main (int argc, char **argv, char **
token_flush();
if(status<0){
VANESSA_LOGGER_DEBUG("protocol->in_get_pw");
- if (io_get_err(client_io) == io_err_timeout)
+ if (io_get_err(client_io) == io_err_timeout) {
VANESSA_LOGGER_ERR_UNSAFE("Fatal Error: Timeout reading "
"authentication information from "
"client%s: Exiting child",
from_to_host_str);
- else
+ } else {
VANESSA_LOGGER_ERR_UNSAFE("Fatal Error reading authentication "
"information from client%s: "
"Exiting child", from_to_host_str);
+ }
perdition_exit_cleanly(-1);
}
else if(status == 1){
@@ -944,11 +945,12 @@ int main (int argc, char **argv, char **
}
else if(status<0){
VANESSA_LOGGER_DEBUG_UNSAFE("protocol->out_authenticate %d",
status);
- if (io_get_err(client_io) == io_err_timeout)
+ if (io_get_err(client_io) == io_err_timeout) {
VANESSA_LOGGER_ERR("Fatal error: Timeout authenticating user. "
"Exiting child.");
- else
+ } else {
VANESSA_LOGGER_ERR("Fatal error authenticating user. Exiting
child.");
+ }
perdition_exit_cleanly(-1);
}
@@ -992,11 +994,12 @@ int main (int argc, char **argv, char **
if(io_pipe(server_io, client_io, buffer, BUFFER_SIZE,
&bytes_written,&bytes_read,&auth_log)<0){
VANESSA_LOGGER_DEBUG("vanessa_socket_pipe");
- if (io_get_err(client_io) == io_err_timeout)
+ if (io_get_err(client_io) == io_err_timeout) {
VANESSA_LOGGER_ERR("Fatal error: Timeout piping data. "
"Exiting child.");
- else
+ } else {
VANESSA_LOGGER_ERR("Fatal error piping data. Exiting child.");
+ }
perdition_exit_cleanly(-1);
}
Hello Simon!
Thank you for the patch - as this is a production enviroment with over
3000 users, I don't
want to try the patch when you are unsure if it is working :)
To get further into troubleshooting - that are the rpm libaries of
vanessa - i think the
configure script of perdition will use them and they should be the most
recent versions, or am I wrong?
libvanessa_socket1-0.0.10-2.1
libvanessa_logger0-0.0.8-18.1
libvanessa_adt0-0.0.8-6.1
I can compile the vanessa stuff myself (in an alternative /opt/
directory) but I don't know
how to tell the perdition configure script to use them and not the rpm
ones - so maybe
you can help me here. That would enable me to compile perdition and
vanessa completely from sources.
So far I compiled logger and adt but the vanessa_socket also dies with:
[root@mailgw vanessa_socket-0.0.10]# make
make all-recursive
make[1]: Entering directory `/root/perdition-1.18/vanessa_socket-0.0.10'
Making all in libvanessa_socket
make[2]: Entering directory
`/root/perdition-1.18/vanessa_socket-0.0.10/libvanessa_socket'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I.. -g -O2 -MT vanessa_socket_client.lo -MD -MP -MF
.deps/vanessa_socket_client.Tpo -c -o vanessa_socket_client.lo
vanessa_socket_client.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT
vanessa_socket_client.lo -MD -MP -MF .deps/vanessa_socket_client.Tpo -c
vanessa_socket_client.c -fPIC -DPIC -o .libs/vanessa_socket_client.o
vanessa_socket_client.c: In function »vanessa_socket_client_src_open«:
vanessa_socket_client.c:200: Fehler: expected expression before »else«
vanessa_socket_client.c:221: Fehler: expected expression before »else«
make[2]: *** [vanessa_socket_client.lo] Fehler 1
make[2]: Leaving directory
`/root/perdition-1.18/vanessa_socket-0.0.10/libvanessa_socket'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/root/perdition-1.18/vanessa_socket-0.0.10'
make: *** [all] Fehler 2
Thank you for your help!
regards
martin
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
9:42 a.m.
Maybe you first try it with unsetting LANG before
building. Sometimes
non
english language settings disturb things.
Regards,
Simon (another one)
Hi (other) Simon :)
nope - doesn't make any difference
whatever - thanks for the input
3 Jun
3 Jun
4:19 a.m.
On Wed, Jun 02, 2010 at 09:32:44AM +0200, Martin Hochreiter wrote:
Fair enough. But it would be interesting to see if it makes
the build problem go away.
Thanks.
I suspect that your installation of vanessa_logger is not the latest
version and that some macros provided by it are causing the problem
that you are seeing. Could you try the following patch for perdition.c ?
It should fix the build-errors that you are seeing, but I'm not sure
that the result will run as expected.
Index: perdition/perdition/perdition.c
===================================================================
--- perdition.orig/perdition/perdition.c 2010-06-02 14:05:21.000000000 +0900
+++ perdition/perdition/perdition.c 2010-06-02 14:06:01.000000000 +0900
@@ -704,15 +704,16 @@ int main (int argc, char **argv, char **
token_flush();
if(status<0){
VANESSA_LOGGER_DEBUG("protocol->in_get_pw");
- if (io_get_err(client_io) == io_err_timeout)
+ if (io_get_err(client_io) == io_err_timeout) {
VANESSA_LOGGER_ERR_UNSAFE("Fatal Error: Timeout reading "
"authentication information from "
"client%s: Exiting child",
from_to_host_str);
- else
+ } else {
VANESSA_LOGGER_ERR_UNSAFE("Fatal Error reading authentication "
"information from client%s: "
"Exiting child", from_to_host_str);
+ }
perdition_exit_cleanly(-1);
}
else if(status == 1){
@@ -944,11 +945,12 @@ int main (int argc, char **argv, char **
}
else if(status<0){
VANESSA_LOGGER_DEBUG_UNSAFE("protocol->out_authenticate %d",
status);
- if (io_get_err(client_io) == io_err_timeout)
+ if (io_get_err(client_io) == io_err_timeout) {
VANESSA_LOGGER_ERR("Fatal error: Timeout authenticating user. "
"Exiting child.");
- else
+ } else {
VANESSA_LOGGER_ERR("Fatal error authenticating user. Exiting
child.");
+ }
perdition_exit_cleanly(-1);
}
@@ -992,11 +994,12 @@ int main (int argc, char **argv, char **
if(io_pipe(server_io, client_io, buffer, BUFFER_SIZE,
&bytes_written,&bytes_read,&auth_log)<0){
VANESSA_LOGGER_DEBUG("vanessa_socket_pipe");
- if (io_get_err(client_io) == io_err_timeout)
+ if (io_get_err(client_io) == io_err_timeout) {
VANESSA_LOGGER_ERR("Fatal error: Timeout piping data. "
"Exiting child.");
- else
+ } else {
VANESSA_LOGGER_ERR("Fatal error piping data. Exiting child.");
+ }
perdition_exit_cleanly(-1);
}
Hello Simon!
Thank you for the patch - as this is a production enviroment with
over 3000 users, I don't
want to try the patch when you are unsure if it is working :) To get further into troubleshooting - that are the rpm
libaries of
vanessa - i think the
configure script of perdition will use them and they should be the
most recent versions, or am I wrong?
libvanessa_socket1-0.0.10-2.1
libvanessa_logger0-0.0.8-18.1
libvanessa_adt0-0.0.8-6.1
Those version should be fine.
I assume that you also have:
libvanessa_adt0-devel-0.0.8-6.1
libvanessa_logger0-devel-0.0.8-18.1
libvanessa_socket1-devel-0.0.10-2.1
Actually, I just tested building 1.18 against them on x86_64 CentOS and
it seemed to work out fine.
What I suspect is that there is another (older) version of
libvanessa_logger.h on the system and that this is being
used instead of the version that came with
libvanessa_logger0-devel-0.0.8-18.1 (/usr/include/vanessa_logger.h).
I can compile the vanessa stuff myself (in an
alternative /opt/
directory) but I don't know
how to tell the perdition configure script to use them and not the
rpm ones - so maybe
you can help me here. That would enable me to compile perdition and
vanessa completely from sources.
There isn't an easy way to tell perdition to prefer a particular directory
for those libraries.
So far I compiled logger and adt but the
vanessa_socket also dies with:
[root@mailgw vanessa_socket-0.0.10]# make
make all-recursive
make[1]: Entering directory `/root/perdition-1.18/vanessa_socket-0.0.10'
Making all in libvanessa_socket
make[2]: Entering directory
`/root/perdition-1.18/vanessa_socket-0.0.10/libvanessa_socket'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I.. -g -O2 -MT vanessa_socket_client.lo -MD -MP -MF
.deps/vanessa_socket_client.Tpo -c -o vanessa_socket_client.lo
vanessa_socket_client.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT
vanessa_socket_client.lo -MD -MP -MF .deps/vanessa_socket_client.Tpo
-c vanessa_socket_client.c -fPIC -DPIC -o
.libs/vanessa_socket_client.o
vanessa_socket_client.c: In function »vanessa_socket_client_src_open«:
vanessa_socket_client.c:200: Fehler: expected expression before »else«
vanessa_socket_client.c:221: Fehler: expected expression before »else«
make[2]: *** [vanessa_socket_client.lo] Fehler 1
make[2]: Leaving directory
`/root/perdition-1.18/vanessa_socket-0.0.10/libvanessa_socket'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/root/perdition-1.18/vanessa_socket-0.0.10'
make: *** [all] Fehler 2
This appears to be the same problem that you're having with compiling perdition.
4 Jun
4 Jun
8:47 a.m.
New subject: Perdition make error [build solved - but unusable]
Those version should be fine.
I assume that you also have:
libvanessa_adt0-devel-0.0.8-6.1
libvanessa_logger0-devel-0.0.8-18.1
libvanessa_socket1-devel-0.0.10-2.1
So, after purging the devel packets and reinstalling them the build works.
I have included the ldap - mailhost patch but perdition is not really
working -
can somebody tell me whats wrong with the "Exiting on signal 11"
messages please?
Jun 4 10:38:39 perdition[3175]: vanessa_socket_daemon_setid: uid=99
euid=99 gid=99 egid=99
Jun 4 10:38:47 perdition[3195]: Connect: 91.113.81.11->195.202.144.2
Jun 4 10:38:48 perdition[3195]: SSL connection using AES128-SHA
Jun 4 10:38:48 perdition[3195]: username_add_domain:
username_add_domain 0 1
Jun 4 10:38:48 perdition[3195]: Exiting on signal 11
Jun 4 10:38:48 perdition[3197]: Connect: 195.202.144.1->195.202.144.2
Jun 4 10:38:48 perdition[3197]: __perdition_ssl_connection: SSL_accept:
An EOF that violates the protocol has occurred
Jun 4 10:38:48 perdition[3197]: __perdition_ssl_connection: no shared
ciphers?
Jun 4 10:38:48 perdition[3197]: perdition_ssl_server_connection:
perdition_ssl_connection
Jun 4 10:38:48 perdition[3197]: main: perdition_ssl_server_connection SSL
Jun 4 10:38:48 perdition[3197]: Fatal error establishing SSL connection
to client
Jun 4 10:38:49 perdition[3198]: Connect: 91.113.81.11->195.202.144.2
Jun 4 10:38:49 perdition[3198]: SSL connection using AES128-SHA
Jun 4 10:38:49 perdition[3198]: username_add_domain:
username_add_domain 0 1
Jun 4 10:38:49 perdition[3198]: Exiting on signal 11
Jun 4 10:38:49 perdition[3199]: Connect: 91.113.81.11->195.202.144.2
Jun 4 10:38:49 perdition[3199]: SSL connection using AES128-SHA
Jun 4 10:38:49 perdition[3199]: username_add_domain:
username_add_domain 0 1
Jun 4 10:38:49 perdition[3199]: Exiting on signal 11
Jun 4 10:38:51 perdition[3200]: Connect: 85.127.17.0->195.202.144.2
Jun 4 10:38:51 perdition[3200]: SSL connection using AES128-SHA
Jun 4 10:38:51 perdition[3200]: username_add_domain:
username_add_domain 0 1
Jun 4 10:38:51 perdition[3200]: Exiting on signal 11
Jun 4 10:38:51 perdition[3201]: Connect: 85.127.17.0->195.202.144.2
Jun 4 10:38:51 perdition[3201]: SSL connection using AES128-SHA
Jun 4 10:38:51 perdition[3201]: username_add_domain:
username_add_domain 0 1
Jun 4 10:38:51 perdition[3201]: Exiting on signal 11
Jun 4 10:38:51 perdition[3202]: Connect: 85.127.17.0->195.202.144.2
Jun 4 10:38:51 perdition[3202]: SSL connection using AES128-SHA
Jun 4 10:38:51 perdition[3202]: username_add_domain:
username_add_domain 0 1
Jun 4 10:38:51 perdition[3202]: Exiting on signal 11
Jun 4 10:38:52 perdition[3203]: Connect: 93.82.45.20->195.202.144.2
Jun 4 10:38:52 perdition[3203]: SSL connection using AES256-SHA
Jun 4 10:38:52 perdition[3203]: username_add_domain:
username_add_domain 0 1
Jun 4 10:38:52 perdition[3203]: Exiting on signal 11
Jun 4 10:38:53 perdition[3214]: Connect: 195.202.144.1->195.202.144.2
Jun 4 10:38:53 perdition[3214]: SSL connection using AES128-SHA
Jun 4 10:38:53 perdition[3214]: username_add_domain:
username_add_domain 0 1
Jun 4 10:38:53 perdition[3214]: Exiting on signal 11
Jun 4 10:38:53 perdition[3215]: Connect: 195.202.144.1->195.202.144.2
Jun 4 10:38:53 perdition[3215]: SSL connection using AES128-SHA
Jun 4 10:38:53 perdition[3215]: username_add_domain:
username_add_domain 0 1
Jun 4 10:38:53 perdition[3215]: Exiting on signal 11
Jun 4 10:38:53 perdition[3216]: Connect: 195.202.144.1->195.202.144.2
Jun 4 10:38:53 perdition[3216]: SSL connection using AES128-SHA
Jun 4 10:38:53 perdition[3216]: username_add_domain:
username_add_domain 0 1
Jun 4 10:38:53 perdition[3216]: Exiting on signal 11
Jun 4 10:39:05 perdition[3222]: Connect: 94.198.57.158->195.202.144.2
Jun 4 10:39:05 perdition[3222]: SSL connection using AES128-SHA
Jun 4 10:39:05 perdition[3222]: username_add_domain:
username_add_domain 0 1
Jun 4 10:39:05 perdition[3222]: Exiting on signal 11
Jun 4 10:39:05 perdition[3223]: Connect: 94.198.57.158->195.202.144.2
Jun 4 10:39:05 perdition[3223]: SSL connection using AES128-SHA
Jun 4 10:39:05 perdition[3223]: username_add_domain:
username_add_domain 0 1
Jun 4 10:39:05 perdition[3223]: Exiting on signal 11
Jun 4 10:39:05 perdition[3224]: Connect: 94.198.57.158->195.202.144.2
Jun 4 10:39:05 perdition[3224]: SSL connection using AES128-SHA
Jun 4 10:39:06 perdition[3224]: username_add_domain:
username_add_domain 0 1
Jun 4 10:39:06 perdition[3224]: Exiting on signal 11
Jun 4 10:39:06 perdition[3225]: Connect: 195.202.144.1->195.202.144.2
Jun 4 10:39:06 perdition[3225]: SSL connection using AES256-SHA
Jun 4 10:39:06 perdition[3226]: Connect: 213.164.8.18->195.202.144.2
Jun 4 10:39:06 perdition[3225]: username_add_domain:
username_add_domain 0 1
Jun 4 10:39:06 perdition[3225]: Exiting on signal 11
Jun 4 10:39:06 perdition[3226]: SSL connection using AES128-SHA
Jun 4 10:39:06 perdition[3226]: username_add_domain:
username_add_domain 0 1
Jun 4 10:39:06 perdition[3226]: Exiting on signal 11
7 Jun
7 Jun
6:31 a.m.
New subject: Perdition make error [build solved - but unusable]
On Fri, Jun 04, 2010 at 10:47:06AM +0200, Martin Hochreiter wrote:
Hi Martin,
"Exiting on signal 11" indicates that there has been a segmentation fault.
Or in other words, an access to memory that doesn't belong to Perdition.
Or in other words, a bug.
If I was to debug this problem I would try and get perdition to dump a core
file, probably by setting ulimit -c unlimited and then running perdition
--no_daemon. I would then use gdb to inspect the core file to find out
where the segmentation fault occurred.
Those version should be fine.
I assume that you also have:
libvanessa_adt0-devel-0.0.8-6.1
libvanessa_logger0-devel-0.0.8-18.1
libvanessa_socket1-devel-0.0.10-2.1
So, after purging the devel packets and reinstalling them the build works.
I have included the ldap - mailhost patch but perdition is not
really working -
can somebody tell me whats wrong with the "Exiting on signal 11"
messages please?
8 Jun
8 Jun
12:44 p.m.
New subject: Perdition make error [build solved - but unusable]
Hi Martin,
"Exiting on signal 11" indicates that there has been a segmentation fault.
Or in other words, an access to memory that doesn't belong to Perdition.
Or in other words, a bug.
If I was to debug this problem I would try and get perdition to dump a core
file, probably by setting ulimit -c unlimited and then running perdition
--no_daemon. I would then use gdb to inspect the core file to find out
where the segmentation fault occurred.
Hi played around a little bit and it seems to be related to TLS connections
on "plaintext" ports
If you enable STARTTLS and the according conf options for pop3 and imap4
these connections get that "Exiting on signal 11" error.
If I comment them out the pop3 and imap4 connections are working.
Is there a chance to get that working again?
regards
martin
9 Jun
9 Jun
2:25 a.m.
New subject: Perdition make error [build solved - but unusable]
On Tue, Jun 08, 2010 at 02:44:40PM +0200, Martin Hochreiter wrote:
Hi Martin,
thanks for tracking that down. Could you send me you configuration details?
Hi Martin,
"Exiting on signal 11" indicates that there has been a segmentation fault.
Or in other words, an access to memory that doesn't belong to Perdition.
Or in other words, a bug.
If I was to debug this problem I would try and get perdition to dump a core
file, probably by setting ulimit -c unlimited and then running perdition
--no_daemon. I would then use gdb to inspect the core file to find out
where the segmentation fault occurred.
Hi played around a little bit and it seems to be related to TLS connections
on "plaintext" ports
If you enable STARTTLS and the according conf options for pop3 and imap4
these connections get that "Exiting on signal 11" error.
If I comment them out the pop3 and imap4 connections are working.
Is there a chance to get that working again?
6:18 a.m.
New subject: Perdition make error [build solved - but unusable]
Am 2010-06-09 04:25, schrieb Simon Horman:
Hi Martin,
thanks for tracking that down. Could you send me you configuration details?
sure - these are the imap4 and pop3 confs that NOT working
(as the imap4s and pop3s is working, i dont post them) :
####################################
# IMAP4
imap_capability "IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA ACL ACL2=UNION STARTTLS"
pid_file /var/run/perdition/perdition.imap4.pid
#
####################################
# SETTINGS
log_facility /var/log/perdition.imap4
connection_logging
#debug
#no_lookup
#
####################################
# LDAP
map_library /opt/perdition180/lib/libperditiondb_ldap.so.0
map_library_opt
ldap://127.0.0.1:389/ou=Users,dc=fh-stpoelten,dc=ac.at?uid,mailhost?sub?(uid=%25s)
#
####################################
# SSL
ssl_mode tls_listen
ssl_cert_file /etc/ssl/x_fhstp_ac_at.crt
ssl_key_file /etc/ssl/x_fhstp_ac_at.key
ssl_ca_path /etc/pki/tls/private/
ssl_ca_accept_self_signed
####################################
# POP3
pid_file /var/run/perdition/perdition.pop3.pid
#
####################################
# SETTINGS
log_facility /var/log/perdition.pop3
connection_logging
#debug
#no_lookup
#
####################################
# LDAP
map_library /opt/perdition180/lib/libperditiondb_ldap.so.0
map_library_opt
ldap://127.0.0.1:389/ou=Users,dc=fh-stpoelten,dc=ac.at?uid,mailhost?sub?(uid=%25s)
#
####################################
# SSL
ssl_mode tls_listen
ssl_cert_file /etc/ssl/x_fhstp_ac_at.crt
ssl_key_file /etc/ssl/x_fhstp_ac_at.key
5076
days inactive
5085
days old
18 comments
4 participants
participants (4)
-
Martin Hochreiter -
Simon Horman -
Simon Matter -
Thomas Hager