-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can't find warden.sock? #51
Comments
Could you let me know some more information of your instllation? |
Thanks for your reply. I'm trying to reinstall CF. If the problem still exists after I complete the installation, I will consult you again. |
Hi,yudai. When i completed this command, I run "sudo ./local/start_processes.sh" to start it, then i got the first error: Error 1): monit: action failed -- There is no service by that name(nats_stream_forwarder). Then i delete "nats_stream_forwarder" in your script and rerun the command. When I changed "nats://nats:c1oudc0w@:4222" to "nats://nats:c1oudc0w@192.168.2.219:4222" in health_manager_next.yml, the health_manager_next can start normally. Now let me paste the error logs of other four components. 2)warden.stderr.log:
3)cloud_controller_ng.stderr.log 4)jobs_work.stderr.log 5)dea.stderr.log So,yudai,Can you give me some suggestions? |
Thank you for the report
This is a bug of the installer. I've fixed it in the testing branch and now I am testing it. I'm not sure the cause of the error of CC yet. This might be solved by using the latest cf-release. |
Thanks for your reply! I found a error log in warden.log,like this: { Then i run three commands: Then the warden and dea_next components can run normally. Also i found a error log in db_migrate.stderr.log: I guess that this error is related to cloud_controller_ng? |
I've pushed some commit to the testing branch. It should fix the problem of nats_stream_forwarder and health_manager. I'm now investigating the problem of CCNG. I'll let you know when I figure out the cause. |
Ok, Thank you very much,yudai! |
I've pushed some commits to the master branch. It should work wit the latest cf-release. Please give it a try. |
Now the warden seems to bounce between failed: Process 'nats' running and not monitored: Process 'nats' running in the warden log, i can see: Tasks: TOP => warden:start The dea.stderr.log and dea.stdout.log is empty. {"timestamp":1385545368.31445,"message":"nats.message.received","log_level":"debug","source":"Dea::Nats","data":{"subject":"response to router.greet","data":{"id":"0fe940da5326453c42314d6f7f6f4f13","hosts":["192.168.128.133"],"minimumRegisterIntervalInSeconds":5}},"thread_id":16121980,"fiber_id":24397740,"process_id":4405,"file":"/var/vcap/packages/dea_next/lib/dea/nats.rb","lineno":144,"method":"handle_incoming_message"} Regards, |
Please confirm that you have restarted your server. |
Hello, yes i can confirm i restarted before trying. Please let me know if i can do anything else. Regards, |
@Digit-Elektra which Ubuntu version are you using? |
Log of Warden process may have some helpful information. Please check /var/vcap/sys/log/monit directory for it. |
Now,everything is ok in my server! Thanks,yudai. |
Hello, everything is working now. I reinstalled today from the trunk, and that worked! Many thanks. |
I try installing on Debian Wheezy, and meet something similar, while after uninstall apparmor, it works well now. |
What revision of cf_nise_installer are you using? |
So your CF works fine now? |
I can't find the warden.sock in "/var/vcap/data/warden/", so the warden component can't be started.
Anyone can help me?
The text was updated successfully, but these errors were encountered: