$worker_connections must be an integer #460

jacobbuck · 2014-09-24T23:03:10Z

When following the quick start guide, I get stuck at the following:

Running Puppet with site.pp...
stdin: is not a tty
warning: Could not retrieve fact fqdn
$worker_connections must be an integer. at /tmp/vagrant-puppet-1/modules-0/nginx/manifests/config.pp:87 on node precise32
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

puppet apply --modulepath '/tmp/vagrant-puppet-1/modules-0:/etc/puppet/modules' --manifestdir /tmp/vagrant-puppet-1/manifests --detailed-exitcodes /tmp/vagrant-puppet-1/manifests/site.pp || [ $? -eq 2 ]

Stdout from the command:

warning: Could not retrieve fact fqdn


Stderr from the command:

stdin: is not a tty
$worker_connections must be an integer. at /tmp/vagrant-puppet-1/modules-0/nginx/manifests/config.pp:87 on node precise32

My site.pp file looks like:

class { 'nginx': }

nginx::resource::vhost { 'example.com':
  www_root => '/vagrant/www',
}

Just started learning this Puppet stuff, and not to a good start 😢

The text was updated successfully, but these errors were encountered:

jfryman · 2014-09-24T23:23:22Z

Can you please tell me what version of the module you're currently using?

Jacob Buck wrote:

When following the quick start guide, I get stuck at the following:

|Running Puppet with site.pp...
stdin: is not a tty
warning: Could not retrieve fact fqdn
$worker_connections must be an integer. at
/tmp/vagrant-puppet-1/modules-0/nginx/manifests/config.pp:87 on node
precise32
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

puppet apply --modulepath
'/tmp/vagrant-puppet-1/modules-0:/etc/puppet/modules' --manifestdir
/tmp/vagrant-puppet-1/manifests --detailed-exitcodes
/tmp/vagrant-puppet-1/manifests/site.pp || [ $? -eq 2 ]

Stdout from the command:

warning: Could not retrieve fact fqdn

Stderr from the command:

stdin: is not a tty
$worker_connections must be an integer. at
/tmp/vagrant-puppet-1/modules-0/nginx/manifests/config.pp:87 on node
precise32
|

My site.pp file looks like:

|class { 'nginx': }

nginx::resource::vhost { 'example.com':
www_root => '/vagrant/www',
}
|

Just started learning this Puppet stuff, and not to a good start 😢

—
Reply to this email directly or view it on GitHub
#460.

jacobbuck · 2014-09-24T23:26:38Z

Latest version installed via puppet module install, which I believe is v0.1.0.

jfryman · 2014-09-24T23:32:25Z

Interesting. How about the version of Puppet?

jacobbuck · 2014-09-24T23:33:26Z

Puppet 3.7.1, installed via gem.

jfryman · 2014-09-24T23:35:34Z

@jacobbuck Sorry for all the questions! Is this an masterless-less install or with a Puppet Master?

jfryman · 2014-09-24T23:39:06Z

@jacobbuck ah, nm. I see the details I need in the output. Give me just a few minutes to try and reproduce...

jacobbuck · 2014-09-24T23:39:13Z

@jfryman That's alright. I'm using the Puppet Apply Provisioner in Vagrant (v1.5.4).

jfryman · 2014-09-24T23:42:02Z

@jacobbuck Last question, I promise! :)

Are you using librarian-puppet or r10k to install the module, or did you just download the module?

jacobbuck · 2014-09-24T23:47:14Z

Neither, I'm just using the puppet module subcommand:

puppet module install jfryman-nginx --modulepath ./modules

Though I might investigate using librarian-puppet or r10k later.

jfryman · 2014-09-24T23:49:01Z

🆒

Can I have you run the following command, and see if everything works afterword?

puppet module install ripienaar-module_data --modulepath ./modules

EDIT: Misspelled ripienaar...

jacobbuck · 2014-09-24T23:51:40Z

Hmm...

$ puppet module install ripinnear-module_data --modulepath ./modules
Notice: Preparing to install into /[redacted]/modules ...
Notice: Downloading from https://forgeapi.puppetlabs.com ...
Error: Could not install 'ripinnear-module_data' (latest)
  No releases are available from https://forgeapi.puppetlabs.com
    Does 'ripinnear-module_data' have at least one published release?

jfryman · 2014-09-24T23:52:22Z

@jacobbuck sorry, I misspelt ripienaar. Always gets me. 😢

puppet module install ripienaar-module_data --modulepath ./modules

jacobbuck · 2014-09-24T23:54:42Z

@jfryman Easily done 😄 Looks much better:

$ puppet module install ripienaar-module_data --modulepath ./modules
Notice: Preparing to install into /[redacted]/modules ...
Notice: Downloading from https://forgeapi.puppetlabs.com ...
Notice: Installing -- do not interrupt ...
/[redacted]/modules
└── ripienaar-module_data (v0.0.3)

Just running a vagrant up now

jacobbuck · 2014-09-25T00:00:23Z

@jfryman Hang on, forgot I was trying out apache. Started again with nginx:

