Error "kitinerary-extractor: not found"

Hi,

this morning I’ve clicked on updating the Mail app to 5.1.0.

After a while I have seen this message in the /dev/stdout:

sh: /var/www/html/custom_apps/mail/vendor/nextcloud/kitinerary-bin/src/../bin/kitinerary-extractor: not found
sh: flatpak: not found
sh: kitinerary-extractor: not found

40 minutes before I’ve found this error 2 times in the log:

Exception while executing repair step Insert background jobs for all accounts
...
"exception": {
        "Exception": "BadFunctionCallException",
        "Message": "debug is not a valid attribute",
        "Code": 0,
        "Trace": [
            {
                "file": "/var/www/html/lib/public/AppFramework/Db/Entity.php",
                "line": 59,
                "function": "setter",
                "class": "OCP\\AppFramework\\Db\\Entity",
                "type": "->",
                "args": [
                    "debug",
                    [
                        false
                    ]
                ]
            },
...

The Mail app seems to be working.

Is it save to ignore it?

BR SMF

System:
Self hosted, containerized around the official docker image, not the AIO solution.
NC 31.0.5, Postgresql 17.4, Redis 7.2, Nginx 1.28, Talk HPB AIO 2.0.2
Almalinux 9.6, Podman 5.4, updated this morning

hey @mf-in-mun

first thing that came to my mind when I read your errorlog

is: try another level on logs.. debug is the most chatty one.
other than that: try restarting your system completely or reboot (the good old Windows-way). And last but not least try Github issue-tracker and see if something similar was reported, already.

And update from your side will be appreciated

Hi @JimmyKater,

thank you very much for your reply :+1:.

Loglevel has been 2 (default) nextcloud:/var/www/html$ php occ config:system:get loglevel 2 for quite a while.

In the meantime there was an entry in Github

Luckily my Nextcloud doesn’t die.

I’ve restarted my Pod and will check the logs.
If there is anything new I will come back.

BR

this will solve the problem on here since there seems nothing left to do for us about this bug. Hence I’m gonna close this topic. If any more questions will turn up pls don’t hesitate to post them under this bug on GH.
Congratulations to the solution-checkmark you received :slight_smile:

This topic was automatically closed after 16 hours. New replies are no longer allowed.