Error while running berks install - windows

I have a windows instance which on top of that I'm running a windows docker container. On the instance itself I'm succeed to execute berks vendor/install without any issues. However on a windows docker container running on that machine it doesn't work and throws me a timeout error.
The error wasn't clear enough so I decided to execute librarian-chef install and got some more output. It appears that there is something related to SSL connection.
I tried several things after a long research during last couple days but still getting same error.
Resolving cookbook dependencies...
Fetching 'firefox' from source at .
Fetching 'firefox_test' from source at test/fixtures/cookbooks/firefox_test
Fetching cookbook index from https://supermarket.chef.io...
[2017-08-02T09:09:19+00:00] ERROR: Timeout connecting to https://supermarket.chef.io/universe, retry 1/5
[2017-08-02T09:14:24+00:00] ERROR: Timeout connecting to https://supermarket.chef.io/universe, retry 2/5
[2017-08-02T09:19:29+00:00] ERROR: Timeout connecting to https://supermarket.chef.io/universe, retry 3/5
[2017-08-02T09:24:34+00:00] ERROR: Timeout connecting to https://supermarket.chef.io/universe, retry 4/5
[2017-08-02T09:29:39+00:00] ERROR: Timeout connecting to https://supermarket.chef.io/universe, retry 5/5
Error retrieving universe from source: https://supermarket.chef.io
* [Berkshelf::APIClient::TimeoutError] Unable to connect to: universe
Using firefox (4.0.0) from source at .
Using firefox_test (0.1.0) from source at test/fixtures/cookbooks/firefox_test
Cookbook 'dmg' (4.0.0) not found in any of the sources! This can happen if the remote cookbook has been deleted or if the sources inside the Berksfile have changed Please run berks update dmg to resolve to a valid version.
I would be grateful if anyone could assist here.
Thanks in advance

I have the same error; this only happens when I am logged into my company's network. When I am on the internet directly, there is no issue; so I suspect it is a problem with a proxy server, or something in my company's network.
Slava: I sincerely hope that this is the same kind of problem; I just did not want to duplicate the question; please let me know and I can create a different item.
When I get this problem, the error message is:
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: 1 actions failed.
>>>>>> Failed to complete #converge action: [Error connecting to https://supermarket.chef.io/universe - Failed to open TCP connection to supermarket.chef.io:443 (getaddrinfo: No address associated with hostname)] on default-centos-67
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration
in my case, the web proxy needed to be set properly.

Related

yarn install failing due to http://blip.strongloop.com/ being offline

yarn install
or
yarn upgrade
result in this error:
[1/4] 🔍 Resolving packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
error An unexpected error occurred: "http://blip.strongloop.com/zone#0.3.4: getaddrinfo ENOTFOUND blip.strongloop.com".
info If you think this is a bug, please open a bug report with the information provided in "/Users/ff/projects/network_tools_portal/network_tools_portal_ui/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/upgrade for documentation about this command.
the error log includes this additional info:
zone.js#~0.10.3:
version "0.10.3"
resolved "https://registry.npmjs.org/zone.js/-/zone.js-0.10.3.tgz"
integrity sha512-LXVLVEq0NNOqK/fLJo3d0kfzd4sxwn2/h67/02pjCjfKDxgx1i9QqpvtHD8CrBnSSwMw5+dy11O7FRX5mkO7Cg==
zone.js#~0.11.4:
version "0.11.5"
resolved "https://registry.npmjs.org/zone.js/-/zone.js-0.11.5.tgz"
integrity sha512-D1/7VxEuQ7xk6z/kAROe4SUbd9CzxY4zOwVGnGHerd/SgLIVU5f4esDzQUsOCeArn933BZfWMKydH7l7dPEp0g==
dependencies:
tslib "^2.3.0"
zone#^0.3.4:
version "0.3.4"
resolved "https://registry.npmjs.org/zone/-/zone-0.3.4.tgz"
integrity sha1-XshPKNHiYftrLpoDHMrOZOnH3ec=
optionalDependencies:
sl-blip "http://blip.strongloop.com/zone#0.3.4"
Seems like the optional dependency, sl-blip, is the problem. It seems to not be on the interwebs anymore. Any help would be greatly appreciated
BTW, there is no proxy at play here.
In the end, I removed Yarn from the equation and did an npm update and the problem was gone.

Passwordless chef client bootstrapping

