-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: "Unable to generate a URL for the named route" messages with every update #43910
Comments
These all appear to be pre-update (they're from v28.0.2). You're seeing these because your Do they stop after the update is successful? Are those apps functioning (e.g. photos, maps, keeweb, files, etc)? |
Yes, they are all working. I get these messages with every update I start, like today, when I updated from v28.0.2 to v28.0.3 |
I get this message after successfully (or so it seems) upgrading manually to 29.0.1, except it is for many applications -- which don't work, consequently:
Should I raise a new ticket for this? |
@mayonezo This may just be a PHP opcache caching matter. The safest thing to do is to restart mod_php/fpm after an upgrade. What method, precisely, are you using to upgrade Nextcloud? Also, what are your PHP's web/fpm @cmigliorini Same question to you. |
Same issue after upgrade to 29.0.1 Opcache values were configured as specified by former documentation and not an issue before. A restart of... well eventually just the entire system, so I can't miss anything, didn't help either. |
Oh, my applications aeem to work though. |
Commented out -- default.
As for restarting, I did restart php/fpm several times -- in fact I upgraded from 8.1 to 8.2 then 8.3 just in case (other issue I had where that seemed relevant to at least try, since we could not find any reasonable explanation). Only thing I'm yet to try is to restart memcache and the bloody server :) |
Won't work, have done that, just in case I missed a service. |
restarting memcache did not help. Also you asked: I first upgraded to 28.0.6.1 through the web updater, then ran into #45491, so I upgraded manually -- downloaded the zip from the URL offered by the web updater, then went through the f... manual :). It worked, then Memories required that I upgraded Posgres to 14, which I did. But I'm still having this issue... |
Funny thing: it first concerned 4 apps, none of them would actually be accessible. Now only Tasks and Memories are inaccessible and I only get the message for them. No warning, no console message, no error, no redirect. Also I realize that I'm spamming this ticket which does not exactly applies to my case (my 29.0.1 works but for these messages -- and Memories but that might be irrelevant). Before I shut up until requested to talk: I verified (browser devtools, logger app) that every time the logger polls for new entries, I get several of these (Info) messages for both apps (Tasks, Memories). So it's definitely the backend trying to find routes for apps and failing to do so. |
Disabling "fulltextsearch" then reenabling it solved the issue. Don't know if that works for @mayonezo @EnderArchery ? |
It seemed to work for a view seconds but... no, they came back |
Indeed, I wrote too fast. Maybe this: #45223 (comment), will try later |
It was established the cause is -> nextcloud/fulltextsearch#842. Not a Nextcloud Server issue. |
opcache.validate_timestamps=1 is commented out and I think you did not quite finish your answer? What do I simply need?
|
I don't have fulltextsearch installed.
|
Bug description
I get a bunch of these errors with every update:
Steps to reproduce
Expected behavior
No error messages.
Installation method
Manual
Nextcloud Server version
28.0.3
Operating system
Debian
PHP engine version
8.2
Web server
Apache
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
update
Are you using the Nextcloud Server Encryption module?
No
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: