The lss: line isn't there in the original polynomial from the near-repdigit Web interface, and as I wrote earlier in another topic, as long as the sieving side matches the usual recommended side implied by the type: line, the poly doesn't fail :smile:
All of the other recent GNFS polys which are still fully visible in the 14e management page have a lss: line, but multiple SNFS polys, such as #1442 13601_61_minus1, don't, and siever on the grid clients don't fail on these polys.

C164_159978_10262 factors
 

C164_159978_10262 factors

[code]p79 factor: 4766810075511487434911465766569047757783816417278851092890204825135327119935063
p85 factor: 4713139448874607477535005971654558298593994738547653012328478882915430001345704087049[/code]
7.2M matrix (TD=110)

Factors uploaded to Factordb.
(Truncated) log attached and at: [url]https://pastebin.com/1xRf4PLm[/url]

C215_46988659_29
(46988659^29-1)/46988658=
[code]
65434296264879485831057770993488700245967650017100071066373555801095079019465292289811876502805313831172779822893945904680867232753021773924258110416408044145755384753131700041017654832754227289103683721688682472361
[/code]Is already in the Factordb:
[URL]http://www.factordb.com/index.php?id=1100000001060474966[/URL]

It splits as:
[code]
p106: 4672601456018195178699471914588665537722988275510203132077093911934729158719497712508274838757971243020753
p110: 14003825680574946026452519246879959936758227574144910522162981447781462580995284001498760348577141562692776537[/code]So maybe somebody else already did the postprocessing and didn't post it in this thread (or I haven't noticed).

[QUOTE=VictordeHolland;495919]C215_46988659_29
(46988659^29-1)/46988658=
[code]
65434296264879485831057770993488700245967650017100071066373555801095079019465292289811876502805313831172779822893945904680867232753021773924258110416408044145755384753131700041017654832754227289103683721688682472361
[/code]Is already in the Factordb:
[URL]http://www.factordb.com/index.php?id=1100000001060474966[/URL]

It splits as:
[code]
p106: 4672601456018195178699471914588665537722988275510203132077093911934729158719497712508274838757971243020753
p110: 14003825680574946026452519246879959936758227574144910522162981447781462580995284001498760348577141562692776537[/code]So maybe somebody else already did the postprocessing and didn't post it in this thread (or I haven't noticed).[/QUOTE]

It looks like I grabbed the wrong dataset when I did [url=https://www.mersenneforum.org/showpost.php?p=495644&postcount=203]Phi_29(Phi_3(25457)/13)[/url]. Can someone tell me the correct name for this job? I can't decipher it. It was just completed a couple days ago.

[QUOTE=RichD;495921]It looks like I grabbed the wrong dataset when I did [url=https://www.mersenneforum.org/showpost.php?p=495644&postcount=203]Phi_29(Phi_3(25457)/13)[/url]. Can someone tell me the correct name for this job? I can't decipher it. It was just completed a couple days ago.[/QUOTE]

I found the queue request [url=https://www.mersenneforum.org/showpost.php?p=492561&postcount=1541]here[/url] but I don't remember seeing another dataset ending in _29.

C217_69655517_29, or more probably C216_49852639_29 ?

[QUOTE=debrouxl;495929]C217_69655517_29, or more probably C216_49852639_29 ?[/QUOTE]
C217_69655517_29
Shows as FF in the Factordb:
[url]http://factordb.com/index.php?query=69655517%5E29-1[/url]

C216_49852639_29
Is still CF in Factordb:
[url]http://factordb.com/index.php?query=49852639%5E29-1[/url]

[QUOTE=VictordeHolland;495937]C216_49852639_29
Is still CF in Factordb:
[url]http://factordb.com/index.php?query=49852639%5E29-1[/url][/QUOTE]

That is the one that went by Phi_29(Phi_3(25457)/13) in the queue name. It shows completed as # 1355. Obviously, I grabbed the wrong dataset.

[QUOTE=RichD;495944]That is the one that went by Phi_29(Phi_3(25457)/13) in the queue name. It shows completed as # 1355. Obviously, I grabbed the wrong dataset.[/QUOTE]
Does anybody got a copy of this dataset, I can't find it on the server?
Just to be sure: I'm looking for the relations of the C216 cofactor of [B]49852639[/B]^29-1 (the one that is displayed as factored but isn't) so we can clean this up.
[code]
342979604182615255258693254421748108228322604383289993800565370414344839359283788981547172276819546740023979366342120920148747230565238271359993792909152771442330156630035414193369265772093168266608867254556175688641[/code]

There doesn't seem to be any new relations coming in for C179_374xx231_19. Probably old WUs from previously submitted work that expired. I started this job building a matrix at TD=96 with just over 400 hours remaining.

[QUOTE=VictordeHolland;495919]C215_46988659_29
(46988659^29-1)/46988658=
[code]
65434296264879485831057770993488700245967650017100071066373555801095079019465292289811876502805313831172779822893945904680867232753021773924258110416408044145755384753131700041017654832754227289103683721688682472361
[/code]Is already in the Factordb:
[URL]http://www.factordb.com/index.php?id=1100000001060474966[/URL]

It splits as:
[code]
p106: 4672601456018195178699471914588665537722988275510203132077093911934729158719497712508274838757971243020753
p110: 14003825680574946026452519246879959936758227574144910522162981447781462580995284001498760348577141562692776537[/code]So maybe somebody else already did the postprocessing and didn't post it in this thread (or I haven't noticed).[/QUOTE]

Victor should be credited with this job since he reserved and processed the job correctly. I will start the sieving locally (for the correct job) in a couple months since I am over subscribe at the moment.