Hi,
I''ve had a class with the following setup:
class drupal6 {
site (
$ensure = ''present'',
$dbname,
$dbpw,
$dbserver,
$sitefqdn,
$modules = ""
)
{
....
}
....
}
I added the parameter alias to drupal6:site and now I''m getting the
following error on the client: "Could not run Puppet configuration
client: Parameter alias failed: /usr/share/drupal6/sites/
scisoc.feds.ca/files can not create alias scisoc.uwaterloo.ca: object
already exists at /srv/puppet/modules/drupal6/manifests/init.pp:179"
The object that already exists differs from run to run (is get
different line numbers seemingly randomly on different resources
defined in drupal6) but the error is still the same. After reverting
to a puppet config version that had worked previously I still get the
same error message. I have no idea why the error still occurs on the
client machine even though I reverted all of my changes back to a
version that was working previously. I know now that alias is a meta
parameter but why would it still be set after the reversion? Has
anyone else seen this issue or know how to resolve it? I''m running
(Debian 2.6.26-26lenny1) puppet package 0.25.4-2~b. Thanks.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
What is ''site''?? Define or class?? You haven''t specified. Better check your puppet doco.. Den On 19/01/2011, at 3:20, Lithium <brad.krane@gmail.com> wrote:> Hi, > > I''ve had a class with the following setup: > > class drupal6 { > site ( > $ensure = ''present'', > $dbname, > $dbpw, > $dbserver, > $sitefqdn, > $modules = "" > ) > { > .... > } > .... > } > > I added the parameter alias to drupal6:site and now I''m getting the > following error on the client: "Could not run Puppet configuration > client: Parameter alias failed: /usr/share/drupal6/sites/ > scisoc.feds.ca/files can not create alias scisoc.uwaterloo.ca: object > already exists at /srv/puppet/modules/drupal6/manifests/init.pp:179" > > The object that already exists differs from run to run (is get > different line numbers seemingly randomly on different resources > defined in drupal6) but the error is still the same. After reverting > to a puppet config version that had worked previously I still get the > same error message. I have no idea why the error still occurs on the > client machine even though I reverted all of my changes back to a > version that was working previously. I know now that alias is a meta > parameter but why would it still be set after the reversion? Has > anyone else seen this issue or know how to resolve it? I''m running > (Debian 2.6.26-26lenny1) puppet package 0.25.4-2~b. Thanks. > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Sorry, I missed that part. Site is a define. Looking at the logs I''m also getting a different message at random: Could not run Puppet configuration client: Parameter alias failed: Munging failed for value "scisoc.uwaterloo.ca" in class alias: Cannot alias Mysql::Database-user[scisoc_drupal6-monitoring] to scisoc.uwaterloo.ca; resource Mysql::Database- user[scisoc.uwaterloo.ca] already exists I only get one error logged per puppet run so I hadn''t seen this other message until now. Any idea what it could mean? I''m still not sure why this problem would persist after reverting the puppet config for this client back to the state before it was happening, something seems to be preventing the client from getting back to the state it was in before the change that caused it was made. On Jan 18, 8:14 pm, Denmat <tu2bg...@gmail.com> wrote:> What is ''site''?? Define or class?? You haven''t specified. Better check your puppet doco.. > > Den > > On 19/01/2011, at 3:20, Lithium <brad.kr...@gmail.com> wrote: > > > > > > > > > Hi, > > > I''ve had a class with the following setup: > > > class drupal6 { > > site ( > > $ensure = ''present'', > > $dbname, > > $dbpw, > > $dbserver, > > $sitefqdn, > > $modules = "" > > ) > > { > > .... > > } > > .... > > } > > > I added the parameter alias to drupal6:site and now I''m getting the > > following error on the client: "Could not run Puppet configuration > > client: Parameter alias failed: /usr/share/drupal6/sites/ > > scisoc.feds.ca/files can not create alias scisoc.uwaterloo.ca: object > > already exists at /srv/puppet/modules/drupal6/manifests/init.pp:179" > > > The object that already exists differs from run to run (is get > > different line numbers seemingly randomly on different resources > > defined in drupal6) but the error is still the same. After reverting > > to a puppet config version that had worked previously I still get the > > same error message. I have no idea why the error still occurs on the > > client machine even though I reverted all of my changes back to a > > version that was working previously. I know now that alias is a meta > > parameter but why would it still be set after the reversion? Has > > anyone else seen this issue or know how to resolve it? I''m running > > (Debian 2.6.26-26lenny1) puppet package 0.25.4-2~b. Thanks. > > > -- > > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en.-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Without seeing your code, does the user ''scisoc.uwaterloo.ca'' already exist in your manifest? Or maybe you didn''t fully revert your changes? Also puppet doesn''t revert changes made to nodes unless you tell it how. Other tip would be to try virtualizing the resource and realize it, or striping out what you are trying to do into a smaller class so you can test what you are trying to do works. If it doesn''t copy that code so we can see what you are trying to do. Cheers, Den On 20/01/2011, at 2:23, Lithium <brad.krane@gmail.com> wrote:> Sorry, I missed that part. Site is a define. Looking at the logs I''m > also getting a different message at random: > > Could not run Puppet configuration client: Parameter alias failed: > Munging failed for value "scisoc.uwaterloo.ca" in class alias: Cannot > alias Mysql::Database-user[scisoc_drupal6-monitoring] to > scisoc.uwaterloo.ca; resource Mysql::Database- > user[scisoc.uwaterloo.ca] already exists > > I only get one error logged per puppet run so I hadn''t seen this other > message until now. Any idea what it could mean? > > I''m still not sure why this problem would persist after reverting the > puppet config for this client back to the state before it was > happening, something seems to be preventing the client from getting > back to the state it was in before the change that caused it was made. > > On Jan 18, 8:14 pm, Denmat <tu2bg...@gmail.com> wrote: >> What is ''site''?? Define or class?? You haven''t specified. Better check your puppet doco.. >> >> Den >> >> On 19/01/2011, at 3:20, Lithium <brad.kr...@gmail.com> wrote: >> >> >> >> >> >> >> >>> Hi, >> >>> I''ve had a class with the following setup: >> >>> class drupal6 { >>> site ( >>> $ensure = ''present'', >>> $dbname, >>> $dbpw, >>> $dbserver, >>> $sitefqdn, >>> $modules = "" >>> ) >>> { >>> .... >>> } >>> .... >>> } >> >>> I added the parameter alias to drupal6:site and now I''m getting the >>> following error on the client: "Could not run Puppet configuration >>> client: Parameter alias failed: /usr/share/drupal6/sites/ >>> scisoc.feds.ca/files can not create alias scisoc.uwaterloo.ca: object >>> already exists at /srv/puppet/modules/drupal6/manifests/init.pp:179" >> >>> The object that already exists differs from run to run (is get >>> different line numbers seemingly randomly on different resources >>> defined in drupal6) but the error is still the same. After reverting >>> to a puppet config version that had worked previously I still get the >>> same error message. I have no idea why the error still occurs on the >>> client machine even though I reverted all of my changes back to a >>> version that was working previously. I know now that alias is a meta >>> parameter but why would it still be set after the reversion? Has >>> anyone else seen this issue or know how to resolve it? I''m running >>> (Debian 2.6.26-26lenny1) puppet package 0.25.4-2~b. Thanks. >> >>> -- >>> You received this message because you are subscribed to the Google Groups "Puppet Users" group. >>> To post to this group, send email to puppet-users@googlegroups.com. >>> To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. >>> For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Den, It was the second problem, not reverting all of my code. I still had a drupal6::site with the alias parameter (which I renamed to not conflict with the meta params to sitealias) set to ''scisoc.uwaterloo.ca''. After I changed alias to sitealias puppet ran fine. It was hard to pin down from the error messages especially since it seemed that the error would just associate itself to a random resource within the drupal6 class and not on anyone thing in specific. Thanks for being a sounding board, it was appreciated! Cheers, On Jan 19, 1:25 pm, Denmat <tu2bg...@gmail.com> wrote:> Without seeing your code, does the user ''scisoc.uwaterloo.ca'' already exist in your manifest? Or maybe you didn''t fully revert your changes? Also puppet doesn''t revert changes made to nodes unless you tell it how. > > Other tip would be to try virtualizing the resource and realize it, or striping out what you are trying to do into a smaller class so you can test what you are trying to do works. If it doesn''t copy that code so we can see what you are trying to do. > > Cheers, > Den > > On 20/01/2011, at 2:23, Lithium <brad.kr...@gmail.com> wrote: > > > > > > > > > Sorry, I missed that part. Site is a define. Looking at the logs I''m > > also getting a different message at random: > > > Could not run Puppet configuration client: Parameter alias failed: > > Munging failed for value "scisoc.uwaterloo.ca" in class alias: Cannot > > alias Mysql::Database-user[scisoc_drupal6-monitoring] to > > scisoc.uwaterloo.ca; resource Mysql::Database- > > user[scisoc.uwaterloo.ca] already exists > > > I only get one error logged per puppet run so I hadn''t seen this other > > message until now. Any idea what it could mean? > > > I''m still not sure why this problem would persist after reverting the > > puppet config for this client back to the state before it was > > happening, something seems to be preventing the client from getting > > back to the state it was in before the change that caused it was made. > > > On Jan 18, 8:14 pm, Denmat <tu2bg...@gmail.com> wrote: > >> What is ''site''?? Define or class?? You haven''t specified. Better check your puppet doco.. > > >> Den > > >> On 19/01/2011, at 3:20, Lithium <brad.kr...@gmail.com> wrote: > > >>> Hi, > > >>> I''ve had a class with the following setup: > > >>> class drupal6 { > >>> site ( > >>> $ensure = ''present'', > >>> $dbname, > >>> $dbpw, > >>> $dbserver, > >>> $sitefqdn, > >>> $modules = "" > >>> ) > >>> { > >>> .... > >>> } > >>> .... > >>> } > > >>> I added the parameter alias to drupal6:site and now I''m getting the > >>> following error on the client: "Could not run Puppet configuration > >>> client: Parameter alias failed: /usr/share/drupal6/sites/ > >>> scisoc.feds.ca/files can not create alias scisoc.uwaterloo.ca: object > >>> already exists at /srv/puppet/modules/drupal6/manifests/init.pp:179" > > >>> The object that already exists differs from run to run (is get > >>> different line numbers seemingly randomly on different resources > >>> defined in drupal6) but the error is still the same. After reverting > >>> to a puppet config version that had worked previously I still get the > >>> same error message. I have no idea why the error still occurs on the > >>> client machine even though I reverted all of my changes back to a > >>> version that was working previously. I know now that alias is a meta > >>> parameter but why would it still be set after the reversion? Has > >>> anyone else seen this issue or know how to resolve it? I''m running > >>> (Debian 2.6.26-26lenny1) puppet package 0.25.4-2~b. Thanks. > > >>> -- > >>> You received this message because you are subscribed to the Google Groups "Puppet Users" group. > >>> To post to this group, send email to puppet-users@googlegroups.com. > >>> To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > >>> For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en.-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
My pleasure. On 20/01/2011, at 8:45, Lithium <brad.krane@gmail.com> wrote:> Den, > > It was the second problem, not reverting all of my code. I still had a > drupal6::site with the alias parameter (which I renamed to not > conflict with the meta params to sitealias) set to > ''scisoc.uwaterloo.ca''. After I changed alias to sitealias puppet ran > fine. It was hard to pin down from the error messages especially since > it seemed that the error would just associate itself to a random > resource within the drupal6 class and not on anyone thing in > specific. > > Thanks for being a sounding board, it was appreciated! > > Cheers, > > On Jan 19, 1:25 pm, Denmat <tu2bg...@gmail.com> wrote: >> Without seeing your code, does the user ''scisoc.uwaterloo.ca'' already exist in your manifest? Or maybe you didn''t fully revert your changes? Also puppet doesn''t revert changes made to nodes unless you tell it how. >> >> Other tip would be to try virtualizing the resource and realize it, or striping out what you are trying to do into a smaller class so you can test what you are trying to do works. If it doesn''t copy that code so we can see what you are trying to do. >> >> Cheers, >> Den >> >> On 20/01/2011, at 2:23, Lithium <brad.kr...@gmail.com> wrote: >> >> >> >> >> >> >> >>> Sorry, I missed that part. Site is a define. Looking at the logs I''m >>> also getting a different message at random: >> >>> Could not run Puppet configuration client: Parameter alias failed: >>> Munging failed for value "scisoc.uwaterloo.ca" in class alias: Cannot >>> alias Mysql::Database-user[scisoc_drupal6-monitoring] to >>> scisoc.uwaterloo.ca; resource Mysql::Database- >>> user[scisoc.uwaterloo.ca] already exists >> >>> I only get one error logged per puppet run so I hadn''t seen this other >>> message until now. Any idea what it could mean? >> >>> I''m still not sure why this problem would persist after reverting the >>> puppet config for this client back to the state before it was >>> happening, something seems to be preventing the client from getting >>> back to the state it was in before the change that caused it was made. >> >>> On Jan 18, 8:14 pm, Denmat <tu2bg...@gmail.com> wrote: >>>> What is ''site''?? Define or class?? You haven''t specified. Better check your puppet doco.. >> >>>> Den >> >>>> On 19/01/2011, at 3:20, Lithium <brad.kr...@gmail.com> wrote: >> >>>>> Hi, >> >>>>> I''ve had a class with the following setup: >> >>>>> class drupal6 { >>>>> site ( >>>>> $ensure = ''present'', >>>>> $dbname, >>>>> $dbpw, >>>>> $dbserver, >>>>> $sitefqdn, >>>>> $modules = "" >>>>> ) >>>>> { >>>>> .... >>>>> } >>>>> .... >>>>> } >> >>>>> I added the parameter alias to drupal6:site and now I''m getting the >>>>> following error on the client: "Could not run Puppet configuration >>>>> client: Parameter alias failed: /usr/share/drupal6/sites/ >>>>> scisoc.feds.ca/files can not create alias scisoc.uwaterloo.ca: object >>>>> already exists at /srv/puppet/modules/drupal6/manifests/init.pp:179" >> >>>>> The object that already exists differs from run to run (is get >>>>> different line numbers seemingly randomly on different resources >>>>> defined in drupal6) but the error is still the same. After reverting >>>>> to a puppet config version that had worked previously I still get the >>>>> same error message. I have no idea why the error still occurs on the >>>>> client machine even though I reverted all of my changes back to a >>>>> version that was working previously. I know now that alias is a meta >>>>> parameter but why would it still be set after the reversion? Has >>>>> anyone else seen this issue or know how to resolve it? I''m running >>>>> (Debian 2.6.26-26lenny1) puppet package 0.25.4-2~b. Thanks. >> >>>>> -- >>>>> You received this message because you are subscribed to the Google Groups "Puppet Users" group. >>>>> To post to this group, send email to puppet-users@googlegroups.com. >>>>> To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. >>>>> For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en. >> >>> -- >>> You received this message because you are subscribed to the Google Groups "Puppet Users" group. >>> To post to this group, send email to puppet-users@googlegroups.com. >>> To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. >>> For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.