Re: [Puppet Users] puppetdb question !!!
Sorry for re-opening a old thread but I am still struggling on related topic.. Step 1: I am copying some .rb files to the /usr/lib/ruby/site_ruby/ruby/1.8/facter/ folder Step 2: A facter command gives me the values for all new custom / external facts But the values for new facts will not get into puppetdb untill a next agent run... Is there a way to run puppet from within a manifest or any other way to force "replace facts" remotely on the agent ??? On Monday, March 31, 2014 1:12:32 AM UTC+5:30, Rakesh K wrote: > > I am not copying the facts to the facts.d folder.. > > but i am creating the facts as .rb files and placing them into > /usr/lib/ruby/site_ruby/ruby/1.8/facter/. > > > On Sun, Mar 30, 2014 at 8:48 PM, Christopher Wood < > christopher_w...@pobox.com> wrote: > >> After copying these facts into /etc/facter/facts.d, are you kicking off >> another puppet agent run? Facts get sent to the master on each agent run, >> not before. >> >> http://docs.puppetlabs.com/guides/custom_facts.html#viewing-fact-values >> >> On Sun, Mar 30, 2014 at 07:35:54PM +0530, Rakesh Kathpal wrote: >> >Hi , >> > >> >I am still struggling on the replace fact part, is there any way >> >to force replace_facts for a node. >> > >> >I am actually adding new facts by coping them directly into the >> facter dir >> >but unfortunately they are not getting replicated to puppetdb. Is >> there >> >any way to force puppetdb to replace_facts. >> > >> >This is really urgent for me, any help is greatly appreciated. >> > >> >Regards, >> > >> >Rakesh K. >> > >> >On Wed, Mar 12, 2014 at 1:25 PM, Rakesh Kathpal <[1] >> rkath...@gmail.com> >> >wrote: >> > >> > [2]https://tickets.puppetlabs.com/browse/PDB-508 >> > >> > On Tue, Mar 11, 2014 at 10:28 PM, Ken Barber <[3] >> k...@puppetlabs.com> >> > wrote: >> > >> >> Just a suggestion .. it will really good if you can add field >> "date >> >added" >> >> to the certname table just reporting purposes. >> > >> >Feel free to raise that as a feature request here Rakesh: >> >[4]https://tickets.puppetlabs.com/browse/PDB >> > >> >ken. >> >-- >> >You received this message because you are subscribed to the >> Google >> >Groups "Puppet Users" group. >> >To unsubscribe from this group and stop receiving emails from >> it, send >> >an email to [5]puppet-users+unsubscr...@googlegroups.com. >> >To view this discussion on the web visit >> >[6] >> https://groups.google.com/d/msgid/puppet-users/CAE4bNT%3D6LBjFCDrym8auMw7ufxMwBmV_d6x-yTO4CxdMPkdKqQ%40mail.gmail.com >> . >> >For more options, visit [7]https://groups.google.com/d/optout. >> > >> >-- >> >You received this message because you are subscribed to the Google >> Groups >> >"Puppet Users" group. >> >To unsubscribe from this group and stop receiving emails from it, >> send an >> >email to [8]puppet-users+unsubscr...@googlegroups.com. >> >To view this discussion on the web visit >> >[9] >> https://groups.google.com/d/msgid/puppet-users/CAEJrXMW8zjnUaAaQ%3DJapew%2Bja5fnAJdy1G6fTyO%3Dws%3D4%2Bt4ZLg%40mail.gmail.com >> . >> >For more options, visit [10]https://groups.google.com/d/optout. >> > >> > References >> > >> >Visible links >> >1. mailto:rkath...@gmail.com >> >2. https://tickets.puppetlabs.com/browse/PDB-508 >> >3. mailto:k...@puppetlabs.com >> >4. https://tickets.puppetlabs.com/browse/PDB >> >5. mailto:puppet-users%2bunsubscr...@googlegroups.com >> >6. >> https://groups.google.com/d/msgid/puppet-users/CAE4bNT%3D6LBjFCDrym8auMw7ufxMwBmV_d6x-yTO4CxdMPkdKqQ%40mail.gmail.com >> >7. https://groups.google.com/d/optout >> >8. mailto:puppet-users+unsubscr...@googlegroups.com >> >9. >> https://groups.google.com/d/msgid/puppet-users/CAEJrXMW8zjnUaAaQ%3DJapew%2Bja5fnAJdy1G6fTyO%3Dws%3D4%2Bt4ZLg%40mail.gmail.com?utm_medium=email&utm_source=footer >> > 10. https://groups.google.com/d/optout >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/20140330151817.GA24743%40iniquitous.heresiarch.ca >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52aa6b56-a63a-441a-855b-eb37c9c0a451%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Passing parameters for a class in Dashboard
Ok.. I understand ... I can simply include the class and assign it to my
node.. but how will dashboard know which parameters refers to which class?
There could be a parameter like "ensure => present" and it could have been
used in multiple classes that I have included, how will these things be
taken care of?
On Tuesday, August 7, 2012 12:08:09 AM UTC+5:30, Kenneth Lo wrote:
>
> In dashboard parameters are assigned via group.
>
> So basically you just create a group, assign some parameters there,
> include some nodes and your class in it.
>
> Parameters created via dashboard group are at the global top scope I
> believe.
>
> --KL
>
> From: Rakesh K >
> Reply-To: "puppet...@googlegroups.com " <
> puppet...@googlegroups.com >
> Date: Mon, 6 Aug 2012 05:50:37 -0700
> To: "puppet...@googlegroups.com "
>
> >
> Subject: [Puppet Users] Re: Passing parameters for a class in Dashboard
>
>
>
>
> Or in other words , how do I make sure that following config is applied to
> my node through dashboard
>
> class base1 {
>
> package { ["rsync", "xinetd"]: ensure => present }
> service { "xinetd": ensure => running }
>
> include rsyncd
> $password = generate("/usr/bin/pwgen", 8, 1)
>
> user { "dba":
> ensure => present,
> comment => "DB user",
> gid => "dba",
> shell => "/bin/false",
> require => Group["dba"],
> }
>
> group { "dba":
> ensure => present,
> }
>
> file { "/backup-mysql":
> ensure => directory,
> mode => 0775,
> owner => "dba",
> group => "dba",
> }
>
> file { "/home/dba/rsyncd.secret":
> content => "backup:${password}",
> replace => no,
> mode => 0460,
> owner=> "root",
> group => "dba",
> require => User['dba'],
> }
>
> rsyncd::export { "backup":
> path => "/backup-mysql",
> chroot => true,
> readonly => true,
> uid => "dba",
> gid => "dba",
> users => "backup",
> secrets => "/home/dba/rsyncd.secret",
> allow => "192.168.0.0/24",
> require => [File["/backup-mysql"], File["/home/dba/rsyncd.secret"]],
> }
>
> }
>
> node 'pclient1.example.com' {
> include base1
> }
>
>
>
>
>
> On Monday, August 6, 2012 2:44:00 PM UTC+5:30, Rakesh K wrote:
>>
>> Hi,
>>
>> I have recently installed puppet and components including dashboard on my
>> server. I am new to puppet and what I am trying to achieve here is passing
>> parameters via dashboard
>>
>> What I can see right now is under Add Class in dashboard, I can only pass
>> the class names. Whereas when I can include classes via nodes.pp I can also
>> pass parameters.
>>
>> How can do this from dashboard,
>>
>> eg. if I want to achieve the following from dashboard how will I be able
>> to do it
>>
>> /etc/puppet/manifests/nodes.pp
>> class baseclass {
>> class { 'mysql': }
>> class { 'mysql::server':
>> #config_hash => { 'root_password' => 'mypass' }
>> }
>> mysql::db { 'mydb':
>> user => 'myuser',
>> password => 'mypass',
>> host => 'localhost',
>> grant=> ['all'],
>> }
>> }
>>
>> node 'pclient1.example.com' {
>> include baseclass
>> }
>>
>>
>> And this is how my site.pp looks like
>>
>> [root@pmast1 ~]# cat /etc/puppet/manifests/site.pp
>> import 'nodes.pp'
>> $puppetserver = 'pmast1.example.com'
>> filebucket { "main":
>> server => "puppet",
>> path => false,
>> }
>> File { backup => "main" }
>>
>> Please suggest.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/hqByM-qJEegJ.
> To post to this group, send email to puppe...@googlegroups.com
> .
> To unsubscribe from this group, send email to
> puppet-user...@googlegroups.com .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise private information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the email by you is prohibited.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/sX2fXrzbKywJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Issues with installing some modules !!!
Also can you please guide me as to how can I try this from the dashboard ?
I know I can simply include the mysql class and assign it to my node.. but
how can I actually pass these parameters and how will dashboard know which
parameters refers to which class?
On Wednesday, August 8, 2012 11:14:58 AM UTC+5:30, Rakesh K wrote:
>
>
> Actually I have tried fresh install of the module multiple times after
> clearing all traces of the mysql package on the client but still getting
> the same result.
>
> I am using the same nodes.pp as above as the password is not set at
> all, I hv not tried using the old_password parameter at all.
>
> Please suggest.
>
>
> On Wednesday, August 8, 2012 2:21:43 AM UTC+5:30, Ryan Coleman wrote:
>>
>> On Mon, Aug 6, 2012 at 2:05 AM, Rakesh K wrote:
>> > Any updates ??
>>
>> Sorry Rakesh, I was waiting for your response to Nan's comments. I've
>> pasted them below for reference.
>>
>> >>>
>>
>> Yeah, per Ryan, most likely you already have an existing password, and
>> you need to set old_root_password before you can set the new password:
>>
>> ...
>> config_hash => {
>> root_password => 'mypass',
>> old_root_password => 'oldpass',
>> }
>>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/1XPnGzLQ2pUJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Issues with installing some modules !!!
Actually I have tried fresh install of the module multiple times after
clearing all traces of the mysql package on the client but still getting
the same result.
I am using the same nodes.pp as above as the password is not set at
all, I hv not tried using the old_password parameter at all.
Please suggest.
On Wednesday, August 8, 2012 2:21:43 AM UTC+5:30, Ryan Coleman wrote:
>
> On Mon, Aug 6, 2012 at 2:05 AM, Rakesh K >
> wrote:
> > Any updates ??
>
> Sorry Rakesh, I was waiting for your response to Nan's comments. I've
> pasted them below for reference.
>
> >>>
>
> Yeah, per Ryan, most likely you already have an existing password, and
> you need to set old_root_password before you can set the new password:
>
> ...
> config_hash => {
> root_password => 'mypass',
> old_root_password => 'oldpass',
> }
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/SG8Y3H6hQjgJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Passing parameters for a class in Dashboard
Or in other words , how do I make sure that following config is applied to
my node through dashboard
class base1 {
package { ["rsync", "xinetd"]: ensure => present }
service { "xinetd": ensure => running }
include rsyncd
$password = generate("/usr/bin/pwgen", 8, 1)
user { "dba":
ensure => present,
comment => "DB user",
gid => "dba",
shell => "/bin/false",
require => Group["dba"],
}
group { "dba":
ensure => present,
}
file { "/backup-mysql":
ensure => directory,
mode => 0775,
owner => "dba",
group => "dba",
}
file { "/home/dba/rsyncd.secret":
content => "backup:${password}",
replace => no,
mode => 0460,
owner=> "root",
group => "dba",
require => User['dba'],
}
rsyncd::export { "backup":
path => "/backup-mysql",
chroot => true,
readonly => true,
uid => "dba",
gid => "dba",
users => "backup",
secrets => "/home/dba/rsyncd.secret",
allow => "192.168.0.0/24",
require => [File["/backup-mysql"], File["/home/dba/rsyncd.secret"]],
}
}
node 'pclient1.example.com' {
include base1
}
On Monday, August 6, 2012 2:44:00 PM UTC+5:30, Rakesh K wrote:
>
> Hi,
>
> I have recently installed puppet and components including dashboard on my
> server. I am new to puppet and what I am trying to achieve here is passing
> parameters via dashboard
>
> What I can see right now is under Add Class in dashboard, I can only pass
> the class names. Whereas when I can include classes via nodes.pp I can also
> pass parameters.
>
> How can do this from dashboard,
>
> eg. if I want to achieve the following from dashboard how will I be able
> to do it
>
> /etc/puppet/manifests/nodes.pp
> class baseclass {
> class { 'mysql': }
> class { 'mysql::server':
> #config_hash => { 'root_password' => 'mypass' }
> }
> mysql::db { 'mydb':
> user => 'myuser',
> password => 'mypass',
> host => 'localhost',
> grant=> ['all'],
> }
> }
>
> node 'pclient1.example.com' {
> include baseclass
> }
>
>
> And this is how my site.pp looks like
>
> [root@pmast1 ~]# cat /etc/puppet/manifests/site.pp
> import 'nodes.pp'
> $puppetserver = 'pmast1.example.com'
> filebucket { "main":
> server => "puppet",
> path => false,
> }
> File { backup => "main" }
>
> Please suggest.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/hqByM-qJEegJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Passing parameters for a class in Dashboard
Hi,
I have recently installed puppet and components including dashboard on my
server. I am new to puppet and what I am trying to achieve here is passing
parameters via dashboard
What I can see right now is under Add Class in dashboard, I can only pass
the class names. Whereas when I can include classes via nodes.pp I can also
pass parameters.
How can do this from dashboard,
eg. if I want to achieve the following from dashboard how will I be able to
do it
/etc/puppet/manifests/nodes.pp
class baseclass {
class { 'mysql': }
class { 'mysql::server':
#config_hash => { 'root_password' => 'mypass' }
}
mysql::db { 'mydb':
user => 'myuser',
password => 'mypass',
host => 'localhost',
grant=> ['all'],
}
}
node 'pclient1.example.com' {
include baseclass
}
And this is how my site.pp looks like
[root@pmast1 ~]# cat /etc/puppet/manifests/site.pp
import 'nodes.pp'
$puppetserver = 'pmast1.example.com'
filebucket { "main":
server => "puppet",
path => false,
}
File { backup => "main" }
Please suggest.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/IIkh7layBQwJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Issues with installing some modules !!!
Any updates ??
On Wednesday, August 1, 2012 12:23:22 PM UTC+5:30, Rakesh K wrote:
>
> Hi,
>
> I am new to puppet and have started evaluating various features in last
> few days. I am not a developer and am mostly going to use the modules
> available on github or puppet forge.
>
> Currently I have tried all easier modules and they seem to work perfectly
> without any issues, but now the problem is arising when I am trying to use
> modules like mysql, tomcat etc...
>
> For mysql I am using the module
> https://github.com/puppetlabs/puppetlabs-mysql
>
> What I am observing is mysql is gets installed and everything but no db is
> added, also intermittently the password is not set, it is neither not blank
> nor does it set the password that I have mentioned. The nodes.pp that I am
> using is as follows
>
> [root@pmast1 manifests]# cat /etc/puppet/manifests/nodes.pp
> class baseclass {
> class { 'mysql': }
> class { 'mysql::server':
> #config_hash => { 'root_password' => 'mypass' }
> }
> mysql::db { 'mydb':
> user => 'myuser',
> password => 'mypass',
> host => 'localhost',
> grant=> ['all'],
> }
> }
>
> node 'pclient1.example.com' {
> include baseclass
> }
>
> Now as in nodes.pp if I try to set the password it gives me the error
> below on the puppet client node
>
> [root@pclient1 ~]# puppetd --test
> notice: Ignoring --listen on onetime run
> info: Caching catalog for pclient1.example.com
> info: Applying configuration version '1343801984'
> notice: /Stage[main]/Mysql::Config/
> Exec[set_mysql_rootpw]/returns: mysqladmin: connect to server at
> 'localhost' failed
> notice: /Stage[main]/Mysql::Config/Exec[set_mysql_rootpw]/returns: error:
> 'Access denied for user 'root'@'localhost' (using password: NO)'
> err: /Stage[main]/Mysql::Config/Exec[set_mysql_rootpw]/returns: change
> from notrun to 0 failed: mysqladmin -u root password mypass returned 1
> instead of one of [0] at /etc/puppet/modules/mysql/manifests/config.pp:94
> notice: /File[/root/.my.cnf]: Dependency Exec[set_mysql_rootpw] has
> failures: true
> warning: /File[/root/.my.cnf]: Skipping because of failed dependencies
> notice: /Stage[main]/Mysql::Config/Exec[mysqld-restart]: Dependency
> Exec[set_mysql_rootpw] has failures: true
> warning: /Stage[main]/Mysql::Config/Exec[mysqld-restart]: Skipping because
> of failed dependencies
> notice: Finished catalog run in 0.56 seconds
>
>
> And in case I do not specify the password in the nodes.pp, not sure what
> password is sets but only adds the mysql service to the client node.
>
> I am sure I am missing something and here but not sure what...
>
> Also in case of tomcat I am having similar issues not sure how can I add
> applications or tomcat in the /usr/local/tomcat path.
>
> Thanks for your help in advance.
>
> Rakesh K.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/kPdVuKK1b0EJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Issues with installing some modules !!!
Can Someone please help me out with this ???
On Wednesday, August 1, 2012 12:23:22 PM UTC+5:30, Rakesh K wrote:
>
> Hi,
>
> I am new to puppet and have started evaluating various features in last
> few days. I am not a developer and am mostly going to use the modules
> available on github or puppet forge.
>
> Currently I have tried all easier modules and they seem to work perfectly
> without any issues, but now the problem is arising when I am trying to use
> modules like mysql, tomcat etc...
>
> For mysql I am using the module
> https://github.com/puppetlabs/puppetlabs-mysql
>
> What I am observing is mysql is gets installed and everything but no db is
> added, also intermittently the password is not set, it is neither not blank
> nor does it set the password that I have mentioned. The nodes.pp that I am
> using is as follows
>
> [root@pmast1 manifests]# cat /etc/puppet/manifests/nodes.pp
> class baseclass {
> class { 'mysql': }
> class { 'mysql::server':
> #config_hash => { 'root_password' => 'mypass' }
> }
> mysql::db { 'mydb':
> user => 'myuser',
> password => 'mypass',
> host => 'localhost',
> grant=> ['all'],
> }
> }
>
> node 'pclient1.example.com' {
> include baseclass
> }
>
> Now as in nodes.pp if I try to set the password it gives me the error
> below on the puppet client node
>
> [root@pclient1 ~]# puppetd --test
> notice: Ignoring --listen on onetime run
> info: Caching catalog for pclient1.example.com
> info: Applying configuration version '1343801984'
> notice: /Stage[main]/Mysql::Config/
> Exec[set_mysql_rootpw]/returns: mysqladmin: connect to server at
> 'localhost' failed
> notice: /Stage[main]/Mysql::Config/Exec[set_mysql_rootpw]/returns: error:
> 'Access denied for user 'root'@'localhost' (using password: NO)'
> err: /Stage[main]/Mysql::Config/Exec[set_mysql_rootpw]/returns: change
> from notrun to 0 failed: mysqladmin -u root password mypass returned 1
> instead of one of [0] at /etc/puppet/modules/mysql/manifests/config.pp:94
> notice: /File[/root/.my.cnf]: Dependency Exec[set_mysql_rootpw] has
> failures: true
> warning: /File[/root/.my.cnf]: Skipping because of failed dependencies
> notice: /Stage[main]/Mysql::Config/Exec[mysqld-restart]: Dependency
> Exec[set_mysql_rootpw] has failures: true
> warning: /Stage[main]/Mysql::Config/Exec[mysqld-restart]: Skipping because
> of failed dependencies
> notice: Finished catalog run in 0.56 seconds
>
>
> And in case I do not specify the password in the nodes.pp, not sure what
> password is sets but only adds the mysql service to the client node.
>
> I am sure I am missing something and here but not sure what...
>
> Also in case of tomcat I am having similar issues not sure how can I add
> applications or tomcat in the /usr/local/tomcat path.
>
> Thanks for your help in advance.
>
> Rakesh K.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/uysf_bslZCwJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Issues with installing some modules !!!
Hi,
I am new to puppet and have started evaluating various features in last few
days. I am not a developer and am mostly going to use the modules available
on github or puppet forge.
Currently I have tried all easier modules and they seem to work perfectly
without any issues, but now the problem is arising when I am trying to use
modules like mysql, tomcat etc...
For mysql I am using the module
https://github.com/puppetlabs/puppetlabs-mysql
What I am observing is mysql is gets installed and everything but no db is
added, also intermittently the password is not set, it is neither not blank
nor does it set the password that I have mentioned. The nodes.pp that I am
using is as follows
[root@pmast1 manifests]# cat /etc/puppet/manifests/nodes.pp
class baseclass {
class { 'mysql': }
class { 'mysql::server':
#config_hash => { 'root_password' => 'mypass' }
}
mysql::db { 'mydb':
user => 'myuser',
password => 'mypass',
host => 'localhost',
grant=> ['all'],
}
}
node 'pclient1.example.com' {
include baseclass
}
Now as in nodes.pp if I try to set the password it gives me the error below
on the puppet client node
[root@pclient1 ~]# puppetd --test
notice: Ignoring --listen on onetime run
info: Caching catalog for pclient1.example.com
info: Applying configuration version '1343801984'
notice: /Stage[main]/Mysql::Config/
Exec[set_mysql_rootpw]/returns: mysqladmin: connect to server at
'localhost' failed
notice: /Stage[main]/Mysql::Config/Exec[set_mysql_rootpw]/returns: error:
'Access denied for user 'root'@'localhost' (using password: NO)'
err: /Stage[main]/Mysql::Config/Exec[set_mysql_rootpw]/returns: change from
notrun to 0 failed: mysqladmin -u root password mypass returned 1 instead
of one of [0] at /etc/puppet/modules/mysql/manifests/config.pp:94
notice: /File[/root/.my.cnf]: Dependency Exec[set_mysql_rootpw] has
failures: true
warning: /File[/root/.my.cnf]: Skipping because of failed dependencies
notice: /Stage[main]/Mysql::Config/Exec[mysqld-restart]: Dependency
Exec[set_mysql_rootpw] has failures: true
warning: /Stage[main]/Mysql::Config/Exec[mysqld-restart]: Skipping because
of failed dependencies
notice: Finished catalog run in 0.56 seconds
And in case I do not specify the password in the nodes.pp, not sure what
password is sets but only adds the mysql service to the client node.
I am sure I am missing something and here but not sure what...
Also in case of tomcat I am having similar issues not sure how can I add
applications or tomcat in the /usr/local/tomcat path.
Thanks for your help in advance.
Rakesh K.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/cmCymGkqgf4J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
