b-s error: "Failure when trying to send AMH reply; EFAULT"

[Hegner, Travis]

Hi All,

I apologize if this has been covered already, but I have been unable to find a solution. I have installed brutus-server 2.0.5, and compiled the latest brutus-keyring, and evolution-brutus from svn. I have configured e-b but when I try to connect I get the following message on the brutus-server log:
--------------------
< 13:49:10.748000 > .\BrutusLogOnS_impl.cpp:630 - Entering BRUTUS_BrutusLogOn_i::GetVersion()
< 13:49:10.748000 > .\BrutusLogOnS_impl.cpp:648 - Leaving BRUTUS_BrutusLogOn_i::GetVersion()
< 13:49:15.436000 > .\BrutusLogOnS_impl.cpp:677 - Attempting logon for MAPI profile "0e4543c2-2b78-11de-af4e-00044b02fbac"
< 13:49:15.436000 > .\BrutusLogOnS_impl.cpp:704 - Validating LifeLine object reference
< 13:49:15.436000 > .\BrutusLogOnS_impl.cpp:705 - IOR:010000002600000049444c3a6f6d632e6272757475732f4252555455532f427275747573436865636b3a312e30000000010000000000000070000000010102000a0000003132372e302e302e3100f00f2700000014010f004e555436a3e849150f0b0002000000010000004c5243410149180d02000000f402000a00020000000000000008000000011e3501004f41540100000014000000011e350101000105000000000901010000000000
< 13:49:36.567000 > .\BrutusLogOnS_impl.cpp:714 - system exception, ID 'IDL:omg.org/CORBA/NO_RESPONSE:1.0'
TAO exception, minor code = e (Failure when trying to send AMH reply; EFAULT), completed = NO
--------------------
< 13:49:56.166000 > .\BrutusLogOnS_impl.cpp:630 - Entering BRUTUS_BrutusLogOn_i::GetVersion()
< 13:49:56.166000 > .\BrutusLogOnS_impl.cpp:648 - Leaving BRUTUS_BrutusLogOn_i::GetVersion()
< 13:50:04.105000 > .\BrutusLogOnS_impl.cpp:677 - Attempting logon for MAPI profile "295767b2-2b78-11de-a02b-00044b02fbac"
< 13:50:04.199000 > .\BrutusLogOnS_impl.cpp:704 - Validating LifeLine object reference
< 13:50:04.199000 > .\BrutusLogOnS_impl.cpp:705 - IOR:010000002600000049444c3a6f6d632e6272757475732f4252555455532f427275747573436865636b3a312e30000000010000000000000070000000010102000a0000003132372e302e302e3100f00f2700000014010f004e555436a3e849150f0b0002000000010000004c5243410149180d01000000f402000a00020000000000000008000000011e3501004f41540100000014000000011e350101000105000000000901010000000000
< 13:50:25.408000 > .\BrutusLogOnS_impl.cpp:714 - system exception, ID 'IDL:omg.org/CORBA/NO_RESPONSE:1.0'
TAO exception, minor code = e (Failure when trying to send AMH reply; EFAULT), completed = NO
--------------------
I wasn't sure on the "Receiving Email" tab which "Server" should be configured, so the first log entry is with my exchange 2007 server configured, the second entry is with my brutus server configured. As you can see, the error is the same.

With brutus-server 2.0.5, I had to find an older version of msvcr90.dll, and msvcp90.dll, and modify the *.manifest files accordingly. Two of those files had the wrong version in them anyway, but even after correcting them, lorica would fail to start, stating in the windows event log that the manifest identity didn't match the identity of the component requested. After putting the older dll's in place, and modifying the manifest files accordingly, lorica and brutus started without error.

e-b/b-k: Ubuntu Intrepid AMD64
b-s/lorica: windows xp 32bit
exchange: 2007

I also manually modified the generated configure scripts to allow building from my lsb_release -sc, but I saw that someone already offered a patch for that on the list.

Any help is greatly appreciated!

Travis Hegner

[Jules Colding]

Hi Travis,

Post by Hegner, Travis
I apologize if this has been covered already, but I have been unable
to find a solution. I have installed brutus-server 2.0.5, and
compiled the latest brutus-keyring, and evolution-brutus from svn. I
have configured e-b but when I try to connect I get the following

<snip>

Post by Hegner, Travis
--------------------
I wasn't sure on the "Receiving Email" tab which "Server" should be
configured, so the first log entry is with my exchange 2007 server
configured, the second entry is with my brutus server configured. As
you can see, the error is the same.

It seems like the brutus server can't resolve your client. Please
install lorica on the client too and it should really work.

Post by Hegner, Travis
With brutus-server 2.0.5, I had to find an older version of
msvcr90.dll, and msvcp90.dll, and modify the *.manifest files
accordingly.

Ah, you seem to have downloaded 2.0.5 in the half hour windows when
the manifest files were wrong. Please download again and everything
should be good. Please let me know if it isn't!

Post by Hegner, Travis
Two of those files had the wrong version in them anyway, but even
after correcting them, lorica would fail to start, stating in the
windows event log that the manifest identity didn't match the
identity of the component requested. After putting the older dll's
in place, and modifying the manifest files accordingly, lorica and
brutus started without error.
e-b/b-k: Ubuntu Intrepid AMD64
b-s/lorica: windows xp 32bit
exchange: 2007
I also manually modified the generated configure scripts to allow
building from my lsb_release -sc, but I saw that someone already
offered a patch for that on the list.

Must have slipped passed my attention. Could you please tell me which
mail or send a new patch?

Thanks,
jules

[Hegner, Travis]

Hi Jules,

Thanks for the tip. I re-installed brutus server and was able to get e-b working on my laptop. I'm still getting the same error on my desktop, however, so I will attempt to build lorica.

I'm not sure why it works on one machine and not the other as they are both 64bit ubuntu intrepid. I may try the deb packages from my laptop on my desktop to see what happens as well.

