nextcloud / nextcloud/mail

GLIBC_2.33 not found

Open
#7,603 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug regression
Dominant language
JavaScript
Stars
1k
Forks
348
Avg merge
12h 28m
Merged PRs (30d)
91

Description

Steps to reproduce
  1. setup fresh install of dockered NextCloud latest version fpm edition
  2. install mail app
  3. connect mail app to mail server
  4. get mails
  5. read Nextcloud Logs
Expected behavior

No error

Actual behavior

[15-Nov-2022 20:21:30] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it
/var/www/html/custom_apps/mail/vendor/christophwurst/kitinerary-bin/src/../bin/kitinerary-extractor: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /var/www/html/custom_apps/mail/vendor/christophwurst/kitinerary-bin/src/../bin/kitinerary-extractor)
sh: 1: flatpak: not found
sh: 1: kitinerary-extractor: not found

Mail app version

2.1.1

Mailserver or service

docker mailserver

Operating system

Dockered Nextcloud 25.0.1-fpm

PHP engine version

PHP 8.1

Web server

Nginx

Database

MariaDB

Additional info

whenever I open mail app I get [15-Nov-2022 20:21:30] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it.
and then glibc error

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure with the Dockered Nextcloud 25.0.1-fpm setup, Mail app 2.1.1, and the reported mail workflow. Inspect the kitinerary-extractor path under custom_apps/mail/vendor/christophwurst/kitinerary-bin and the Nextcloud logs; done means the GLIBC_2.33, flatpak, and extractor errors no longer occur when opening or reading mail.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, linux, mariadb, nginx, php
Domain
backend, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.