uuh ... /inet addr[...]/ as pattern in ip.rb? a wild guess ... if the 
output is localized - then puppet won't be able to get the IP address info, 
right? 
check. 

*l1215022:~ # facter | grep _eth*
*l1215022:~ # export LC_ALL="en_US"*
*l1215022:~ # facter | grep _eth*
ipaddress_eth0 => 130.250.8.15
macaddress_eth0 => 00:50:56:99:05:02
macaddress_eth1 => 00:50:56:99:18:02
netmask_eth0 => 255.255.255.0
*l1215022:~ #* 

oh boy. seriously? NO ONE noticed that before?? I'm stunned right now.






Am Donnerstag, 6. September 2012 08:17:02 UTC+2 schrieb Axel Bock:
>
> Hi Krysztof, 
>
> like this: 
>
> eth0      Link encap:Ethernet  Hardware Adresse 00:50:56:99:05:02
>           inet Adresse:130.250.8.15  Bcast:130.250.8.255  
> Maske:255.255.255.0
>           inet6 Adresse: fe80::250:56ff:fe99:502/64 
> Gültigkeitsbereich:Verbindung
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:3351042 errors:0 dropped:14 overruns:0 frame:0
>           TX packets:5629216 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 Sendewarteschlangenlänge:1000
>           RX bytes:831103271 (792.6 Mb)  TX bytes:5488168284 (5233.9 Mb)
>
> eth1      Link encap:Ethernet  Hardware Adresse 00:50:56:99:18:02
>           BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 Sendewarteschlangenlänge:1000
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>
> lo        Link encap:Lokale Schleife
>           inet Adresse:127.0.0.1  Maske:255.0.0.0
>           inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:250524 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:250524 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 Sendewarteschlangenlänge:0
>           RX bytes:59997729 (57.2 Mb)  TX bytes:59997729 (57.2 Mb)
>
>
> And @Ashley - no, there is an /sbin/ifconfig, as you can see ... isn't 
> "Senderwarteschlangenlänge" a _great_ word? ;))
>
> Greetings!
> Axel.
>
>
>
> Am Mittwoch, 5. September 2012 18:40:19 UTC+2 schrieb Krzysztof Wilczynski:
>>
>> Hi,
>>
>> How does your ifconfig -a output looks like?
>>
>> Suspects:
>>
>> https://github.com/puppetlabs/facter/blob/master/lib/facter/interfaces.rb
>> https://github.com/puppetlabs/facter/blob/master/lib/facter/util/ip.rb
>>
>> KW
>>
>> On Wednesday, 5 September 2012 09:52:03 UTC+1, Axel Bock wrote:
>>>
>>> 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/-/2thIa4dZxkcJ.
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.

Reply via email to