-
-
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] Database access not working for cron script #5770
Comments
Running it manually in the container works fine: root@freshrss-8477cdcbbc-9lwt7:/var/www/FreshRSS# . /var/www/FreshRSS/Docker/env.txt; \
su www-data -s /bin/sh -c 'php /var/www/FreshRSS/app/actualize_script.php' \
2>> /proc/1/fd/2 > /tmp/FreshRSS.log
root@freshrss-8477cdcbbc-9lwt7:/var/www/FreshRSS# cat /tmp/FreshRSS.log
Results:
yaleman OK
End. (And there's fresh updates in my feed) |
Alkarex
added a commit
to Alkarex/FreshRSS
that referenced
this issue
Oct 29, 2023
fix FreshRSS#5770 Note, the syntax complying with https://www.shellcheck.net/wiki/SC2002 does not seem to work in ash / Alpine
I have made a patch #5772 |
Alkarex
added a commit
that referenced
this issue
Oct 29, 2023
fix #5770 Note, the syntax complying with https://www.shellcheck.net/wiki/SC2002 does not seem to work in ash / Alpine
Merged. Tests of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Feeds are not updating and this error appears in the logs:
I recently upgraded to 1.22.0 and migrated from sqlite to postgres. Reading and marking existing posts read works, but the cron script is throwing errors about being unable to connect to the database:
And no updates are happening to feeds since the upgrade - until I exec into the container and run the actualize script manually.
To Reproduce
Steps to reproduce the behavior:
Using the following docker container:
Config db section:
The environment variables are confirmed to be working otherwise no data would appear - but the reader functionality and marking them read works.
Expected behavior
Feeds to be updated automatically with the cron timer.
Screenshots
n/a
Environment information (please complete the following information):
Additional context
The error would indicate that it's somehow loading the configuration but not getting the environment variables from the container? They need to come from there because it's running in kubernetes and are dynamically set on startup to point at the DB.
The text was updated successfully, but these errors were encountered: