How to solve the not monitored problem when installing CloudFoundry with cf_nise_installer

This article mainly explains "how to solve the not monitored problem when installing CloudFoundry using cf_nise_installer". Interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to solve the not monitored problem when installing CloudFoundry using cf_nise_installer.

Using github.com/yudai/cf_nise_installer to install the cf v2 version, the installation process is fine, but at startup, it appears:

Warden not monitored

Dea_next not monitored

View the log: / var/vcap/data/sys/log/

{"timestamp": 1398210883.1947148, "message": "Configuration", "log_level": "info", "source": "Warden::Server", "data": {"server": {"unix_domain_path": "/ var/vcap/data/warden/warden.sock", "unix_domain_permissions": 1398210883.1947148, "container_klass": "Warden::Container::Linux", "container_grace_time": 300, "job_output_limit": 10485760 "quota": {"disk_quota_enabled": true}, "allow_nested_warden": false, "container_rootfs_path": "/ var/vcap/packages/rootfs_lucid64", "container_depot_path": "/ var/vcap/data/warden/depot", "pidfile": "/ var/vcap/sys/run/warden/warden.pid"}, "logging": {"level": "debug", "file": "/ var/vcap/sys/log/warden/warden.log"} "network": {"pool_network": "10.254.0.0 port 22", "deny_networks": [], "allow_networks": [], "mtu": 1500}, "port": {"pool_start_port": 61001, "pool_size": 4000}, "user": {"pool_start_uid": 20000, "pool_size": 14890600}, "fiber_id": 14890600, "process_id": 5745 "file": "/ var/vcap/data/packages/warden/42/warden/lib/warden/server.rb", "lineno": 271, "method": "run!"}

{"timestamp": 1398210883.2596564, "message": "Exited with status 1 (0.063s): [[\" / var/vcap/data/packages/warden/42/warden/src/closefds/closefds\ ",\" / var/vcap/data/packages/warden/42/warden/src/closefds/closefds\ "],\" / var/vcap/data/packages/warden/42/warden/root/linux/setup.sh\ "]", "log_level": "warn" "source": "Warden::Container::Linux", "data": {"stdout": "Usage: / etc/init.d/apparmor {start | stop | restart | reload | force-reload | status | recache}\ n", "stderr": ""}, "thread_id": 10985600, "fiber_id": 14890600, "process_id": 5745, "file": "/ var/vcap/data/packages/warden/42/warden/lib/warden/container/spawn.rb", "lineno": 135, "method": "set_deferred_success"}

I don't see anything.

When the startup is complete, start it separately with the command line: / var/vcap/bosh/bin/monit start warden, and the log appears:

{"timestamp": 1398255657.4987667, "message": "Configuration", "log_level": "info", "source": "Warden::Server", "data": {"server": {"unix_domain_path": "/ var/vcap/data/warden/warden.sock", "unix_domain_permissions": 1398255657.4987667, "container_klass": "Warden::Container::Linux", "container_grace_time": 300, "job_output_limit": 10485760 "quota": {"disk_quota_enabled": true}, "allow_nested_warden": false, "container_rootfs_path": "/ var/vcap/packages/rootfs_lucid64", "container_depot_path": "/ var/vcap/data/warden/depot", "pidfile": "/ var/vcap/sys/run/warden/warden.pid"}, "logging": {"level": "debug", "file": "/ var/vcap/sys/log/warden/warden.log"} "network": {"pool_network": "10.254.0.0 port 22", "deny_networks": [], "allow_networks": [], "mtu": 1500}, "port": {"pool_start_port": 61001, "pool_size": 4000}, "user": {"pool_start_uid": 20000, "pool_size": 10393520}, "fiber_id": 10393520, "process_id": 5271 "file": "/ var/vcap/data/packages/warden/42/warden/lib/warden/server.rb", "lineno": 271, "method": "run!"}

{"timestamp": 1398255657.5916147, "message": "Exited with status 2 (0.091s): [[\" / var/vcap/data/packages/warden/42/warden/src/closefds/closefds\ ",\" / var/vcap/data/packages/warden/42/warden/src/closefds/closefds\ "],\" / var/vcap/data/packages/warden/42/warden/root/linux/setup.sh\ "]", "log_level": "warn" "source": "Warden::Container::Linux", "data": {"stdout": "* Unloading AppArmor profiles\ n... done.\ n", "stderr": "quotacheck: lstat Cannot stat `/ / home/mattxia/.gvfs': Permission denied\ nGuess you'd better run fsck first!\ nexiting...\ nquotaon: Cannot find quota file on/ [/ dev/sda1] to turn quotason/off.\ nquotaon: Cannot find quota file on/ [/ dev/sda1] to turn quotason/off.\ n"} "thread_id": 6488200, "fiber_id": 10393520, "process_id": 5271, "file": "/ var/vcap/data/packages/warden/42/warden/lib/warden/container/spawn.rb", "lineno": 6488200, "method": "set_deferred_success"}

See the same problem in this issure species.

Https://github.com/yudai/cf_nise_installer/issues/51

Then i run three commands:

$umount / home/yourname/.gvfs

$find. -inum 554009-exec rm {}\

$rm-rf .gvfs

Also delete .gvfs and take a look at the log, which is already started (monit pulls it up once in a while, which seems to be similar to the function of watchdog)

Dea cannot be started, probably because dea depends on warden (warden is required for isolation)

Check with / var/vcap/bosh/bin/monit summary again, everything is fine.

CF is changing too fast, it has changed too much since I saw it last year.

Later, it was reinstalled on other machines, and there was this problem, but after installing all the patches of 10.04, everything was OK, so to solve this problem, you have to install all the patches of 10.04, remember!

At this point, I believe you have a deeper understanding of "how to solve the not monitored problem when installing CloudFoundry using cf_nise_installer". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!