After upgrade from 15.11.5 to 16.0,GitLab CE down, cpu 100%

General
21

In my case there is Active Directory integration and the LDAP “connection string” to the AD contains an OU (“Organisational Unit”) with an Umlaut.

I’ve now renamed the OU in our Active Directory to not contain an Umlaut anymore.

This Umlaut OU worked flawlessly with GitLab since several years; V 16 broke it.

22

@iwalker : for our configuration, it was here :

gitlab_rails['ldap_servers'] = YAML.load <<-'EOS' # remember to close this block with 'EOS' below
  # [...]
  label: 'LDAP académique'
  # [...]
1 Like
23

we have an “é” in login button label. guess we could replace it with é I’ll try that tonight

1 Like
24

oups doesn’t show in html… replace with “and eacute ;”

25

Could be good to report it as an issue with Gitlab - especially since it used to work fine in previous versions. Could just be a minor regression that needs to be fixed to add that support back in.

2 Likes
26

for us it was a “§” character in an automatically generated password for ldap binding.

1 Like
27

For us it was a “ü” and a “ö” in a label for open-id-connect. This maxed out 16 vCPUs and 32GB of RAM resulting in a non-availability of a Gitlab EE system at our university.

Worked flawlessly with Gitlab v15 - please fix.

28

OK, I’ve created an issue:

Hopefully I did not make too many mistakes when creating the issue. Feedback welcome.

4 Likes
29

Disable ldap and all is well :slight_smile:

Снимок экрана 2023-05-24 132713
Снимок экрана 2023-05-24 1327131904×674 36.7 KB

1 Like
30

It’s been over 24 hours but the cpu is still 100%. I also did the security update. There is no change. The application is getting errors in the interface. For example; on board, when issues are opened

image_2023-05-24_100458039
image_2023-05-24_1004580392111×160 7.79 KB

image_2023-05-24_100532268
image_2023-05-24_100532268863×151 7.43 KB

1 Like
32

Check your config file with the following command:

grep --color='auto' -P -n "[\x80-\xFF]" /etc/gitlab/gitlab.rb
remove/replace all found characters

1 Like
33

Here’s a workaround. Set this in /etc/gitlab/gitlab.rb and run gitlab-ctl reconfigure:

gitlab_rails['env'] = {
  'LANG' => 'C.UTF-8'
}

A fix is in Fix Sidekiq crash when gitlab.yml contains UTF-8 characters (!121782) · Merge requests · GitLab.org / GitLab · GitLab.

7 Likes
34

Thanks a lot, Stan!

More debugging insights in rails configuration_file encoding error (#412767) · Issues · GitLab.org / GitLab · GitLab

FYI, Non-ASCII characters (like German Umlauts) in gitlab.rb makes V 16 unusuable (#412832) · Issues · GitLab.org / GitLab · GitLab was closed as duplicate.

2 Likes
35

Your solution worked!! Thanks a lot! :grinning:

1 Like
36

Hey,
Here is a nifty tool to check the upgrade path: Upgrade Path
As far as I saw, you have to first update to 15.11.6, the you can go to V16.

37

This also worked for me. It brought our VM to an extremely unresponsive standstill for 24 hours.

Until the fix is in place I suggest putting this fix somewhere in the release notes, as I only came across this by chance from a Reddit search.

38

FYI, fix has been backported, and released in 16.0.2: GitLab Security Release: 16.0.2, 15.11.7, and 15.10.8 | GitLab

1 Like