Issue #14710 has been updated by Brent Hensarling.
Hello,
I ran the test script as you suggested, however, Cron emailed us the exact same
error message:
**/var/lib/puppet/lib/puppet/facter: Is a directory -
/var/lib/puppet/lib/puppet/facter (Errno::EISDIR)
from /usr/bin/facter:19:in `load'
from /usr/bin/facter:19
**
When I executed the script in an interactive shell, it worked just fine. I'm
not sure why it's only freaking out when we launch it via Cron. In fact,
simply creating a BASH script that executes "facter" by itself will cause the
above error to be output by Cron. Here's the output of 'facter -p' on our
puppet master, for your reference:
architecture => i386
domain => luma-pictures.com
facterversion => 1.6.6
fqdn => sv-puppetmaster01.luma-pictures.com
hardwareisa => i686
hardwaremodel => i686
hostname => sv-puppetmaster01
id => root
interfaces => eth0,lo,sit0
ipaddress => 100.100.100.14
ipaddress_eth0 => 100.100.100.14
ipaddress_lo => 127.0.0.1
is_virtual => true
kernel => Linux
kernelmajversion => 2.6
kernelrelease => 2.6.18-194.26.1.el5.centos.plusxen
kernelversion => 2.6.18
local_access => true
logged_in_user => none
lsbdistcodename => Final
lsbdistdescription => CentOS release 5.5 (Final)
lsbdistid => CentOS
lsbdistrelease => 5.5
lsbmajdistrelease => 5
lsbrelease =>
:core-3.1-ia32:core-3.1-noarch:graphics-3.1-ia32:graphics-3.1-noarch
macaddress => 02:70:83:2D:89:44
macaddress_eth0 => 02:70:83:2D:89:44
memory_banks => none
memory_speeds => none
memoryfree => 1.18 GB
memorysize => 3.18 GB
memorytotal => 3.18 GB
netmask => 255.255.255.0
netmask_eth0 => 255.255.255.0
netmask_lo => 255.0.0.0
network_eth0 => 100.100.100.0
network_lo => 127.0.0.0
nrpe_cfg_file => /etc/nagios/nrpe.cfg
nrpe_plugin_directory => /usr/lib/nagios/plugins
nvidia_ver => none
operatingsystem => CentOS
operatingsystemrelease => 5.5
osfamily => RedHat
path =>
/usr/local/sbin:/usr/bin:/usr/local/bin:/sbin:/bin:/usr/sbin:/root/bin:/usr/local/rush/bin:/opt/dell/srvadmin/bin/:/opt/dell/srvadmin/sbin/:/root/bin
physicalprocessorcount => 0
processor0 => Intel(R) Xeon(R) CPU 5140 @ 2.33GHz
processor1 => Intel(R) Xeon(R) CPU 5140 @ 2.33GHz
processorcount => 2
ps => ps -ef
puppetversion => 2.7.9
rubysitedir => /usr/lib/ruby/site_ruby/1.8
rubyversion => 1.8.6
rush_in_blacklist => false
rush_in_host_file => false
rush_status => NA
selinux => false
swapfree => 3.94 GB
swapsize => 3.97 GB
timezone => PDT
uniqueid => 007f0100
uptime => 14 days
uptime_days => 14
uptime_hours => 344
uptime_seconds => 1240178
video_card => none
virtual => xenu
vlan => 100
Let me know if you need any other troubleshooting information from us.
Thanks for the assistance,
JP
----------------------------------------
Bug #14710: Facter outputs an error when a script that runs "facter -p" is
launched via Cron.
https://projects.puppetlabs.com/issues/14710#change-64120
Author: Brent Hensarling
Status: Needs More Information
Priority: Normal
Assignee: Brent Hensarling
Category:
Target version:
Keywords:
Branch:
Affected Facter version: 1.6.6
Hello,
I have noticed that our puppetmaster outputs a strange error when it tries to
run a BASH script via Cron that runs "facter -p" within the script. Here is
the error that Cron sends to us via email:
Cron Daemon [email protected]
/var/lib/puppet/lib/puppet/facter: Is a directory -
/var/lib/puppet/lib/puppet/facter (Errno::EISDIR)
from /usr/bin/facter:19:in `load'
from /usr/bin/facter:19
/var/lib/puppet/lib/puppet/facter: Is a directory -
/var/lib/puppet/lib/puppet/facter (Errno::EISDIR)
from /usr/bin/facter:19:in `load'
from /usr/bin/facter:19
I have attached 2 examples of scripts that generate this issue. Our
puppetmaster has Facter 1.6.6 and Puppet 2.7.9 installed. O/S is CentOS 5.5.
Google searches didn't reveal much information about the problem. The only
threads I found that even referenced the same error output can be found here:
http://www.puppetlogs.com/puppet/%23puppet-2011-06-27.log.html
http://groups.google.com/group/puppet-users/browse_thread/thread/7a1b95adca7c17af/2cceda3ad28422ae
It should be noted that running "facter -p" on the machine via the command line
produces no issues at all. Nor do any errors occur when running the script
from the command line as well. We only see this issue when the attached
scripts are launched via Cron.
Can you please advise if this is a possible bug in Facter, or if it's something
we're doing wrong on our end. Let me know if you need any further debugging
information from me
Thanks!
JP Baysari
Luma Pictures
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