brutus-keyring:
Index: release.sh
===================================================================
--- release.sh (revision 114)
+++ release.sh (working copy)
@@ -67,6 +67,12 @@
"hardy")
codename="Hardy"
;;
+ "intrepid")
+ codename="Intrepid"
+ ;;
+ "jaunty")
+ codename="Jaunty"
+ ;;
*)
echo "Unsupported Ubuntu release"
exit 1
Index: acinclude.m4
===================================================================
--- acinclude.m4 (revision 114)
+++ acinclude.m4 (working copy)
@@ -253,6 +253,12 @@
"hardy")
BRUTUS_DIST_RELEASE="Ubuntu%20Hardy"
;;
+ "intrepid")
+ BRUTUS_DIST_RELEASE="Ubuntu%20Intrepid"
+ ;;
+ "jaunty")
+ BRUTUS_DIST_RELEASE="Ubuntu%20Jaunty"
+ ;;
*)
AC_MSG_ERROR([[Unable to determine Ubuntu release]])
;;

evolution-brutus:
Index: release.sh
===================================================================
--- release.sh (revision 335)
+++ release.sh (working copy)
@@ -69,6 +69,12 @@
"hardy")
codename="Hardy"
;;
+ "intrepid")
+ codename="Intrepid"
+ ;;
+ "jaunty")
+ codename="Jaunty"
+ ;;
*)
echo "Unsupported Ubuntu release"
exit 1
Index: acinclude.m4
===================================================================
--- acinclude.m4 (revision 335)
+++ acinclude.m4 (working copy)
@@ -254,6 +254,12 @@
"hardy")
BRUTUS_DIST_RELEASE="Ubuntu%20Hardy"
;;
+ "intrepid")
+ BRUTUS_DIST_RELEASE="Ubuntu%20Intrepid"
+ ;;
+ "jaunty")
+ BRUTUS_DIST_RELEASE="Ubuntu%20Jaunty"
+ ;;
*)
AC_MSG_ERROR([[Unable to determine Ubuntu release]])
;;
@@ -403,6 +409,14 @@
LIBMAGICK='libmagick10'
LIBMAGICK_DEV='libmagick9-dev'
;;
+ "intrepid")
+ LIBMAGICK='libmagick10'
+ LIBMAGICK_DEV='libmagick9-dev'
+ ;;
+ "jaunty")
+ LIBMAGICK='libmagickwand1'
+ LIBMAGICK_DEV='libmagicwand-dev'
+ ;;
*)
AC_MSG_ERROR([[This Ubuntu release is not supported]])
;;

As you can see, I tossed the jaunty release in there as well since it is scheduled two days from now, but I have NOT YET TESTED building on Jaunty, so feel free to leave that out if you wish. I will test that sometime this week and let you know if it works.

I am still baffled as to why e-b works on my laptop without lorica, but not on my desktop… in the mean time I will work on building lorica, but do you have any other ideas as to what could cause that error. You mentioned something before about not being able to resolve the client, could you elaborate on that at all? I control all internal and external DNS (as well as everything else) for my environment, so I am pretty limitless when It comes to troubleshooting and testing.

The only other differences were that my laptop is off site, connected over a hardware vpn (seemingly local to the machine itself), but my desktop is on the same subnet as both the exchange server, and the brutus server. I am even using the same brutus-server for both clients.

Thanks again for all your support,

Travis

From: brutus-bounces-***@public.gmane.org [mailto:brutus-bounces-***@public.gmane.org] On Behalf Of Jules Colding
Sent: Monday, April 20, 2009 3:55 AM
To: brutus-list
Subject: Re: b-s error: "Failure when trying to send AMH reply; EFAULT"

Hi Travis,

On 17/04/2009, at 20.11, Hegner, Travis wrote:

I apologize if this has been covered already, but I have been unable to find a solution. I have installed brutus-server 2.0.5, and compiled the latest brutus-keyring, and evolution-brutus from svn. I have configured e-b but when I try to connect I get the following message on the brutus-server log:

<snip>

--------------------
I wasn't sure on the "Receiving Email" tab which "Server" should be configured, so the first log entry is with my exchange 2007 server configured, the second entry is with my brutus server configured. As you can see, the error is the same.

It seems like the brutus server can't resolve your client. Please install lorica on the client too and it should really work.





With brutus-server 2.0.5, I had to find an older version of msvcr90.dll, and msvcp90.dll, and modify the *.manifest files accordingly.


Ah, you seem to have downloaded 2.0.5 in the half hour windows when the manifest files were wrong. Please download again and everything should be good. Please let me know if it isn't!




Two of those files had the wrong version in them anyway, but even after correcting them, lorica would fail to start, stating in the windows event log that the manifest identity didn't match the identity of the component requested. After putting the older dll's in place, and modifying the manifest files accordingly, lorica and brutus started without error.

e-b/b-k: Ubuntu Intrepid AMD64
b-s/lorica: windows xp 32bit
exchange: 2007

I also manually modified the generated configure scripts to allow building from my lsb_release -sc, but I saw that someone already offered a patch for that on the list.

Must have slipped passed my attention. Could you please tell me which mail or send a new patch?

Thanks,
jules

[Jules Colding]

Hi Travis,

Post by Hegner, Travis
Hi Jules,
Thanks for the tip. I re-installed brutus server and was able to get
e-b working on my laptop. I'm still getting the same error on my
desktop, however, so I will attempt to build lorica.
I'm not sure why it works on one machine and not the other as they
are both 64bit ubuntu intrepid. I may try the deb packages from my
laptop on my desktop to see what happens as well.

Do tell me if you find an error to be fixed.

