savannah-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-users] Unable to upload release tarball to Download Area


From: Bob Proulx
Subject: Re: [Savannah-users] Unable to upload release tarball to Download Area
Date: Wed, 3 Apr 2019 19:20:25 -0600
User-agent: Mutt/1.10.1 (2018-07-13)

Asher Gordon wrote:
> > I am getting pretty close to having the mirror problem understood. At
> > the moment my brains are leaking out my ears from trying to get my
> > mind wrapped around it.
> 
> Sounds painful! ;-)

Pain is simply weakness leaving the body.  Sometimes the soul tags
along with it. :-)

I have gained an understanding now.  I know what needs to be done to
solve the problem.  At root cause I had broken one of the cron scripts
in moving it from system to system.  It wasn't updating a timestamp
which caused a monitoring script in the redirector to think the mirror
was out of sync when it was not.  It needs to look not at the absolute
age but the relative age however.  The reference should be the
upstream source, which is known to the redirector, not the time now.
And there needs to be a fallback when there are no mirrors.

I am a huge fan of continuous improvement. :-)

> I am now having problems with sftp and sshfs. See below:
>   $ mkdir mnt
>   $ sshfs address@hidden:/releases/c2py mnt
>   Enter passphrase for key '/home/asher/.ssh/id_rsa':
>   remote host has disconnected
>   $ sftp address@hidden:/releases/c2py
>   Enter passphrase for key '/home/asher/.ssh/id_rsa':
>   Connection closed
> (scp still works fine)

I'll need to investigate.

> Are these also related to the same bug? It would be nice to use
> sshfs because I could easily manage the directory as if it were
> local.

This may or may not be related to a previous security vulnerability
that Sylvain reported and fixed a couple of years ago which forced a
loss of support for some file copy protocols.  As such the
documentation may not have caught up to the new reality.  I remember
there being new restrictions on file deletion that didn't exist
before.  Therefore sshfs might just not be allowed through the command
filter at this time.

As you might imagine it isn't allowed to run arbitrary commands.
Therefore all of the ssh commands are filtered through an sv_membersh
filter before being allowed through.

> Also, rsync works if I do not use `-a'. However, if I do use `-a',
> it gets stuck at "sending incremental file list" (you need `-v' to
> see the message). Hopefully this information will help you fix the
> bug(s).

That one is definitely known due to the sv_membersh filter.  I will
add that as a note to the rsync method in the documentation.  The
example shown was without options.

    scp release.tar.gz address@hidden:/releases/project/
    rsync release.tar.gz address@hidden:/releases/project/
    sftp address@hidden:/releases/project/ # interactive mode

However sshfs is documented as working.  I'll give it a try and see
what methods it is trying to use for file access.

> Thank you very much for your great work on Savannah!

Happy to help!

Bob



reply via email to

[Prev in Thread] Current Thread [Next in Thread]