Firefly III
-
Support guidelines
I've found a bug and checked that ...
DescriptionThis one's an odd one. I've been using Firefly successfully for months. I haven't required any updates to the background docker or OS for roughly 2 months and have been happily trans actioning my entire life. After 5 successful uses of the importer with CSV files, I received this error error screen (also see attached screenshot): Could not poll the database: SQLSTATE[HY000] [2006] MySQL server has gone away (Connection: mysql, SQL: select Firefly was unresponsive. A reboot appeared to clear it up, as I had multiple containers all go down at the same time. My file paths also disappeared, but returned on reboot. I proceeded to login to firefly and see that all was well and working again. After checking one of the files I had uploaded without error messages, this appeared:
So after the first error, firefly was no longer saving attachments. I checked the attachments I had added prior to the error and they are present in the storage folder. Attachments I added after the error, show as if they are present in the attachments section on the transaction page, and link to the url expected, but were never uploaded by firefly. I wasn't able to get logs for adding of those files because I wasn't aware the issue had occurred. After turning debug mode on, the inability to add files solved itself. After turning debug off, the issue has not resumed. Debug informationDebug information generated at 2024-05-04 22:41:20 for Firefly III version v6.1.15.
Expected behaviourAttachments showing on transactions page without error message are expected to have been uploaded. Steps to reproduceError is reproducible only for the files that have entries but that were never added to the /storage folder. Additional infoI can provide the detailed debug logs on request but they contain sensitive information so I would like to not post on the issue. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
|
Hey, thanks for opening an issue. So, is this still happening or..? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, |
Beta Was this translation helpful? Give feedback.
-
|
Mmm, indeed. Send me the logs at [email protected]. I may not be able to find anything but who knows! |
Beta Was this translation helpful? Give feedback.
-
|
Sent. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
I seem to have determined the issue. The sata cable to the appdata folder was slightly jiggled out of the port. Just enough to be causing computer wide issues and odd errors, some files were functioning completely normally and some were disappearing. I believe firefly was attempting to upload documents into a section of the drive that was getting lost data packets. SMART showing data packet loss errors equivalent to the number of attachments that I lost. Seems it was a hardware error and not related to firefly. |
Beta Was this translation helpful? Give feedback.
-
|
Also want to say, after deleting the error'ing files from the transactions, the feature that redirects the attachment URL to the transaction it was originally attached to made it a breeze to determine which files went where and correct everything. |
Beta Was this translation helpful? Give feedback.
-
|
What a strangely beautiful error, and kudos for finding the issue! A jiggly port is not yet on my list, hah! Also: glad to be of service in regard to the redirect. I knew it would be helpful one day! |
Beta Was this translation helpful? Give feedback.
I seem to have determined the issue. The sata cable to the appdata folder was slightly jiggled out of the port. Just enough to be causing computer wide issues and odd errors, some files were functioning completely normally and some were disappearing. I believe firefly was attempting to upload documents into a section of the drive that was getting lost data packets. SMART showing data packet loss errors equivalent to the number of attachments that I lost. Seems it was a hardware error and not related to firefly.