Post by Hegner, Travis
Index: release.sh
===================================================================
--- release.sh (revision 114)
+++ release.sh (working copy)
@@ -67,6 +67,12 @@
"hardy")
codename="Hardy"
;;
+ "intrepid")
+ codename="Intrepid"
+ ;;
+ "jaunty")
+ codename="Jaunty"
+ ;;
*)
echo "Unsupported Ubuntu release"
exit 1
Index: acinclude.m4
===================================================================
--- acinclude.m4 (revision 114)
+++ acinclude.m4 (working copy)
@@ -253,6 +253,12 @@
"hardy")
BRUTUS_DIST_RELEASE="Ubuntu%20Hardy"
;;
+ "intrepid")
+
BRUTUS_DIST_RELEASE="Ubuntu%20Intrepid"
+ ;;
+ "jaunty")
+
BRUTUS_DIST_RELEASE="Ubuntu%20Jaunty"
+ ;;
*)
AC_MSG_ERROR([[Unable to determine Ubuntu release]])
;;
Index: release.sh
===================================================================
--- release.sh (revision 335)
+++ release.sh (working copy)
@@ -69,6 +69,12 @@
"hardy")
codename="Hardy"
;;
+ "intrepid")
+ codename="Intrepid"
+ ;;
+ "jaunty")
+ codename="Jaunty"
+ ;;
*)
echo "Unsupported Ubuntu release"
exit 1
Index: acinclude.m4
===================================================================
--- acinclude.m4 (revision 335)
+++ acinclude.m4 (working copy)
@@ -254,6 +254,12 @@
"hardy")
BRUTUS_DIST_RELEASE="Ubuntu%20Hardy"
;;
+ "intrepid")
+
BRUTUS_DIST_RELEASE="Ubuntu%20Intrepid"
+ ;;
+ "jaunty")
+
BRUTUS_DIST_RELEASE="Ubuntu%20Jaunty"
+ ;;
*)
AC_MSG_ERROR([[Unable to determine Ubuntu release]])
;;
@@ -403,6 +409,14 @@
LIBMAGICK='libmagick10'
LIBMAGICK_DEV='libmagick9-dev'
;;
+ "intrepid")
+ LIBMAGICK='libmagick10'
+ LIBMAGICK_DEV='libmagick9-dev'
+ ;;
+ "jaunty")
+ LIBMAGICK='libmagickwand1'
+ LIBMAGICK_DEV='libmagicwand-dev'
+ ;;
*)
AC_MSG_ERROR([[This Ubuntu release is not supported]])
;;
As you can see, I tossed the jaunty release in there as well since
it is scheduled two days from now, but I have NOT YET TESTED
building on Jaunty, so feel free to leave that out if you wish. I
will test that sometime this week and let you know if it works.

Both applied. Thanks!

Post by Hegner, Travis
I am still baffled as to why e-b works on my laptop without lorica,
but not on my desktop…

Most likely a DNS or routing issue...

Post by Hegner, Travis
in the mean time I will work on building lorica, but do you have any
other ideas as to what could cause that error. You mentioned
something before about not being able to resolve the client, could
you elaborate on that at all? I control all internal and external
DNS (as well as everything else) for my environment, so I am pretty
limitless when It comes to troubleshooting and testing.

The client must be routable from the server.

Post by Hegner, Travis
The only other differences were that my laptop is off site,
connected over a hardware vpn (seemingly local to the machine
itself), but my desktop is on the same subnet as both the exchange
server, and the brutus server. I am even using the same brutus-
server for both clients.

I'll bet a fair share of my right arm that your vpn NIC isn't the one
which e-b thinks is the NIC to use when contacting the server. You
should use lorica. It really should resolve this for you.

Best,
jules

[Hegner, Travis]

Well, the laptop itself does not use any vpn software, I have a router that does that for me, so for all intents and purposes, the laptop is local to both the brutus, and exchange servers, just on a different subnet. But, aside from those facts the laptop is the one that works, even without lorica.

It's the desktop that doesn't work. Although it just dawned on me that I am using vlans on my desktop, with a crazy mixture of virtual, physical, and sub intervaces, as well as vmware workstation, and all the crazy network 'enhancements' it uses, so e-b could be using the wrong interface from that perspective.

Lorica should solve this for me?

From: brutus-bounces-***@public.gmane.org [mailto:brutus-bounces-***@public.gmane.org] On Behalf Of Jules Colding
Sent: Tuesday, April 21, 2009 10:34 AM
To: brutus-list
Subject: Re: b-s error: "Failure when trying to send AMH reply; EFAULT"

Hi Travis,

On 21/04/2009, at 16.21, Hegner, Travis wrote:


Hi Jules,

Thanks for the tip. I re-installed brutus server and was able to get e-b working on my laptop. I'm still getting the same error on my desktop, however, so I will attempt to build lorica.

I'm not sure why it works on one machine and not the other as they are both 64bit ubuntu intrepid. I may try the deb packages from my laptop on my desktop to see what happens as well.

Do tell me if you find an error to be fixed.



brutus-keyring:
Index: release.sh
===================================================================
--- release.sh (revision 114)
+++ release.sh (working copy)
@@ -67,6 +67,12 @@
"hardy")
codename="Hardy"
;;
+ "intrepid")
+ codename="Intrepid"
+ ;;
+ "jaunty")
+ codename="Jaunty"
+ ;;
*)
echo "Unsupported Ubuntu release"
exit 1
Index: acinclude.m4
===================================================================
--- acinclude.m4 (revision 114)
+++ acinclude.m4 (working copy)
@@ -253,6 +253,12 @@
"hardy")
BRUTUS_DIST_RELEASE="Ubuntu%20Hardy"
;;
+ "intrepid")
+ BRUTUS_DIST_RELEASE="Ubuntu%20Intrepid"
+ ;;
+ "jaunty")
+ BRUTUS_DIST_RELEASE="Ubuntu%20Jaunty"
+ ;;
*)
AC_MSG_ERROR([[Unable to determine Ubuntu release]])
;;