I am bit familiar with Chef and its bootstrapping techniques. I am trying to bootstrap my new chef-client/node without passing password
I tried below by generating a ssh key but still failing
knife bootstrap MY_NODE_IP -x SERVER_ADMIN_USERNAME -i PATH_TO_KEY_FILE --sudo --node-name THE_NODE_NAME
On triggering above command on Chef DK getting error as below
WARN: [SSH] PTY requested: stderr will be merged into stdout
WARN: [SSH] connection failed, terminating (#<Net::SSH::AuthenticationFailed: Authentication failed for user user#mynode>)
ERROR: Train::Transports::SSHFailed: SSH session could not be established
I also tried doing manual installation as per below instruction , but again a failure https://serverfault.com/questions/761167/how-to-manually-set-up-a-chef-node
I created a client manually, but I was unable to create a node in chef server manually. Please suggest
Getting network error as below
Networking Error:
-----------------
Error connecting to https://myserver/organizations/organization/nodes/mynode - Failed to open TCP connection to www.internet:8080 (getaddrinfo: Name or service not known)
Bootstrapping from my chef DK also throws an error
Is there a way to bootstrap linux chef client without using password from a windows chef DK?
Below is my Chef environment
1.Chef Infra Client: 15.14.0
2.Chef Workstation 0.8.7.1
3.Chef-server 12.18.14

greenplum initialization failed

When I tried to initialize Greenplum I got the following error
20180408:23:21:02:017614 gpstop:datanode3:root-[INFO]:-Starting gpstop with args:
20180408:23:21:02:017614 gpstop:datanode3:root-[INFO]:-Gathering information and validating the environment...
20180408:23:21:02:017614 gpstop:datanode3:root-[ERROR]:-gpstop error: postmaster.pid file does not exist. is Greenplum instance already stopped?
also when i tried to check gpstate command i got the following error
20180408:23:21:48:017711 gpstate:datanode3:root-[INFO]:-Starting gpstate with args:
20180408:23:21:48:017711 gpstate:datanode3:root-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 5.7.0 build f7c6eb5-oss'
20180408:23:21:48:017711 gpstate:datanode3:root-[CRITICAL]:-gpstate failed. (Reason='could not connect to server: Connection refused
I also did the configuration an add a permission on PostgreSQL.conf, but the same issue
You have pasted the output of gpstop.
gpstop error: postmaster.pid file does not exist. is Greenplum
instance already stopped?
Which means that the database is not running.

Illegal Argument Exception: Unable to access BASE URL: httpHDP Installation

I'm trying to install HDP2.3 with ambari. I had already installed ambari client and server. In three nodes. When I'm selecting stack - I'm getting unable to access BASE URL error. Please see below error image.
Also in server logs, I can see the Error as:
Resource_management.core.exceptions.Fail: Execution of '/usr/bin/yum -d 0 -e 0 -y install hdp-select' returned 1. Error: Cannot retrieve repository metadata (repomd.xml) for repository: HDP-2.3. Please verify its path and try again
How can I resolve this issue?
for me maintaining the Internet-Proxy solved the issue.
Link
Kind regards,
Roman

Cert already in hash table exception

I am using chef dk version 12 and i have done basic setup and uploaded many cookbooks , currently i am using remote_directory in my default.rb
What i have observed is whenever there are too many files /hierarchy in the directory the upload fails with the below exception :-
ERROR: SSL Validation failure connecting to host: xyz.com - SSL_write: cert already in hash table
ERROR: Could not establish a secure connection to the server.
Use `knife ssl check` to troubleshoot your SSL configuration.
If your Chef Server uses a self-signed certificate, you can use
`knife ssl fetch` to make knife trust the server's certificates.
Original Exception: OpenSSL::SSL::SSLError: SSL_write: cert already in hash table
As mentioned earlier connection to server isnt a problem it happens only when there are too many files/the hierarchy is more .
Can you please suggest what i can do? I have tried searching online for solutions but failed to get a solution
I have checked the question here but it doesnt solve my problem
Chef uses embedded ruby and openssl for people not working with chef
Some updates on suggestion of tensibai,
The exceptions have changed since adding the option of --concurrency 1 ,
Initially i had received,
INFO: HTTP Request Returned 403 Forbidden:ERROR: Failed to upload filepath\file (7a81e65b51f0d514ec645da49de6417d) to example.com:443/bookshelf/… 3088476d373416dfbaf187590b5d5687210a75&Expires=1435139052&Signature=SP/70MZP4C2U‌​dUd9%2B5Ct1jEV1EQ%3D : 403 "Forbidden" <?xml version="1.0" encoding="UTF-8"?><Error><Code>AccessDenied</Code><Message>Access Denied</Message>
Then yesterday it has changed to
INFO: HTTP Request Returned 413 Request Entity Too Large: error
ERROR: Request Entity Too Large
Response: JSON must be no more than 1000000 bytes.
Should i decrease the number of files or is there any other option?
Knife --version results in Chef: 12.3.0
Should i decrease the number of files or is there any other option?
Ususally the files inside a cookbook are not intended to be too large and too numerous, if you got a lot of files to ditribute it's a sign you should change the way you distribute thoose files.
One option could be to make a tarball, but this makes harder to manage the deleted files.
Another option if you're on an internal chef-server is to follow the advice here and change the client_max_body_size 2M; value for nginx but I can't guarantee it will work.
I had same error and i ran chef-server-ctl reconfigure on chef server then tried uploading cookbook again and all started working fine again

Resources