Other Factordb Problems

[VictordeHolland]

Originally Posted by LaurV

What's that?!?

Loco Loco number?

[pakaran]

Originally Posted by LaurV

What's that?!?

An element of the Lucas sequence (I misspelled it!), which is defined like the Fibonacci sequence except starting with 2,1 rather than 1,1.

So you get the sequence
Fibonacci:1,1,2,3,5,8,13,21,34,55...
or
Lucas:2,1,3,4,7,11,18,29,47,76,...

[LaurV]

Ok, I got it. That is Lucky's number... Or was it Lucy's number...

[pakaran]

Let me present what is probably not the first, but is the first known to me, certifiably doubly loco titanic prime:

69^666+31337^42+727

Note that this is almost certainly not the *smallest* certifiably doubly loco titanic prime; that achievement waits for a loco amateur mathematician who is better at mental locorhythms than myself. The first portion of the sum accounts for essentially all of the number's magnitude, since 31337 < 10^4.5. Fortunately, the 727 not only appeared earlier than I expected (roughly a minute with pfgw), but also did not crash into my computer. Certification took almost an hour, but with other tasks running niced, and browsing the web.

This number might actually be regarded as triply loco, since it has 4069 bits.

[Stargate38]

I tried to upload an Aliquot sequence that I just started working on, but I ended up with this:

C:\Pictures\aliqueit112\aliqueit112>aliqueit_win64 4197563000 -s 160
Reading config file...
ggnfs_clean_cmd = del cols*.* deps*.* factor.easy lpindex*.* rels*.* numFF.txt numrels.txt tmp.job spmat sp-index test.fb matsave matsave.bak test.dat*
null_device = nul
makedir_cmd = mkdir
prefer_yafu = true
ecm_cmd = C:\Pictures\ecm644_win64_i7\ecm.exe
ecmpy_cmd = python.exe ecm.py
yafu_cmd = C:\Pictures\aliqueit112\aliqueit112\yafu-1.33\yafu-x64.exe
msieve_cmd = C:\Pictures\msieve152\msieve152.exe
ggnfs_cmd = c:\strawberry\perl\bin\perl.exe "C:\Pictures\ggnfs-svn413-win64-core2\factMsieve.pl"
use_ecmpy = false
use_msieve_polyfind = true
detect_merge = false
trial_cutoff = 8675309
gnfs_cutoff = 103
hide_output_limit = 95
neat_factor_limit_ecm = 45
neat_factor_limit_pm1 = 45
neat_factor_limit_pp1 = 40
result_file_prefix = alq_
log_file = aliqueit.log
save_log = true
ecm_tempfile = aliqueit_ecm_temp.log
ecm_depth = 45 10, 50 15, 55 20, 60 30, 65 40, 70 60, 73 90, 76 120, 79 150, 82 180, 83 200, 86 300, 90 400, 93 500, 96 600, 99 700, 102 800, 106 900, 110 1000, 114 1100, 118 1200, 122 1300
big_ecm_cutoff = 65
qs_k = 0.448
qs_m = -11.26
gnfs_k = 0.235
gnfs_m = 9.4
b1scale_ecm = 1.0
b2scale_ecm = 1.0
b1scale_pm1 = 1.0
b2scale_pm1 = 1.0
b1scale_pp1 = 1.0
b2scale_pp1 = 1.0
Sending 1128 lines...
SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc
syswgetrc = c:/progra~1/wget/etc/wgetrc
--2015-11-02 16:56:20--  http://factorization.ath.cx/search.php?report=true
Resolving factorization.ath.cx... 176.9.39.214
Connecting to factorization.ath.cx|176.9.39.214|:80... connected.
HTTP request sent, awaiting response... Read error (Connection timed out) in headers.
Retrying.

--2015-11-02 17:11:20--  (try: 2)  http://factorization.ath.cx/search.php?report=true
Connecting to factorization.ath.cx|176.9.39.214|:80... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

<snip>

I tried later, but I got the same response

--2015-11-02 17:18:06--  http://factorization.ath.cx/search.php?report=true
Resolving factorization.ath.cx... 176.9.39.214
Connecting to factorization.ath.cx|176.9.39.214|:80... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

--2015-11-02 17:18:13--  (try: 2)  http://factorization.ath.cx/search.php?report=true
Connecting to factorization.ath.cx|176.9.39.214|:80... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

--2015-11-02 17:18:21--  (try: 3)  http://factorization.ath.cx/search.php?report=true
Connecting to factorization.ath.cx|176.9.39.214|:80... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