evolution-brutus:
Index: release.sh
===================================================================
--- release.sh (revision 335)
+++ release.sh (working copy)
@@ -69,6 +69,12 @@
"hardy")
codename="Hardy"
;;
+ "intrepid")
+ codename="Intrepid"
+ ;;
+ "jaunty")
+ codename="Jaunty"
+ ;;
*)
echo "Unsupported Ubuntu release"
exit 1
Index: acinclude.m4
===================================================================
--- acinclude.m4 (revision 335)
+++ acinclude.m4 (working copy)
@@ -254,6 +254,12 @@
"hardy")
BRUTUS_DIST_RELEASE="Ubuntu%20Hardy"
;;
+ "intrepid")
+ BRUTUS_DIST_RELEASE="Ubuntu%20Intrepid"
+ ;;
+ "jaunty")
+ BRUTUS_DIST_RELEASE="Ubuntu%20Jaunty"
+ ;;
*)
AC_MSG_ERROR([[Unable to determine Ubuntu release]])
;;
@@ -403,6 +409,14 @@
LIBMAGICK='libmagick10'
LIBMAGICK_DEV='libmagick9-dev'
;;
+ "intrepid")
+ LIBMAGICK='libmagick10'
+ LIBMAGICK_DEV='libmagick9-dev'
+ ;;
+ "jaunty")
+ LIBMAGICK='libmagickwand1'
+ LIBMAGICK_DEV='libmagicwand-dev'
+ ;;
*)
AC_MSG_ERROR([[This Ubuntu release is not supported]])
;;

As you can see, I tossed the jaunty release in there as well since it is scheduled two days from now, but I have NOT YET TESTED building on Jaunty, so feel free to leave that out if you wish. I will test that sometime this week and let you know if it works.

Both applied. Thanks!




I am still baffled as to why e-b works on my laptop without lorica, but not on my desktop…

Most likely a DNS or routing issue...



in the mean time I will work on building lorica, but do you have any other ideas as to what could cause that error. You mentioned something before about not being able to resolve the client, could you elaborate on that at all? I control all internal and external DNS (as well as everything else) for my environment, so I am pretty limitless when It comes to troubleshooting and testing.

The client must be routable from the server.



The only other differences were that my laptop is off site, connected over a hardware vpn (seemingly local to the machine itself), but my desktop is on the same subnet as both the exchange server, and the brutus server. I am even using the same brutus-server for both clients.


I'll bet a fair share of my right arm that your vpn NIC isn't the one which e-b thinks is the NIC to use when contacting the server. You should use lorica. It really should resolve this for you.

Best,
jules

[Jules Colding]

Post by Hegner, Travis
Well, the laptop itself does not use any vpn software, I have a
router that does that for me, so for all intents and purposes, the
laptop is local to both the brutus, and exchange servers, just on a
different subnet. But, aside from those facts the laptop is the one
that works, even without lorica.
It's the desktop that doesn't work. Although it just dawned on me
that I am using vlans on my desktop, with a crazy mixture of
virtual, physical, and sub intervaces, as well as vmware
workstation, and all the crazy network 'enhancements' it uses, so e-
b could be using the wrong interface from that perspective.
Lorica should solve this for me?

In short, yes. Lorica will create kind of a client-server tunnel which
will do vpn-ish tricks to make everything work.

Best,
jules

Post by Hegner, Travis
On Behalf Of Jules Colding
Sent: Tuesday, April 21, 2009 10:34 AM
To: brutus-list
Subject: Re: b-s error: "Failure when trying to send AMH reply; EFAULT"
Hi Travis,
Hi Jules,
Thanks for the tip. I re-installed brutus server and was able to get
e-b working on my laptop. I'm still getting the same error on my
desktop, however, so I will attempt to build lorica.
I'm not sure why it works on one machine and not the other as they
are both 64bit ubuntu intrepid. I may try the deb packages from my
laptop on my desktop to see what happens as well.
Do tell me if you find an error to be fixed.
Index: release.sh
===================================================================
--- release.sh (revision 114)
+++ release.sh (working copy)
@@ -67,6 +67,12 @@
"hardy")
codename="Hardy"
;;
+ "intrepid")
+ codename="Intrepid"
+ ;;
+ "jaunty")
+ codename="Jaunty"
+ ;;
*)
echo "Unsupported Ubuntu release"
exit 1
Index: acinclude.m4
===================================================================
--- acinclude.m4 (revision 114)
+++ acinclude.m4 (working copy)
@@ -253,6 +253,12 @@
"hardy")
BRUTUS_DIST_RELEASE="Ubuntu%20Hardy"
;;
+ "intrepid")
+
BRUTUS_DIST_RELEASE="Ubuntu%20Intrepid"
+ ;;
+ "jaunty")
+
BRUTUS_DIST_RELEASE="Ubuntu%20Jaunty"
+ ;;
*)
AC_MSG_ERROR([[Unable to determine Ubuntu release]])
;;
Index: release.sh
===================================================================
--- release.sh (revision 335)
+++ release.sh (working copy)
@@ -69,6 +69,12 @@
"hardy")
codename="Hardy"
;;
+ "intrepid")
+ codename="Intrepid"
+ ;;
+ "jaunty")
+ codename="Jaunty"
+ ;;
*)
echo "Unsupported Ubuntu release"
exit 1
Index: acinclude.m4
===================================================================
--- acinclude.m4 (revision 335)
+++ acinclude.m4 (working copy)
@@ -254,6 +254,12 @@
"hardy")
BRUTUS_DIST_RELEASE="Ubuntu%20Hardy"
;;
+ "intrepid")
+
BRUTUS_DIST_RELEASE="Ubuntu%20Intrepid"
+ ;;
+ "jaunty")
+
BRUTUS_DIST_RELEASE="Ubuntu%20Jaunty"
+ ;;
*)
AC_MSG_ERROR([[Unable to determine Ubuntu release]])
;;
@@ -403,6 +409,14 @@
LIBMAGICK='libmagick10'
LIBMAGICK_DEV='libmagick9-dev'
;;
+ "intrepid")
+ LIBMAGICK='libmagick10'
+ LIBMAGICK_DEV='libmagick9-dev'
+ ;;
+ "jaunty")
+ LIBMAGICK='libmagickwand1'
+ LIBMAGICK_DEV='libmagicwand-dev'
+ ;;
*)
AC_MSG_ERROR([[This Ubuntu release is not supported]])
;;
As you can see, I tossed the jaunty release in there as well since
it is scheduled two days from now, but I have NOT YET TESTED
building on Jaunty, so feel free to leave that out if you wish. I
will test that sometime this week and let you know if it works.
Both applied. Thanks!
I am still baffled as to why e-b works on my laptop without lorica, but not on my desktop…
Most likely a DNS or routing issue...
in the mean time I will work on building lorica, but do you have any
other ideas as to what could cause that error. You mentioned
something before about not being able to resolve the client, could
you elaborate on that at all? I control all internal and external
DNS (as well as everything else) for my environment, so I am pretty
limitless when It comes to troubleshooting and testing.
The client must be routable from the server.
The only other differences were that my laptop is off site,
connected over a hardware vpn (seemingly local to the machine
itself), but my desktop is on the same subnet as both the exchange
server, and the brutus server. I am even using the same brutus-
server for both clients.
I'll bet a fair share of my right arm that your vpn NIC isn't the
one which e-b thinks is the NIC to use when contacting the server.
You should use lorica. It really should resolve this for you.
Best,
jules
_______________________________________________
brutus mailing list
http://www.42tools.com/mailman/listinfo/brutus

