Colab question

[Uncwilly]

So I had/have a colab session. It finished 1 P-1 and then the CPU part did not start another.

0200429_000702 ( 0:44):  99924313 stage 2 complete. 113978 transforms. Time: 2529.885 sec.
20200429_000702 ( 0:44): Starting stage 2 GCD - please be patient.
20200429_000732 ( 0:44):  98157911  74 to 75   78.9%   6m45s  1756.67    1.997s | 3636/4620, 757/960 |  20.83G | 10429.0M/s |   82485
20200429_000740 ( 0:45): Stage 2 GCD complete. Time: 36.372 sec.
20200429_000740 ( 0:45):  99924313 completed P-1, B1=775000, B2=15112500, E=6, Wh8: 19FD743E
20200429_000740 ( 0:45):  99924313 completed P-1, B1=775000, B2=15112500, E=6, Wh8: 19FD743E, AID: 40bb898f0b301263139f3535d43fabc3
20200429_000832 ( 0:45):  98157911  74 to 75   82.0%   5m45s  1757.55    1.996s | 3781/4620, 787/960 |  20.83G | 10434.3M/s |   82485
20200429_000932 ( 0:46):  98157911  74 to 75   85.1%   4m46s  1752.28    2.002s | 3921/4620, 817/960 |  20.83G | 10403.0M/s |   82485
20200429_001032 ( 0:47):  98157911  74 to 75   88.2%   3m46s  1755.79    1.998s | 4068/4620, 847/960 |  20.83G | 10423.8M/s |   82485
20200429_001132 ( 0:48):  98157911  74 to 75   91.4%   2m46s  1751.40    2.003s | 4204/4620, 877/960 |  20.83G | 10397.8M/s |   82485
20200429_001232 ( 0:49):  98157911  74 to 75   94.5%   1m46s  1760.19    1.993s | 4348/4620, 907/960 |  20.83G | 10450.0M/s |   82485
20200429_001332 ( 0:50):  98157911  74 to 75   97.6%   0m46s  1753.15    2.001s | 4504/4620, 937/960 |  20.83G | 10408.2M/s |   82485
20200429_001420 ( 0:51): no factor for M98157911 from 2^74 to 2^75 [mfaktc 0.21 barrett76_mul32_gs]
20200429_001420 ( 0:51): tf(): total time spent: 32m 15.475s
20200429_001420 ( 0:51): Starting trial factoring M97438519 from 2^74 to 2^75 (39.27 GHz-days)

20200429_001425 ( 0:51):  Exponent  TF Level  % Done     ETA   GHzD/D  Itr Time |   Class #,   Seq # |    #FCs | SieveRate |  SieveP
20200429_001428 ( 0:51):  97438519  74 to 75    0.1%  32m15s  1751.22    2.018s |    0/4620,   1/960 |  20.98G | 10396.7M/s |   82485
20200429_001529 ( 0:52):  97438519  74 to 75    3.6%  31m02s  1755.57    2.013s |  164/4620,  35/960 |  20.98G | 10422.5M/s |   82485
20200429_001629 ( 0:53):  97438519  74 to 75    6.8%  30m03s  1754.70    2.014s |  317/4620,  65/960 |  20.98G | 10417.4M/s |   82485
20200429_001743 ( 0:55):  97438519  74 to 75    9.5%  29m10s  1754.70    2.014s |  432/4620,  91/960 |  20.98G | 10417.4M/s |   82485
20200429_001844 ( 0:56):  97438519  74 to 75   13.8%  27m52s  1750.35    2.019s |  636/4620, 132/960 |  20.98G | 10391.6M/s |   82485
20200429_002004 ( 0:57):  97438519  74 to 75   16.8%  26m48s  1756.44    2.012s |  776/4620, 161/960 |  20.98G | 10427.7M/s |   82485
20200429_002105 ( 0:58):  97438519  74 to 75   21.0%  25m30s  1750.35    2.019s |  969/4620, 202/960 |  20.98G | 10391.6M/s |   82485
20200429_002224 ( 0:59):  97438519  74 to 75   24.1%  24m32s  1750.35    2.019s | 1109/4620, 231/960 |  20.98G | 10391.6M/s |   82485
20200429_002325 ( 1:00):  97438519  74 to 75   28.2%  23m06s  1757.31    2.011s | 1304/4620, 271/960 |  20.98G | 10432.9M/s |   82485
20200429_002446 ( 1:02):  97438519  74 to 75   31.4%  22m07s  1755.57    2.013s | 1445/4620, 301/960 |  20.98G | 10422.5M/s |   82485
20200429_002546 ( 1:03):  97438519  74 to 75   35.5%  20m50s  1750.35    2.019s | 1641/4620, 341/960 |  20.98G | 10391.6M/s |   82485

