[email protected] as always!

On Wed, Mar 14, 2012 at 5:34 PM, Srinivasan S <
[email protected]> wrote:

> **
> Hi Sebastian
>
> In the interim, I can email the patched files across to you guys if
> needed.
>
> Regards
> Srini
> Sent on my BlackBerry® from Vodafone
> ------------------------------
> *From: * Sebastian Stadil <[email protected]>
> *Sender: * [email protected]
> *Date: *Wed, 14 Mar 2012 13:55:22 -0700
> *To: *<[email protected]>
> *ReplyTo: * [email protected]
> *Subject: *Re: class RRDGraph redeclared.
>
> We talked about this internally, but should have used this discussion
> list. We want to have stable releases on a certain cycle, made available to
> the public through https://scalr.net/pricing/open-source/
>
> We're considering how to move to an open development process, but haven't
> come to a decision. Since it's not a revenue-pressing matter, it hasn't
> been prioritized like getting you guys raid support, a reporting dashboard,
> or integrated monitoring.
>
> On Wed, Mar 14, 2012 at 12:14 PM, mavinman <[email protected]> wrote:
>
>> No, not really.  But I'll think about it depending on how many issues
>> like this arise.
>>
>> I think I'm a little confused as to how this whole Scalr open source
>> process works.  I (and I'm sure other developers) have no problem
>> fixing bugs/issues in Scalr as they arise - and understand that for
>> support issues I'd have to purchase a contract.  The issue is that (as
>> far as I know) there's no source control repository or process to
>> submit fixes to Scalr.  I don't think it would be wise for both Srini
>> and me to implement a zillion application wide changes in our own
>> local copy of Scalr if there's no way for the community to benefit
>> from it.
>>
>> If we don't want to purchase support, are we simply supposed fix all
>> the problems each individually ourselves, wait until the next version
>> of scalr comes out, and then check to see if our problems have been
>> fixed?
>>
>> On Mar 14, 1:47 pm, Sebastian Stadil <[email protected]> wrote:
>> > Hi Josh,
>> >
>> > Have you considered getting a support contract for issues such as this
>> one?
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Wed, Mar 14, 2012 at 9:08 AM, mavinman <[email protected]> wrote:
>> > > Can we get a reply from a scalr engineer about an offiical fix for
>> > > this?  I've had this issue as well, and don't want to find/replace the
>> > > whole project.
>> >
>> > > On Mar 12, 10:20 pm, Srini <[email protected]> wrote:
>> > > > Couple of more issues.  For anyone ending up like me with the latest
>> > > > versions of PHP RRD tool, there are incompatibilities.  First was
>> the
>> > > > RRDGraph class I described below.  Others are:
>> >
>> > > > 1. Signatures of rrd_create and rrd_update have probably changed.
>> > > > 2. The app/src/LibWebta/library/Data/RRD/class.RRD.php needs to be
>> > > updated.
>> > > > 3. rrd_create() requires only 2 parameters, comment out the third
>> (count)
>> > > > 4. rrd_update() requries the second argument to be of type array
>> and not
>> > > > string.  Create a new array() object, push the string constructed
>> in the
>> > > > Udpate() function into the array and call the rrd_update() with the
>> array
>> > > > as the second parameter
>> >
>> > > > With these changes the RRDTool starts collecting all the required
>> > > > statistics :)
>> >
>> > > > Regards
>> > > > Srini
>> >
>> > > > On Monday, March 12, 2012 3:42:51 PM UTC+5:30, Srini wrote:
>> >
>> > > > > Hi
>> >
>> > > > > I installed the RRDtools and the pecl php-rrdtool yesterday to
>> start
>> > > > > collecting statistics.
>> >
>> > > > > After setting up rrdtool / php extension and loading it all my
>> cron
>> > > jobs
>> > > > > started failing.  When I tracked the php errors, I found a number
>> of
>> > > these
>> > > > > messages in the php error log: PHP Fatal error:  Cannot redeclare
>> class
>> > > > > RRDGraph in
>> > > > >
>> /var/www/html/app/src/LibWebta/library/Data/RRD/class.RRDGraph.php on
>> > > line
>> > > > > 464
>> >
>> > > > > The problem seems to be that PHP rrdtool extension has an RRDGraph
>> > > class (
>> > > > >http://www.php.net/manual/en/class.rrdgraph.php) and the LibWebta
>> class
>> > > > > in scalr is also having a class called RRDGraph.  I ended up
>> grep'ing
>> > > for
>> > > > > all instances of RRDGraph in scalr source and changing it to a
>> > > different
>> > > > > name.  It is now running fine.
>> >
>> > > > > Can the Scalr development team please check this and let us know?
>> > >  Ideally
>> > > > > the RRDGraph class in libwebta needs to be renamed so there is no
>> clash
>> > > > > with the php extension.
>> >
>> > > > > Regards
>> > > > > Srini
>> >
>> > > --
>> > > You received this message because you are subscribed to the Google
>> Groups
>> > > "scalr-discuss" group.
>> > > To post to this group, send email to [email protected].
>> > > To unsubscribe from this group, send email to
>> > > [email protected].
>> > > For more options, visit this group at
>> > >http://groups.google.com/group/scalr-discuss?hl=en.
>> >
>> > --
>> >
>> > Follow us: Twitter <https://twitter.com/#!/scalr> -
>> > Facebook<https://www.facebook.com/Scalr>
>> >  - Blog <http://blog.scalr.net/>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "scalr-discuss" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected].
>> For more options, visit this group at
>> http://groups.google.com/group/scalr-discuss?hl=en.
>>
>>
>
>
> --
>
>
> Follow us: Twitter <https://twitter.com/#!/scalr> - 
> Facebook<https://www.facebook.com/Scalr>
>  - Blog <http://blog.scalr.net/>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "scalr-discuss" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/scalr-discuss?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "scalr-discuss" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/scalr-discuss?hl=en.
>



-- 


Follow us: Twitter <https://twitter.com/#!/scalr> -
Facebook<https://www.facebook.com/Scalr>
 - Blog <http://blog.scalr.net/>

-- 
You received this message because you are subscribed to the Google Groups 
"scalr-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/scalr-discuss?hl=en.

Reply via email to