Ubuntu Metrics server is not accepting reports

[Tim Andersson]

gnome-initial-setup now prompts to send a report immediately, and when it does, it fails, I'll attach a screenshot in the comments. Even when I clicked "Don't send to ubuntu" or however it's phrased, I still encountered the error message pop up in the comments.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-initial-setup 46~alpha-2ubuntu1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 23 10:38:31 2024
InstallationDate: Installed on 2024-01-23 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SourcePackage: gnome-initial-setup
UpgradeStatus: No upgrade log present (probably fresh install)

[Tim Andersson (andersson123)]

(I'm also aware this could just be an issue with the metrics server, but I just wanted to report the bug to draw attention to the issue)

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2050884

[Brian Murray (brian-murray)]

Given that https://metrics.ubuntu.com isn't responding for me I suspect its a server issue.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[corrado venturini (corradoventu)]

??duplicate of https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2049670
and https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/2049596

[Tim Andersson (andersson123)]

Absolutely, definitely a server issue, also, I get the error popup even when I choose not to send metrics, which doesn't seem right.

[Tim Andersson (andersson123)]

And as Corrado pointed out, this is infact a duplicate. I'll mark it as such.

[Jeremy Bícha (jbicha)]

I think it is useful to use this issue to track the server issue and save 2049670 for the client issue in gnome-initial-setup.

[Tim Andersson (andersson123)]

Okay, sounds good :)

[corrado venturini (corradoventu)]

ubuntu-report continues to try to send data

Jan 25 11:18:27 corrado-n4-nn-0125 systemd[1165]: Started ubuntu-report.path - Pending report trigger for Ubuntu Report.
Jan 25 11:18:44 corrado-n4-nn-0125 systemd[1791]: Started ubuntu-report.path - Pending report trigger for Ubuntu Report.
Jan 25 11:18:44 corrado-n4-nn-0125 systemd[1791]: Started ubuntu-report.service - Ubuntu report sends pending metrics data.
Jan 25 11:18:54 corrado-n4-nn-0125 ubuntu-report[1812]: level=error msg="data were not delivered successfully to metrics server, retrying in 30s"
Jan 25 11:18:57 corrado-n4-nn-0125 systemd[1165]: Stopped ubuntu-report.path - Pending report trigger for Ubuntu Report.
Jan 25 11:19:34 corrado-n4-nn-0125 ubuntu-report[1812]: level=error msg="data were not delivered successfully to metrics server, retrying in 60s"
Jan 25 11:20:44 corrado-n4-nn-0125 ubuntu-report[1812]: level=error msg="data were not delivered successfully to metrics server, retrying in 120s"
Jan 25 11:22:54 corrado-n4-nn-0125 ubuntu-report[1812]: level=error msg="data were not delivered successfully to metrics server, retrying in 240s"
Jan 25 11:27:04 corrado-n4-nn-0125 ubuntu-report[1812]: level=error msg="data were not delivered successfully to metrics server, retrying in 480s"
Jan 25 11:35:14 corrado-n4-nn-0125 ubuntu-report[1812]: level=error msg="data were not delivered successfully to metrics server, retrying in 960s"
Jan 25 11:51:25 corrado-n4-nn-0125 ubuntu-report[1812]: level=error msg="data were not delivered successfully to metrics server, retrying in 1800s"
Jan 25 12:21:35 corrado-n4-nn-0125 ubuntu-report[1812]: level=error msg="data were not delivered successfully to metrics server, retrying in 1800s"

[Nathan Teodosio (nteodosio)]

https://salsa.debian.org/gnome-team/gnome-initial-setup/-/merge_requests/23

[Tim Andersson (andersson123)]

hi, we're still experiencing this just FYI, I've experienced it in every noble desktop install I've tested today

[Leó Kolbeinsson (leok)]

Confirm this no longer present in Ubuntu Noble Desktop daily ISO dated 20240410

[corrado venturini (corradoventu)]

after fix i see many messages about:
Apr 10 13:16:06 corrado-n9-nn-0410 systemd[1883]: Started ubuntu-report.path - Pending report trigger for Ubuntu Report.
Apr 10 13:16:17 corrado-n9-nn-0410 systemd[2530]: Started ubuntu-report.path - Pending report trigger for Ubuntu Report.
Apr 10 13:16:29 corrado-n9-nn-0410 systemd[1883]: Stopped ubuntu-report.path - Pending report trigger for Ubuntu Report.
Apr 10 13:18:50 corrado-n9-nn-0410 systemd[2530]: Stopped ubuntu-report.path - Pending report trigger for Ubuntu Report.
Apr 10 13:19:14 corrado-n9-nn-0410 systemd[1329]: Started ubuntu-report.path - Pending report trigger for Ubuntu Report.
Apr 10 13:19:34 corrado-n9-nn-0410 systemd[1877]: Started ubuntu-report.path - Pending report trigger for Ubuntu Report.
Apr 10 13:19:46 corrado-n9-nn-0410 systemd[1329]: Stopped ubuntu-report.path - Pending report trigger for Ubuntu Report.
Apr 10 13:21:47 corrado-n9-nn-0410 systemd[1877]: Stopped ubuntu-report.path - Pending report trigger for Ubuntu Report.
Apr 10 14:08:33 corrado-n9-nn-0410 systemd[1344]: Started ubuntu-report.path - Pending report trigger for Ubuntu Report.
Apr 10 14:08:45 corrado-n9-nn-0410 systemd[1897]: Started ubuntu-report.path - Pending report trigger for Ubuntu Report.
Apr 10 14:08:57 corrado-n9-nn-0410 systemd[1344]: Stopped ubuntu-report.path - Pending report trigger for Ubuntu Report.

[Nathan Teodosio (nteodosio)]

Corrado, the released fix was only for the consumer (gnome-initial-setup).

I think that, if you chose to send system information to Canonical and it failed, which is at the moment guaranteed to happen because the service is not up yet, ubuntu-report schedules a new attempt to send the report.

If that is ad infinitum or spams your system logs, please file a new bug against ubuntu-report[1].

[1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+filebug.