HP[sub]6[/sub]9396, HP[sub]2[/sub]4864 and HP[sub]2[/sub]5448 need be fixed.

Something strange happened with aliquiet sequence 842592 - last ~700 indexes disappeared.

[QUOTE=unconnected;208062]Something strange happened with aliquiet sequence 842592 - last ~700 indexes disappeared.[/QUOTE]

Index 6579 is corrupt (57 is treated as a prime.).

There are many sequences that are not correct in the DB. It's time that those get fixed in the DB

same problem with me for 4380: 57 treated as prime at index 1887, whilst I'm happily factoring at index 2144.

calling the [url=http://factorization.ath.cx/workerstatus.php]Worker status[/url] causes an error!

[QUOTE=kar_bon;208254]calling the [url=http://factorization.ath.cx/workerstatus.php]Worker status[/url] causes an error![/QUOTE]

...namely this one:

[code]select workid, fid, type, B1, B2, num, workqueue.uid, fullname from workqueue left join users on workqueue.uid=users.uid order by prio desc limit 50 - Can't create/write to file '/mnt/tmp/MY4G41G3' (Errcode: 13)
Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /var/www/nx/workerstatus.php on line 57[/code]

Edit: There are currently [B]11 million[/B] numbers queued - is prime testing no longer working? Do the local workers do work at all?

I think the extending of aliquot sequences up to 4M has put too much of a strain on the DB.

[QUOTE=10metreh;208279]I think the extending of aliquot sequences up to 4M has put too much of a strain on the DB.[/QUOTE]

Who is doing this? :question:

I dunno. They haven't told me and I'm the first person I'd expect them to tell.

[QUOTE=Andi47;208280]Who is doing this? :question:[/QUOTE]
That'd be me.

[QUOTE=10metreh;208279]I think the extending of aliquot sequences up to 4M has put too much of a strain on the DB.[/QUOTE]

Looks like the workers are not "working", since I finished 4 days ago and still no progress on the work queue.