Sweet. Thanks Kevin for helping out Ilim! Its too bad the libs built from Cyrus SASL source don't work out. But yea, we can worry about that later.
@Ilim: Migrating to Mesos sounds good! On Thu, Aug 15, 2013 at 1:35 PM, İlim Uğur <[email protected]> wrote: > There is finally some good news on the issue. With the help of lyda from > #mesos IRC channel, I managed to see my code successfully run on a virtual > Ubuntu 12.04 Server, and on an Ubuntu 13.04 Desktop, after downloading > libsasl2-dev and libsasl2-modules via apt-get. You may test it yourself by > cloning it from my github repo on http://github.com/ilimugur/sasltrial > > I have been compiling Cyrus SASL from the source since the beginning of > the program, but it turns out the packages were the better way to go. > > Just to remind everyone, this code is a sample client-server application > that does anonymous authentication using Cyrus SASL library. > > I will now proceed with migrating the classes I coded into Mesos source. > > Feel free to ask any questions you may have. > > - İlim > > > > > 2013/8/14 İlim Uğur <[email protected]> > >> Hey Vinod, >> >> Nothing in particular is blocking me from sharing my vagrant environment, >> actually. As soon as I saw that Cyrus SASL seemed to work decently, I >> wanted to make some progress before preparing a configuration file for my >> setup. I am new to Vagrant, but I guess I can form a configuration file >> today, with some shell scripting. >> >> You are correct on what is not working with my setup. The server side >> gives out an error when AuthenticatorServer::startAuthProcess() calls >> sasl_server_start(). Internally, as far as GDB helps, it seems >> sasl_server_start() calls sasl_server_step(), which returns SASL_NOMECH, >> causing server to fail the authentication negotiation. I got as deep as I >> can trace with GDB and as it turns out, a function named >> _sasl_auxprop_lookup() in lib/auxprop.c returns SASL_NOMECH after failing >> to find an auxprop plugin. This is, I suppose, the same reason why >> sample-client and sample-server shipped with Cyrus SASL do not work on my >> setup. >> >> The only irrational part to the issue is, auxprop plugin, which helps >> checking passwords, is looked for during anonymous authentication, even >> though anonymous mechanism does not require a password. Does it? I suspect >> the problem is again with the setup, as I had managed to run sample-client >> and sample-server on an Ubuntu 12.04 Desktop(not virtual) two weeks ago. >> Would Jan have any ideas on this part? >> >> Have some experience relevant to your question of what happens when I try >> without Vagrant, too. On a physical Ubuntu 13.04 Desktop, which I set up a >> week ago, I am getting a compilation error when on the "make" stage of >> Cyrus SASL installation, in digestmd5.c, to be specific. I will try it on a >> plain virtual Ubuntu 12.04 server(without Vagrant) and let you know of the >> result. >> >> - İlim >> >> >> >> >> 2013/8/12 Vinod Kone <[email protected]> >> >>> Hey Ilim. >>> >>> Great to hear that you are making progress. Can you let us know what is >>> blocking you from sharing your vagrant environment? Is it something we >>> can >>> help with? >>> >>> Also, I'm a bit confused about what is working and what isn't in your >>> vagrant + virtual box setup. If I understand correctly the client seems >>> to >>> be working but the server is not? Is this true even if you take vagrant + >>> virtual box out of the equation, i.e, ubuntu on bare metal? >>> >>> Cheers, >>> >>> -- Vinod >>> >>> >>> On Sun, Aug 11, 2013 at 10:50 PM, İlim Uğur <[email protected]> wrote: >>> >>> > Hey, >>> > >>> > There is some progress with the issue, and although it is not >>> completely >>> > resolved yet, I wanted to let everyone hear about the progress. >>> > >>> > When Vinod and Jan mentioned setting up some common environment, I >>> decided >>> > to try a tool I heard about, called Vagrant ( >>> http://www.vagrantup.com/ ). >>> > It basically helps you set up a custom work environment with the help >>> of VM >>> > technologies. Then you can share the configuration of your dev. >>> environment >>> > with the rest of the development team and you get to have the same >>> > workspace. >>> > >>> > I created a default Ubuntu 12.04 server using Vagrant and installed >>> all the >>> > relevant packages and files in it. Sadly, I can not share my workspace >>> > configuration for the moment. Still, as pluginviewer command listed >>> > seemingly all the plugins we wanted Cyrus SASL to install, it appears >>> > everything worked fine on this Ubuntu box. >>> > >>> > I had encountered problems with trying to install Cyrus SASL to a >>> virtual >>> > Ubuntu 12.04 server I created using VirtualBox. I also could not >>> > successfully run sample-client and sample-server code provided by Cyrus >>> > SASL on this box(i.e. the one I created using Vagrant). However, I did >>> > manage to correct a few mistakes in my code, which, for the client >>> side at >>> > least, seem to work fine now, at least on the mentioned dev. >>> environment. >>> > >>> > There is an issue on the server-side code, though. I tried tracing the >>> > program using GDB, but it seems a function(sasl_server_step) returns >>> > something(SASL_NOMECH) it actually can not return. I will go on looking >>> > into that in a few hours. >>> > >>> > It feels great to finally have made some progress with the issue. I >>> hope I >>> > can make faster progress after resolving this. >>> > >>> > - İlim >>> > >>> > >>> > >>> > >>> > 2013/8/10 Jan Schaumann <[email protected]> >>> > >>> > > ?lim U?ur <[email protected]> wrote: >>> > > >>> > > > He suggested I should redo the configuration step, this time >>> specifying >>> > > the >>> > > > plugin directory parameter. I did what he suggested, it had no >>> effect. >>> > > the >>> > > > tool called pluginviewer showed that I only have EXTERNAL plugin >>> > > available. >>> > > > So he thought the problem is not my code but the way I installed >>> sasl. >>> > > >>> > > I can't tell for certain, but my instinct and experience suggests >>> that >>> > > this likely to be the cause. >>> > > >>> > > Where do you currently develop on? Is this host accessible by others >>> > > (Vinod and me) to help troubleshoot the issue? >>> > > >>> > > If not, then I think we should consider setting up an EC2 instance to >>> > > poke around together; long-distance trouble-shooting is always >>> tricky. >>> > > >>> > > > dwhite ilim: if pluginviewer is failing, then you have a >>> fundamental >>> > > > problem with your sasl install. >>> > > > dwhite you could strace pluginview, to see where it's looking for >>> > shared >>> > > > libraries >>> > > > dwhite you may have a mix of cyrus sasl installed (native ubuntu >>> > packages >>> > > > and newly compiled packages). ldd on one of your binaries may >>> confirm >>> > > that. >>> > > > dwhite at this point i'd rule out your code being the primary >>> issue. >>> > > >>> > > All of this sounds like good ways to try to troubleshoot the >>> > > installation. Did you follow these suggestions? >>> > > >>> > > -Jan >>> > > >>> > >>> >> >> > -- > You received this message because you are subscribed to the Google Groups > "Twitter GSOC" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. >