[Hegner, Travis]

Good Day All,

I have been working to build lorica from source on Ubuntu Intrepid. So far here are the patches I have made to get as far as I am. I don't know if these changes will break other dists, but I'll provide them anyway:

Index: m4/platform_adapt.m4
===================================================================
--- m4/platform_adapt.m4 (revision 520)
+++ m4/platform_adapt.m4 (working copy)
@@ -266,6 +266,12 @@
"xhardy")
LORICA_DIST_RELEASE="Ubuntu%20Hardy"
;;
+ "xintrepid")
+ LORICA_DIST_RELEASE="Ubuntu%20Intrepid"
+ ;;
+ "xjaunty")
+ LORICA_DIST_RELEASE="Ubuntu%20Jaunty"
+ ;;
*)
AC_MSG_ERROR([[Unable to determine Ubuntu release]])
;;
Index: src/lorica/ConfigBase.cpp
===================================================================
--- src/lorica/ConfigBase.cpp (revision 520)
+++ src/lorica/ConfigBase.cpp (working copy)
@@ -562,7 +562,7 @@
ACE_ARGV*
Lorica::Config::get_ifr_options(const bool Debug)
{
- if (Debug)
+ if (Debug) {}
; // kill compiler warning

if (ifr_args_.size() > 0)
Index: release.sh
===================================================================
--- release.sh (revision 520)
+++ release.sh (working copy)
@@ -81,6 +81,12 @@
"hardy")
codename="Hardy"
;;
+ "intrepid")
+ codename="Intrepid"
+ ;;
+ "jaunty")
+ codename="Jaunty"
+ ;;
*)
echo "Unsupported Ubuntu release"
exit 1
Index: tests/fileConfig/main.cpp
===================================================================
--- tests/fileConfig/main.cpp (revision 520)
+++ tests/fileConfig/main.cpp (working copy)
@@ -23,6 +23,7 @@

#include <string>
#include <iostream>
+#include <memory>