[Chuck]

Originally Posted by Uncwilly

So I had/have a colab session. It finished 1 P-1 and then the CPU part did not start another.

I have three of four notebooks that also stopped doing P-1

[kladner]

I saw something similar from sessions that ran overnight.

[Uncwilly]

That was about the time that GPU72.com had some server maintenance.

[kladner]

Originally Posted by Uncwilly

That was about the time that GPU72.com had some server maintenance.

Sorry. I don't understand.

[Uncwilly]

Originally Posted by kladner

Sorry. I don't understand.

GPU72 had some server downtime yesterday (time zone dependent). The P-1 in my example did not start a new exponent at about that same time. Maybe it was not able to get new work.

[chalsall]

Originally Posted by Uncwilly

GPU72 had some server downtime yesterday (time zone dependent).

Yeah... Sorry guys. Cascading SPEs...

Things should be back to nominal now (1500 UTC).

[kladner]

Originally Posted by Uncwilly

GPU72 had some server downtime yesterday (time zone dependent). The P-1 in my example did not start a new exponent at about that same time. Maybe it was not able to get new work.

DOH! Thanks.

[mrk74]

First let me say everything seems to be running fine as far as I can tell. I'm doing some P-1 only (darn usage limits) Anyway, I finished one exponent and went on to the next and when the next one started I got this. Don't know if it means anything substantial or not but thought I would let it be known.

20200429_203344 ( 6:39): [Comm thread Apr 29 20:33] PrimeNet error 7: Invalid parameter 

20200429_203344 ( 6:39): [Comm thread Apr 29 20:33] parameter c: Invalid string length: 0

[chalsall]

Originally Posted by mrk74

Don't know if it means anything substantial or not but thought I would let it be known.

Thanks for the report. That looks like a comms error between the mprime client and either the GPU72 and/or Primenet server(s). This happens sometimes.

There is some resiliency there, so the run /should/ be cleanly sent. Does it appear in your completed list?

[mrk74]

Originally Posted by chalsall

Does it appear in your completed list?

The one previous to this happening does. That error message came up AFTER the next payload way fetched.

20200429_203328 ( 6:39): Exiting. 20200429_203328 ( 6:39):  20200429_203328 ( 6:39):  20200429_203328 ( 6:39): Payload exited.  Fetching next payload... 20200429_203338 ( 6:39): Sending Telemetry for 94354c530186358ff6a3fb2770c89d7c (e87b899158d2a3c35978e884756e18ae) 20200429_203338 ( 6:39): Fetching payload... 20200429_203342 ( 6:39): CPU Payload starting... 20200429_203344 ( 6:39): [Main thread Apr 29 20:33] Mersenne number primality test program version 29.8 20200429_203344 ( 6:39): [Main thread Apr 29 20:33] Optimizing for CPU architecture: Core i3/i5/i7, L2 cache size: 256 KB, L3 cache size: 45 MB 20200429_203344 ( 6:39): [Main thread Apr 29 20:33] Starting worker. 20200429_203344 ( 6:39): [Comm thread Apr 29 20:33] Updating computer information on the server 20200429_203344 ( 6:39): [Work thread Apr 29 20:33] Worker starting 20200429_203344 ( 6:39): [Work thread Apr 29 20:33] Optimal P-1 factoring of M99894071 using up to 10240MB of memory. 20200429_203344 ( 6:39): [Work thread Apr 29 20:33] Assuming no factors below 2^77 and 2 primality tests saved if a factor is found. 20200429_203344 ( 6:39): [Comm thread Apr 29 20:33] PrimeNet error 7: Invalid parameter 20200429_203344 ( 6:39): [Comm thread Apr 29 20:33] parameter c: Invalid string length: 0 20200429_203344 ( 6:39): [Comm thread Apr 29 20:33] Visit http://mersenneforum.org for help. 20200429_203344 ( 6:39): [Comm thread Apr 29 20:33] Will try contacting server again in 70 minutes. 20200429_203344 ( 6:39): [Work thread Apr 29 20:33] Optimal bounds are B1=775000, B2=15112500 20200429_203344 ( 6:39): [Work thread Apr 29 20:33] Chance of finding a factor is an estimated 2.93% 20200429_203344 ( 6:39): [Work thread Apr 29 20:33] Using FMA3 FFT length 5376K, Pass1=896, Pass2=6K, clm=2 20200429_203346 ( 6:39): [Work thread Apr 29 20:33] Using 8961MB of memory.  Processing 201 relative primes (231 of 432 already processed).