Dear Didier,
I have some troubles while using. Tracewin crashes with the following (the are many more lines of "QIODevice::read: device not open" message):
...
QIODevice::read: device not open
QIODevice::read: device not open
QIODevice::read: device not open
QIODevice::read: device not open
(process:4181943): GLib-ERROR **: 14:18:19.044: Creating pipes for GWakeup: Trop de fichiers ouverts
[1]+ Trappe pour point d'arrêt et de trace (core dumped)$HOME/TraceWin/TraceWin
You can download an example here : https://mycore.core-cloud.net/index.php ... TNuZJixE8B
My computer runs Fedora, and I use several servers under Fedora and AlmaLinux.
Best regards,
Emmanuel
Error study crashes
Re: Error study crashes
Dear Emmanuel,
Don't worry about message "QIODevice::read: device not open", your problem comes from somewhere else and I can't understand it at the moment.
Could you increase the limit of files that can be opened at the same time under linx using the command "ulimit -n 16384" and see if the error persists.
Regards,
Didier
Don't worry about message "QIODevice::read: device not open", your problem comes from somewhere else and I can't understand it at the moment.
Could you increase the limit of files that can be opened at the same time under linx using the command "ulimit -n 16384" and see if the error persists.
Regards,
Didier
Re: Error study crashes
Dear Didier,
I had the message "QIODevice::read: device not open" in the past but here, it was scarier... The number of cores might be the source of the multiple messages.
I tried the command ulimit -n 16384 but got the same error. I did some search about ulimit command, and then tried to increase the limit with ulimit -n 63536, as I checked the limits as described here https://community.rsa.com/s/article/Wha ... -Lifecycle. But it didn't work.
So, I'm still stuck with this issue. You might be right pointing at a linux setting, so I'm going to search on this aspect on my side.
Best regards.
Emmanuel
I had the message "QIODevice::read: device not open" in the past but here, it was scarier... The number of cores might be the source of the multiple messages.
I tried the command ulimit -n 16384 but got the same error. I did some search about ulimit command, and then tried to increase the limit with ulimit -n 63536, as I checked the limits as described here https://community.rsa.com/s/article/Wha ... -Lifecycle. But it didn't work.
So, I'm still stuck with this issue. You might be right pointing at a linux setting, so I'm going to search on this aspect on my side.
Best regards.
Emmanuel
Re: Error study crashes
Dear Emmanuel,
You have around ten servers for a total of around 600 cores. For my part, I can test 100 to 200 cores, but on a single server. It would be interesting to know whether the problem comes from the number of cores or the number of servers.
Regards,
Didier
You have around ten servers for a total of around 600 cores. For my part, I can test 100 to 200 cores, but on a single server. It would be interesting to know whether the problem comes from the number of cores or the number of servers.
Regards,
Didier
Re: Error study crashes
Dear Emmauel,
For your information, I've fixed the problem with the "QIODevice::read: device not open" message. It won't change anything, but it will avoid poluting the display with the unusable warning.
Regards,
Didier
For your information, I've fixed the problem with the "QIODevice::read: device not open" message. It won't change anything, but it will avoid poluting the display with the unusable warning.
Regards,
Didier
Re: Error study crashes
Dear Didier,
Thank you for the upgrade.
FYI the error study also crashed on the windows server. At the same time I launched the error study on one linux server, and... It's still running.
Emmanuel
Thank you for the upgrade.
FYI the error study also crashed on the windows server. At the same time I launched the error study on one linux server, and... It's still running.
Emmanuel