int main (int, char *[])
{

Once again, the jaunty info is just kind of tossed in there and I have not yet tested building on that dist. I'm hoping someone can shed some light as I'm kind of stuck at this point. "make" is successful, "make dist" is also successful, but "make dist-deb-bin" dies at the following error.

cp /home/thegner/tools/lorica/deb/lorica-1.0.13/support_files/brutus/ifr.cache /home/thegner/tools/lorica/deb/lorica-1.0.13/ifr.cache
cp: cannot stat `/home/thegner/tools/lorica/deb/lorica-1.0.13/support_files/brutus/ifr.cache': No such file or directory

I have tried various things like copying the "support_files" dir from ~/tools/lorica/support_files, to the missing "support_files" location, but then I get errors that the binary data has changed on all the files within. My assumption is that the directory, and subsequent files are supposed to be auto-generated, but I'm not sure from where. If someone could point me in the right direction, I would be most appreciative, and, of course, will provide a patch back.

Thanks,

Travis

From: brutus-bounces-***@public.gmane.org [mailto:brutus-bounces-***@public.gmane.org] On Behalf Of Jules Colding
Sent: Wednesday, April 22, 2009 3:24 AM
To: brutus-list
Subject: Re: b-s error: "Failure when trying to send AMH reply; EFAULT"


On 21/04/2009, at 16.45, Hegner, Travis wrote:


Well, the laptop itself does not use any vpn software, I have a router that does that for me, so for all intents and purposes, the laptop is local to both the brutus, and exchange servers, just on a different subnet. But, aside from those facts the laptop is the one that works, even without lorica.

It's the desktop that doesn't work. Although it just dawned on me that I am using vlans on my desktop, with a crazy mixture of virtual, physical, and sub intervaces, as well as vmware workstation, and all the crazy network 'enhancements' it uses, so e-b could be using the wrong interface from that perspective.

Lorica should solve this for me?

In short, yes. Lorica will create kind of a client-server tunnel which will do vpn-ish tricks to make everything work.

Best,
jules





From: brutus-bounces-***@public.gmane.org<mailto:brutus-bounces-***@public.gmane.org> [mailto:brutus-bounces-***@public.gmane.org] On Behalf Of Jules Colding
Sent: Tuesday, April 21, 2009 10:34 AM
To: brutus-list
Subject: Re: b-s error: "Failure when trying to send AMH reply; EFAULT"

Hi Travis,

On 21/04/2009, at 16.21, Hegner, Travis wrote:



Hi Jules,

Thanks for the tip. I re-installed brutus server and was able to get e-b working on my laptop. I'm still getting the same error on my desktop, however, so I will attempt to build lorica.

I'm not sure why it works on one machine and not the other as they are both 64bit ubuntu intrepid. I may try the deb packages from my laptop on my desktop to see what happens as well.

Do tell me if you find an error to be fixed.




brutus-keyring:
Index: release.sh
===================================================================
--- release.sh (revision 114)
+++ release.sh (working copy)
@@ -67,6 +67,12 @@
"hardy")
codename="Hardy"
;;
+ "intrepid")
+ codename="Intrepid"
+ ;;
+ "jaunty")
+ codename="Jaunty"
+ ;;
*)
echo "Unsupported Ubuntu release"
exit 1
Index: acinclude.m4
===================================================================
--- acinclude.m4 (revision 114)
+++ acinclude.m4 (working copy)
@@ -253,6 +253,12 @@
"hardy")
BRUTUS_DIST_RELEASE="Ubuntu%20Hardy"
;;
+ "intrepid")
+ BRUTUS_DIST_RELEASE="Ubuntu%20Intrepid"
+ ;;
+ "jaunty")
+ BRUTUS_DIST_RELEASE="Ubuntu%20Jaunty"
+ ;;
*)
AC_MSG_ERROR([[Unable to determine Ubuntu release]])
;;

evolution-brutus:
Index: release.sh
===================================================================
--- release.sh (revision 335)
+++ release.sh (working copy)
@@ -69,6 +69,12 @@
"hardy")
codename="Hardy"
;;
+ "intrepid")
+ codename="Intrepid"
+ ;;
+ "jaunty")
+ codename="Jaunty"
+ ;;
*)
echo "Unsupported Ubuntu release"
exit 1
Index: acinclude.m4
===================================================================
--- acinclude.m4 (revision 335)
+++ acinclude.m4 (working copy)
@@ -254,6 +254,12 @@
"hardy")
BRUTUS_DIST_RELEASE="Ubuntu%20Hardy"
;;
+ "intrepid")
+ BRUTUS_DIST_RELEASE="Ubuntu%20Intrepid"
+ ;;
+ "jaunty")
+ BRUTUS_DIST_RELEASE="Ubuntu%20Jaunty"
+ ;;
*)
AC_MSG_ERROR([[Unable to determine Ubuntu release]])
;;
@@ -403,6 +409,14 @@
LIBMAGICK='libmagick10'
LIBMAGICK_DEV='libmagick9-dev'
;;
+ "intrepid")
+ LIBMAGICK='libmagick10'
+ LIBMAGICK_DEV='libmagick9-dev'
+ ;;
+ "jaunty")
+ LIBMAGICK='libmagickwand1'
+ LIBMAGICK_DEV='libmagicwand-dev'
+ ;;
*)
AC_MSG_ERROR([[This Ubuntu release is not supported]])
;;

As you can see, I tossed the jaunty release in there as well since it is scheduled two days from now, but I have NOT YET TESTED building on Jaunty, so feel free to leave that out if you wish. I will test that sometime this week and let you know if it works.

Both applied. Thanks!





I am still baffled as to why e-b works on my laptop without lorica, but not on my desktop…

Most likely a DNS or routing issue...




in the mean time I will work on building lorica, but do you have any other ideas as to what could cause that error. You mentioned something before about not being able to resolve the client, could you elaborate on that at all? I control all internal and external DNS (as well as everything else) for my environment, so I am pretty limitless when It comes to troubleshooting and testing.

The client must be routable from the server.




The only other differences were that my laptop is off site, connected over a hardware vpn (seemingly local to the machine itself), but my desktop is on the same subnet as both the exchange server, and the brutus server. I am even using the same brutus-server for both clients.


I'll bet a fair share of my right arm that your vpn NIC isn't the one which e-b thinks is the NIC to use when contacting the server. You should use lorica. It really should resolve this for you.

Best,
jules

[Hegner, Travis]

Index: acinclude.m4
===================================================================
--- acinclude.m4 (revision 336)
+++ acinclude.m4 (working copy)
@@ -415,7 +415,7 @@
;;
"jaunty")
LIBMAGICK='libmagickwand1'
- LIBMAGICK_DEV='libmagicwand-dev'
+ LIBMAGICK_DEV='libmagickwand-dev'
;;
*)
AC_MSG_ERROR([[This Ubuntu release is not supported]])

After this fix from the typo of my original patch, then brutus-keyring, and evolution-brutus both build successfully on both intrepid and jaunty.

In Jaunty, however, I have a strange issue where the connection is made, and I can see the public folders without issue, but my mailbox shows up as just a folder icon with no text, and I can't access any of the information in it.

At least it builds and installs! :)

I have not yet tried the lorica client in jaunty.

Travis

From: brutus-bounces-***@public.gmane.org [mailto:brutus-bounces-***@public.gmane.org] On Behalf Of Hegner, Travis
Sent: Wednesday, April 22, 2009 10:01 AM
To: brutus-list
Subject: RE: b-s error: "Failure when trying to send AMH reply; EFAULT"

Good Day All,

I have been working to build lorica from source on Ubuntu Intrepid. So far here are the patches I have made to get as far as I am. I don't know if these changes will break other dists, but I'll provide them anyway:

Index: m4/platform_adapt.m4
===================================================================
--- m4/platform_adapt.m4 (revision 520)
+++ m4/platform_adapt.m4 (working copy)
@@ -266,6 +266,12 @@
"xhardy")
LORICA_DIST_RELEASE="Ubuntu%20Hardy"
;;
+ "xintrepid")
+ LORICA_DIST_RELEASE="Ubuntu%20Intrepid"
+ ;;
+ "xjaunty")
+ LORICA_DIST_RELEASE="Ubuntu%20Jaunty"
+ ;;
*)
AC_MSG_ERROR([[Unable to determine Ubuntu release]])
;;
Index: src/lorica/ConfigBase.cpp
===================================================================
--- src/lorica/ConfigBase.cpp (revision 520)
+++ src/lorica/ConfigBase.cpp (working copy)
@@ -562,7 +562,7 @@
ACE_ARGV*
Lorica::Config::get_ifr_options(const bool Debug)
{
- if (Debug)
+ if (Debug) {}
; // kill compiler warning

if (ifr_args_.size() > 0)
Index: release.sh
===================================================================
--- release.sh (revision 520)
+++ release.sh (working copy)
@@ -81,6 +81,12 @@
"hardy")
codename="Hardy"
;;
+ "intrepid")
+ codename="Intrepid"
+ ;;
+ "jaunty")
+ codename="Jaunty"
+ ;;
*)
echo "Unsupported Ubuntu release"
exit 1
Index: tests/fileConfig/main.cpp
===================================================================
--- tests/fileConfig/main.cpp (revision 520)
+++ tests/fileConfig/main.cpp (working copy)
@@ -23,6 +23,7 @@

#include <string>
#include <iostream>
+#include <memory>

int main (int, char *[])
{

Once again, the jaunty info is just kind of tossed in there and I have not yet tested building on that dist. I'm hoping someone can shed some light as I'm kind of stuck at this point. "make" is successful, "make dist" is also successful, but "make dist-deb-bin" dies at the following error.

cp /home/thegner/tools/lorica/deb/lorica-1.0.13/support_files/brutus/ifr.cache /home/thegner/tools/lorica/deb/lorica-1.0.13/ifr.cache
cp: cannot stat `/home/thegner/tools/lorica/deb/lorica-1.0.13/support_files/brutus/ifr.cache': No such file or directory

I have tried various things like copying the "support_files" dir from ~/tools/lorica/support_files, to the missing "support_files" location, but then I get errors that the binary data has changed on all the files within. My assumption is that the directory, and subsequent files are supposed to be auto-generated, but I'm not sure from where. If someone could point me in the right direction, I would be most appreciative, and, of course, will provide a patch back.

Thanks,

Travis

From: brutus-bounces-***@public.gmane.org [mailto:brutus-bounces-***@public.gmane.org] On Behalf Of Jules Colding
Sent: Wednesday, April 22, 2009 3:24 AM
To: brutus-list
Subject: Re: b-s error: "Failure when trying to send AMH reply; EFAULT"


On 21/04/2009, at 16.45, Hegner, Travis wrote:

Well, the laptop itself does not use any vpn software, I have a router that does that for me, so for all intents and purposes, the laptop is local to both the brutus, and exchange servers, just on a different subnet. But, aside from those facts the laptop is the one that works, even without lorica.

It's the desktop that doesn't work. Although it just dawned on me that I am using vlans on my desktop, with a crazy mixture of virtual, physical, and sub intervaces, as well as vmware workstation, and all the crazy network 'enhancements' it uses, so e-b could be using the wrong interface from that perspective.

Lorica should solve this for me?

In short, yes. Lorica will create kind of a client-server tunnel which will do vpn-ish tricks to make everything work.

Best,
jules




From: brutus-bounces-***@public.gmane.org<mailto:brutus-bounces-***@public.gmane.org> [mailto:brutus-bounces-***@public.gmane.org] On Behalf Of Jules Colding
Sent: Tuesday, April 21, 2009 10:34 AM
To: brutus-list
Subject: Re: b-s error: "Failure when trying to send AMH reply; EFAULT"

Hi Travis,

On 21/04/2009, at 16.21, Hegner, Travis wrote:


Hi Jules,

Thanks for the tip. I re-installed brutus server and was able to get e-b working on my laptop. I'm still getting the same error on my desktop, however, so I will attempt to build lorica.

I'm not sure why it works on one machine and not the other as they are both 64bit ubuntu intrepid. I may try the deb packages from my laptop on my desktop to see what happens as well.

Do tell me if you find an error to be fixed.



brutus-keyring:
Index: release.sh
===================================================================
--- release.sh (revision 114)
+++ release.sh (working copy)
@@ -67,6 +67,12 @@
"hardy")
codename="Hardy"
;;
+ "intrepid")
+ codename="Intrepid"
+ ;;
+ "jaunty")
+ codename="Jaunty"
+ ;;
*)
echo "Unsupported Ubuntu release"
exit 1
Index: acinclude.m4
===================================================================
--- acinclude.m4 (revision 114)
+++ acinclude.m4 (working copy)
@@ -253,6 +253,12 @@
"hardy")
BRUTUS_DIST_RELEASE="Ubuntu%20Hardy"
;;
+ "intrepid")
+ BRUTUS_DIST_RELEASE="Ubuntu%20Intrepid"
+ ;;
+ "jaunty")
+ BRUTUS_DIST_RELEASE="Ubuntu%20Jaunty"
+ ;;
*)
AC_MSG_ERROR([[Unable to determine Ubuntu release]])
;;

