Hi Gilles,

I just finished testing this and had a similar experience in Centos6.  It 
appears that this is a known issue and we have a ticket currently under 
investigation with the same error from your logs.

I did have successful tests using Ubuntu for my MariaDB role.  Can you test 
using Ubuntu and verify is issues persist for you?

Many thanks,
Wm. Marc O'Brien
Scalr Technical Support

On Wednesday, November 16, 2016 at 3:12:35 AM UTC-7, Gilles O wrote:
>
> Sure, please find the attached log.
> Thanks!
> G
>
> Le mardi 15 novembre 2016 18:54:13 UTC+1, Marc O'Brien a écrit :
>>
>> Hi Gilles,
>>
>> Operation "system.init" is the Scalarizr agent attempting to initialize 
>> and failing.  We would need to take a look at your full agent logs to 
>> determine the cause of the 404.  Can you attach those logs here?
>>
>> Many thanks,
>> Wm. Marc O'Brien
>> Scalr Technical Support
>>
>>
>>
>> On Monday, November 14, 2016 at 8:32:12 AM UTC-7, Gilles O wrote:
>>>
>>> Hi all,
>>>
>>> i'm using a centOS7.2 image with mariaDB on it ; 
>>> after volume init etc, the scalarizr (4.10.2) sends out an error like :
>>>
>>> 2016-11-14 14:41:41,077+00:00 - ERROR - scalarizr.ops.system.init - 
>>> Operation "system.init" (id: 096e764d-117d-48c3-8203-52def9f0ed3b) failed. 
>>> Reason: HTTP Error 404: Not Found
>>>
>>> The operation juste before in the scalarizer_debug.log is 
>>> 2016-11-14 14:41:39,231+00:00 - DEBUG - scalarizr.util - system: 
>>> ('/usr/bin/yum', 'repolist', '--verbose')
>>> and is successful.
>>>
>>> Same image but just without mariadb is running fine.
>>>
>>> scalR version is 5.11.22 opensource.
>>>
>>> The server causing the issue is running on openstack ;
>>> an identical image runs fine on aws/ec2.
>>>
>>> Do you have any idea what ops.system.init is throuwing this error ? And 
>>> how to correct it ?
>>> Thanks
>>> G
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"scalr-discuss" 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/d/optout.

Reply via email to