-
-
Notifications
You must be signed in to change notification settings - Fork 777
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] Not working after update to 1.23.1 #6088
Comments
I was able to load the /i/?c=update&a=checkInstall page and everything is green. It says PHP version is 8.2.7. It doesn't say the database version. |
The update page says " An update of FreshRSS is available (Version 1.19.2), but check permissions on /var/www/FreshRSS directory. HTTP server must have have write permission" |
The logs page loaded and it has some errors:
It also seems that after I updated the timestamp screwed up. The latest timestamps are as above. Previous to updating to the :latest docker branch the timestamps in the logs were correct. |
Probably similar to #6057 (comment)
|
I do see categories on the side panel. The first time I click "update feeds" the message "There are no feeds to update" immediately pops up. If I click it again the request times out with a "Bad gateway" response. If I try to add a new feed I sometimes get "Bad gateway" and sometimes get an error page that says "Error 403 - Forbidden You don’t have permission to access this page [CSRF]" /i/?c=error&rid=b5c11670fff07250 |
The timestamp of your log entry is a bit strange |
It must be a -1internally, which for a timestamp converted to date looks like 1969-12-31 15:59:59. I assume the -1 represents an error state internally somewhere. Any thoughts on what logs or configs I could look at to try to diagnose a bit more? |
My guess is that the maximum execution time of 30s has been too short for some of the automatic database updates. If you do not have an export, try to see whether a new export is working:
|
I didn't make a backup export before upgrading, but the command to export does successfully run. Is there a way to increase the maximum execution time? |
To get you back to a working state, as the export worked, you can try to:
|
I spun up a new docker container with empty data and extensions volumes and then imported the exported sqlite backup there. The command line seemed to work, and I see the feeds in the new freshrss endpoint. The experience seems about the same as before. Errors, and not allowing me to fetch new feeds and I can't update read status. The only message in the logs is
|
Strange timestamp you get there. If the import works and you get that message, it could be that the access rights on your SQLite file are not good. Try at least to restart the container once, and also double-check. |
Maybe it is an issue with the latest version on arm architecture? I did a clean install on my raspberry pi and just loading the start page I get frequent "Request Timeout" (that seem to happen immediately) and am only able to get through after multiple refreshes. |
I was able to get back to a working state by using the freshrss/freshrss:1.18.1-arm docker image. I will try using a more recent image later |
It would be interesting to test some more. One way is to build locally: freshrss:
image: freshrss/freshrss:latest
build:
# Pick #latest (stable release) or #edge (rolling release) or a specific release like #1.23.1
context: https://github.com/FreshRSS/FreshRSS.git#latest
# Pick Docker/Dockerfile for Debian-based image or Docker/Dockerfile-Alpine for Alpine-based image
dockerfile: Docker/Dockerfile-Alpine
... Trying both our Debian-based image ( |
What OS architecture do you run, more precisely? ( |
model name: ARMv7 Processor rev 3 (v7l) |
Would you have a chance to try the builds as I suggested? |
Not yet. I tried upgrading to the next release after my current (1.19.0-arm) but it has the same behavior of instability. I will try doing a build next. |
I think I set it up to build but got the same results with the same error message. Is standing up this docker compose file sufficient to have the underlying service built? Do I need to take other actions?
|
any news here? |
I deleted and did a clean install. When I try to import the backup exported by 1.18 into the latest I get this error: $ cli/import-sqlite-for-user.php --user joshua --filename data/users/joshua/joshua-20240508.sqlite --force-overwrite |
It sounds like kind is a new column that was introduced. Is there a way to make it default to something innocuous rather than blow up? https://github.com/FreshRSS/FreshRSS/blob/edge/app/Models/CategoryDAO.php#L227C1-L230 |
Thanks for the bug report @lelanophilus |
Did you try with our |
I don't think so, I created the docker container with freshrss/freshrss:latest as the image. |
If you can, just try the same with |
This attempt is with 1.23.2-dev. I think same error, though different spot maybe. PHP Fatal error: Uncaught PDOException: SQLSTATE[HY000]: General error: 1 no such column: kind in /var/www/FreshRSS/lib/Minz/Pdo.php:93 |
Import fixed with #6450 freshrss:
image: freshrss/freshrss:6450
build:
context: http://github.com/Alkarex/FreshRSS.git#fix-import
dockerfile: Docker/Dockerfile-Alpine
... |
That worked, thank you so much! |
Describe the bug
I was on the last freshrss/freshrss:arm release and upgraded to freshrss/freshrss:latest in docker. Now new feeds won't download and the console is very buggy. Trying to update read status doesn't persist after page refresh. Looking in the docker logs I see:
I did find https://github.com/FreshRSS/FreshRSS/blob/edge/lib/Minz/Request.php#L331 but couldn't really understand why that might be timing out.
Any suggestions for how this might be fixed?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
To be able to update feeds and refresh.
Environment information (please complete the following information):
Additional context
I upgraded to try to use the html/xpath scraping feed. I don't know if it was working properly before I tried to create an html/xpath feed but that feed never worked and when I try to delete it I can still see it show up in the "feeds with errors" view of the subscription management page.
The text was updated successfully, but these errors were encountered: