Checksum mismatch in .gitlab_kas_secret post-install & gitlab-ctl reconfigure

4. joulukuuta 2021 klo 12.57
Sijainti: Vianhallintajärjestelmät: Gitlab
Avainsanat: Debian, Ubuntu

Summary

I’m running debsums -c daily, hoping to catch file corruption and/or other abnormalities early. (The Debian package even provides a pre-made cronjob for this task.)

debsums -c gitlab-ce reports .gitlab_kas_secret as deviating from the provided md5sum.

Steps to reproduce

  1. apt install gitlab-ce
  2. vi /etc/gitlab/gitlab.rb # set external URL
  3. gitlab-ctl reconfigure
  4. debsums -c gitlab-ce

What is the current bug behavior?

# debsums -c gitlab-ce
/opt/gitlab/embedded/service/gitlab-rails/.gitlab_kas_secret

What is the expected correct behavior?

# debsums -c gitlab-ce
#

Details of package version

Provide the package version installation details
ii  gitlab-ce      14.5.1-ce.0  amd64        GitLab Community Edition (including NGINX, Postgres, Redis)

Environment details

  • Operating System: Ubuntu 20.04
  • Installation Target, remove incorrect values:
    • VM
  • Installation Type, remove incorrect values:
    • New Installation
  • Is there any other software running on the machine: plenty
  • Is this a single or multiple node installation? single

Configuration details

Provide the relevant sections of `/etc/gitlab/gitlab.rb`
external_url 'http://localhost'

Related issues

#2635 is basically the same, but I’ve never seen debsums complain about schema.rb.

Vastaa viestiin sen kontekstissa (Gitlab)

4.4.0: snapshots broken when netcam_high_url used with recommended width and height values

3. joulukuuta 2021 klo 16.45
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Motion, Ubuntu

  1. Reviewed guide and contributing documents? Yes
  2. version 4.4.0
  3. installed as a package or compiled from sources: deb
  4. standalone or part of third party: standalone
  5. video stream source: net cam
  6. hardware: x86 (amd64)
  7. operating system: Ubuntu 20.04

Short description

In Motion 4.4.0, using recommended values of width and height results in broken snapshots, when netcam_high_url is used. Either the warning about using a different resolution is incorrect, or the creation of snapshots breaks when width and height are set so as to not cause a warning on startup.

Background

I have a 1080p camera (a TP-Link Tapo C100) with a 360p substream, so I’ve specied both URLs as follows:

netcam_url "rtsp://192.168.1.206/stream2"                                        
netcam_high_url "rtsp://192.168.1.206/stream1"

I’ve set up snapshots to occur with snapshot_interval = 60.

If I set width and height based on the main stream (1920×1080), Motion starts up with a warning:

netcam_rtsp_ntc: The network camera is sending pictures in a different
netcam_rtsp_ntc: size than specified in the configuration file.
netcam_rtsp_ntc: The picture is being transcoded into the size 
netcam_rtsp_ntc: requested in the configuration.  If possible change
netcam_rtsp_ntc: netcam or configuration to indicate the same size
netcam_rtsp_ntc: to possibly lower CPU usage.
netcam_rtsp_ntc: Netcam: 640 x 360 => Config: 1920 x 1080

This implies I should set width and height based on the lower resolution stream, so I’ve done that, and the warning goes away.

With Motion 4.3.2, the snapshots were saved as I would expect, albeit of course now in the lower resolution (360p), whereas I’d prefer them in the full 1080p.

After upgrading to 4.4.0, the snapshots are still 360p, but now their content is garbled and green:

01-20211203161040-snapshot

I haven’t looked at the code, but what this looks like to me is as if Motion is now using the high resolution URL for the image data, but the lower resolution dimensions, and the resulting file is a (broken) crop of the full resolution image. Indeed, if I set width and height based on the full stream (i.e. back to 1920×1080), the snapshots now appear the full resolution and without corruption.

Pictures from detected motion (picture_output) do not appear to be affected, i.e. they are saved in the correct 1080p resolution and look fine, regardless of the values of width and height. Video output likewise appears in the higher resolution, as I would expect.

Here’s a minimal configuration that reproduces this issue for me, minus netcam_userpass.

log_level 8

target_dir "/home/jani/tmp"

netcam_url "rtsp://192.168.1.206/stream2"
netcam_high_url "rtsp://192.168.1.206/stream1"

