baasbox on openshift error 503 - openshift

I have a small problem, i'am trying to install the mbaas "baasbox" on openshift and i'am getting 503 page, what does it could be??
here is the tutorial that i followed here
the rhc tail give me
[2014-04-11 01:13:50] INFO WEBrick 1.3.1
[2014-04-11 01:13:50] INFO ruby 1.8.7 (2011-06-30) [x86_64-linux]
[2014-04-11 01:13:50] INFO WEBrick::HTTPServer#start: pid=398035 port=8080
127.8.255.129 - - [11/Apr/2014:01:14:27 EDT] "GET / HTTP/1.1" 200 39915
-> / 127.8.255.129 - - [11/Apr/2014:01:54:06 EDT] "GET / HTTP/1.1" 304 0
-> / [2014-04-11 01:57:39] INFO going to shutdown ... [2014-04-11 01:57:39] INFO WEBrick::HTTPServer#start done.
and here is the content of the start file
BASEDIR=$(dirname $0)
$BASEDIR/stop
rm $OPENSHIFT_REPO_DIR/bin/RUNNING_PID
nohup java -Dorient.baasbox.path=$OPENSHIFT_DATA_DIR/baasbox -Dorient.baasbox.admin_password=admin -Dapplication.code=1234567890 -Dhttp.port=$OPENSHIFT_DIY_PORT -Dhttp.address=$OPENSHIFT_DIY_IP $* -cp "$OPENSHIFT_REPO_DIR/bin/lib/*" play.core.server.NettyServer $OPENSHIFT_REPO_DIR/bin $OPENSHIFT_DIY_LOG_DIR/baasbox.log > $OPENSHIFT_DIY_LOG_DIR/nohup.log 2>&1 &

there was a problem in the baasbox start file.
here is the complete issue https://github.com/baasbox/baasbox/issues/303
the start file was updated in the baasbox repo, this is the new one.
BASEDIR=$(dirname $0)
$BASEDIR/stop
rm $OPENSHIFT_REPO_DIR/bin/RUNNING_PID
nohup java -Dorient.baasbox.path=$OPENSHIFT_DATA_DIR/baasbox -Dorient.baasbox.admin_password=admin -Dapplication.code=1234567890 -Dhttp.port=$OPENSHIFT_DIY_PORT -Dhttp.address=$OPENSHIFT_DIY_IP $* -cp "$OPENSHIFT_REPO_DIR/bin/lib/*" play.core.server.NettyServer $OPENSHIFT_REPO_DIR/bin $OPENSHIFT_DIY_LOG_DIR/baasbox.log &

Related

Error installing RVM (Ruby version Manager ) on Amazon Linux 2 AMI

Trying to build a custom amazon image using Packer.
Having trouble installing RVM on the image. Not sure why this is happening because I followed documentation.
This is the comman i'm running:
"sudo gpg2 --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3
7D2BAF1CF37B13E2069D6956105BD0E739499BDB",
"curl -sSL https://get.rvm.io | bash -s stable"
The error
==> amazon-ebs: gpg: keyring `/root/.gnupg/secring.gpg' created
==> amazon-ebs: gpg: keyring `/root/.gnupg/pubring.gpg' created
==> amazon-ebs: gpg: requesting key D39DC0E3 from hkp server keys.gnupg.net
==> amazon-ebs: gpg: requesting key 39499BDB from hkp server keys.gnupg.net
amazon-ebs: gpgkeys: HTTP fetch error 6: Could not resolve host: keys.gnupg.net
==> amazon-ebs: gpg: no valid OpenPGP data found.
==> amazon-ebs: gpg: Total number processed: 0

Cannot install MYSQL on Fedora - Curl error TIMEOUT on repo.mysql.com

