On Mar 03 2015, Holger Levsen <hol...@layer-acht.org> wrote:
> Hi Nikolas,
> On Montag, 2. März 2015, Nikolaus Rath wrote:
>> Almost certain. I could be certain if I could see the log with the
>> failed test, but it seems that port 80 on reproducible.debian.net is
>> down at the moment:
> it's up again, though it's port 443 :)
> do you still have problems getting the logs?

I managed to get the logs yesterday, but right now it seems down again:

$ ping -c 3 reproducible.debian.net
PING reproducible.debian.net ( 56(84) bytes of data.
64 bytes from ip46-16-73-183.pbiaas.com ( icmp_seq=1 ttl=53 
time=181 ms
64 bytes from ip46-16-73-183.pbiaas.com ( icmp_seq=2 ttl=53 
time=183 ms
64 bytes from ip46-16-73-183.pbiaas.com ( icmp_seq=3 ttl=53 
time=188 ms

--- reproducible.debian.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 181.074/184.085/188.064/2.955 ms

$ curl --connect-timeout 30 --verbose https://reproducible.debian.net/
* Hostname was NOT found in DNS cache
*   Trying
* Connection timed out after 30001 milliseconds
* Closing connection 0
curl: (28) Connection timed out after 30001 milliseconds

>> Is there any way I could ssh into your build host to debug locally?
> no, sorry. (there are no user accounts from ldap like on .debian.org machines 
> on it.)
> did you try to reproduce the problem with pbuilder locally? I think it's more 
> likely a problem with pbuilder than with the reproducible stuff on jenkins. 
> (But I'm offline atm so I cannot test myself.)

I tried, but for me it works just fine with pbuilder.


GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

Attachment: signature.asc
Description: PGP signature

Reproducible-builds mailing list

Reply via email to