centos is capable of creating the role, however mysql-proxy does not seem
compatible with the scalr scripts, the mysql-proxy binary which is
installed does cannot read a config file, and has different parameter
options than what is expected.
the log just sits at the following for all ubuntu installs for mysql-proxy.
root@ip-xxx:/var/log# tail -f role-builder.log
2012-07-09 17:14:32,924 - DEBUG - scalarizr.util.log - Enabling log
messaging
2012-07-09 17:14:32,925 - DEBUG - scalarizr.handlers.hooks - Hook on
'hello'() {}
2012-07-09 17:14:32,925 - DEBUG - scalarizr.util.sqlite_server - create
cursor 2513861
2012-07-09 17:14:32,927 - DEBUG - scalarizr.util.sqlite_server - Execute
result: {'rowcount': -1, 'data': []}
2012-07-09 17:14:32,928 - DEBUG - scalarizr.handlers.script_executor -
STATE[script_executor.in_progress]: None
2012-07-09 17:14:32,928 - DEBUG - scalarizr.util.sqlite_server - create
cursor 2513861
2012-07-09 17:14:32,930 - DEBUG - scalarizr.util.sqlite_server - Execute
result: {'rowcount': -1, 'data': []}
2012-07-09 17:14:32,930 - DEBUG - scalarizr.handlers.script_executor -
Restoring 0 in-progress scripts
2012-07-09 17:14:32,930 - DEBUG - scalarizr.config - Reading file
/etc/scalr/private.d/.state
2012-07-09 17:14:32,931 - DEBUG - scalarizr.handlers.hooks - Hook on
'start'() {}
2012-07-09 17:15:01,786 - DEBUG - scalarizr.messaging.p2p.producer -
Sending message 'Log' into queue 'log'
2012-07-09 17:15:01,787 - DEBUG - scalarizr.util.sqlite_server - create
cursor 2513837
2012-07-09 17:15:01,792 - DEBUG - scalarizr.util.sqlite_server - Execute
result: {'rowcount': 1, 'data': []}
2012-07-09 17:15:01,794 - DEBUG - scalarizr.messaging.p2p.producer -
Delivering message 'Log' <?xml version="1.0" ?><message
id="79ebdfd0-ab00-4caa-aec2-33cfcbb84b2e"
name="Log"><meta><szr_version>0.9.r3629</szr_version><server_id>b2d20736-7a04-4ef3-ac7b-13e974a7c126</server_id><timestamp>Mon
09 Jul 2012 17:15:01
UTC</timestamp></meta><body><entries><item><stack_trace></stack_trace><pathname>/usr/lib/pymodules/python2.7/scalarizr/__init__.py</pathname><name>scalarizr</name><level>INFO</level><msg>[pid:
11561] Starting scalarizr
0.9.r3629</msg><lineno>675</lineno></item><item><stack_trace></stack_trace><pathname>/usr/lib/pymodules/python2.7/scalarizr/config.py</pathname><name>scalarizr.config</name><level>INFO</level><msg>State:
importing</msg><lineno>928</lineno></item><item><stack_trace></stack_trace><pathname>/usr/lib/pymodules/python2.7/scalarizr/handlers/mysqlproxy.py</pathname><name>scalarizr.handlers.mysqlproxy</name><level>INFO</level><msg>Updating
mysql-proxy backends
list</msg><lineno>145</lineno></item><item><stack_trace></stack_trace><pathname>/usr/lib/pymodules/python2.7/scalarizr/__init__.py</pathname><name>scalarizr</name><level>INFO</level><msg>Starting
API server on
http://0.0.0.0:8010</msg><lineno>345</lineno></item><item><stack_trace></stack_trace><pathname>/usr/lib/pymodules/python2.7/scalarizr/messaging/p2p/consumer.py</pathname><name>scalarizr.messaging.p2p.consumer</name><level>INFO</level><msg>Building
message consumer server on
0.0.0.0:8013</msg><lineno>56</lineno></item><item><stack_trace></stack_trace><pathname>/usr/lib/pymodules/python2.7/scalarizr/handlers/lifecycle.py</pathname><name>scalarizr.handlers.lifecycle</name><level>INFO</level><msg>Server
will be imported into
Scalr</msg><lineno>170</lineno></item></entries></body></message>
2012-07-09 17:15:01,795 - DEBUG - scalarizr.messaging.p2p.security -
Encrypting message
2012-07-09 17:15:02,134 - DEBUG - scalarizr.messaging.p2p.producer -
Message 'Log' delivered (message_id: 79ebdfd0-ab00-4caa-aec2-33cfcbb84b2e)
2012-07-09 17:15:02,135 - DEBUG - scalarizr.util.sqlite_server - create
cursor 2485061
2012-07-09 17:15:02,199 - DEBUG - scalarizr.util.sqlite_server - Execute
result: {'rowcount': 1, 'data': []}
here is the process list, with one defunct scalr process.
root@ip-10-176-23-49:/var/log# ps xau |grep scal
root 707 0.0 0.0 13132 1600 ? Ss 17:10 0:00 /bin/bash
/tmp/scalr-builder.sh
root 11561 0.5 1.1 196028 20000 ? Sl 17:14 0:02
/usr/bin/python /usr/local/bin/scalarizr --import -y -o
server-id=b2d20736-7a04-4ef3-ac7b-13e974a7c126 -o role-name=db-proxy -o
crypto-key=tz4hx/mCnKiu+AzXkfG9Ks0VO+qUm0rX5Pe05jI2VRW25eZ0BrnPfw== -o
platform=ec2 -o behaviour=,chef,mysqlproxy -o
queryenv-url=http://xxx/query-env -o
messaging-p2p.producer-url=http://209.99.111.85/messaging
root 11570 0.0 0.0 0 0 ? Zs 17:14 0:00
[scalarizr] <defunct>
root 11601 0.0 1.3 98888 22644 ? S 17:14 0:00
/usr/bin/python /usr/local/bin/scalarizr --import -y -o
server-id=b2d20736-7a04-4ef3-ac7b-13e974a7c126 -o role-name=db-proxy -o
crypto-key=tz4hx/mCnKiu+AzXkfG9Ks0VO+qUm0rX5Pe05jI2VRW25eZ0BrnPfw== -o
platform=ec2 -o behaviour=,chef,mysqlproxy -o
queryenv-url=http://xxx/query-env -o
messaging-p2p.producer-url=http://209.99.111.85/messaging
root 11726 0.0 0.0 7976 908 pts/0 S+ 17:22 0:00 grep
--color=auto scal
here is the output of the cronjob
2012-07-09 12:23:26,101 - INFO [tran4ffb138dd7a8c:Logger@36] - 'Starting
BundleTasksManager cronjob...'
2012-07-09 12:23:26,101 - INFO [tran4ffb138dd7a8c:Logger@24] - 'Found 3
bundle tasks.'
2012-07-09 12:23:28,101 - INFO [tran4ffb138dd7a8c:Logger@382] - 'Open
stream to: ssh2.sftp://CONNECTION/var/log/role-builder-output.log'
2012-07-09 12:23:28,101 - INFO [tran4ffb138dd7a8c:Logger@382] - 'Open
stream to: ssh2.sftp://CONNECTION/var/log/role-builder-output.log'
2012-07-09 12:23:28,101 - INFO [tran4ffb138dd7a8c:Logger@382] - 'Open
stream to: ssh2.sftp://CONNECTION/var/log/role-builder-output.log'
2012-07-09 12:23:28,101 - INFO [tran4ffb138dd7a8c:Logger@387] - 'Reading:
/var/log/role-builder-output.log'
2012-07-09 12:23:28,101 - INFO [tran4ffb138dd7a8c:Logger@387] - 'Reading:
/var/log/role-builder-output.log'
2012-07-09 12:23:28,101 - INFO [tran4ffb138dd7a8c:Logger@387] - 'Reading:
/var/log/role-builder-output.log'
On Monday, July 9, 2012 11:28:00 AM UTC-5, Chris wrote:
>
> The crons are running, as centos is able to completely create roles
> without any issues
>
> crontab -l
> #*/5 * * * * /usr/local/squid-graph/squid-graph -c --tcp-only
> --output-dir=/var/www/html/squid-graph <
> /var/log/squid/access-production.log
> */2 * * * * /usr/bin/php -q /opt/scalr/app/cron-ng/cron.php --Poller
> * * * * * /usr/bin/php -q /opt/scalr/app/cron/cron.php --Scheduler2
> */10 * * * * /usr/bin/php -q /opt/scalr/app/cron/cron.php
> --MySQLMaintenance
> * * * * * /usr/bin/php -q /opt/scalr/app/cron/cron.php --DNSManagerPoll
> 17 5 * * * /usr/bin/php -q /opt/scalr/app/cron/cron.php --RotateLogs
> */2 * * * * /usr/bin/php -q /opt/scalr/app/cron/cron.php --EBSManager
> */20 * * * * /usr/bin/php -q /opt/scalr/app/cron/cron.php --RolesQueue
> */5 * * * * /usr/bin/php -q /opt/scalr/app/cron-ng/cron.php
> --DbMsrMaintenance
> */2 * * * * /usr/bin/php -q /opt/scalr/app/cron-ng/cron.php --Scaling
> */5 * * * * /usr/bin/php -q /opt/scalr/app/cron/cron.php --DBQueueEvent
> */2 * * * * /usr/bin/php -q /opt/scalr/app/cron/cron.php --SzrMessaging
> */4 * * * * /usr/bin/php -q /opt/scalr/app/cron/cron.php --RDSMaintenance
> */2 * * * * /usr/bin/php -q /opt/scalr/app/cron/cron.php
> --BundleTasksManager >> /var/log/scalrizer.log
> * * * * * /usr/bin/php -q /opt/scalr/app/cron-ng/cron.php
> --ScalarizrMessaging
> * * * * * /usr/bin/php -q /opt/scalr/app/cron-ng/cron.php --MessagingQueue
> */2 * * * * /usr/bin/php -q /opt/scalr/app/cron-ng/cron.php --DeployManager
> */2 * * * * /usr/bin/php -q /opt/scalr/app/cron/cron.php --UsageStatsPoller
> * * * * * /usr/bin/php -q /opt/scalr/app/cron-ng/cron.php --SNMPStatsPoller
>
> On Monday, July 9, 2012 11:21:03 AM UTC-5, DicsyDel wrote:
>>
>> Make sure that cronjobs on scalr properly installed. In this particular
>> case cronjob BundleTasksManager responsible for building roles.
>>
>> Regards,
>> Igor
>>
>> On 9 July 2012 19:13, Chris <[email protected]> wrote:
>>
>>> trying to build the mysql-proxy role hangs on every version of ubuntu as
>>> well
>>>
>>>
>>> Jul 9, 2012 07:12:06
>>> Server status: running
>>> Jul 9, 2012 07:10:05
>>> Server status: running
>>> Jul 9, 2012 07:08:06
>>> Server status: running
>>> Jul 9, 2012 07:07:52
>>> Server status: running
>>> Jul 9, 2012 07:06:07
>>> Server status: running
>>> Jul 9, 2012 07:04:05
>>> Server status: running
>>> Jul 9, 2012 07:02:06
>>> Server status: running
>>> Jul 9, 2012 07:00:07
>>> Server status: running
>>> Jul 9, 2012 06:58:06
>>> Server status: running
>>> Jul 9, 2012 06:56:07
>>> Server status: running
>>> Jul 9, 2012 06:54:06
>>> Server status: running
>>> Jul 9, 2012 06:52:06
>>> Server status: running
>>> Jul 9, 2012 06:50:07
>>> Installing software [ OK ]
>>> Jul 9, 2012 06:50:05
>>> Server status: running
>>> Jul 9, 2012 06:48:08
>>> Creating runlist [ OK ]
>>> Jul 9, 2012 06:48:08
>>> Unpacking cookbooks [ OK ]
>>> Jul 9, 2012 06:48:08
>>> Creating chef configuration file [ OK ]
>>> Jul 9, 2012 06:48:08
>>> Installing chef [ OK ]
>>> Jul 9, 2012 06:48:08
>>> Installing rubygems [ OK ]
>>> Jul 9, 2012 06:48:08
>>> Unpacking rubygems [ OK ]
>>> Jul 9, 2012 06:48:08
>>> Downloading rubygems [ OK ]
>>> Jul 9, 2012 06:48:08
>>> Installing essential packages [ OK ]
>>> Jul 9, 2012 06:48:08
>>> Updating package list [ OK ]
>>> Jul 9, 2012 06:48:05
>>> Server status: running
>>> Jul 9, 2012 06:46:09
>>> Launching role builder routines on server
>>> Jul 9, 2012 06:46:08
>>> Uploading chef recipes...
>>> Jul 9, 2012 06:46:07
>>> Uploading builder scripts...
>>> Jul 9, 2012 06:46:06
>>> Initializing SSH2 session to the server
>>> Jul 9, 2012 06:46:06
>>> Server status: running
>>> Jul 9, 2012 06:44:08
>>> Bundle task status: preparing-environment
>>> Jul 9, 2012 06:44:07
>>> Server status: running
>>>
>>> On Monday, July 9, 2012 10:16:41 AM UTC-5, Chris wrote:
>>>>
>>>> the mysql-proxy add-on role does not appear to be working for centos. I
>>>> cannot connect to localhost:4040 on the app roles, nor do i see anything
>>>> using port 4040/3306 on the proxy server via netstat -nap, and nothing in
>>>> xinetd, nor any .lua files and mysql-proxy is not running. Am i missing
>>>> something?
>>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "scalr-discuss" group.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msg/scalr-discuss/-/B9qrsX8SNUUJ.
>>>
>>> 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 view this discussion on the web visit
https://groups.google.com/d/msg/scalr-discuss/-/uMsB6JwPfu8J.
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.