evolution-brutus:
Index: release.sh
===================================================================
--- release.sh (revision 335)
+++ release.sh (working copy)
@@ -69,6 +69,12 @@
"hardy")
codename="Hardy"
;;
+ "intrepid")
+ codename="Intrepid"
+ ;;
+ "jaunty")
+ codename="Jaunty"
+ ;;
*)
echo "Unsupported Ubuntu release"
exit 1
Index: acinclude.m4
===================================================================
--- acinclude.m4 (revision 335)
+++ acinclude.m4 (working copy)
@@ -254,6 +254,12 @@
"hardy")
BRUTUS_DIST_RELEASE="Ubuntu%20Hardy"
;;
+ "intrepid")
+ BRUTUS_DIST_RELEASE="Ubuntu%20Intrepid"
+ ;;
+ "jaunty")
+ BRUTUS_DIST_RELEASE="Ubuntu%20Jaunty"
+ ;;
*)
AC_MSG_ERROR([[Unable to determine Ubuntu release]])
;;
@@ -403,6 +409,14 @@
LIBMAGICK='libmagick10'
LIBMAGICK_DEV='libmagick9-dev'
;;
+ "intrepid")
+ LIBMAGICK='libmagick10'
+ LIBMAGICK_DEV='libmagick9-dev'
+ ;;
+ "jaunty")
+ LIBMAGICK='libmagickwand1'
+ LIBMAGICK_DEV='libmagicwand-dev'
+ ;;
*)
AC_MSG_ERROR([[This Ubuntu release is not supported]])
;;