I am trying to install MySQL 8.0 Community Edition on Fedora 34. I installed the repo rom from https://dev.mysql.com/downloads/repo/yum/
After running sudo dnf install mysql-community-server I am getting the below error output:
MySQL 8.0 Community Server 0.0 B/s | 0 B 12:42
Errors during downloading metadata for repository 'mysql80-community':
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30020 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/x86_64/repodata/c55e90c7ab0dc694323139988d5868a381c441ff-primary.xml.gz [Resolving timed out after 30096 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/x86_64/repodata/c55e90c7ab0dc694323139988d5868a381c441ff-primary.xml.gz [Resolving timed out after 30000 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/x86_64/repodata/c55e90c7ab0dc694323139988d5868a381c441ff-primary.xml.gz [Resolving timed out after 30001 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30001 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/x86_64/repodata/5920395724110a6f03637c4f6187bfa801f8a70b-filelists.xml.gz [Resolving timed out after 30096 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30004 milliseconds]
Error: Failed to download metadata for repo 'mysql80-community': Yum repo downloading error: Downloading error(s): repodata/c55e90c7ab0dc694323139988d5868a381c441ff-primary.xml.gz - Cannot download, all mirrors were already tried without success; repodata/5920395724110a6f03637c4f6187bfa801f8a70b-filelists.xml.gz - Cannot download, all mirrors were already tried without success
MySQL Connectors Community 0.0 B/s | 0 B 08:39
Errors during downloading metadata for repository 'mysql-connectors-community':
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-connectors-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30026 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-connectors-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30001 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-connectors-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30023 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-connectors-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30006 milliseconds]
Error: Failed to download metadata for repo 'mysql-connectors-community': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
MySQL Tools Community 0.0 B/s | 0 B 08:38
Errors during downloading metadata for repository 'mysql-tools-community':
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30053 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30007 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30000 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30101 milliseconds]
Error: Failed to download metadata for repo 'mysql-tools-community': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
MySQL Tools Preview 0.0 B/s | 0 B 08:17
Errors during downloading metadata for repository 'mysql-tools-preview':
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-preview/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30004 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-preview/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30000 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-preview/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30027 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-preview/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30031 milliseconds]
Error: Failed to download metadata for repo 'mysql-tools-preview': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
MySQL 8.0 Community Server - Source 0.0 B/s | 0 B 08:28
Errors during downloading metadata for repository 'mysql80-community-source':
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30125 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30000 milliseconds]
Error: Failed to download metadata for repo 'mysql80-community-source': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
MySQL Connectors Community - Source 0.0 B/s | 0 B 08:44
Errors during downloading metadata for repository 'mysql-connectors-community-source':
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-connectors-community/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30000 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-connectors-community/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30002 milliseconds]
Error: Failed to download metadata for repo 'mysql-connectors-community-source': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
MySQL Tools Community - Source 0.0 B/s | 0 B 08:45
Errors during downloading metadata for repository 'mysql-tools-community-source':
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-community/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30029 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-community/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30084 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-community/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30000 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-community/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30001 milliseconds]
Error: Failed to download metadata for repo 'mysql-tools-community-source': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
MySQL Tools Preview - Source 0.0 B/s | 0 B 08:36
Errors during downloading metadata for repository 'mysql-tools-preview-source':
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-preview/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30007 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-preview/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 32320 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-preview/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30001 milliseconds]
Error: Failed to download metadata for repo 'mysql-tools-preview-source': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Ignoring repositories: mysql80-community, mysql-connectors-community, mysql-tools-community, mysql-tools-preview, mysql80-community-source, mysql-connectors-community-source, mysql-tools-community-source, mysql-tools-preview-source
Last metadata expiration check: 0:31:20 ago on Sunday 11 July 2021 10:46:17 AM.
No match for argument: mysql-community-server
Error: Unable to find a match: mysql-community-server
[root#fedora ~]#
Installed Repo Package:
[rajiv#fedora yum.repos.d]$ dnf list installed | grep mysql
mysql80-community-release.noarch fc34-1 ##commandline
[rajiv#fedora yum.repos.d]$
RepoList:
[rajiv#fedora ~]$ sudo dnf repolist
[sudo] password for rajiv:
repo id repo name
fedora Fedora 34 - x86_64
fedora-cisco-openh264 Fedora 34 openh264 (From Cisco) - x86_64
fedora-modular Fedora Modular 34 - x86_64
google-chrome google-chrome
mysql-connectors-community MySQL Connectors Community
mysql-connectors-community-source MySQL Connectors Community - Source
mysql-tools-community MySQL Tools Community
mysql-tools-community-source MySQL Tools Community - Source
mysql-tools-preview MySQL Tools Preview
mysql-tools-preview-source MySQL Tools Preview - Source
mysql80-community MySQL 8.0 Community Server
mysql80-community-source MySQL 8.0 Community Server - Source
updates Fedora 34 - x86_64 - Updates
updates-modular Fedora Modular 34 - x86_64 - Updates
Contents of Repo:
[rajiv#fedora yum.repos.d]$ pwd
/etc/yum.repos.d
[rajiv#fedora yum.repos.d]$ ls
_copr_phracek-PyCharm.repo fedora.repo fedora-updates-testing-modular.repo mysql-community.repo rpmfusion-nonfree-steam.repo
fedora-cisco-openh264.repo fedora-updates-modular.repo fedora-updates-testing.repo mysql-community-source.repo
fedora-modular.repo fedora-updates.repo google-chrome.repo rpmfusion-nonfree-nvidia-driver.repo
[rajiv#fedora yum.repos.d]$ tac mysql-community.repo
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
gpgcheck=1
enabled=1
baseurl=http://repo.mysql.com/yum/mysql-tools-preview/fc/$releasever/$basearch/
name=MySQL Tools Preview
[mysql-tools-preview]
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
gpgcheck=1
enabled=1
baseurl=http://repo.mysql.com/yum/mysql-tools-community/fc/$releasever/$basearch/
name=MySQL Tools Community
[mysql-tools-community]
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
gpgcheck=1
enabled=1
baseurl=http://repo.mysql.com/yum/mysql-connectors-community/fc/$releasever/$basearch/
name=MySQL Connectors Community
[mysql-connectors-community]
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
gpgcheck=1
enabled=1
baseurl=http://repo.mysql.com/yum/mysql-8.0-community/fc/$releasever/$basearch/
name=MySQL 8.0 Community Server
[mysql80-community]
[rajiv#fedora yum.repos.d]$ tac mysql-community-source.repo
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
gpgcheck=1
enabled=1
baseurl=http://repo.mysql.com/yum/mysql-tools-preview/fc/$releasever/SRPMS
name=MySQL Tools Preview - Source
[mysql-tools-preview-source]
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
gpgcheck=1
enabled=1
baseurl=http://repo.mysql.com/yum/mysql-tools-community/fc/$releasever/SRPMS
name=MySQL Tools Community - Source
[mysql-tools-community-source]
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
gpgcheck=1
enabled=1
baseurl=http://repo.mysql.com/yum/mysql-connectors-community/fc/$releasever/SRPMS
name=MySQL Connectors Community - Source
[mysql-connectors-community-source]
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
gpgcheck=1
enabled=1
baseurl=http://repo.mysql.com/yum/mysql-8.0-community/fc/$releasever/SRPMS
name=MySQL 8.0 Community Server - Source
[mysql80-community-source]
[rajiv#fedora yum.repos.d]$
I tried reinstalling the repo package, but it still the same issue. Please advice. Thanks!
After a bit of troubleshooting, following steps has enabled to get the installation right: -
Installation Steps: [Component]-[FileNameReference]
Configuration - mysql-community-common
Client Plugins - mysql-community-client
Shared Library - mysql-community-libs
Development Libraries - mysql-community-devel
Client Utilties - mysql-community-client
MySQL Server - mysql-community-server
Workbench - mysql-community-workbench

Failed to start gunicorn.service: Unit gunicorn.service is masked

I am trying to deploy django web application on alibabacloud everything seems to be working perfectly(running gunicorn --bind 0.0.0.0:8000 project_name.wsgi on virtual environment)
Then after deactivating the virtual environment and setting up
[Unit]
Description=gunicorn daemon
After=network.target
[Service]
User=admin
Group=www-data
WorkingDirectory=/home/admin/project_name
ExecStart=/home/admin/project_name/myprojectenv/bin/gunicorn --access-logfile - --workers 3 --bind
unix:/home/admin/project_name/project_name.sock project_name.wsgi:application
in /etc/systemd/system/gunicorn.service
then running sudo systemctl start gunicorn I keep getting the error
Failed to start gunicorn.service: Unit gunicorn.service is masked.
Please how can I fix this?
I have tried systemctl unmask gunicorn.socket but it keeps showing me the error
Unit gunicorn.socket does not exist, proceeding anyway.
Failed to unmask unit: The name org.freedesktop.PolicyKit1 was not provided
by any .service files

Gcloud sql proxy startup script runs but gives out an error

Here is my startup script:
#! /bin/sh
sudo apt-get update
sudo apt-get install mysql-client
wget https://dl.google.com/cloudsql/cloud_sql_proxy.linux.amd64 -O cloud_sql_proxy
chmod +x cloud_sql_proxy
sudo mkdir /cloudsql; sudo chmod 777 /cloudsql
./cloud_sql_proxy -dir=/cloudsql --instances=a:us-east4:b &
Here is the error I get:
Feb 19 22:12:38 instance-group-1-th2f startup-script: INFO startup-
script: 2019/02/19 22:12:38 errors parsing config:
Feb 19 22:12:38 instance-group-1-th2f startup-script: INFO startup-script: #011Get https://www.googleapis.com/sql/v1beta4/projects/a/instances/b?alt=json&prettyPrint=false: dial tcp: lookup www.googleapis.com on [::1]:53: read udp [::1]:52058->[::1]:53: read: connection refused
Feb 19 22:12:38 instance-group-1-th2f startup-script: INFO startup-script: 2019/02/19 22:12:38 Ready for new connections
If I open the instance manually and run the following, it will work:
./cloud_sql_proxy -dir=/cloudsql -instances=a:us-east4:b &
I am guessing that it is an authentication problem, but based on this:
Note: If your Compute Engine instance has either the Full API access
or Cloud SQL API scope, you can skip this step; you do not need to
provide a certificate file when you start the proxy.
It shouldn't have any problems since mine has a Full API access
I have a second gen instance and the Cloud SQL Admin API is enabled.
dial tcp: lookup www.googleapis.com on [::1]:53: read udp [::1]:52058->[::1]:53: read: connection refused
It doesn't look like your issue is authenticated related, but instead you are unable to either lookup or reach www.googleapis.com. Do you have a firewall that might be blocking the outgoing connection?

chef cookbook install chrome centos7

I am trying to install chrome on my centos 7 desktop using chefdk and local mode. chrome installs fine using yum directly, I am using this as a learning exercise in chef. So far it is failing on a dependency check for apt on both centos 7.2 and macosx 10.11.5. Details for centos only appear below. Base cookbooks, eg yum and apt install fine, so I am missing something here.
Thanks for any help.
CentOS Linux release 7.2.1511 (Core)
Installed: yum-3.4.3-132.el7.centos.0.1.noarch
using
chefdk.x86_64 0.15.15-1.el7 #/chefdk-0.15.15-1.el7.x86_64
knife cookbook show chrome
chrome 1.2.2
When I try to install:
sudo sudo chef-client --local-mode --runlist 'recipe[chrome]' 2>&1 | tee /export/cookbooks/install_chrome_from_cookbook.2.log
it tries to use apt and fails because of an apt version failure : see log below.
What could the problem be?
cat /export/cookbooks/install_chrome_from_cookbook.2.log
` [2016-06-28T00:35:35-04:00] WARN: No config file found or specified on command line, using command line options.
> [2016-06-28T00:35:35-04:00] INFO: Auto-discovered chef repository at /export
> [2016-06-28T00:35:36-04:00] INFO: Started chef-zero at chefzero://localhost:8889 with repository at /export
> One version per cookbook
> [2016-06-28T00:35:36-04:00] INFO: Forking chef instance to converge...
> [2016-06-28T00:35:36-04:00] INFO: *** Chef 12.11.18 ***
> [2016-06-28T00:35:36-04:00] INFO: Platform: x86_64-linux
> [2016-06-28T00:35:36-04:00] INFO: Chef-client pid: 7293
> [2016-06-28T00:35:38-04:00] INFO: GET /organizations/chef/nodes/nuctv-w.lfz.net
> [2016-06-28T00:35:38-04:00] INFO: Setting the run_list to [#<Chef::RunList::RunListItem:0x00000004e13468 #version=nil, #type=:recipe, #name="chrome">] from CLI options
> [2016-06-28T00:35:38-04:00] INFO: Run List is [recipe[chrome]]
> [2016-06-28T00:35:38-04:00] INFO: Run List expands to [chrome]
> [2016-06-28T00:35:38-04:00] INFO: Starting Chef Run for nuctv-w.lfz.net
> [2016-06-28T00:35:38-04:00] INFO: Running start handlers
> [2016-06-28T00:35:38-04:00] INFO: Start handlers complete.
> [2016-06-28T00:35:38-04:00] INFO: POST /organizations/chef/reports/nodes/nuctv-w.lfz.net/runs
> --- POST BODY ---
> {"action":"start","run_id":"8532d8c8-2e83-45e3-b867-f55f264a93df","start_time":"2016-06-28 00:35:38 -0400"}
> --- END POST BODY ---
> [2016-06-28T00:35:38-04:00] INFO: HTTP Request Returned 404 Not Found: Object not found:
> [2016-06-28T00:35:38-04:00] INFO: POST /organizations/chef/environments/_default/cookbook_versions
> --- POST BODY ---
> {"run_list":["chrome"]}
> --- END POST BODY ---
> [2016-06-28T00:35:39-04:00] INFO: #<ChefZero::RestErrorResponse: 412: Could not satisfy version constraints for: apt>
> /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chef-zero-4.6.2/lib/chef_zero/endpoints/environment_cookbook_versions_endpoint.rb:42:in `post'
> ....
> /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chef-12.11.18/bin/chef-client:26:in `<top (required)>'
> /bin/chef-client:52:in `load'
> /bin/chef-client:52:in `<main>'
> [2016-06-28T00:35:39-04:00] INFO: HTTP Request Returned 412 Precondition Failed: Could not satisfy version constraints for: apt
> ================================================================================
> Error Resolving Cookbooks for Run List:
> ================================================================================
> Missing Cookbooks:
------------------
Could not satisfy version constraints for: apt
Expanded Run List:
------------------
* chrome
Platform:
---------
x86_64-linux
[2016-06-28T00:35:39-04:00] ERROR: Running exception handlers
[2016-06-28T00:35:39-04:00] ERROR: Exception handlers complete
[2016-06-28T00:35:39-04:00] FATAL: Stacktrace dumped to /root/.chef/local-mode-cache/cache/chef-stacktrace.out
[2016-06-28T00:35:39-04:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2016-06-28T00:35:39-04:00] ERROR: 412 "Precondition Failed"
[2016-06-28T00:35:40-04:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)`
Chef dependencies are always required, even if they won't be used. If you use the more modern cookbook upload tools like Berkshelf or chef push it will take care of this for you.