Chromium upload failure (regular ftp)

Asked by Rob Savoury

Hello, once again the issue with large uploads is happening. Similar issues were reported by me in Feburary [1] and March [2] of this year. After approximately 10 attempts at uploading the latest Chromium in the past two days I am now reporting the issue.

Here is the terminal output of the latest attempted upload, with UTC timestamps:

2024-05-25T02:21:13,454531534+00:00
D: Splitting host argument out of ppa:savos.
D: Setting host argument.
Checking signature on .changes
gpg: ../chromium-browser-125.0.6422.112-0ubuntu0.18.04.1sav0_result/chromium-browser_125.0.6422.112-0ubuntu0.18.04.1sav0_source.changes: Valid signature from 2E2CC42845C9AB64
Checking signature on .dsc
gpg: ../chromium-browser-125.0.6422.112-0ubuntu0.18.04.1sav0_result/chromium-browser_125.0.6422.112-0ubuntu0.18.04.1sav0.dsc: Valid signature from 2E2CC42845C9AB64
Uploading to ppa (via ftp to ppa.launchpad.net):
  Uploading chromium-browser_125.0.6422.112-0ubuntu0.18.04.1sav0.dsc: done.
  Uploading chromium-browser_125.0.6422.112.orig.tar.xz: 3385287k/3385288k
2024-05-25T03:07:46,344069921+00:00

As can be seen the upload hangs at completion, perhaps a timeout issue again with unauthenticated (non-sftp) uploads?

[1] https://answers.launchpad.net/launchpad/+question/709449
[2] https://answers.launchpad.net/launchpad/+question/709488

Question information

Language:
English Edit question
Status:
Open
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Rob Savoury (savoury1) said :
#1

Days later and I am still unable to upload the latest Chromium, and I have made probably 20 further attempts since reporting this bug. Here is the latest terminal output:

2024-05-27T20:25:41,150883914+00:00
D: Splitting host argument out of ppa:savos.
D: Setting host argument.
Checking signature on .changes
gpg: ../chromium-browser-125.0.6422.112-0ubuntu0.18.04.1sav0_result/chromium-browser_125.0.6422.112-0ubuntu0.18.04.1sav0_source.changes: Valid signature from 2E2CC42845C9AB64
Checking signature on .dsc
gpg: ../chromium-browser-125.0.6422.112-0ubuntu0.18.04.1sav0_result/chromium-browser_125.0.6422.112-0ubuntu0.18.04.1sav0.dsc: Valid signature from 2E2CC42845C9AB64
Uploading to ppa (via ftp to ppa.launchpad.net):
  Uploading chromium-browser_125.0.6422.112-0ubuntu0.18.04.1sav0.dsc: done.
  Uploading chromium-browser_125.0.6422.112.orig.tar.xz: 3385287k/3385288k
2024-05-27T20:59:56,747847475+00:00

This issue is preventing me from updating Chromium with fixes for a number of high severity security vulnerabilities for my many PPA users. I would greatly appreciate a response and a fix as soon as possible. Thank you.

Revision history for this message
Guruprasad (lgp171188) said (last edit ):
#2

Hi Rob, thank you for reaching out. I am sorry for the issues that you have been facing while trying to upload a chromium package. While we investigate this, can you try uploading using authenticated sftp so that you can release package updates without more delays? I am suggesting this solely based on the information you had shared with us the previous times that authenticated sftp worked but did so very slowly in comparison to plain FTP.

Revision history for this message
Rob Savoury (savoury1) said :
#3

Hi, thanks for the response. Although I did not mention it in this bug report I did also try the upload a number of times with sftp, and it also failed a number of times trying that method. Due this bug report being about regular ftp I didn't think to include the terminal output from the failed sftp upload attempts, but it happened several times after several hours of uploading. An error was given in the terminal along the lines of failure to connect/authenticate to the remote host.

However, finally I did manage to get the upload to succeed using sftp last night. It took about 10 hours on my Internet connection using this method. Given that the issue as reported was with unauthenticated ftp uploading I'll leave this bug report open for now, until hopefully some idea about what's causing the problem is revealed.

Revision history for this message
Rob Savoury (savoury1) said :
#4

Terminal output from another regular ftp upload failure today:

2024-06-01T11:32:18,416306658+00:00
D: Splitting host argument out of ppa:savos.
D: Setting host argument.
Checking signature on .changes
gpg: ../chromium-browser-125.0.6422.141-0ubuntu0.18.04.1sav0_result/chromium-browser_125.0.6422.141-0ubuntu0.18.04.1sav0_source.changes: Valid signature from 2E2CC42845C9AB64
Checking signature on .dsc
gpg: ../chromium-browser-125.0.6422.141-0ubuntu0.18.04.1sav0_result/chromium-browser_125.0.6422.141-0ubuntu0.18.04.1sav0.dsc: Valid signature from 2E2CC42845C9AB64
Uploading to ppa (via ftp to ppa.launchpad.net):
  Uploading chromium-browser_125.0.6422.141-0ubuntu0.18.04.1sav0.dsc: done.
  Uploading chromium-browser_125.0.6422.141.orig.tar.xz: 3389241k/3389242k
2024-06-01T12:19:21,759378855+00:00

So I will once again try with sftp and if it doesn't work I will this time include the terminal output.

Revision history for this message
Simone Pelosi (pelpsi) said :
#5

Hey Rob! Sorry for the late reply, is this still an issue?

Revision history for this message
Rob Savoury (savoury1) said :
#6

Hi, thanks for the response. Yes, very large uploads are still failing for me via regular ftp. Here's the latest terminal output wrapped with UTC timestamps:

2024-06-16T04:25:21,110014072+00:00
D: Splitting host argument out of ppa:savos.
D: Setting host argument.
Checking signature on .changes
gpg: ../chromium-browser-126.0.6478.61-0ubuntu0.18.04.1sav0_result/chromium-browser_126.0.6478.61-0ubuntu0.18.04.1sav0_source.changes: Valid signature from 2E2CC42845C9AB64
Checking signature on .dsc
gpg: ../chromium-browser-126.0.6478.61-0ubuntu0.18.04.1sav0_result/chromium-browser_126.0.6478.61-0ubuntu0.18.04.1sav0.dsc: Valid signature from 2E2CC42845C9AB64
Uploading to ppa (via ftp to ppa.launchpad.net):
  Uploading chromium-browser_126.0.6478.61-0ubuntu0.18.04.1sav0.dsc: done.
  Uploading chromium-browser_126.0.6478.61.orig.tar.xz: 4067457k/4067458k
2024-06-16T05:21:40,246281464+00:00

There seems to be some kind of timeout happening again, as with my previous reports of this issue with very large uploads. Overnight I will try sftp and see if that works. It has definitely been more reliable in general, only occasionally failing. But it's extremely slow to do sftp for such large uploads, ie. 10+ hours for me with these Chromium source files.

Can you help with this problem?

Provide an answer of your own, or ask Rob Savoury for more information if necessary.

To post a message you must log in.