$ puppet module install jfryman-nginx --modulepath ./modules
Notice: Preparing to install into /path/to/vagrant/project/modules ...
Notice: Downloading from https://forgeapi.puppetlabs.com ...
Notice: Installing -- do not interrupt ...
/path/to/vagrant/project/modules
└─┬ jfryman-nginx (v0.1.0)
  ├── puppetlabs-apt (v1.6.0)
  ├── puppetlabs-concat (v1.1.1)
  ├── puppetlabs-stdlib (v4.3.2)
  └── ripienaar-module_data (v0.0.3)
$ puppet module install ripienaar-module_data --modulepath ./modules
Notice: Preparing to install into /path/to/vagrant/project/modules ...
Notice: Module ripienaar-module_data 0.0.3 is already installed.

Still get the same errors when running vagrant up.

jfryman · 2014-09-25T00:13:26Z

@jacobbuck ok, trying to get a vagrant environment to reproduce. One moment...

jfryman · 2014-09-25T00:26:36Z

OK. I can reproduce now... working on a fix.

jfryman · 2014-09-25T00:35:22Z

@jacobbuck OK! I have a fix.

I apologize that this has been a bit of a pain right off the bat. We're actually right in the middle of some major changes to this module, and so anything in the 0.1.x branch is probably going to be a bit rough for a bit. If you want/need some stability in the meantime, I recommend that you use v0.0.10 for the time being.

Anyway... here's what I did.

What is missing is you'll need to configure Hiera in your Vagrantfile to load the module_data backend. I thought this wasn't necessary, but it seems it is (/cc @3flex)

Take a look at this gist... https://gist.github.com/jfryman/e9f08affec54307e5198

I'm going to push out an update to the documentation so this is less confusing for new folks. Sorry for the inconvenience, and I hope this doesn't spoil your fun. :)

jacobbuck · 2014-09-25T01:30:59Z

@jfryman Great stuff. I also realised that the hashicorp/precise32 box is running Puppet v2.7.19 (ahem @mitchellh). Might find a better supported box, or use packer. For now v0.0.10 runs without a hitch.
Thanks for your help.

deepjoy · 2014-09-26T16:42:43Z

I'm trying to install 0.0.10 but can't unless I download the tgz. Since this is a vagrant based setup I'd like to avoid doing that. I have tried

puppet-module install jfryman/nginx -v 0.0.10
puppet module install jfryman/nginx -v 0.0.10
puppet-module install jfryman-nginx --version 0.0.10
puppet-module install jfryman-nginx --version=0.0.10
puppet-module install jfryman-nginx --version="<0.1.0"

etc.

No Matter what I do puppet module always installs version 0.1.1 instead. Am I missing something? What bash command can I run to install version 0.0.10?

Using Puppet 2.7 with precise64 loaded from https://cloud-images.ubuntu.com/vagrant/precise/current/

Current nginx module complains: > Could not retrieve catalog from remote server: Error 400 on SERVER: > $worker_connections must be an integer. This appears to be non-trivial to fix, with the maintainer stating [1]: > We're actually right in the middle of some major changes to this > module, and so anything in the 0.1.x branch is probably going to be a > bit rough for a bit. If you want/need some stability in the meantime, > I recommend that you use v0.0.10 for the time being. So, downgrading seems like a reasonable option for now. [1] voxpupuli/puppet-nginx#460 (comment)

jfryman mentioned this issue Sep 25, 2014

Add instructions on bootstrapping puppet-module-data #461

Merged

jfryman closed this as completed in #461 Sep 25, 2014

delfuego mentioned this issue Oct 20, 2014

specify exact jfryman-nginx puppet module version to install vilmibm/puppet-tilde#10

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

$worker_connections must be an integer #460

$worker_connections must be an integer #460

jacobbuck commented Sep 24, 2014

jfryman commented Sep 24, 2014

jacobbuck commented Sep 24, 2014

jfryman commented Sep 24, 2014

jacobbuck commented Sep 24, 2014

jfryman commented Sep 24, 2014

jfryman commented Sep 24, 2014

jacobbuck commented Sep 24, 2014

jfryman commented Sep 24, 2014

jacobbuck commented Sep 24, 2014

jfryman commented Sep 24, 2014

jacobbuck commented Sep 24, 2014

jfryman commented Sep 24, 2014

jacobbuck commented Sep 24, 2014

jacobbuck commented Sep 25, 2014

jfryman commented Sep 25, 2014

jfryman commented Sep 25, 2014

jfryman commented Sep 25, 2014

jacobbuck commented Sep 25, 2014

deepjoy commented Sep 26, 2014

$worker_connections must be an integer #460

$worker_connections must be an integer #460

Comments

jacobbuck commented Sep 24, 2014

jfryman commented Sep 24, 2014

jacobbuck commented Sep 24, 2014

jfryman commented Sep 24, 2014

jacobbuck commented Sep 24, 2014

jfryman commented Sep 24, 2014

jfryman commented Sep 24, 2014

jacobbuck commented Sep 24, 2014

jfryman commented Sep 24, 2014

jacobbuck commented Sep 24, 2014

jfryman commented Sep 24, 2014

jacobbuck commented Sep 24, 2014

jfryman commented Sep 24, 2014

jacobbuck commented Sep 24, 2014

jacobbuck commented Sep 25, 2014

jfryman commented Sep 25, 2014

jfryman commented Sep 25, 2014

jfryman commented Sep 25, 2014

jacobbuck commented Sep 25, 2014

deepjoy commented Sep 26, 2014