As you can see, I tossed the jaunty release in there as well since it is scheduled two days from now, but I have NOT YET TESTED building on Jaunty, so feel free to leave that out if you wish. I will test that sometime this week and let you know if it works.

Both applied. Thanks!




I am still baffled as to why e-b works on my laptop without lorica, but not on my desktop…

Most likely a DNS or routing issue...



in the mean time I will work on building lorica, but do you have any other ideas as to what could cause that error. You mentioned something before about not being able to resolve the client, could you elaborate on that at all? I control all internal and external DNS (as well as everything else) for my environment, so I am pretty limitless when It comes to troubleshooting and testing.

The client must be routable from the server.



The only other differences were that my laptop is off site, connected over a hardware vpn (seemingly local to the machine itself), but my desktop is on the same subnet as both the exchange server, and the brutus server. I am even using the same brutus-server for both clients.


I'll bet a fair share of my right arm that your vpn NIC isn't the one which e-b thinks is the NIC to use when contacting the server. You should use lorica. It really should resolve this for you.

Best,
jules

[Jules Colding]

Post by Hegner, Travis
Index: acinclude.m4
===================================================================
--- acinclude.m4 (revision 336)
+++ acinclude.m4 (working copy)
@@ -415,7 +415,7 @@
;;
"jaunty")
LIBMAGICK='libmagickwand1'
- LIBMAGICK_DEV='libmagicwand-dev'
+ LIBMAGICK_DEV='libmagickwand-dev'
;;
*)
AC_MSG_ERROR([[This Ubuntu release is not supported]])

Applied, thanks.

--
jules

Post by Hegner, Travis
After this fix from the typo of my original patch, then brutus-
keyring, and evolution-brutus both build successfully on both
intrepid and jaunty.
In Jaunty, however, I have a strange issue where the connection is
made, and I can see the public folders without issue, but my mailbox
shows up as just a folder icon with no text, and I can't access any
of the information in it.
At least it builds and installs! :)
I have not yet tried the lorica client in jaunty.
Travis

[Jules Colding]

Hi Travis,

Post by Hegner, Travis
Index: m4/platform_adapt.m4
===================================================================
--- m4/platform_adapt.m4 (revision 520)
+++ m4/platform_adapt.m4 (working copy)
@@ -266,6 +266,12 @@
"xhardy")
LORICA_DIST_RELEASE="Ubuntu%20Hardy"
;;
+ "xintrepid")
+
LORICA_DIST_RELEASE="Ubuntu%20Intrepid"
+ ;;
+ "xjaunty")
+
LORICA_DIST_RELEASE="Ubuntu%20Jaunty"
+ ;;
*)
AC_MSG_ERROR([[Unable to determine Ubuntu release]])
;;

Applied, thanks.

Post by Hegner, Travis
Index: src/lorica/ConfigBase.cpp
===================================================================
--- src/lorica/ConfigBase.cpp (revision 520)
+++ src/lorica/ConfigBase.cpp (working copy)
@@ -562,7 +562,7 @@
ACE_ARGV*
Lorica::Config::get_ifr_options(const bool Debug)
{
- if (Debug)
+ if (Debug) {}
; // kill compiler warning
if (ifr_args_.size() > 0)

I'm wondering about this change. Did the original code produce a
warning with your compiler?

Post by Hegner, Travis
Index: release.sh
===================================================================
--- release.sh (revision 520)
+++ release.sh (working copy)
@@ -81,6 +81,12 @@
"hardy")
codename="Hardy"
;;
+ "intrepid")
+ codename="Intrepid"
+ ;;
+ "jaunty")
+ codename="Jaunty"
+ ;;
*)
echo "Unsupported Ubuntu release"
exit 1

Applied, thanks.

Post by Hegner, Travis
Index: tests/fileConfig/main.cpp
===================================================================
--- tests/fileConfig/main.cpp (revision 520)
+++ tests/fileConfig/main.cpp (working copy)
@@ -23,6 +23,7 @@
#include <string>
#include <iostream>
+#include <memory>
int main (int, char *[])
{

Was memory.h needed to build on intrepid? It builds fine everywhere
else.

Post by Hegner, Travis
Once again, the jaunty info is just kind of tossed in there and I
have not yet tested building on that dist. I'm hoping someone can
shed some light as I'm kind of stuck at this point. "make" is
successful, "make dist" is also successful, but "make dist-deb-bin"
dies at the following error.
cp /home/thegner/tools/lorica/deb/lorica-1.0.13/support_files/brutus/
ifr.cache /home/thegner/tools/lorica/deb/lorica-1.0.13/ifr.cache
cp: cannot stat `/home/thegner/tools/lorica/deb/lorica-1.0.13/
support_files/brutus/ifr.cache': No such file or directory

Hmm... "~/tools/lorica/deb/lorica-1.0.13/support_files/brutus/" is an
external, so it should have been checked out when you pull lorica from
svn. Please check that the external property is pull-able by you (svn
propedit svn:external .).

Thanks,
jules