Closed cpraveen412 closed 8 years ago
cf-gitbot
commented
8 years ago We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/132911489
The labels on this github issue will be updated when the story is started.
aaronshurley
commented
8 years ago Hi,
We'd like to gather a bit more information so that we can help troubleshoot this issue. Could you please provide the following:
monit summary on the failing broker VM (probably have to run this command as root)?Thanks, Aaron & Natalie
robdimsdale
commented
8 years ago also @cpraveen412 thanks for providing the manifest. In future, could you add the manifest as a gist rather than inlining it into the issue? Thanks
cpraveen412
commented
8 years ago Hi @aaronshurley and @robdimsdale Here are the answers for above questions -> I'm Using V31 -> It is a fresh install -> +-------------------------------------------------------------+----------+-----+--------------------+---------------+ | VM | State | AZ | VM Type | IPs | +-------------------------------------------------------------+----------+-----+--------------------+---------------+ | arbitrator_z3/0 (73ea3884-d553-4c6f-a98b-4815e2bed081) | running | n/a | arbitrator_z3 | 192.168.6.174 | | cf-mysql-broker_z1/0 (daa6c271-679a-4daa-a75e-9aedd571c568) | starting | n/a | cf-mysql-broker_z1 | 192.168.6.120 | | cf-mysql-broker_z2/0 (0202ca75-156c-4dde-bd93-e0a4ee9a28cf) | running | n/a | cf-mysql-broker_z2 | 192.168.6.121 | | mysql_z1/0 (0ab15ac2-5779-44a8-9e3f-e50d04b524d1) | running | n/a | mysql_z1 | 192.168.6.170 | | mysql_z2/0 (f8ce5bbb-9255-49a9-bace-e2e5b38e1001) | running | n/a | mysql_z2 | 192.168.6.172 | | proxy_z1/0 (26b19392-2514-42d9-bdee-3f025d91980c) | running | n/a | proxy_z1 | 192.168.6.171 | | proxy_z2/0 (4d26361f-7101-43cd-9448-fd421461be8f) | running | n/a | proxy_z2 | 192.168.6.173 | +-------------------------------------------------------------+----------+-----+--------------------+---------------+
-> Using Scripts
->
-> CF-245 and it is successfully running
https://gist.github.com/cpraveen412/df736aa719ccfe7c046ffef0a8724573
robdimsdale
commented
8 years ago Could you get us any errors from the cf-mysql-broker log file on the cf-mysql-broker-z1 vm?
They can be found at /var/vcap/sys/log/cf-mysql-broker/cf-mysql-broker.log
cpraveen412
commented
8 years ago Hi @robdimsdale there is no such file in that path. I have route-registrator.stderr.log and route-registrator.stdout.log.
There is nothing in route-registrator.stderr log
aaronshurley
commented
8 years ago @cpraveen412 can you post the output of those two files?
robdimsdale
commented
8 years ago What are the contents of both of those files?
On Oct 25, 2016 6:38 AM, "cpraveen412" notifications@github.com wrote:
Hi @robdimsdale https://github.com/robdimsdale there is no such file in that path. I have route-registrator.stderr.log and route-registrator.stdout.log.
There is nothing in route-registrator.stderr log
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cloudfoundry/cf-mysql-release/issues/135#issuecomment-256036750, or mute the thread https://github.com/notifications/unsubscribe-auth/AG5U5j2ldKzf-FGq4EDb0Cvekh1n8wvkks5q3gZCgaJpZM4KdMNN .
cpraveen412
commented
8 years ago hi @aaronshurley and @robdimsdale
The file route-registrator.stderr.log is empy. route-registrator.stdout.log has nearly 180000 lines and i'm unable to copy in here and gist is also not taking.
https://drive.google.com/file/d/0B1wds6Pgc6AsNHBPUXJfYi1nOTA/view?usp=sharing
Please open the link above for out.log file
Thank You
aaronshurley
commented
8 years ago Thanks, those logs indicate the route-registrar component is working fine, which is good news.
However, we are surprised that there are no logs for the other components.
Can you show us what log files exist by running the following:
ls -al /var/vcap/sys/log/cf-mysql-brokerCan you also provide the contents of the following file: /var/vcap/monit/monit.log
Could you also try running the following two commands and share their output:
/var/vcap/packages/syslog_aggregator/setup_syslog_forwarder.sh /var/vcap/jobs/cf-mysql-broker/config; echo $?and:
/var/vcap/packages/mariadb/bin/mysql \
--defaults-file="/var/vcap/jobs/cf-mysql-broker/config/mylogin.cnf" \
< "/var/vcap/cf-mysql-broker/config/cf_mysql_broker_setup.sql"; echo $?Thanks, @robdimsdale && Aaron
cpraveen412
commented
8 years ago hi @aaronshurley & @robdimsdale
aaronshurley
commented
8 years ago Thank you for the responses. Unfortunately, we had a typo in that last command. Could you please run this command and provide the output (please make sure to run the command as root):
/var/vcap/packages/mariadb/bin/mysql \
--defaults-file="/var/vcap/jobs/cf-mysql-broker/config/mylogin.cnf" \
< "/var/vcap/jobs/cf-mysql-broker/config/cf_mysql_broker_setup.sql"; echo $?Thanks, Aaron && Rob
cpraveen412
commented
8 years ago Hi @aaronshurley
vcap@e141cee6-2287-4b93-9ccc-86c7b015aa45:/var/vcap/sys/log/cf-mysql-broker$ /var/vcap/packages/mariadb/bin/mysql \
--defaults-file="/var/vcap/jobs/cf-mysql-broker/config/mylogin.cnf" \ < "/var/vcap/jobs/cf-mysql-broker/config/cf_mysql_broker_setup.sql"; echo $?ERROR 2003 (HY000): Can't connect to MySQL server on '192.168.6.233' (111 "Connection refused") 1
I got a question here. In the stub i gave 192.168.6.233 for existing load balancer. Actually this is CF HA-Proxy address. Is this why it is not working?
jpalermo
commented
8 years ago Yes, this sounds correct. The cf_mysql.host property should be set to the load balancer that is in front of the mysql proxy instances. The cf-mysql service needs a different load balancer from the cf load balancer.
If you don't have one, you can run a single proxy and use the ip address of that proxy for cf_mysql.host, but of course the system will not be highly available in that situation.
cpraveen412
commented
8 years ago hi @aaronshurley , @jpalermo & @robdimsdale Finally I used following manifest based on @jpalermo's suggestion. But i targetted to mysql_z1 directly rather than proxy_z1. I think I have to explore again for a full scale deployment
https://gist.github.com/cpraveen412/7365236c1ffd72e533958344833fae40
Thank you all for your fast response and support
Hi Team!! I got the following error while I was deploying MySQL service on vSphere for CF
Started updating job cf-mysql-broker_z1 > cf-mysql-broker_z1/0 (daa6c271-679a-4daa-a75e-9aedd571c568) (canary). Failed: 'cf-mysql-broker_z1/0 (daa6c271-679a-4daa-a75e-9aedd571c568)' is not running after update. Review logs for failed jobs: cf-mysql-broker, quota-enforcer (00:10:21)
Error 400007: 'cf-mysql-broker_z1/0 (daa6c271-679a-4daa-a75e-9aedd571c568)' is not running after update. Review logs for failed jobs: cf-mysql-broker, quota-enforcer
I checked for the logs cf-mysql-broker, quota-enforcer in cf-mysql-broker VM. but couldn't find any (/var/vcap/sys/log/cf-mysql-broker/)
Please help me on this
cf-mysql-deployment.yml