Menu

#26570 Rsync to frs.sourceforge.net very slow or hanging

closed
nobody
None
lin20-microG
2025-03-10
2025-03-07
M S
No

Dear team,

seems that 'rsync' to frs.sourceforge.net "takes ages" or does not work at all.
When attempting to push a release via rsync to frs.sourceforge.net - different from before - the upload either is extremely slow or hangs (what used to be 2-3 minutes before, isn't now even finished after more than half an hour) - could you please check?

Many thanks, M.

Discussion

  • SourceForge Support

    Hi,

    Thank you for letting us know.
    I have escalated this to our DevOps team to investigate further.

    Sincerely,

    SourceForge Support

     
  • M S

    M S - 2025-03-07

    Thanks - just as additional info:
    When trying with 'scp', it shows right now a bandwidth of ~ 25KB/s (!)

     
  • SourceForge Support

    Hello,

    Is this still an issue?
    Our team has been working on your report and we would like to have your feedback.

    Sincerely,
    SourceForge Support

     
  • M S

    M S - 2025-03-07

    Hello support team, unfortunately, it is still an issue.
    Please refer to the attached screenshot - still only ~42KB/s upload rate
    Thanks & regards - M

     
  • SourceForge Support

    Hi,

    Can you do a traceroute to frs.sourceforge.net
    To help our team look into this issue.

    Sincerely,
    SourceForge Support

     
  • M S

    M S - 2025-03-07

    root@spalona ~ # traceroute frs.sourceforge.net
    traceroute to frs.sourceforge.net (216.105.38.21), 30 hops max, 60 byte packets
    1 100.80.134.129 (100.80.134.129) 0.492 ms 0.441 ms 0.519 ms
    2 core32.hel1.hetzner.com (213.239.224.129) 0.315 ms 0.413 ms core31.hel1.hetzner.com (213.239.224.125) 0.362 ms
    3 * * *
    4 * * *
    5 core10.ams.hetzner.com (213.239.224.121) 27.264 ms core10.ams.hetzner.com (213.239.224.117) 27.256 ms core10.ams.hetzner.com (213.239.224.121) 27.229 ms
    6 * port-channel1.core1.ams1.he.net (184.104.198.118) 26.380 ms *
    7 * * *
    8 100ge0-72.core2.nyc5.he.net (184.104.195.165) 95.998 ms 96.493 ms 96.524 ms
    9 port-channel18.core3.ash1.he.net (184.104.195.161) 103.717 ms * 101.468 ms
    10 * * *
    11 port-channel10.core4.lax2.he.net (72.52.92.122) 204.946 ms * *
    12 lightedge-solutions.e0-31.switch2.lax3.he.net (184.105.154.77) 191.751 ms 188.310 ms 190.542 ms
    13 TE0-1-1-0-sndgcalwper01.as11320.net (216.243.211.27) 192.069 ms 194.216 ms TE0-0-1-0-sndgcalwper01.as11320.net (216.243.211.25) 195.277 ms
    14 host-74-211-243-216.lightedge.com (216.243.211.74) 245.422 ms 174.013 ms 174.058 ms
    15 host-34-211-243-216.lightedge.com (216.243.211.34) 218.532 ms 173.819 ms 187.788 ms
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *
    root@spalona ~ #

     
  • M S

    M S - 2025-03-07

    traceroute now also attached as screenshot

     
  • M S

    M S - 2025-03-07

    attachment

     
  • M S

    M S - 2025-03-08

    Dear support team,
    today, all seems to be "back to normal" - hence from my point of view, the ticket can be closed.
    Kind regards - Markus

     
  • SourceForge Support

    • status: open --> closed
     
  • SourceForge Support

    Hi,

    Thank you for your feedback
    With your issue resolved, this ticket will be closed.

    Sincerely,
    SourceForge Support

     

Log in to post a comment.

MongoDB Logo MongoDB