Question: Have the network configuration of OpenCSW been changed?

[Dagobert Michelsen]

Halklo Jan,

> Am 03.12.2019 um 10:12 schrieb Jan Holzhüter <jh at baltic-online.de>:
> 
> Hi,
> hast du ipv6 localhost script laufen lassen?

Ja, z.B.

root at unstable10s [unstable10s]:/root > ifconfig -a
lo0:7: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000 
e1000g1:6: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
        inet 192.168.1.32 netmask ffffff00 broadcast 192.168.1.255
lo0:10: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
        inet6 ::1/128 


das sieht für mich gut aus.
Und für die nicht-gebooteten Rechner müssted as ja nach wie vor gehen.



Besten DAnk

  — Dago

> 
>> Am 03.12.2019 um 09:16 schrieb Dagobert Michelsen via buildfarm <buildfarm at lists.opencsw.org>:
>> 
>> Hi Yusuke,
>> 
>> Am 03.12.2019 um 00:41 schrieb Yusuke Endoh <mame at ruby-lang.org <mailto:mame at ruby-lang.org>>:
>>> I'm Yusuke Endoh, a member of Ruby development team.
>>> 
>>> Since 2 A.M. 1st Dec. 2019 UTC, our Ruby CIs on OpenCSW have failed.
>>> The failure looks related to network configuration about localhost.
>>> 
>>> https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable10s/ruby-master/log/20191202T171915Z.fail.html.gz <https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable10s/ruby-master/log/20191202T171915Z.fail.html.gz>
>>> 
>>> ```
>>> DRb::DRbConnError: drbssl://::1:35909 <drbssl://::1:35909> - #<Errno::ECONNREFUSED: Connection refused - connect(2) for "::1" port 35909>
>>> ```
>>> 
>>> So, I'd like to ask if something network stuff was changed?
>> 
>> We rebooted the machine and some of the networking setup doesn’t come up automatically due to
>> routing issues between the global zone and local zones. However, I just looked and as far as I can
>> say it looks good to me.
>> 
>>> If it is an intentional change, I'd be happy to tackle to fix the issue on the side of Ruby test suite.
>>> I have seen the issue on unstable10s, 10x, 11s, and 11x.
>> 
>> unstable10x, unstable11s and unstable11x have not been rebooted, these are different machines,
>> so if you see the error there too it is not related due to networking on the rebooted host.
>> 
>>> FWIW, `nslookup localhost` fails to find 127.0.0.1.
>>> 
>>> ```
>>> rubyci at unstable10s [unstable10s]:~ > nslookup localhost                                                
>>> Server:         192.168.1.6
>>> Address:        192.168.1.6#53
>>> 
>>> ** server can't find localhost: NXDOMAIN
>>> ```
>> 
>> It is our normal configuration to not resolve localhost via DNS, but you can resolve it locally
>> with the resolver lib:
>> 
>> root at unstable10s [unstable10s]:/root > getent hosts localhost 
>> 127.0.0.1       localhost
>> root at unstable10s [unstable10s]:/root > nslookup localhost
>> Server:         192.168.1.6
>> Address:        192.168.1.6#53
>> 
>> ** server can't find localhost: NXDOMAIN
>> 
>> zsh: 26934 exit 1     nslookup localhost
>> root at unstable10s [unstable10s]:/root > getent hosts localhost
>> 127.0.0.1       localhost
>> root at unstable10s [unstable10s]:/root > 
>> 
>> 
>> Maybe you can describe what the test actually does and why it technically fails,
>> I am not sure at the moment what has changed, be it the build machine configuration
>> or something in your code or something else.
>> 
>> 
>> Best regards
>> 
>>   — Dago
>> 
>> 
>> -- 
>> "You don't become great by trying to be great, you become great by wanting to do something,
>> and then doing it so hard that you become great in the process." - xkcd #896
>> 

-- 
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/buildfarm/attachments/20191203/5905a254/attachment.html>