--2015-11-02 17:18:28--  (try: 4)  http://factorization.ath.cx/search.php?report=true
Connecting to factorization.ath.cx|176.9.39.214|:80... connected.
HTTP request sent, awaiting response...  No data received.
Retrying.

<snip>

In Firefox, I get "The connection was reset". Ping and Tracert results:

C:\Pictures\aliqueit112\aliqueit112>ping www.factordb.com

Pinging www.factordb.com [176.9.39.214] with 32 bytes of data:
Reply from 176.9.39.214: bytes=32 time=738ms TTL=40
Reply from 176.9.39.214: bytes=32 time=1767ms TTL=40
Reply from 176.9.39.214: bytes=32 time=1323ms TTL=40
Reply from 176.9.39.214: bytes=32 time=1283ms TTL=40

Ping statistics for 176.9.39.214:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 738ms, Maximum = 1767ms, Average = 1277ms

C:\Pictures\aliqueit112\aliqueit112>tracert www.factordb.com

Tracing route to www.factordb.com [176.9.39.214]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2     2 ms     1 ms     1 ms  100.90.246.121
  3   617 ms   753 ms   529 ms  69.35.206.45
  4   644 ms  1071 ms   543 ms  69.35.204.59
  5   743 ms   654 ms  1499 ms  69.35.204.33
  6   758 ms  1315 ms  1292 ms  63.156.154.41
  7     *        *        *     Request timed out.
  8   957 ms  1283 ms  1369 ms  63.146.27.146
  9   733 ms   993 ms   696 ms  141.136.109.173
 10   736 ms  1304 ms  1292 ms  77.67.76.142
 11   721 ms   709 ms   731 ms  213.239.245.6
 12   726 ms   721 ms   770 ms  213.239.245.217
 13  1214 ms   718 ms   736 ms  213.239.245.90
 14   727 ms   729 ms   722 ms  213.239.244.6
 15   715 ms   719 ms  1009 ms  176.9.39.214

Trace complete.

C:\Pictures\aliqueit112\aliqueit112>

If you noticed that the latency is extra large, it's because I recently switched to satellite internet (HughesNet).

[chris2be8]

It's back up now, but with no workers connected.

The problem started late last night and affected allprojectstats.com as well as factordb.com (they have the same IP address). It recovered an hour or two after midday today.

I think the web server at that IP address was down, since requests just timed out.

Chris

[vebis]

factordb.com showed for a short time that it's moving to a new server

[henryzz]

With a system that age it is possible that it is no longer stable.

[henryzz]

Originally Posted by henryzz

Is there a backup of the database anywhere?

Anyone know the answer to this?

I am aware that a lot of people use this as a repository and there are many big factorizations in the factordb that aren't elsewhere. We could do with an offsite backup somewhere. We have had forum members disappear before.

[LaurV]

Originally Posted by henryzz

Anyone know the answer to this?

I am aware that a lot of people use this as a repository and there are many big factorizations in the factordb that aren't elsewhere. We could do with an offsite backup somewhere. We have had forum members disappear before.

+1. We subscribe to this, and sustain your point from all our heart (when we have one).
My biggest issue with FDB is Syd's availability to make changes. We still have aliquots broken after 3 years, when the fix would take less than a minute - delete the broken index and some LaurV guy will restore the factorization, in time. We know he has real life, but it looks to us like he doesn't care at all. In the past we asked for admin/mod rights there to mend some wires, but we got no answer, we made a user which is not used for anything (like no credits, not even a remark, that is why we stopped using yoyo's script to factor small composites, we used to do this a lot in the past for ~120-130 digits range, a very good work type when you have nothing to do with your CPU for a day or so and don't want to start a longer job). Yet, after years, when you click on "users" you still get the "under construction".
We started using FDB less and less, and (after the boost we got when Dubslow's site was done, and another one when it got mirrored) we let our aliquot reservations to die slow... We don't really feel a motivation, if you know what we mean...

[schickel]

Originally Posted by henryzz

Anyone know the answer to this?

I am aware that a lot of people use this as a repository and there are many big factorizations in the factordb that aren't elsewhere. We could do with an offsite backup somewhere. We have had forum members disappear before.

I think I started to answer this earlier but got sidetracked or something. The only extant backup was a torrent that was seeded that consisted of a straight backup of just the number table, but none of the front-end code that make it worlds more useful than just a bunch of numbers thrown in a pile. I'm sure you could find the messages covering this topic near the bottom of the archive in the sub-forum. It was at least a couple of years ago....