hello list!!
I am having some trouble with a postfix module I am attempting to
implement. as always, your input is extremely valuable and would be
appreciated
here''s what''s going on:
## errors
err: //postfix/Package[postfix-pflogsum.x86_64]/ensure: change from
absent to present failed: Could not find package
postfix-pflogsum.x86_64
notice: //postfix/Cron[pflogsum]: Dependency
package[postfix-pflogsum.x86_64] has 1 failures
warning: //postfix/Cron[pflogsum]: Skipping because of failed dependencies
err: //postfix/Service[postfix]/ensure: change from stopped to running
failed: Could not start Service[postfix]: Execution of ''/sbin/service
postfix start'' returned 1: at
/etc/puppet/modules/postfix/manifests/init.pp:35
err: //postfix/File[/etc/aliases.db]: Failed to retrieve current state
of resource: Error 400 on SERVER: Permission denied -
/etc/puppet/modules/postfix/files/aliases.db Could not retrieve file
metadata for puppet:///postfix/aliases.db: Error 400 on SERVER:
Permission denied - /etc/puppet/modules/postfix/files/aliases.db at
/etc/puppet/modules/postfix/manifests/init.pp:17
As you can see pflogsum is not being installed and the postfix service
is not starting. also the aliases.db file that I am attempting to
share doesn''t get transferred. although
## ls of files
[root@puppet ~]# ls -l /etc/puppet/modules/postfix/files/aliases.db
-rw-r----- 1 root root 12288 Mar 2 16:18
/etc/puppet/modules/postfix/files/aliases.db
## /etc/init.d/modules/postfix/manifests/init.pp
class postfix {
$mailadmin = "nick@$domain"
$packagelist = ["postfix.$architecture",
"postfix-pflogsum.$architecture"]
package { $packagelist:
ensure => "installed"
}
file {
"/etc/aliases.db":
mode => "0640",
source => "puppet:///postfix/aliases.db";
}
file { "/etc/postfix/main.cf":
source => "puppet:///postfix/master.cf";
}
file { "/etc/postfix/master.cf":
source => "puppet:///postfix/master.cf"
}
service { "postfix":
enable => true,
ensure => running,
hasstatus => true,
require => Package["postfix.$architecture"]
}
cron { pflogsum:
hour => 2,
minute => 15,
user => mail,
command => "/usr/sbin/pflogsum -d yesterday /var/log/maillog |
mail -s ''pflogsum from $fqdn'' $mailadmin",
require => Package["postfix-pflogsum.$architecture"]
}
}
so thanks once again for your support without your help I would never
have come as far as I have!
best!
tim
--
GPG me!!
gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
--
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.
postfix-pflogsumm.x86_64, it''s summ not sum. source => "puppet:///postfix/aliases.db"; <--- I don''t think you need the ; anywhere. You''ve got a a few of them. Ramin On Mar 3, 1:14 pm, Tim Dunphy <bluethu...@gmail.com> wrote:> hello list!! > > I am having some trouble with a postfix module I am attempting to > implement. as always, your input is extremely valuable and would be > appreciated > > here''s what''s going on: > > ## errors > > err: //postfix/Package[postfix-pflogsum.x86_64]/ensure: change from > absent to present failed: Could not find package > postfix-pflogsum.x86_64 > notice: //postfix/Cron[pflogsum]: Dependency > package[postfix-pflogsum.x86_64] has 1 failures > warning: //postfix/Cron[pflogsum]: Skipping because of failed dependencies > err: //postfix/Service[postfix]/ensure: change from stopped to running > failed: Could not start Service[postfix]: Execution of ''/sbin/service > postfix start'' returned 1: at > /etc/puppet/modules/postfix/manifests/init.pp:35 > err: //postfix/File[/etc/aliases.db]: Failed to retrieve current state > of resource: Error 400 on SERVER: Permission denied - > /etc/puppet/modules/postfix/files/aliases.db Could not retrieve file > metadata for puppet:///postfix/aliases.db: Error 400 on SERVER: > Permission denied - /etc/puppet/modules/postfix/files/aliases.db at > /etc/puppet/modules/postfix/manifests/init.pp:17 > > As you can see pflogsum is not being installed and the postfix service > is not starting. also the aliases.db file that I am attempting to > share doesn''t get transferred. although > > ## ls of files > > [root@puppet ~]# ls -l /etc/puppet/modules/postfix/files/aliases.db > -rw-r----- 1 root root 12288 Mar 2 16:18 > /etc/puppet/modules/postfix/files/aliases.db > > ## /etc/init.d/modules/postfix/manifests/init.pp > > class postfix { > > $mailadmin = "nick@$domain" > > $packagelist = ["postfix.$architecture", "postfix-pflogsum.$architecture"] > > package { $packagelist: > ensure => "installed" > } > > file { > > "/etc/aliases.db": > mode => "0640", > source => "puppet:///postfix/aliases.db"; > > } > > file { "/etc/postfix/main.cf": > source => "puppet:///postfix/master.cf"; > > } > > file { "/etc/postfix/master.cf": > source => "puppet:///postfix/master.cf" > } > > service { "postfix": > > enable => true, > ensure => running, > hasstatus => true, > require => Package["postfix.$architecture"] > } > > cron { pflogsum: > hour => 2, > minute => 15, > user => mail, > command => "/usr/sbin/pflogsum -d yesterday /var/log/maillog | > mail -s ''pflogsum from $fqdn'' $mailadmin", > require => Package["postfix-pflogsum.$architecture"] > } > > } > > so thanks once again for your support without your help I would never > have come as far as I have! > > best! > tim > > -- > GPG me!! > > gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B-- 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.
On Mar 3, 10:38 pm, Ramin K <ramin.khat...@gmail.com> wrote:> source => "puppet:///postfix/aliases.db"; <--- I don''t think you need > the ; anywhere. You''ve got a a few of them.They are not necessary in that context, but they are valid and harmless. They are needed when you want to put multiple resources into the same declaration, like so: package { "my-package1": ensure => latest; "my-package2": ensure => 0.42; "your-package3": ensure => absent; # The last semicolon is optional } Of course, you can specify as many properties as you like for each resource. John -- 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.
On 03/03/11 21:14, Tim Dunphy wrote:> hello list!! > > I am having some trouble with a postfix module I am attempting to > implement. as always, your input is extremely valuable and would be > appreciated > > > here''s what''s going on: > > ## errors > > err: //postfix/Package[postfix-pflogsum.x86_64]/ensure: change from > absent to present failed: Could not find package > postfix-pflogsum.x86_64 > notice: //postfix/Cron[pflogsum]: Dependency > package[postfix-pflogsum.x86_64] has 1 failures > warning: //postfix/Cron[pflogsum]: Skipping because of failed dependencies > err: //postfix/Service[postfix]/ensure: change from stopped to running > failed: Could not start Service[postfix]: Execution of ''/sbin/service > postfix start'' returned 1: at > /etc/puppet/modules/postfix/manifests/init.pp:35 > err: //postfix/File[/etc/aliases.db]: Failed to retrieve current state > of resource: Error 400 on SERVER: Permission denied - > /etc/puppet/modules/postfix/files/aliases.db Could not retrieve file > metadata for puppet:///postfix/aliases.db: Error 400 on SERVER: > Permission denied - /etc/puppet/modules/postfix/files/aliases.db at > /etc/puppet/modules/postfix/manifests/init.pp:17 > > > > As you can see pflogsum is not being installed and the postfix service > is not starting. also the aliases.db file that I am attempting to > share doesn''t get transferred. although > > ## ls of files > > [root@puppet ~]# ls -l /etc/puppet/modules/postfix/files/aliases.db > -rw-r----- 1 root root 12288 Mar 2 16:18 > /etc/puppet/modules/postfix/files/aliases.dbIs your puppetmaster running as root? It''s unlikely. You either want to change the owner or chmod o+r. HTH, Dan -- 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.
Hi Dan, the puppetmaster daemon is not running as root, however I have other modules running on this machine and a files directory in each that all have the same exact ownership and permissions and are being shared without any problems. tim On Fri, Mar 4, 2011 at 9:18 AM, Daniel Piddock <dgp-goog@corefiling.co.uk> wrote:> On 03/03/11 21:14, Tim Dunphy wrote: >> hello list!! >> >> I am having some trouble with a postfix module I am attempting to >> implement. as always, your input is extremely valuable and would be >> appreciated >> >> >> here''s what''s going on: >> >> ## errors >> >> err: //postfix/Package[postfix-pflogsum.x86_64]/ensure: change from >> absent to present failed: Could not find package >> postfix-pflogsum.x86_64 >> notice: //postfix/Cron[pflogsum]: Dependency >> package[postfix-pflogsum.x86_64] has 1 failures >> warning: //postfix/Cron[pflogsum]: Skipping because of failed dependencies >> err: //postfix/Service[postfix]/ensure: change from stopped to running >> failed: Could not start Service[postfix]: Execution of ''/sbin/service >> postfix start'' returned 1: at >> /etc/puppet/modules/postfix/manifests/init.pp:35 >> err: //postfix/File[/etc/aliases.db]: Failed to retrieve current state >> of resource: Error 400 on SERVER: Permission denied - >> /etc/puppet/modules/postfix/files/aliases.db Could not retrieve file >> metadata for puppet:///postfix/aliases.db: Error 400 on SERVER: >> Permission denied - /etc/puppet/modules/postfix/files/aliases.db at >> /etc/puppet/modules/postfix/manifests/init.pp:17 >> >> >> >> As you can see pflogsum is not being installed and the postfix service >> is not starting. also the aliases.db file that I am attempting to >> share doesn''t get transferred. although >> >> ## ls of files >> >> [root@puppet ~]# ls -l /etc/puppet/modules/postfix/files/aliases.db >> -rw-r----- 1 root root 12288 Mar 2 16:18 >> /etc/puppet/modules/postfix/files/aliases.db > > Is your puppetmaster running as root? It''s unlikely. You either want to > change the owner or chmod o+r. > > HTH, > > Dan > > -- > 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. > >-- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B -- 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.
On Mar 4, 8:24 am, Tim Dunphy <bluethu...@gmail.com> wrote:> the puppetmaster daemon is not running as root, however I have other > modules running on this machine and a files directory in each that > all have the same exact ownership and permissions and are being shared > without any problems.Then the puppetmaster user must belong to group "root" (or one of its aliases); otherwise, it wouldn''t be able to read your other files, either. I wouldn''t be very comfortable with that, though it''s better than running as root. If you want to ensure that the Puppetmaster cannot change the files, then you can instead assign the files and the puppet user to group "puppet" (or some other non-root group) and leave the file modes the same. Files'' groups do not have to coincide with their owners'' groups. Whether you do that or not, though, do ensure that all the directories in the path to your file have group execute permission. Read is not enough. John -- 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.