in the jsreport.config,json I've turned off the preview with
The Error occurs when trying to open in Excel. (something about the excel file need to be repaired)
I think an empty cell would work, But, it would leave that cell un-formatted.
The best would be to format the cell and leave it value blank.
jsreport uses extra processes for heavy work by default. The templating engines are evaluated in the extra process as well as the chrome pdf printing.
This means there is typically no need to scale jsreport main node process.
Thank you for the emailed export.
I'm running the docker container attached to my blob storage with your import for several hours now.
I don't see issues or data lose so far. I keep it running and time from time open the studio.
I run this command
docker run -p 5488:5488 -v c:\work\temp3\home\:/jsreport jsreport/jsreport:2.4.0-full
Not sure what is the IP 220.127.116.11, don't you know it? I guess it will be azure blob storage. So maybe there were some temprary connection issues from the machine running jsreport. I've tried to simulate the same.
However, it is not restarted like it seems it happened in your case. If I open the internet again the app normally works.
What I noticed is that if I keep the internet down for a long time it takes also a long time for app to load in the browser. This is because the compaction interval mentioned here is queing new and new compaction and this blocks the app after the internet is back on. We will fix this so the compaction is not queing when there is already one task.
Another thing which came from analyzing your error.
Error occured during reporter init StorageError: There is already a lease present.
The azure blob storage driver uses azure container lease to lock it and prevent concurrent access. This is maybe useless for you if you have just a single instance, you can disable it using
Based on the logs the app did wait like 50 seconds to get the lease. The default jsreport lease has no such duration. Normally the app would wait until the lease is relased. This looks like something else created the lease. Or maybe you have some custom config in fs-store-azure-storage-persistence.lock?
In every case the corruption shouldn't happen and I don't see how it could so far.
It would help me a lot if you would send me the next time the downloaded container from the azure, so I see what is wrong there.
Disabled Categories are greyed out
This topic will be moved to the category
Looks like your connection to jsreport forum was lost, please wait while we try to reconnect.