Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use_ssl error #58

Open
boconnell2210 opened this issue Mar 12, 2015 · 13 comments
Open

use_ssl error #58

boconnell2210 opened this issue Mar 12, 2015 · 13 comments

Comments

@boconnell2210
Copy link

Does xldeploy process need to be stopped when the puppet agent runs?
I have the puppetmaster and xldeploy server on the same host.

When I run puppet without stopping the xldeploy process (centos 6.5 linux) I receive the following error:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined method `use_ssl=' for #<Net::HTTP uc-01.wdts.local:4516 open=false> at /opt/wdts/puppet/production/modules/xldeploy/manifests/server/config.pp:110 on node uc-01.wdts.local
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

In my params.pp manifest I set it to false:
$ssl = false
$verify_ssl = false

I would like to keep the xldeploy process running during puppet unless I need to update the puppet xldeploy mod.

Thanks, in advance,
Billy

@WianVos
Copy link
Contributor

WianVos commented Mar 12, 2015

Log a ticket .. I'll test it tonight if that is soon enough ..

Regards

Wian

Sent from my iPhone

On 12 Mar 2015, at 08:33, boconnell2210 <notifications@github.commailto:notifications@github.com> wrote:

Does xldeploy process need to be stopped when the puppet agent runs?
I have the puppetmaster and xldeploy server on the same host.

When I run puppet without stopping the xldeploy process (centos 6.5 linux) I receive the following error:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined method `use_ssl=' for # at /opt/wdts/puppet/production/modules/xldeploy/manifests/server/config.pp:110 on node uc-01.wdts.local
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

In my params.pp manifest I set it to false:
$ssl = false
$verify_ssl = false

I would like to keep the xldeploy process running during puppet unless I need to update the puppet xldeploy mod.

Thanks, in advance,
Billy

Reply to this email directly or view it on GitHubhttps://github.com//issues/58.

@boconnell2210
Copy link
Author

It can wait until tonight. Thanks.

I did open an issue, so it should be there, let me know if you can’t find it.

On Mar 12, 2015, at 10:27 AM, WianVos notifications@github.com wrote:

Log a ticket .. I'll test it tonight if that is soon enough ..

Regards

Wian

Sent from my iPhone

On 12 Mar 2015, at 08:33, boconnell2210 <notifications@github.commailto:notifications@github.com> wrote:

Does xldeploy process need to be stopped when the puppet agent runs?
I have the puppetmaster and xldeploy server on the same host.

When I run puppet without stopping the xldeploy process (centos 6.5 linux) I receive the following error:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined method `use_ssl=' for # at /opt/wdts/puppet/production/modules/xldeploy/manifests/server/config.pp:110 on node uc-01.wdts.local
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

In my params.pp manifest I set it to false:
$ssl = false
$verify_ssl = false

I would like to keep the xldeploy process running during puppet unless I need to update the puppet xldeploy mod.

Thanks, in advance,
Billy

Reply to this email directly or view it on GitHubhttps://github.com//issues/58.

Reply to this email directly or view it on GitHub.

@WianVos
Copy link
Contributor

WianVos commented Mar 13, 2015

found it :-)

@WianVos
Copy link
Contributor

WianVos commented Mar 13, 2015

billy i can't find the code referenced in the error .. are u on a recent pull of the module ?

@boconnell2210
Copy link
Author

I am using the latest, at least I thought I was, I will check on it.

@boconnell2210
Copy link
Author

I have the latest, also using puppet version 3.7.4

2 things that I adjusted that is perhaps causing this issue as a requirement for our systems.
We use oracle java, not openjdk.
java -version
java version "1.7.0_67"
Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

Also, we are in a closed environment, so I am downloading the xldeploy install packages from a local server, uc-01, not https://dist.xebialabs.com/xl-deploy/....

The files I adjusted from the defaults are:
lib/puppet/provider/xldeploy_plugin_netinstall/curl.rb
lib/puppet/type/xldeploy_plugin_netinstall.rb

I am going to look into that some more to figure out if the problem lies there.

@WianVos
Copy link
Contributor

WianVos commented Mar 20, 2015

how are u doing on this?

@boconnell2210
Copy link
Author

Well, I couldnt quite figure out where it was coming from.

I simply commented out line 110 mentioned above and I have yet to see an repercussions from it.

Here is the bit I commented out

ini settings

ini_setting {
'xldeploy.admin.password':
setting => 'admin.password';
#value => to_xldeploy_md5($admin_password, $rest_url);

It allows me to not have to stop the service.

You can close this issue, unless you want more information on it.

@WianVos
Copy link
Contributor

WianVos commented Mar 20, 2015

No .. I won't close and I have a pretty good idea now where this is comming from .

Regards Wian

Sent from my iPhone

On 20 Mar 2015, at 18:44, boconnell2210 <notifications@github.commailto:notifications@github.com> wrote:

Well, I couldnt quite figure out where it was coming from.

I simply commented out line 110 mentioned above and I have yet to see an repercussions from it.

Here is the bit I commented out

ini settings

ini_setting {
'xldeploy.admin.password':
setting => 'admin.password';
#value => to_xldeploy_md5($admin_password, $rest_url);

It allows me to not have to stop the service.

You can close this issue, unless you want more information on it.

Reply to this email directly or view it on GitHubhttps://github.com//issues/58#issuecomment-84171902.

@WianVos
Copy link
Contributor

WianVos commented Mar 31, 2015

Billy can u do a run with the original code and a --trace flag ?

@boconnell2210
Copy link
Author

Here are the trace results from the failure. If you need more, please let me know.

Debug: Caching connection for https://uc-01.wdts.local:8140
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined method use_ssl=' for #<Net::HTTP uc-01.wdts.local:4516 open=false> at /opt/wdts/puppet/production/modules/xldeploy/manifests/server/config.pp:111 on node uc-01.wdts.local /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:207:inis_http_200?'
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:100:in find' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:201:infind'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:291:in retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:327:inthinmark'
/usr/lib/ruby/1.8/benchmark.rb:308:in realtime' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:326:inthinmark'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:290:in retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:61:inretrieve_catalog'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:104:in prepare_and_retrieve_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:203:inrun_internal'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:132:in run' /usr/lib/ruby/site_ruby/1.8/puppet/context.rb:64:inoverride'
/usr/lib/ruby/site_ruby/1.8/puppet.rb:244:in override' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:131:inrun'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:47:in run' /usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:20:inlock'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:47:in run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:117:inwith_client'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:44:in run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:82:inrun_in_fork'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:43:in run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:179:incall'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:179:in controlled_run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:41:inrun'
/usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:356:in onetime' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:322:inrun_command'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:381:in run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:507:inplugin_hook'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:381:in run' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:488:inexit_on_fail'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:381:in run' /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:146:inrun'
/usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:92:in `execute'
/usr/bin/puppet:8
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Debug: Using cached connection for https://uc-01.wdts.local:8140
Debug: Caching connection for https://uc-01.wdts.local:8140
Debug: Closing connection for https://uc-01.wdts.local:8140

@WianVos
Copy link
Contributor

WianVos commented Apr 13, 2015

Billy this output makes no sense if u look at the last version of the module .. which one are u on .. and did u modilfy in any way ?

@ltutar
Copy link
Contributor

ltutar commented Dec 23, 2015

@boconnell2210 Can we close this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants