-
Notifications
You must be signed in to change notification settings - Fork 217
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
FPP slow upload - CRASH #5073
Comments
What's the date on that ci? There's a Dec 9th version, but seems to be just as slow. |
December 12. https://github.com/MartinMueller2003/ESPixelStick/actions/runs/12304517834 I just tried the latest CI with the same result. Xlights crashed 5 minutes into the upload. At the 5 minute mark, my sequence was only about 35% uploaded. (Dig-Octa, 2400 pixels) |
The crash dumps seems to point to a meteor effect. It appears the upload was finished? Says rendercache - wonder if you can try disabling that. Cant see how this log relates to an fpp connect however.
|
Sorry, I uploaded the wrong log. The logs are new to me. I ran it again. Here's the new log. https://drive.google.com/file/d/1hZ-EnIZDdMz6xwH3E6Hl0Kar8ZPQKRlR/view?usp=drive_link |
I managed to isolate a controller and one sequence to better show the crash. I started FPP upload at 07:39:00. Xlights Crashed at 07:44:10, FIVE MINUTES into the upload. On this firmware the upload was about 70% complete. On the newer firmware, it would be about 30% complete. Log File: https://drive.google.com/file/d/1URlIuf1YbKsB2LgmqBM-_-RpWZaVxf2F/view?usp=drive_link Show Folder: https://drive.google.com/drive/folders/1N9PFxpYTBUmEB5F80IDBbsPKfU6DvUZ6?usp=drive_link |
This crash log is related to the mentioned issue above, Xlights crashes somewhere in the middle of the upload of a long sequence (10 minutes seq). It looks like a problem with the progress_callback function. 2024-12-24 08:56:54,894 14456 log_curl [INFO] FPPConnect Adding CURL - URL: http://192.168.50.58/api/file/sequences Method: PATCH Start: 0 Length: 0 Total: 0 Walking from an exception. |
That first line is interesting.. And is likely the divide by 0 error.
|
The browser doesn't like the url and wants to block it for security
reasons. However using curl I get:
<br />
<b>Notice</b>: readfile(): Read of 8192 bytes failed with errno=21 Is a
directory in <b>/opt/fpp/www/api/controllers/files.php</b> on line
<b>435</b><br />
Op di 24 dec 2024 om 15:55 schreef Daryl ***@***.***>:
… That first line is interesting..
2024-12-24 08:56:54,894 14456 log_curl [INFO] FPPConnect Adding CURL -
URL: http://192.168.50.58/api/file/sequences Method: PATCH Start: 0
Length: 0 Total: 0
And is likely the divide by 0 error.
So what does this return in a browser?
http://192.168.50.58/api/file/sequences
It is like there is something messed up on the sequences on your sd card.
—
Reply to this email directly, view it on GitHub
<#5073 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALBHM4ZFR6UZBA4PSEAXWDD2HFYUHAVCNFSM6AAAAABT7KYO5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRRGIYDMMJVGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I further checked the api and if I modify the URL for example:
http://192.168.50.58/api/file/sequences/seq.fseq it downloads the file in
the browser that is in /home/fpp/media/sequences/
just going to http://192.168.50.58/api/file/sequences shows:
Error: /home/fpp/media/sequences/ is a directory. (after a slight mod in
files.php to see the directory in the output)
Xlights should append the name of the sequence after
http://192.168.50.58/api/file/sequences/
Maybe there was a glitch in the connection when Xlights queried fpp for the
remote available files, returned nothing and somehow made the problem
persistent.
By using the fpp browser I deleted the corrupt sequence, but the problem
persisted. Uploading resulted in a corrupted remote fpp sequence and only
by manual uploading the sequence with fpp-gui I got the sequence working.
Op di 24 dec 2024 om 17:04 schreef Allard Dijk ***@***.***>:
… The browser doesn't like the url and wants to block it for security
reasons. However using curl I get:
<br />
<b>Notice</b>: readfile(): Read of 8192 bytes failed with errno=21 Is a
directory in <b>/opt/fpp/www/api/controllers/files.php</b> on line
<b>435</b><br />
Op di 24 dec 2024 om 15:55 schreef Daryl ***@***.***>:
> That first line is interesting..
> 2024-12-24 08:56:54,894 14456 log_curl [INFO] FPPConnect Adding CURL -
> URL: http://192.168.50.58/api/file/sequences Method: PATCH Start: 0
> Length: 0 Total: 0
>
> And is likely the divide by 0 error.
> So what does this return in a browser?
>
> http://192.168.50.58/api/file/sequences
> It is like there is something messed up on the sequences on your sd card.
>
> —
> Reply to this email directly, view it on GitHub
> <#5073 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ALBHM4ZFR6UZBA4PSEAXWDD2HFYUHAVCNFSM6AAAAABT7KYO5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRRGIYDMMJVGQ>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
|
NOTE: IF YOU DO NOT ATTACH A SEQUENCE THAT DEMONSTRATES YOUR PROBLEM THEN THERE IS A HIGH PROBABILITY YOUR ISSUE WILL JUST BE CLOSED AND NOT INVESTIGATED.
Describe the bug
Xlights "Crashes" at the 5 minute mark during FPP connect upload. Espixelstick firmware version ci-12304517834 takes longer to receive sequence uploads from FPP connect. Changes in the firmware reduces file corruption but makes the upload time longer. My megatree (2400 pixels/8 ports, Dig-Octa) gets to about 40% uploaded when Xlights crashes at the 5 minute mark. I'm guessing that it is timing out.
To Reproduce
Steps to reproduce the behavior:
Run FPP connect with a 300 pixel per port 8 port dig octa or dig quad using expixelstick firmware version ci-12304517834.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions (please complete the following information):
Additional context
Add any other context about the problem here.
Attachments
Link to show folder and log file.
https://drive.google.com/drive/folders/1AW6Bhc-A2ZlVZANqHJDGjp1KUWwyT3Rr?usp=sharing
The text was updated successfully, but these errors were encountered: