Server unrresponsive

Server unrresponsive

[Daniel Pimentel]

Hi Guix, I tried install in my desktop (amd64) and server is very busy.

Message: server is unresponsive

Thanks.

-- 
Daniel Pimentel (d4n1)

Re: Server unrresponsive

[Ludovic Courtès]

This message suggests that hydra.gnu.org, the server that provides
pre-compiled binaries, is somewhat slow.

This is unfortunately too frequent and we hope to switch to a more
powerful front-end server.

Thanks,
Ludo’.

Re: Server unrresponsive

[Daniel Pimentel]

On 2015-01-21 12:04, ludo@gnu.org wrote:
> This message suggests that hydra.gnu.org, the server that provides
> pre-compiled binaries, is somewhat slow.
> 
> This is unfortunately too frequent and we hope to switch to a more
> powerful front-end server.
> 
> Thanks,
> Ludo’.
Allright, I used the options "--no-distributes" and work.

Thanks,
-- 
Daniel Pimentel (d4n1)

Re: Server unrresponsive

[Sree Harsha Totakura]

On 01/21/2015 04:04 PM, Ludovic Courtès wrote:
> This message suggests that hydra.gnu.org, the server that provides
> pre-compiled binaries, is somewhat slow.
> 
> This is unfortunately too frequent and we hope to switch to a more
> powerful front-end server.
> 
I believe switching to hydra.gnunet.org may be helpful.  Have you
considered it?

Sree

Re: Server unrresponsive

[Ludovic Courtès]

Sree Harsha Totakura <sreeharsha@totakura.in> skribis:

> On 01/21/2015 04:04 PM, Ludovic Courtès wrote:
>> This message suggests that hydra.gnu.org, the server that provides
>> pre-compiled binaries, is somewhat slow.
>> 
>> This is unfortunately too frequent and we hope to switch to a more
>> powerful front-end server.
>> 
> I believe switching to hydra.gnunet.org may be helpful.  Have you
> considered it?

I think we have just the right size in terms of x86 build machines.  The
front-end itself shouldn’t also be a build machine, because it already
has enough to do (evaluations + HTTP requests, which includes providing
compressed archives on demand.)

So I would like to keep hydra.gnunet.org as a build machine and to
switch to a dedicated box for the front-end.

The FSF might be able to help with that, otherwise we’ll go ahead and
get ourselves another machine, I think.  But I think it’s time to fix
that issue now.

Thanks,
Ludo’.

Re: Server unrresponsive

[John Darrington]

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

I kindof presumed it was the bandwidth to hydra which was the problem.  Not the 
machine itself.

Are you sure which problem needs to be solved before we spend $$$ on it?

On Tue, Jan 27, 2015 at 11:11:36PM +0100, Ludovic Courtès wrote:
     
     I think we have just the right size in terms of x86 build machines.  The
     front-end itself shouldn’t also be a build machine, because it already
     has enough to do (evaluations + HTTP requests, which includes providing
     compressed archives on demand.)
     
     So I would like to keep hydra.gnunet.org as a build machine and to
     switch to a dedicated box for the front-end.
     
     The FSF might be able to help with that, otherwise we’ll go ahead and
     get ourselves another machine, I think.  But I think it’s time to fix
     that issue now.
     
     Thanks,
     Ludo’.
     

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: Server unrresponsive

[Adam Pribyl]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1329 bytes --]

On Fri, 30 Jan 2015, John Darrington wrote:

> I kindof presumed it was the bandwidth to hydra which was the problem.  Not the
> machine itself.
>
> Are you sure which problem needs to be solved before we spend $$$ on it?

Most of the time I was seeing that hydra is unresponsive and guix will 
fetch the source instead a substitute, but ATM I am getting a message:

guix substitute-binary: warning: while fetching 
http://hydra.gnu.org/nar/nax41ygqk14w23nbyzfh4i23vxl3qf01-python-3.3.5: 
server is somewhat slow

but it is still fetching the substitute from there. The hydra admin should 
find what is the cause.


> On Tue, Jan 27, 2015 at 11:11:36PM +0100, Ludovic Courtès wrote:
>
>     I think we have just the right size in terms of x86 build machines.  The
>     front-end itself shouldn’t also be a build machine, because it already
>     has enough to do (evaluations + HTTP requests, which includes providing
>     compressed archives on demand.)
>
>     So I would like to keep hydra.gnunet.org as a build machine and to
>     switch to a dedicated box for the front-end.
>
>     The FSF might be able to help with that, otherwise we’ll go ahead and
>     get ourselves another machine, I think.  But I think it’s time to fix
>     that issue now.
>
>     Thanks,
>     Ludo’.

Re: Server unrresponsive

[Ludovic Courtès]

Adam Pribyl <pribyl@lowlevel.cz> skribis:

> Most of the time I was seeing that hydra is unresponsive and guix will
> fetch the source instead a substitute, but ATM I am getting a message:
>
> guix substitute-binary: warning: while fetching
> http://hydra.gnu.org/nar/nax41ygqk14w23nbyzfh4i23vxl3qf01-python-3.3.5:
> server is somewhat slow

Actually the “unresponsive” message was misleading, which is why I
changed it to “somewhat slow” (after a native speaker pointed out the
bad choice of words.  ;-))

Ludo’.