Srini,

How did you perform the upgrade?  Was it from v3.5? We're thinking of 
upgrading as well but can't seem to find a guide for it.

On Wednesday, January 2, 2013 5:01:15 AM UTC-5, Srini wrote:
>
> Ok. I will try to upgrade. 
>
> Will scalr have a problemif I switch to php 5.4 ? The remi repo is now on 
> 5.4. 
>
> Srini
> Sent on my BlackBerry® from Vodafone
> ------------------------------
> *From: * Igor Savchenko <[email protected] <javascript:>> 
> *Sender: * [email protected] <javascript:> 
> *Date: *Wed, 2 Jan 2013 11:45:12 +0200
> *To: *[email protected] 
> <javascript:><[email protected]<javascript:>
> >
> *ReplyTo: * [email protected] <javascript:> 
> *Subject: *Re: Segmentation fault error after upgrading to 4.0
>
> This issue related to libcurl. It's very old and contain bug: 
> https://bugs.php.net/bug.php?id=61947
>
> This libcurl bug found in 7.15 - 7.19 versions. You need higher one.
>
> Regards,
> Igor
>
>
> On 2 January 2013 11:42, Srinivasan Subramanian 
> <[email protected]<javascript:>
> > wrote:
>
>> libcurl 7.15.5 on Centos 5.7
>> The problem occurs whenever i click Save on a running farm.  
>>
>> Srini
>> On 02-Jan-2013, at 3:08 PM, Igor Savchenko <[email protected]<javascript:>> 
>> wrote:
>>
>> What's version of libcurl installed on the system?
>>
>>
>> On 2 January 2013 11:36, Srinivasan Subramanian 
>> <[email protected]<javascript:>
>> > wrote:
>>
>>> After upgrading to Scalr 4.0 a strange error is occurring.
>>>
>>> When i modify a role of an existing/running farm, the settings are saved 
>>> in the database but i get a "Cannot proceed your request at the moment. 
>>>  Please try again later" error.
>>>
>>> the Apache http error log shows the following message: [Wed Jan 02 
>>> 04:33:25 2013] [notice] child pid 30665 exit signal Segmentation fault (11)
>>>
>>> The pid is that of httpd.
>>>
>>> Any ideas what the issue could be and what i need to look for?
>>>
>>> Regards
>>> Srini
>>>
>>> --
>>>
>>>
>>>
>>
>> -- 
>>  
>>  
>>
>>
>>  -- 
>>  
>>  
>>
>
>  -- 
>  
>  
>

-- 


Reply via email to