Hello, @Joseph: not yet.
@Eric: sure :) . SLES 11 SP2, and the output is here: http://pastebin.com/jqgNmewk But I have an idea. I have another host where it still works. The host it stopped working on has two IP addresses configured on one (!) network device. so an "ip a" gives me: [...] 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:50:56:99:05:02 brd ff:ff:ff:ff:ff:ff *inet 130.250.8.15/24 *brd 130.250.8.255 scope global eth0 *inet 130.250.8.20/24 *brd 130.250.8.255 scope global secondary eth0 [...] Maybe this is not actually covered by the detection algorithm of facter? :) Anyway, thanks for your help! Axel. Am Dienstag, 4. September 2012 23:57:08 UTC+2 schrieb Eric Sorenson: > > Hi Axel - what OS? What version of Facter? What does the output of your > 'ifconfig -a' (or local equivalent) look like? Could you please run 'facter > --debug' and pastebin the output somewhere? > > On Monday, August 20, 2012 1:19:39 AM UTC-7, Axel Bock wrote: >> >> Hi readers, >> >> another problem of mine. A host which worked just fine on friday is now >> not able to find out its own IP address. The reason is pretty simple as far >> as I have figured out: Facter. Facter returns the network interfaces just >> fine: interfaces=eth0,eth1, but then the ipaddress_ETHx entries are >> completely missing. >> >> Any idea what could be the cause of this? >> >> >> Thanks in advance & greetings, >> Axel. >> > -- 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/-/HDWQfJIjv3wJ. 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.
