Getting all errors on 1 Windows 7 Box PBOYZTOY02 using BOINC v7.16.20 PBOYZTOY02 's run for 40 seconds or so then they finish show the error.

754690 RamanujanMachine 12/30/2021 5:21:42 AM Computation for task RNM_general_25_12_a13_b-8_3827_1 finished
754691 RamanujanMachine 12/30/2021 5:21:42 AM Output file RNM_general_25_12_a13_b-8_3827_1_r2079590044_0 for task RNM_general_25_12_a13_b-8_3827_1 absent

<core_client_version>7.16.20</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code 195 (0xc3)</message>
<stderr_txt>
14:04:29 (4468): wrapper (7.7.26016): starting
14:04:29 (4468): wrapper: running execute_from_json.exe (0001.json)
Traceback (most recent call last):
File "C:\Users\serg\AppData\Local\Programs\Python\Python38\Lib\site-packages\PyInstaller\hooks\rthooks\pyi_rth_multiprocessing.py", line 12, in <module>
File "PyInstaller\loader\pyimod03_importers.py", line 476, in exec_module
File "multiprocessing__init__.py", line 16, in <module>
File "PyInstaller\loader\pyimod03_importers.py", line 476, in exec_module
File "multiprocessing\context.py", line 6, in <module>
File "PyInstaller\loader\pyimod03_importers.py", line 476, in exec_module
File "multiprocessing\reduction.py", line 16, in <module>
File "PyInstaller\loader\pyimod03_importers.py", line 476, in exec_module
File "socket.py", line 49, in <module>
ImportError: DLL load failed while importing _socket: The parameter is incorrect.
[5576] Failed to execute script 'pyi_rth_multiprocessing' due to unhandled exception!
14:04:30 (4468): execute_from_json.exe exited; CPU time 0.000000
14:04:30 (4468): app exit status: 0x1
14:04:30 (4468): called boinc_finish(195)

</stderr_txt>
]]>

I had a problem running it on my Windows pc also so only run them on my Linux pc's and it works fine.

I had a problem running it on my Windows pc also so only run them on my Linux pc's and it works fine.

My Windows 10 Laptop runs them fine but the Win 7 one won't, so there has to be a reason it won't run them ...

I had a problem running it on my Windows pc also so only run them on my Linux pc's and it works fine.

My Windows 10 Laptop runs them fine but the Win 7 one won't, so there has to be a reason it won't run them ...

I want to say it could be the version of VBox but maybe not, we've had that discussion at soo many projects I've forgotten which ones

I had a problem running it on my Windows pc also so only run them on my Linux pc's and it works fine.

My Windows 10 Laptop runs them fine but the Win 7 one won't, so there has to be a reason it won't run them ...

I want to say it could be the version of VBox but maybe not, we've had that discussion at soo many projects I've forgotten which ones

Pretty sure this project doesn't use VBox. On Linux, however, it's dynamically linked so you need the right version of GLIBC or it won't work. That means Ubuntu 20 will work, but Ubuntu 18 won't. Debian 9 and 10 (stretch and Buster) won't work. Not sure about Debian 11.

---

Want to find one of the largest known primes? Try PrimeGrid. Or help cure disease at WCG.

I had a problem running it on my Windows pc also so only run them on my Linux pc's and it works fine.

My Windows 10 Laptop runs them fine but the Win 7 one won't, so there has to be a reason it won't run them ...

I want to say it could be the version of VBox but maybe not, we've had that discussion at soo many projects I've forgotten which ones

Pretty sure this project doesn't use VBox. On Linux, however, it's dynamically linked so you need the right version of GLIBC or it won't work. That means Ubuntu 20 will work, but Ubuntu 18 won't. Debian 9 and 10 (stretch and Buster) won't work. Not sure about Debian 11.

Te project runs fine on both my Linux Box's & the Win 10 Box, just won't run on the Win 7 box using the same version of BOINC as the Win 10 Box

As far as I experienced it seems to be a misfigured bunch of WUs of some sorts.
On my Win7 machine, I had a whole lot of RNM_general_25_12_a9 and a8 which errored out immediately yesterday, my current ones are others like RNM_general_25_12_a14 and they run good. Can't find a a13 so far in my logs, but I have some in the stock which yet have to be crunched. I guess they also will error out then...

---

Life is Science, and Science rules. To the universe and beyond
Member of BOINC@Heidelberg
My BOINC-Stats

Ubuntu 20 and 2x Win 10 systems are OK for me. No errors since Oct.

Reactivating this old thread as it has the title I need.

For those of you that run this project, it recently ran out of work for a few days.
On the release of new work I noticed that my RYZEN computer started running constant errors.
All errors are EXIT_TIME_LIMIT_EXCEEDED and it varies as to what that time limit actually is, from mere seconds to many minutes.

Windows computers are not greatly affected by this fault even the RYZENs.
Intel does not seem affected on the older models.
Intel running Linux is having some issues and getting this fault.
AMD RYZEN having heaps of issues, in my case near 100% failure rate.

I have sent of 2 e-mails now to the Admin Team as they don't have a forum to post on.

So far no response and my errored work units are climbing (over 1.500 and counting).

Conan

---

WRONG PLACE

I know it's the wrong place, but there is no forum on Ramanujan Machine so I posted here where there is a lot more action about different projects.

For me these errors are still occurring, no response so far from the project.

Conan

---

I know it's the wrong place, but there is no forum on Ramanujan Machine so I posted here where there is a lot more action about different projects.

For me these errors are still occurring, no response so far from the project.

Conan

Sorry for the mix up. Nothing wrong with your posting here. My original post was in wrong forum.
As for waiting for reply from RAMA project owner(s), appears even the "free support" at their Discord channel is not that actively visited by the project admins.

I have no problem on WIN7 (old Intel Dual core's)... I see one other person had posted on Discord on 9/29 about the "Endstatus 197 ... EXIT_TIME_LIMIT_EXCEEDED" error which appears to have started around 9/25.... >

So, there is an ACTIVE ABORTION which Ramanujan project performs on its tasks.
And that's the source of all the problems.
You {RAMA PROJECT} need to deploy a longer runtime allowance.

---