Hi Lilin, Have you seen this document - https://github.com/Metaswitch/sprout/blob/dev/docs/Development.md?
If it's a fresh checkout of Sprout, you'll need to build the dependencies first, which you can do by running 'make' in the top level Sprout directory. Once this first build is done (which can take a while), then you can move to the quicker builds of running 'make' in Sprout/Sprout, and then 'make deb-only' in the top level Sprout directory. Typically, each repository has documentation covering the function of the component and how to build/develop with it. Our wiki (https://github.com/Metaswitch/clearwater-docs/wiki) has deployment wide information (as well as other interesting/useful information) about Project Clearwater. 'sudo monit status' is the correct monit command. What version of Sprout have you built (i.e. when was the last commit), and what version of the other Clearwater packages do you have on your node? I ask because we recently changed how we use monit, by pulling it into a new clearwater-monit package in the 'Tetris' release. If you've got a mix of packages on your node where some of which expect monit, and some expect clearwater-monit, then you could see these type of errors. If you are running an old version then can you please upgrade? Hope this helps, Ellie -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Lilin Sent: 30 January 2015 23:52 To: [email protected] Subject: [Clearwater] (1) Documents on how to re-compile sprout? (2) Most recent Monit service? Hello all, I noticed that I'm not alone to be interested in trying to modify the source code of sprout. But I discovered no documents about how to set up the compile environment to build sprout from source code: Firstly, I got pjsip.h file missing when I did 'make' in sprout/sprout directory, and don't know how to proceed from there. **Is there some documents on how to (re-)compile sprout? So pursuing the second option, I tried the first option mentioned in the earlier reply as below - to rebuild sprout. My understanding is to install sprout from debian packet first, then run 'make deb' in sprout directory. Three problems arise for the second option: 1. sprout isn't running after the debian-packet install 2. the usual monit command doesn't work; it is now a 'unrecognized' service 3. restart clearwater-monit service doesn't resolve the monit service issue in (2) For monit unable to launch, please advise *how to resolve? ** what is the most current monitor service (that replaced the old 'sudo monit status') for sprout? Thanks, Lilin On 17/11/2014 2:51 PM, Eleanor Merry wrote: > Hi, > > The easiest way is probably to rebuild sprout, and then upgrade your sprout > from the manual install with the updated debian packages. > You can do this by running 'make deb' in the sprout directory - the debian > packages are created in the parent of the top level sprout directory. > > Alternatively, you can build just the Sprout code (run make in the > sprout/sprout directory), and then run 'make deb-only' in the top level > sprout directory. This skips checking the dependencies when building the > debian packages, so is quicker. > > Hope this helps, > > Ellie > > > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Sushant Hiray > Sent: 11 November 2014 08:27 > To: [email protected] > Cc: Mythili Vutukuru; Anmol Garg > Subject: [Clearwater] Tweaking Sprout source code and running it as > daemon > > Dear All, > > I've currently installed sprout via the manual install method > <https://github.com/Metaswitch/clearwater-docs/wiki/Manual-Install> > Everything is working fine in this installation. > > I'm interested in tweaking the source code of sprout. > Particularly I'm interested in tweaking the load_monitor > <https://github.com/Metaswitch/cpp-common/blob/master/src/load_monitor > .cpp> algorithm and seeing the effect on traffic handling. > > I want to know, what is the best way to go ahead. > Is there any way I can update the source code in my current sprout > installation and recompile and run the daemon. > > We tried building the bleeding edge source in a new VM but are facing > some issues > <http://lists.projectclearwater.org/mail-archive/msg01039.html> > (link to mailing list post), so I was particularly looking to check if there > is any alternative way to tweak the source code, recompile it and run it as > daemon. > > Looking forward to your responses. > > Regards, > Sushant Hiray, > Senior Undergrad CSE, > IIT Bombay > _______________________________________________ > Clearwater mailing list > [email protected] > http://lists.projectclearwater.org/listinfo/clearwater > _______________________________________________ > Clearwater mailing list > [email protected] > http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
