I'm trying to migrate my Sinatra App from the legacy Amazon Linux to V2 on Elastic Beanstalk using the Thin Server. The Thin Server refuses to start on deploy. However, it starts fine and works correctly if I manually start it as the webapp user with the command:
bundle exec thin start -R config.ru -e production -C config/thin.yml -V
Here are my configuration files:
.plaform/hooks/prebuild/02_set_permissioms.sh
#!/usr/bin/env bash
echo "Set permissions"
su -s /bin/bash -c "mkdir -p /var/run/thin"
su -s /bin/bash -c "mkdir -p /var/log/thin"
su -s /bin/bash -c "mkdir -p /var/log/thin/rotated"
chown -R webapp:webapp /var/run/thin
chown -R webapp:webapp /var/log/thin
chown -R webapp:webapp /var/log/thin/rotated
.plaform/hooks/03_symlink_pid.sh
#!/bin/bash
echo "Symlink thin PID to web PID"
set -xe
sudo ln -nsf /var/run/thin/thin.0.0.pid /var/pids/web.pid
.platform/nginx/conf.d/elasticbeanstalk-nginx-ruby-upstream.conf
upstream my_app {
server unix:///var/run/thin/thin.0.sock;
}
Procfile
web: bundle exec thin start -R config.ru -e production -C config/thin.yml -V
config/thin/yml
---
chdir: /var/app/current
environment: production
address: 0.0.0.0
port: 9292
timeout: 30
log: /var/log/thin/thin.log
pid: /var/run/thin/thin.pid
max_conns: 1024
max_persistent_conns: 512
require: []
wait: 30
threadpool_size: 20
daemonize: true
socket: /var/run/thin/thin.sock
servers: 1
/var/log/messages
Jan 12 12:45:58 ip-adress systemd: Starting This is web daemon...
Jan 12 12:45:58 ip-adress systemd: Started This is web daemon.
Jan 12 12:45:58 ip-adress systemd: Reloading.
Jan 12 12:45:58 ip-adress systemd: Starting The nginx HTTP and reverse proxy server...
Jan 12 12:45:58 ip-adress nginx: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
Jan 12 12:45:58 ip-adress nginx: nginx: configuration file /etc/nginx/nginx.conf test is successful
Jan 12 12:45:58 ip-adress systemd: Started The nginx HTTP and reverse proxy server.
Jan 12 12:45:58 ip-adress web: NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:45:58 ip-adress web: Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:45:58 ip-adress web: 2022-01-12 12:45:58 +0000 Starting server on /var/run/thin/thin.0.sock ...
Jan 12 12:45:58 ip-adress web: 2022-01-12 12:45:58 +0000 /opt/elasticbeanstalk/.rbenv/versions/2.6.9/bin/thin start --chdir="/var/app/current" --environment="production" --timeout=30 --log="/var/log/thin/thin.0.log" --pid="/var/run/thin/thin.0.pid" --max-conns=1024 --max-persistent-conns=512 --threadpool-size=20 --rackup="config.ru" --trace --daemonize --socket="/var/run/thin/thin.0.sock"
Jan 12 12:45:59 ip-adress healthd: Version 2 of the Ruby SDK will enter maintenance mode as of November 20, 2020. To continue receiving service updates and new features, please upgrade to Version 3. More information can be found here: https://aws.amazon.com/blogs/developer/deprecation-schedule-for-aws-sdk-for-ruby-v2/
Jan 12 12:45:59 ip-adress web: 2022-01-12 12:45:59 +0000 NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:45:59 ip-adress web: 2022-01-12 12:45:59 +0000 Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:45:59 ip-adress systemd: web.service holdoff time over, scheduling restart.
Jan 12 12:45:59 ip-adress systemd: Stopped This is web daemon.
Jan 12 12:45:59 ip-adress systemd: Starting This is web daemon...
Jan 12 12:45:59 ip-adress systemd: Started This is web daemon.
Jan 12 12:46:00 ip-adress web: NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:00 ip-adress web: Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:00 ip-adress web: 2022-01-12 12:46:00 +0000 Starting server on /var/run/thin/thin.0.sock ...
Jan 12 12:46:00 ip-adress web: 2022-01-12 12:46:00 +0000 /opt/elasticbeanstalk/.rbenv/versions/2.6.9/bin/thin start --chdir="/var/app/current" --environment="production" --timeout=30 --log="/var/log/thin/thin.0.log" --pid="/var/run/thin/thin.0.pid" --max-conns=1024 --max-persistent-conns=512 --threadpool-size=20 --rackup="config.ru" --trace --daemonize --socket="/var/run/thin/thin.0.sock"
Jan 12 12:46:00 ip-adress web: 2022-01-12 12:46:00 +0000 NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:00 ip-adress web: 2022-01-12 12:46:00 +0000 Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:01 ip-adress systemd: web.service holdoff time over, scheduling restart.
Jan 12 12:46:01 ip-adress systemd: Stopped This is web daemon.
Jan 12 12:46:01 ip-adress systemd: Starting This is web daemon...
Jan 12 12:46:01 ip-adress systemd: Started This is web daemon.
Jan 12 12:46:01 ip-adress web: NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:01 ip-adress web: Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:01 ip-adress systemd: Created slice User Slice of root.
Jan 12 12:46:01 ip-adress systemd: Started Session 1 of user root.
Jan 12 12:46:01 ip-adress web: 2022-01-12 12:46:01 +0000 Starting server on /var/run/thin/thin.0.sock ...
Jan 12 12:46:01 ip-adress web: 2022-01-12 12:46:01 +0000 /opt/elasticbeanstalk/.rbenv/versions/2.6.9/bin/thin start --chdir="/var/app/current" --environment="production" --timeout=30 --log="/var/log/thin/thin.0.log" --pid="/var/run/thin/thin.0.pid" --max-conns=1024 --max-persistent-conns=512 --threadpool-size=20 --rackup="config.ru" --trace --daemonize --socket="/var/run/thin/thin.0.sock"
Jan 12 12:46:01 ip-adress CloudWatch-PutInstanceData: Cannot obtain instance id from EC2 meta-data.
Jan 12 12:46:01 ip-adress systemd: Removed slice User Slice of root.
Jan 12 12:46:02 ip-adress web: 2022-01-12 12:46:02 +0000 NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:02 ip-adress web: 2022-01-12 12:46:02 +0000 Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:02 ip-adress systemd: web.service holdoff time over, scheduling restart.
Jan 12 12:46:02 ip-adress systemd: Stopped This is web daemon.
Jan 12 12:46:02 ip-adress systemd: Starting This is web daemon...
Jan 12 12:46:02 ip-adress systemd: Started This is web daemon.
Jan 12 12:46:02 ip-adress web: NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:02 ip-adress web: Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:02 ip-adress web: 2022-01-12 12:46:02 +0000 Starting server on /var/run/thin/thin.0.sock ...
Jan 12 12:46:02 ip-adress web: 2022-01-12 12:46:02 +0000 /opt/elasticbeanstalk/.rbenv/versions/2.6.9/bin/thin start --chdir="/var/app/current" --environment="production" --timeout=30 --log="/var/log/thin/thin.0.log" --pid="/var/run/thin/thin.0.pid" --max-conns=1024 --max-persistent-conns=512 --threadpool-size=20 --rackup="config.ru" --trace --daemonize --socket="/var/run/thin/thin.0.sock"
Jan 12 12:46:03 ip-adress web: 2022-01-12 12:46:03 +0000 NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:03 ip-adress web: 2022-01-12 12:46:03 +0000 Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:03 ip-adress systemd: web.service holdoff time over, scheduling restart.
Jan 12 12:46:03 ip-adress systemd: Stopped This is web daemon.
Jan 12 12:46:03 ip-adress systemd: Starting This is web daemon...
Jan 12 12:46:03 ip-adress systemd: Started This is web daemon.
Jan 12 12:46:03 ip-adress web: NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:03 ip-adress web: Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:03 ip-adress web: 2022-01-12 12:46:03 +0000 Starting server on /var/run/thin/thin.0.sock ...
Jan 12 12:46:03 ip-adress web: 2022-01-12 12:46:03 +0000 /opt/elasticbeanstalk/.rbenv/versions/2.6.9/bin/thin start --chdir="/var/app/current" --environment="production" --timeout=30 --log="/var/log/thin/thin.0.log" --pid="/var/run/thin/thin.0.pid" --max-conns=1024 --max-persistent-conns=512 --threadpool-size=20 --rackup="config.ru" --trace --daemonize --socket="/var/run/thin/thin.0.sock"
Jan 12 12:46:04 ip-adress web: 2022-01-12 12:46:04 +0000 NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:04 ip-adress web: 2022-01-12 12:46:04 +0000 Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:04 ip-adress systemd: web.service holdoff time over, scheduling restart.
Jan 12 12:46:04 ip-adress systemd: Stopped This is web daemon.
Jan 12 12:46:04 ip-adress systemd: Starting This is web daemon...
Jan 12 12:46:04 ip-adress systemd: Started This is web daemon.
Jan 12 12:46:04 ip-adress web: NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:04 ip-adress web: Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:04 ip-adress web: 2022-01-12 12:46:04 +0000 Starting server on /var/run/thin/thin.0.sock ...
Jan 12 12:46:04 ip-adress web: 2022-01-12 12:46:04 +0000 /opt/elasticbeanstalk/.rbenv/versions/2.6.9/bin/thin start --chdir="/var/app/current" --environment="production" --timeout=30 --log="/var/log/thin/thin.0.log" --pid="/var/run/thin/thin.0.pid" --max-conns=1024 --max-persistent-conns=512 --threadpool-size=20 --rackup="config.ru" --trace --daemonize --socket="/var/run/thin/thin.0.sock"
Jan 12 12:46:05 ip-adress web: 2022-01-12 12:46:05 +0000 NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:05 ip-adress web: 2022-01-12 12:46:05 +0000 Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:05 ip-adress systemd: web.service holdoff time over, scheduling restart.
Jan 12 12:46:05 ip-adress systemd: Stopped This is web daemon.
Jan 12 12:46:05 ip-adress systemd: start request repeated too quickly for web.service
Jan 12 12:46:05 ip-adress systemd: Failed to start This is web daemon.
Jan 12 12:46:05 ip-adress systemd: Unit web.service entered failed state.
Jan 12 12:46:05 ip-adress systemd: web.service failed.
/var/log/web.stdout.log
Jan 12 12:45:58 ip-ddress web: NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:45:58 ip-ddress web: Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:45:58 ip-ddress web: 2022-01-12 12:45:58 +0000 Starting server on /var/run/thin/thin.0.sock ...
Jan 12 12:45:58 ip-ddress web: 2022-01-12 12:45:58 +0000 /opt/elasticbeanstalk/.rbenv/versions/2.6.9/bin/thin start --chdir="/var/app/current" --environment="production" --timeout=30 --log="/var/log/thin/thin.0.log" --pid="/var/run/thin/thin.0.pid" --max-conns=1024 --max-persistent-conns=512 --threadpool-size=20 --rackup="config.ru" --trace --daemonize --socket="/var/run/thin/thin.0.sock"
Jan 12 12:45:59 ip-ddress web: 2022-01-12 12:45:59 +0000 NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:45:59 ip-ddress web: 2022-01-12 12:45:59 +0000 Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:00 ip-ddress web: NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:00 ip-ddress web: Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:00 ip-ddress web: 2022-01-12 12:46:00 +0000 Starting server on /var/run/thin/thin.0.sock ...
Jan 12 12:46:00 ip-ddress web: 2022-01-12 12:46:00 +0000 /opt/elasticbeanstalk/.rbenv/versions/2.6.9/bin/thin start --chdir="/var/app/current" --environment="production" --timeout=30 --log="/var/log/thin/thin.0.log" --pid="/var/run/thin/thin.0.pid" --max-conns=1024 --max-persistent-conns=512 --threadpool-size=20 --rackup="config.ru" --trace --daemonize --socket="/var/run/thin/thin.0.sock"
Jan 12 12:46:00 ip-ddress web: 2022-01-12 12:46:00 +0000 NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:00 ip-ddress web: 2022-01-12 12:46:00 +0000 Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:01 ip-ddress web: NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:01 ip-ddress web: Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:01 ip-ddress web: 2022-01-12 12:46:01 +0000 Starting server on /var/run/thin/thin.0.sock ...
Jan 12 12:46:01 ip-ddress web: 2022-01-12 12:46:01 +0000 /opt/elasticbeanstalk/.rbenv/versions/2.6.9/bin/thin start --chdir="/var/app/current" --environment="production" --timeout=30 --log="/var/log/thin/thin.0.log" --pid="/var/run/thin/thin.0.pid" --max-conns=1024 --max-persistent-conns=512 --threadpool-size=20 --rackup="config.ru" --trace --daemonize --socket="/var/run/thin/thin.0.sock"
Jan 12 12:46:02 ip-ddress web: 2022-01-12 12:46:02 +0000 NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:02 ip-ddress web: 2022-01-12 12:46:02 +0000 Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:02 ip-ddress web: NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:02 ip-ddress web: Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:02 ip-ddress web: 2022-01-12 12:46:02 +0000 Starting server on /var/run/thin/thin.0.sock ...
Jan 12 12:46:02 ip-ddress web: 2022-01-12 12:46:02 +0000 /opt/elasticbeanstalk/.rbenv/versions/2.6.9/bin/thin start --chdir="/var/app/current" --environment="production" --timeout=30 --log="/var/log/thin/thin.0.log" --pid="/var/run/thin/thin.0.pid" --max-conns=1024 --max-persistent-conns=512 --threadpool-size=20 --rackup="config.ru" --trace --daemonize --socket="/var/run/thin/thin.0.sock"
Jan 12 12:46:03 ip-ddress web: 2022-01-12 12:46:03 +0000 NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:03 ip-ddress web: 2022-01-12 12:46:03 +0000 Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:03 ip-ddress web: NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:03 ip-ddress web: Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:03 ip-ddress web: 2022-01-12 12:46:03 +0000 Starting server on /var/run/thin/thin.0.sock ...
Jan 12 12:46:03 ip-ddress web: 2022-01-12 12:46:03 +0000 /opt/elasticbeanstalk/.rbenv/versions/2.6.9/bin/thin start --chdir="/var/app/current" --environment="production" --timeout=30 --log="/var/log/thin/thin.0.log" --pid="/var/run/thin/thin.0.pid" --max-conns=1024 --max-persistent-conns=512 --threadpool-size=20 --rackup="config.ru" --trace --daemonize --socket="/var/run/thin/thin.0.sock"
Jan 12 12:46:04 ip-ddress web: 2022-01-12 12:46:04 +0000 NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:04 ip-ddress web: 2022-01-12 12:46:04 +0000 Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:04 ip-ddress web: NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:04 ip-ddress web: Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
Jan 12 12:46:04 ip-ddress web: 2022-01-12 12:46:04 +0000 Starting server on /var/run/thin/thin.0.sock ...
Jan 12 12:46:04 ip-ddress web: 2022-01-12 12:46:04 +0000 /opt/elasticbeanstalk/.rbenv/versions/2.6.9/bin/thin start --chdir="/var/app/current" --environment="production" --timeout=30 --log="/var/log/thin/thin.0.log" --pid="/var/run/thin/thin.0.pid" --max-conns=1024 --max-persistent-conns=512 --threadpool-size=20 --rackup="config.ru" --trace --daemonize --socket="/var/run/thin/thin.0.sock"
Jan 12 12:46:05 ip-ddress web: 2022-01-12 12:46:05 +0000 NOTE: Gem::Specification#has_rdoc= is deprecated with no replacement. It will be removed in Rubygems 4
Jan 12 12:46:05 ip-ddress web: 2022-01-12 12:46:05 +0000 Gem::Specification#has_rdoc= called from /var/app/current/vendor/gems/async-rack/async-rack.gemspec:16.
The Thin log is empty and does not through out any errors.
The solution is to not daemonize the Thin server in config.yml
daemonize: false
Related
First step is - sudo yum install snapd
This seems to work fine download the dependencies and all and setup is completed
Installed Version : snapd.x86_64 0:2.45-1.el7
Second step is - sudo systemctl enable --now snapd.socket
Gives output as > Created symlink from /etc/systemd/system/sockets.target.wants/snapd.socket to /usr/lib/systemd/system/snapd.socket.
Now checking status - sudo systemctl status snapd gives:
● snapd.service - Snap Daemon
Loaded: loaded (/usr/lib/systemd/system/snapd.service; disabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Mon 2020-12-07 11:17:28 IST; 16min ago
Main PID: 5726 (code=exited, status=1/FAILURE)
systemd[1]: snapd.service holdoff time over, scheduling restart.
systemd[1]: Stopped Snap Daemon.
systemd[1]: start request repeated too quickly for snapd.service
systemd[1]: Failed to start Snap Daemon.
systemd[1]: Unit snapd.service entered failed state.
systemd[1]: Triggering OnFailure= dependencies of snapd.service.
systemd[1]: snapd.service failed.
systemd[1]: start request repeated too quickly for snapd.service
systemd[1]: Failed to start Snap Daemon.
systemd[1]: snapd.service failed.
Possible Solutions tried- 1) Re-installation after purge, 2) enabled socket and service after reboot again.
journalctl -u snapd.service output:
-- Logs begin at Wed 2020-12-09 11:21:36 IST, end at Thu 2020-12-17 12:40:16 IST. --
Dec 17 12:36:45 whf00jfw systemd[1]: Starting Snap Daemon...
Dec 17 12:36:45 whf00jfw snapd[4639]: AppArmor status: apparmor not enabled
Dec 17 12:36:45 whf00jfw snapd[4639]: daemon.go:343: started snapd/2.45-1.el7 (series 16; classic; devmode) ol/7.6 (amd64) linux/4.14.35-1902.304.6.el7uek.
Dec 17 12:36:46 whf00jfw snapd[4639]: daemon.go:436: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Dec 17 12:36:46 whf00jfw snapd[4639]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: fork/exec /usr/lib/snapd/snap
Dec 17 12:36:46 whf00jfw systemd[1]: snapd.service: main process exited, code=exited, status=1/FAILURE
Dec 17 12:36:46 whf00jfw systemd[1]: Failed to start Snap Daemon.
Dec 17 12:36:46 whf00jfw systemd[1]: Unit snapd.service entered failed state.
Dec 17 12:36:46 whf00jfw systemd[1]: Triggering OnFailure= dependencies of snapd.service.
Dec 17 12:36:46 whf00jfw systemd[1]: snapd.service failed.
Dec 17 12:36:46 whf00jfw systemd[1]: snapd.service holdoff time over, scheduling restart.
Dec 17 12:36:46 whf00jfw snapd[4673]: AppArmor status: apparmor not enabled
Dec 17 12:36:46 whf00jfw systemd[1]: Stopped Snap Daemon.
Dec 17 12:36:46 whf00jfw systemd[1]: Starting Snap Daemon...
Dec 17 12:36:46 whf00jfw snapd[4673]: daemon.go:343: started snapd/2.45-1.el7 (series 16; classic; devmode) ol/7.6 (amd64) linux/4.14.35-1902.304.6.el7uek.
Dec 17 12:36:46 whf00jfw snapd[4673]: daemon.go:436: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Dec 17 12:36:46 whf00jfw snapd[4673]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: fork/exec /usr/lib/snapd/snap
Dec 17 12:36:46 whf00jfw systemd[1]: snapd.service: main process exited, code=exited, status=1/FAILURE
Dec 17 12:36:46 whf00jfw systemd[1]: Failed to start Snap Daemon.
Dec 17 12:36:46 whf00jfw systemd[1]: Unit snapd.service entered failed state.
Dec 17 12:36:46 whf00jfw systemd[1]: Triggering OnFailure= dependencies of snapd.service.
Dec 17 12:36:46 whf00jfw systemd[1]: snapd.service failed.
Dec 17 12:36:46 whf00jfw systemd[1]: snapd.service holdoff time over, scheduling restart.
Dec 17 12:36:46 whf00jfw systemd[1]: Stopped Snap Daemon.
Dec 17 12:36:46 whf00jfw systemd[1]: Starting Snap Daemon...
Dec 17 12:36:46 whf00jfw snapd[4699]: AppArmor status: apparmor not enabled
Dec 17 12:36:46 whf00jfw snapd[4699]: daemon.go:343: started snapd/2.45-1.el7 (series 16; classic; devmode) ol/7.6 (amd64) linux/4.14.35-1902.304.6.el7uek.
Dec 17 12:36:46 whf00jfw snapd[4699]: daemon.go:436: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Dec 17 12:36:46 whf00jfw snapd[4699]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: fork/exec /usr/lib/snapd/snap
Dec 17 12:36:46 whf00jfw systemd[1]: snapd.service: main process exited, code=exited, status=1/FAILURE
Dec 17 12:36:46 whf00jfw systemd[1]: Failed to start Snap Daemon.
Dec 17 12:36:46 whf00jfw systemd[1]: Unit snapd.service entered failed state.
Dec 17 12:36:46 whf00jfw systemd[1]: Triggering OnFailure= dependencies of snapd.service.
Dec 17 12:36:46 whf00jfw systemd[1]: snapd.service failed.
Dec 17 12:36:46 whf00jfw systemd[1]: snapd.service holdoff time over, scheduling restart.
Dec 17 12:36:46 whf00jfw systemd[1]: Stopped Snap Daemon.
Dec 17 12:36:46 whf00jfw systemd[1]: Starting Snap Daemon...
Dec 17 12:36:46 whf00jfw snapd[4745]: AppArmor status: apparmor not enabled
Dec 17 12:36:46 whf00jfw snapd[4745]: daemon.go:343: started snapd/2.45-1.el7 (series 16; classic; devmode) ol/7.6 (amd64) linux/4.14.35-1902.304.6.el7uek.
Dec 17 12:36:46 whf00jfw snapd[4745]: daemon.go:436: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Dec 17 12:36:46 whf00jfw snapd[4745]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: fork/exec /usr/lib/snapd/snap
Dec 17 12:36:46 whf00jfw systemd[1]: snapd.service: main process exited, code=exited, status=1/FAILURE
Dec 17 12:36:46 whf00jfw systemd[1]: Failed to start Snap Daemon.
Dec 17 12:36:46 whf00jfw systemd[1]: Unit snapd.service entered failed state.
Dec 17 12:36:46 whf00jfw systemd[1]: Triggering OnFailure= dependencies of snapd.service.
Dec 17 12:36:46 whf00jfw systemd[1]: snapd.service failed.
Dec 17 12:36:47 whf00jfw systemd[1]: snapd.service holdoff time over, scheduling restart.
Dec 17 12:36:47 whf00jfw systemd[1]: Stopped Snap Daemon.
Dec 17 12:36:47 whf00jfw systemd[1]: Starting Snap Daemon...
Dec 17 12:36:47 whf00jfw snapd[4775]: AppArmor status: apparmor not enabled
Dec 17 12:36:47 whf00jfw snapd[4775]: daemon.go:343: started snapd/2.45-1.el7 (series 16; classic; devmode) ol/7.6 (amd64) linux/4.14.35-1902.304.6.el7uek.
Dec 17 12:36:47 whf00jfw snapd[4775]: daemon.go:436: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Dec 17 12:36:47 whf00jfw snapd[4775]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: fork/exec /usr/lib/snapd/snap
Dec 17 12:36:47 whf00jfw systemd[1]: snapd.service: main process exited, code=exited, status=1/FAILURE
Dec 17 12:36:47 whf00jfw systemd[1]: Failed to start Snap Daemon.
Dec 17 12:36:47 whf00jfw systemd[1]: Unit snapd.service entered failed state.
Dec 17 12:36:47 whf00jfw systemd[1]: Triggering OnFailure= dependencies of snapd.service.
Dec 17 12:36:47 whf00jfw systemd[1]: snapd.service failed.
Dec 17 12:36:47 whf00jfw systemd[1]: snapd.service holdoff time over, scheduling restart.
Dec 17 12:36:47 whf00jfw systemd[1]: Stopped Snap Daemon.
Dec 17 12:36:47 whf00jfw systemd[1]: start request repeated too quickly for snapd.service
Dec 17 12:36:47 whf00jfw systemd[1]: Failed to start Snap Daemon.
Dec 17 12:36:47 whf00jfw systemd[1]: Unit snapd.service entered failed state.
Dec 17 12:36:47 whf00jfw systemd[1]: Triggering OnFailure= dependencies of snapd.service.
Dec 17 12:36:47 whf00jfw systemd[1]: snapd.service failed.
Dec 17 12:36:47 whf00jfw systemd[1]: start request repeated too quickly for snapd.service
Dec 17 12:36:47 whf00jfw systemd[1]: Failed to start Snap Daemon.
Dec 17 12:36:47 whf00jfw systemd[1]: snapd.service failed.
Dec 17 12:40:15 whf00jfw systemd[1]: Starting Snap Daemon...
Dec 17 12:40:15 whf00jfw snapd[5826]: AppArmor status: apparmor not enabled
Dec 17 12:40:15 whf00jfw snapd[5826]: daemon.go:343: started snapd/2.45-1.el7 (series 16; classic; devmode) ol/7.6 (amd64) linux/4.14.35-1902.304.6.el7uek.
Dec 17 12:40:15 whf00jfw snapd[5826]: daemon.go:436: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Dec 17 12:40:15 whf00jfw snapd[5826]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: fork/exec /usr/lib/snapd/snap
Dec 17 12:40:15 whf00jfw systemd[1]: snapd.service: main process exited, code=exited, status=1/FAILURE
Dec 17 12:40:15 whf00jfw systemd[1]: Failed to start Snap Daemon.
Dec 17 12:40:15 whf00jfw systemd[1]: Unit snapd.service entered failed state.
Dec 17 12:40:15 whf00jfw systemd[1]: Triggering OnFailure= dependencies of snapd.service.
Dec 17 12:40:15 whf00jfw systemd[1]: snapd.service failed.
Dec 17 12:40:15 whf00jfw systemd[1]: snapd.service holdoff time over, scheduling restart.
Dec 17 12:40:15 whf00jfw systemd[1]: Stopped Snap Daemon.
Dec 17 12:40:15 whf00jfw systemd[1]: Starting Snap Daemon...
Dec 17 12:40:15 whf00jfw snapd[5855]: AppArmor status: apparmor not enabled
Dec 17 12:40:15 whf00jfw snapd[5855]: daemon.go:343: started snapd/2.45-1.el7 (series 16; classic; devmode) ol/7.6 (amd64) linux/4.14.35-1902.304.6.el7uek.
Dec 17 12:40:15 whf00jfw snapd[5855]: daemon.go:436: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Dec 17 12:40:15 whf00jfw snapd[5855]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: fork/exec /usr/lib/snapd/snap
Dec 17 12:40:15 whf00jfw systemd[1]: snapd.service: main process exited, code=exited, status=1/FAILURE
Dec 17 12:40:15 whf00jfw systemd[1]: Failed to start Snap Daemon.
Dec 17 12:40:15 whf00jfw systemd[1]: Unit snapd.service entered failed state.
Dec 17 12:40:15 whf00jfw systemd[1]: Triggering OnFailure= dependencies of snapd.service.
Dec 17 12:40:15 whf00jfw systemd[1]: snapd.service failed.
Dec 17 12:40:16 whf00jfw systemd[1]: snapd.service holdoff time over, scheduling restart.
Dec 17 12:40:16 whf00jfw systemd[1]: Stopped Snap Daemon.
Dec 17 12:40:16 whf00jfw systemd[1]: Starting Snap Daemon...
Dec 17 12:40:16 whf00jfw snapd[5952]: AppArmor status: apparmor not enabled
Dec 17 12:40:16 whf00jfw snapd[5952]: daemon.go:343: started snapd/2.45-1.el7 (series 16; classic; devmode) ol/7.6 (amd64) linux/4.14.35-1902.304.6.el7uek.
Dec 17 12:40:16 whf00jfw snapd[5952]: daemon.go:436: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Dec 17 12:40:16 whf00jfw snapd[5952]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: fork/exec /usr/lib/snapd/snap
Dec 17 12:40:16 whf00jfw systemd[1]: snapd.service: main process exited, code=exited, status=1/FAILURE
Dec 17 12:40:16 whf00jfw systemd[1]: Failed to start Snap Daemon.
Dec 17 12:40:16 whf00jfw systemd[1]: Unit snapd.service entered failed state.
Dec 17 12:40:16 whf00jfw systemd[1]: Triggering OnFailure= dependencies of snapd.service.
Dec 17 12:40:16 whf00jfw systemd[1]: snapd.service failed.
Dec 17 12:40:16 whf00jfw systemd[1]: snapd.service holdoff time over, scheduling restart.
Dec 17 12:40:16 whf00jfw systemd[1]: Stopped Snap Daemon.
Dec 17 12:40:16 whf00jfw systemd[1]: Starting Snap Daemon...
Dec 17 12:40:16 whf00jfw snapd[6154]: AppArmor status: apparmor not enabled
Dec 17 12:40:16 whf00jfw snapd[6154]: daemon.go:343: started snapd/2.45-1.el7 (series 16; classic; devmode) ol/7.6 (amd64) linux/4.14.35-1902.304.6.el7uek.
Dec 17 12:40:16 whf00jfw snapd[6154]: daemon.go:436: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Dec 17 12:40:16 whf00jfw snapd[6154]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: fork/exec /usr/lib/snapd/snap
Dec 17 12:40:16 whf00jfw systemd[1]: snapd.service: main process exited, code=exited, status=1/FAILURE
Dec 17 12:40:16 whf00jfw systemd[1]: Failed to start Snap Daemon.
Dec 17 12:40:16 whf00jfw systemd[1]: Unit snapd.service entered failed state.
Dec 17 12:40:16 whf00jfw systemd[1]: Triggering OnFailure= dependencies of snapd.service.
Dec 17 12:40:16 whf00jfw systemd[1]: snapd.service failed.
Dec 17 12:40:16 whf00jfw systemd[1]: snapd.service holdoff time over, scheduling restart.
Dec 17 12:40:16 whf00jfw systemd[1]: Stopped Snap Daemon.
Dec 17 12:40:16 whf00jfw systemd[1]: Starting Snap Daemon...
Dec 17 12:40:16 whf00jfw snapd[6260]: AppArmor status: apparmor not enabled
Dec 17 12:40:16 whf00jfw snapd[6260]: daemon.go:343: started snapd/2.45-1.el7 (series 16; classic; devmode) ol/7.6 (amd64) linux/4.14.35-1902.304.6.el7uek.
Dec 17 12:40:16 whf00jfw snapd[6260]: daemon.go:436: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Dec 17 12:40:16 whf00jfw snapd[6260]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: fork/exec /usr/lib/snapd/snap
Dec 17 12:40:16 whf00jfw systemd[1]: snapd.service: main process exited, code=exited, status=1/FAILURE
Dec 17 12:40:16 whf00jfw systemd[1]: Failed to start Snap Daemon.
Dec 17 12:40:16 whf00jfw systemd[1]: Unit snapd.service entered failed state.
Dec 17 12:40:16 whf00jfw systemd[1]: Triggering OnFailure= dependencies of snapd.service.
Dec 17 12:40:16 whf00jfw systemd[1]: snapd.service failed.
Dec 17 12:40:16 whf00jfw systemd[1]: snapd.service holdoff time over, scheduling restart.
Dec 17 12:40:16 whf00jfw systemd[1]: Stopped Snap Daemon.
Dec 17 12:40:16 whf00jfw systemd[1]: start request repeated too quickly for snapd.service
Dec 17 12:40:16 whf00jfw systemd[1]: Failed to start Snap Daemon.
Dec 17 12:40:16 whf00jfw systemd[1]: Unit snapd.service entered failed state.
Dec 17 12:40:16 whf00jfw systemd[1]: Triggering OnFailure= dependencies of snapd.service.
Dec 17 12:40:16 whf00jfw systemd[1]: snapd.service failed.
Dec 17 12:40:16 whf00jfw systemd[1]: start request repeated too quickly for snapd.service
Dec 17 12:40:16 whf00jfw systemd[1]: Failed to start Snap Daemon.
Dec 17 12:40:16 whf00jfw systemd[1]: snapd.service failed.
It appears to be an issue with strict confinement not being supported on operating systems that don't use AppArmor (OL, CentOS, RHEL). There are steps needed to make that work. Did you create the symbolic link?
sudo ln -s /var/lib/snapd/snap /snap
This worked for me:
sudo yum install snapd
sudo ln -s /var/lib/snapd/snap /snap
sudo systemctl enable --now snapd.socket
sudo systemctl restart snapd
<restart session>
sudo snap install firefox
sudo snap install --classic nano
Hi i just set up a trackmania server which works fine when starting via command line. Now i want to manage it with systemd, so it starts on boot and gets restartet if it crashes.
Here is my systemd service file:
[Unit]
Description=Trackmania 2020 Server
After=network.target
[Service]
User=trackmania
Group=trackmania
Restart=always
RestartSec=30
WorkingDirectory=/home/trackmania/server
ExecStart=/home/trackmania/server/TrackmaniaServer /title=Trackmania /game_Settings=Matchsettings/tracklist.txt /dedicated_cfg=dedicated_cfg.txt
[Install]
WantedBy=multi-user.target
When starting the service, the status command returns:
* trackmania_server.service - Trackmania 2020 Server
Loaded: loaded (/etc/systemd/system/trackmania_server.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) since Thu 2020-07-09 21:08:31 UTC; 29s ago
Process: 1759 ExecStart=/home/trackmania/server/TrackmaniaServer /title=Trackmania /game_Settings=Matchsettings/tracklist.txt /dedicated_cfg=dedicated_cfg.txt (code=exited, status=0/SUCCESS)
Main PID: 1759 (code=exited, status=0/SUCCESS)
When stopping the service this is returned:
* trackmania_server.service - Trackmania 2020 Server
Loaded: loaded (/etc/systemd/system/trackmania_server.service; disabled; vendor preset: enabled)
Active: inactive (dead)
Jul 09 21:11:03 vps-zap558747-2 systemd[1]: Started Trackmania 2020 Server.
Jul 09 21:11:03 vps-zap558747-2 TrackmaniaServer[1847]: Starting Trackmania Date=2020-07-07_23_30 Svn=105917 GameVersion=3.3.0...
Jul 09 21:11:03 vps-zap558747-2 TrackmaniaServer[1847]: ManiaPlanet server daemon started with pid=1848 (parent=1847).
Jul 09 21:11:03 vps-zap558747-2 TrackmaniaServer[1847]: Configuration file : dedicated_cfg.txt
Jul 09 21:11:03 vps-zap558747-2 TrackmaniaServer[1847]: Loading system configuration...
Jul 09 21:11:03 vps-zap558747-2 TrackmaniaServer[1847]: ...system configuration loaded
Jul 09 21:11:04 vps-zap558747-2 TrackmaniaServer[1847]: Loading cache...
Jul 09 21:11:04 vps-zap558747-2 TrackmaniaServer[1847]: ...OK
Jul 09 21:11:04 vps-zap558747-2 systemd[1]: trackmania_server.service: Succeeded.
Jul 09 21:11:04 vps-zap558747-2 systemd[1]: Stopped Trackmania 2020 Server.
To me it looks like the server is started when i stop the service and well then immediately terminated again. What am i doing wrong? o.O
Try using the /nodaemon switch on the server command line
While giving sudo update-rc.d -f sonar remove I'm getting the below error
insserv: warning: script 'K01sonarqube' missing LSB tags and overrides
insserv: warning: script 'sonarqube' missing LSB tags and overrides
insserv: warning: script 'sonar' missing LSB tags and overrides
While starting sonarqube i'm getting
● sonarqube.service - SonarQube service
Loaded: loaded (/etc/systemd/system/sonarqube.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Fri 2018-10-19 12:48:24 IST; 14s ago
Process: 11420 ExecStop=/opt/sonarqube/sonarqube-6.7.5/bin/linux-x86-64/sonar.sh stop (code=exited, status=0/SUCCESS)
Process: 11372 ExecStart=/opt/sonarqube/sonarqube-6.7.5/bin/linux-x86-64/sonar.sh start (code=exited, status=0/SUCCESS)
Main PID: 984 (code=exited, status=1/FAILURE)
Oct 19 12:48:24 master-VB systemd[1]: Started SonarQube service.
Oct 19 12:48:24 master-VB systemd[1]: sonarqube.service: Service hold-off time over, scheduling restart.
Oct 19 12:48:24 master-VB systemd[1]: Stopped SonarQube service.
Oct 19 12:48:24 master-VB systemd[1]: sonarqube.service: Start request repeated too quickly.
Oct 19 12:48:24 master-VB systemd[1]: Failed to start SonarQube service.
I'm currently building up a test environment for HPE ALM Octane for my company. This Application uses Elasticsearch. Now I have the problem, that I can't start my Elasticsearchserver and I'm a bit at the end of my nerves ;).
Cause Octane works with Elasticsearch version 2.4.0, I'm also forced to work with this version.
I get the following Error:
Error - Console Screenshot
elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service;
enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2017-02-21 09:40:50 CET; 1h 9min ago
Process: 954 ExecStart=/usr/share/elasticsearch/bin/elasticsearch
-Des.pidfile=${PID_DIR}/elasticsearch.pid
-Des.default.path.home=${ES_HOME} -Des.default.path.logs=${LOG_DIR}
-Des.default.path.data=${DATA_DIR} -Des.default.path.conf=${CONF_DIR}
(code=exited, status=1/FAILURE)
Process: 949 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)
Main PID: 954 (code=exited, status=1/FAILURE)
Feb 21 09:40:50 linux-rfw5 elasticsearch[954]: at java.nio.file.Files.newInputStream(Files.java:152)
Feb 21 09:40:50 linux-rfw5 elasticsearch[954]: at org.elasticsearch.common.settings.Settings$Builder.loadFromPath(Settings.java:1067)
Feb 21 09:40:50 linux-rfw5 elasticsearch[954]: at org.elasticsearch.node.internal.InternalSettingsPreparer.prepareEnvironment(InternalSettingsPreparer.java:88)
Feb 21 09:40:50 linux-rfw5 elasticsearch[954]: at org.elasticsearch.bootstrap.Bootstrap.initialSettings(Bootstrap.java:218)
Feb 21 09:40:50 linux-rfw5 elasticsearch[954]: at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:257)
Feb 21 09:40:50 linux-rfw5 elasticsearch[954]: at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:35)
Feb 21 09:40:50 linux-rfw5 elasticsearch[954]: Refer to the log for complete error details.
Feb 21 09:40:50 linux-rfw5 systemd 1 : elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
Feb 21 09:40:50 linux-rfw5 systemd 1 : elasticsearch.service: Unit entered failed state.
Feb 21 09:40:50 linux-rfw5 systemd 1 : elasticsearch.service: Failed with result 'exit-code'.
I configured the absolute minimum, that is possible. My Configurations:
elasticsearch.yml (/etc/elasticsearch/)
1.1 cluster.name: octane_test
1.2 node.name: elasticNode
1.3 network.host: 127.0.0.1 (yes localhost, cause I'm running the octane server on the same host)
http.port: 9200 elasticsearch (/etc/sysconfig/)
2.1 ES_HEAP_SIZE=4g (4 GB is 50% of the maximum memory)
I appreciate your help ;)
Joel
I am getting this error on my Mesos Master node.
Anyone know what it means and how to resolve it?
bash-4.2$ sudo systemctl status zookeeper
â— zookeeper.service - Apache ZooKeeper
Loaded: loaded (/usr/lib/systemd/system/zookeeper.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2016-08-24 01:44:31 EDT; 2s ago
Process: 3164 ExecStart=/opt/mesosphere/zookeeper/bin/zkServer.sh start-foreground (code=exited, status=1/FAILURE)
Main PID: 3164 (code=exited, status=1/FAILURE)
Aug 24 01:44:31 scsor0004331001.rtp.openenglab.netapp.com systemd[1]: Unit zookeeper.service entered failed state.
Aug 24 01:44:31 scsor0004331001.rtp.openenglab.netapp.com systemd[1]: zookeeper.service failed.
sudo journalctl -u zookeeper
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: Using config: /etc/zookeeper/conf/zoo.cfg
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: 2016-08-24 01:19:52,582 [myid:] - INFO [main:QuorumPeerConfig#103] - Reading configuration from: /etc/zookeeper/conf/zoo.cfg
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: 2016-08-24 01:19:52,587 [myid:] - INFO [main:QuorumPeerConfig#340] - Defaulting to majority quorums
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: 2016-08-24 01:19:52,589 [myid:1] - INFO [main:DatadirCleanupManager#78] - autopurge.snapRetainCount set to 3
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: 2016-08-24 01:19:52,590 [myid:1] - INFO [main:DatadirCleanupManager#79] - autopurge.purgeInterval set to 0
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: 2016-08-24 01:19:52,590 [myid:1] - INFO [main:DatadirCleanupManager#101] - Purge task is not scheduled.
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: 2016-08-24 01:19:52,600 [myid:1] - INFO [main:QuorumPeerMain#127] - Starting quorum peer
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: 2016-08-24 01:19:52,610 [myid:1] - INFO [main:NIOServerCnxnFactory#94] - binding to port 0.0.0.0/0.0.0.0:2181
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: 2016-08-24 01:19:52,611 [myid:1] - ERROR [main:QuorumPeerMain#89] - Unexpected exception, exiting abnormally
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: java.net.BindException: Address already in use
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: at sun.nio.ch.Net.bind0(Native Method)
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: at sun.nio.ch.Net.bind(Net.java:433)
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: at sun.nio.ch.Net.bind(Net.java:425)
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: at org.apache.zookeeper.server.NIOServerCnxnFactory.configure(NIOServerCnxnFactory.java:95)
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: at org.apache.zookeeper.server.quorum.QuorumPeerMain.runFromConfig(QuorumPeerMain.java:130)
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: at org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:111)
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com zookeeper[382]: at org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:78)
Aug 24 01:19:52 scsor0004331001.rtp.openenglab.netapp.com systemd[1]: zookeeper.service: main process exited, code=exited, status=1/FAILURE