netcam_params rtsp_transport=tcp
netcam_high_params rtsp_transport=tcp

width 640
height 360

snapshot_interval 10

Vastaa viestiin sen kontekstissa (Github)

Valoboksi naksuttaa punaisen valon tahtia

15. marraskuuta 2021 klo 18.13
Sijainti: Muut: Oulun Palautepalvelu
Avainsanat: liikenne, Taskila, Toppila, turvallisuus

Taskilan puoleinen jalankulkuvaloboksi naksuttaa punaisen valon (hitaampaa) tahtia vaikka valot ovat vihreät. (Keskipylvään boksi ja Toppilan puoleinen boksi naksuttavat oikein.)

Vastaa viestiin sen kontekstissa (Oulun Palautepalvelu)

Hyllyn halvin tätä kokoa, ei valittamista

12. marraskuuta 2021 klo 19.17
Sijainti: Muut: Prisma
Avainsanat: House, kuluttajuus

Ollut käytössä lähes päivittäin ostamisesta lähtien (tähän mennessä kolmisen viikkoa), ja hyvin on toiminut, eikä kulumisen merkkejä ainakaan vielä havaittavissa. Vältän tietysti pohjan raapimista metallivälineillä, ja pesen ja kuivaan pannun joka käytön jälkeen. Paistan pääasiassa kasviksia, ja lisään pohjalle paistamista varten pikkuisen öljyä, vaikka tuskin tarttuisi ilmankaan.

Vastaa viestiin sen kontekstissa (Prisma)

Tämän takia on aina kynsileikkuri avainnipussa.

12. marraskuuta 2021 klo 15.32
Sijainti: Muut: reddit

Tämän takia on aina kynsileikkuri avainnipussa.

Vastaa viestiin sen kontekstissa (reddit)

Ootte ihania! (*^‿^*)

29. lokakuuta 2021 klo 13.58
Sijainti: Videosivustot: YouTube
Avainsanat: Anne Liljeström, Jari Mäkinen, Ursa

Ootte ihania! (*^‿^*)

Vastaa viestiin sen kontekstissa (YouTube)

New releases not published on Github

26. lokakuuta 2021 klo 11.18
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Github, Mattermost

Summary

Release v1.47.2 was mentioned in another issue’s comments, and Play Store version has indeed been updated, but that release is missing from Github releases.

Steps to reproduce

Open Github releases page for the project.

Expected behavior

Find release v.1.47.2 (or later).

Observed behavior (that appears unintentional)

The current latest release on Github is 1.47.0.

Possible fixes

I don’t know if it’s related, but v.1.47.0 has been tagged ”changeme” instead of the usual vX.Y.Z pattern.

Vastaa viestiin sen kontekstissa (Github)

Opening the hamburger menu works in 95.0a1; closing still partly broken

22. lokakuuta 2021 klo 19.57
Sijainti: Vianhallintajärjestelmät: Mozilla Bugzilla
Avainsanat: Firefox

I tested 95.0a1 (Nightly), and opening the hamburger menu (using the steps I outlined above) works now.

Closing it is still partly broken though, as clicking on the menu button doesn’t close the menu; I think that is bug 1694514.

For a workaround, clicking outside the menu (and the menu button) does close the menu.

Vastaa viestiin sen kontekstissa (Mozilla Bugzilla)

Rengaskriittiset

22. lokakuuta 2021 klo 15.33
Sijainti: Muut: reddit
Avainsanat: turvallisuus

Emme ole rengasvastaisia, vaan *rengaskriittisiä*.

Vastaa viestiin sen kontekstissa (reddit)

I can appreciate avoiding extra trouble for others

6. lokakuuta 2021 klo 13.16
Sijainti: Muut: kieli

Okay, I can appreciate avoiding extra trouble for others, and it’s certainly easier for me to add the workaround translation for just this one case. I’ve now done that (with your suggestion, which was probably as good as this can be).

%{month_name} %{year} would work better for Finnish, as that would allow the month name to be inflected apart from the year (which is how the current accepted translation of this string was intended to work). OTOH, the Finnish way a ”month name + year number” combination in inflected in most, if not all (relevant) cases is like that: add a suffix to the month name, leave the year number as-is. Without workarounds, %{month_year} generally only works for the nominative case.

Vastaa viestiin sen kontekstissa (kieli)

« Uudempia - Vanhempia »