You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The below error happens almost every 2nd day and at around 12:30-13:30 my timezone, and then automatically corrects itself after around 70-90 minutes from the timeline (around 14:40-15:00).
Fatal error: Uncaught Error: Call to a member function bindParam() on bool in /PATH/feeds/app/Models/FeedDAO.php:293
Stack trace:
#0 /PATH/feeds/app/Models/Entry.php(340): FreshRSS_FeedDAO->searchById(29)
#1 /PATH/feeds/app/views/index/normal.phtml(43): FreshRSS_Entry->feed()
#2 /PATH/feeds/lib/Minz/View.php(88): include('/PATH/...')
#3 /PATH/feeds/lib/Minz/View.php(110): Minz_View->includeFile('/views/index/no...')
#4 /PATH/feeds/app/layout/layout.phtml(69): Minz_View->render()
#5 /PATH/feeds/lib/Minz/View.php(88): include('/PATH/...')
#6 /PATH/feeds/lib/Minz/View.php(101): Minz_View->includeFile('/layout/layout....')
#7 /PATH/feeds/lib/Minz/View.php(68): Minz_View->buildLayout()
#8 /PATH/feeds/lib/Minz/Dispatcher.php(56): Minz_View->build()
#9 /PATH/feeds/lib/Minz/FrontController.php(58): Minz_Dispatcher->run()
#10 /PATH/feeds/p/i/index.php(57): Minz_FrontController->run()
#11 {main} thrown in **/PATH/feeds/app/Models/FeedDAO.php on line 293**
To Reproduce
Steps to reproduce the behavior:
No idea how to reproduce, as this happens automatically without me doing anything.
Expected behavior
This error should not happen and my feeds instance and feeds should show, instead I get just this error and no feeds show up.
Screenshots
Environment information (please complete the following information):
The text was updated successfully, but these errors were encountered:
vdbhb59
changed the title
[BUG] Unusual Fata Error, happening almost every 2nd day
[BUG] Unusual Fatal Error, happening almost every 2nd day
May 21, 2023
It it always the same error you get? And is it only when you navigate to a given feed or do you also get an exception when you try to access a category or the main view?
It looks like a temporary database problem.
If you can, try to use our current rolling release 1.21.1-dev, which has changed some related handling of errors.
It it always the same error you get? And is it only when you navigate to a given feed or do you also get an exception when you try to access a category or the main view? It looks like a temporary database problem. If you can, try to use our current rolling release 1.21.1-dev, which has changed some related handling of errors.
Hi Mate,
Sorry for the late reply.
I get the same error every time, same path, same file, same line.
I get it randomly, does not matter if it is main view, or a feed, or even a category. It just throws this same error randomly.
Temp Database Error: Probably.
Rolling release: How do I set it? I have a file "/data/config.php", where the value is: 'environment' => 'development', and something under it as "Salt" (I presume is some sort of encrypted connection value), which I am not sharing here. But how do I switch to the current rolling release, directly from the app itself, please? Cause even if I set it to "production", there is "Blast! No update to apply". Sorry for being a novice mate.
Describe the bug
The below error happens almost every 2nd day and at around 12:30-13:30 my timezone, and then automatically corrects itself after around 70-90 minutes from the timeline (around 14:40-15:00).
To Reproduce
Steps to reproduce the behavior:
No idea how to reproduce, as this happens automatically without me doing anything.
Expected behavior
This error should not happen and my feeds instance and feeds should show, instead I get just this error and no feeds show up.
Screenshots
![image](https://private-user-images.githubusercontent.com/60728004/239728005-3fb8094c-43b0-4345-90c2-ed46ec58021b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTg3NzkxNDcsIm5iZiI6MTcxODc3ODg0NywicGF0aCI6Ii82MDcyODAwNC8yMzk3MjgwMDUtM2ZiODA5NGMtNDNiMC00MzQ1LTkwYzItZWQ0NmVjNTgwMjFiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjE5VDA2MzQwN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWY2Y2E2YjFkNzQ4MTRmNDc2ZmU2ZGNjNGNjN2E1OWY0NTZiNzc2OWEyNjkyZTRiM2U1YmRmNWNlMzgzYWJmMjUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.zYrEWtOzUDruOILqg2RyQigaBD8JMwGRVFsaFeMn8s8)
Environment information (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: