> Chuck Bokath <bokathc@...> writes: > Hi, > I have a question on the steps (please verify) that are required to run > the kraken command line program in 'test' mode. When I run kraken in > this mode, I never get back a key and the output "Found XXXx <at> YY". I have done the following 3 Steps: 1. Downloaded the 40 .dlt files from http://reflextor.com/e100torrents/a51_table_XX.torent to a 3 TB SSD array which is formatted as 3 partitions running ext4 file systems, and have verified the each .dlt file has the correct hash. (see below) 6d36bca865ad5f5b3b95e50be5555f0a 100.dlt d89f2f62a471734fc86844261e709719 108.dlt 9558f5a7152ab8dddc6e5ff819a3fa5f 164.dlt 307cc99d1724bd1b460d7f39d6121048 172.dlt 9e9861bd2272b58737629b7c34eb1064 212.dlt c6a95cda3e55079295cf97706dc9de2e 238.dlt af8167abdfd178a01b2bb3a2ee4f59c8 268.dlt 2ecc836a993a3f71cd710c4455e9780e 324.dlt 183a3427843105942e9b0ab0a852c7db 348.dlt 1bbceb9afda870b76b7e9928409183de 372.dlt 98de5b58c98fafc5ada3897eddf7f31a 396.dlt 3985446a74105d15f6c4b8bd0467771b 420.dlt a0006b7b58e01b97d6bce1b43b015343 492.dlt fa47f2242230b69c5ae7a1196ea0311f 500.dlt 0c93864ad638b531dedf10d85880ee79 124.dlt f0dbac482c9f6d6626a70bf8115515b4 132.dlt 0cbd427fb98dc9cec05bc8cd9eec53c5 180.dlt 8771eba46785c636e606560265efcb6f 188.dlt 7f4fcaec2da609dd794ecff07f1ad890 196.dlt 032414372c864417a502ef1eaaa42454 220.dlt f54c106d3ea9ef442330c5156c14c832 250.dlt d422218e33cb6c421108469940c03d41 276.dlt 75340dda19dc1b1ada8108d47461562a 332.dlt 771ec801ac043291b9f134f75f82a31d 356.dlt 435e2d2755aa5ce9357889bef5ee534f 380.dlt 5bc5814694b412cfb4ba52198492ba1b 404.dlt 44f06b97410bda5b029754de9cc87db4 428.dlt 9db534d5866cc6c8b18eef0bbf6aceae 116.dlt 15768f7f5af4e5467304c7162688425d 140.dlt 55b1bed783fd94a1feb06e70af5cd789 148.dlt cec43159aa1d7ca4982f1c7417b8dd09 156.dlt 69b40dc68cd9d26006f9b1f70ab676ad 204.dlt 6afc1ca6c0005bf2df6782371c56700d 230.dlt 2cf1377b93139fb2a7ec9f687b272d3c 260.dlt 6995a5445330b78380b3ba16642318e9 292.dlt 1cc82ad35788afc4acab95f481e3de9d 340.dlt 59913ab26509afaecd8861a6877b06c6 364.dlt fabeaa1792045a0ab5471aeac7271481 388.dlt 4518baa2a1156451cbc0952eb216cb5f 412.dlt c3c48ba123a1ebd9ea6f0abaa56ac475 436.dlt 2. Once the files are downloaded, i rename them to XXX.dlt and for some reason, running Behemoth.py on the SSD array corrupts the file system. So, i tried running Behemoth.py on a separate 'tradiitonal' box with each SSD partition mounted via NFS. That *seems* to work fine. I added some debug/informational lines in behemoth, and it seems to view the nfs mounted driives as raw delta. Here is my tables.conf output after behemoth runs. (nfs mount is to /table) #Devices: dev/node max_tables Device: /table/d0 15 Device: /table/d1 15 Device: /table/d2 15 #Tables: dev id(advance) offset Table: 0 100 61391195 Table: 0 324 102313103 Table: 0 372 92083796 Table: 0 420 51159177 Table: 0 172 10229859 Table: 0 500 71620051 Table: 0 238 122782426 Table: 0 108 112548115 Table: 0 276 143241494 Table: 0 212 40925806 Table: 0 268 20463152 Table: 0 164 30695372 Table: 0 396 81853546 Table: 0 348 133012367 Table: 0 492 153470574 Table: 1 132 92105823 Table: 1 412 122856754 Table: 1 388 143324460 Table: 1 356 102376597 Table: 1 404 71633752 Table: 1 428 10230895 Table: 1 124 61395110 Table: 1 188 81866011 Table: 1 436 133090367 Table: 1 196 153558800 Table: 1 332 40922624 Table: 1 180 20465981 Table: 1 250 51154849 Table: 1 220 30694865 Table: 1 380 112608311 Table: 2 116 30717010 Table: 2 292 92104793 Table: 2 230 102337536 Table: 2 260 10234365 Table: 2 204 40948946 Table: 2 140 20479594 Table: 2 340 81872471 Table: 2 148 51178935 Table: 2 156 71640116 Table: 2 364 61408430 3. When I run kraken app w/o a port and it loads up all the indexes fine, as a note- i have added info/dbg statement into the app itself to trace the call flow. (see below) Once i get the Kraken> prompt, I select test to verity that the app has loaded and is functioning correctly before I go down any other path. Kraken outputs that it is cracking, then it rather quickly completes. As i read throught he a51 list-the call of Kraken 16 Jul 2010 - Frank mentions it should take 1.5 minutes on a 4 core Phenom II using only cpu power. Im running kraken on a 2 core 3.40GHz x86_64 system w/8GB RAM mounting the SSDs locally through NFS. The output is listed below. In case I did not add the dbg/info statement inthe correct spot, and it still may be churning, i left it run for the weekend, and it was the same output you see below. Is there anything glaringly wrong with my approach? The only thing I can think of is the NFS mounts...has anyone tried this setup, or can offer advice? Device: /table/d0 15 /table/d0 Opening /table/d0 Error code: Success Device: /table/d1 15 /table/d1 Opening /table/d1 Error code: Success Device: /table/d2 15 /table/d2 Opening /table/d2 Error code: Success 0 100 61391195 Allocated 41235072 bytes. ffffffffe5c65889 638e847 1a5ec251a5000 0 324 102313103 Allocated 41259888 bytes. ffffffffe5d6a9ec 60256ad 1a233bb21a000 0 372 92083796 Allocated 41236892 bytes. ffffffffe5d06ebd 58d9c9a 1a47c02eec000 0 420 51159177 Allocated 41247816 bytes. ffffffffe5d94bf3 5ff6bae 1a42c447c7000 0 172 10229859 Allocated 41252956 bytes. ffffffffe5f2e918 5fee19f 1a48be2b2f000 0 500 71620051 Allocated 41253772 bytes. ffffffffe5d159f1 59f280b 1a306393ea000 0 238 122782426 Allocated 41239444 bytes. ffffffffe5d28239 5e638ed 1a3d2be92a000 0 108 112548115 Allocated 41257060 bytes. ffffffffe5dbd475 590643a 1a305e5394000 0 276 143241494 Allocated 41235976 bytes. ffffffffe5ce184d 6276c5c 1a518d9e6b000 0 212 40925806 Allocated 41253276 bytes. ffffffffe5c879ac 6678e55 1a1ca16eeb000 0 268 20463152 Allocated 41248632 bytes. ffffffffe5d5e2df 5dc8966 1a36d16c06000 0 164 30695372 Allocated 41241432 bytes. ffffffffe5c70e7f 5da4898 1a449f3fbf000 0 396 81853546 Allocated 41240688 bytes. ffffffffe5c944be 59ef0af 1a345fd131000 0 348 133012367 Allocated 41236164 bytes. ffffffffe5c88e9d 57e9c52 1a6607949f000 0 492 153470574 Allocated 41239116 bytes. ffffffffe5c8ae6e 5c4aa19 1a3943e05c000 1 132 92105823 Allocated 41404056 bytes.1 388 143324460 Allocated 41257176 bytes. ffffffffe5c69ebd 62d707a 1a46232427000 1 356 102376597 Allocated 41246592 bytes. ffffffffe5cf4159 566028b 1a4771f034000 1 404 71633752 Allocated 41248788 bytes. ffffffffe5c8e027 5d9e8dd 1a423772fa000 1 428 10230895 Allocated 41260184 bytes. ffffffffe5cf5edd 61b9910 1a2e96a66a000 1 124 61395110 Allocated 41274520 bytes. ffffffffe5dfe381 6429656 1a0f70859b000 1 188 81866011 Allocated 41279240 bytes. ffffffffe5dc4271 5dcd6c6 1a40ea2f9e000 1 436 133090367 Allocated 41256180 bytes. ffffffffe5d32471 5eb8eec 1a48ddbb15000 1 196 153558800 Allocated 41243292 bytes. ffffffffe5c56222 6078f66 1a50e5f72f000 1 332 40922624 Allocated 41248652 bytes. ffffffffe5d0dc15 5a47733 1a22ec187e000 1 180 20465981 Allocated 41235184 bytes. ffffffffe5e90612 699bf58 1a44ae096a000 1 250 51154849 Allocated 41281052 bytes. ffffffffe5cbe485 5d38535 19fc3480c1000 1 220 30694865 Allocated 41230652 bytes. ffffffffe5c38068 5e8526d 1a3afd843f000 1 380 112608311 Allocated 41314028 bytes. ffffffffe5d643aa 669a9c5 1a21483030000 2 116 30717010 Allocated 41247488 bytes. ffffffffe5caa2f3 642c67f 1a34915290000 2 292 92104793 Allocated 41250740 bytes. ffffffffe5d2de19 5e47930 1a29759eff000 2 230 102337536 Allocated 41257276 bytes. ffffffffe5cbe632 58e6a68 1a3b8644b1000 2 260 10234365 Allocated 41301076 bytes. ffffffffe5d4ff52 58ecfd5 1a64210fe7000 2 204 40948946 Allocated 41239636 bytes. ffffffffe5c8fe1e 5f47560 1a367ae65d000 2 140 20479594 Allocated 41269576 bytes. ffffffffe5c9ee00 5fad072 1a05a2770e000 2 340 81872471 Allocated 41249048 bytes. ffffffffe5c7f676 6951f93 1a690a5190000 2 148 51178935 Allocated 41237644 bytes. ffffffffe5c8c16a 5c7fc19 1a3cb95003000 2 156 71640116 Allocated 41249180 bytes. ffffffffe5d0ce33 5d3385b 1a3cb1a757000 2 364 61408430 Allocated 41246480 bytes. ffffffffe5c7071a 5e1c09c 1a5b540714000 A5Cpu Threads: 4 Commands are: crack test quit Continue Job? Kraken> test #0, Pushing plaintext onto WorkOrder Stack Cracking (Samples: 51) 0011011100110000000010000011000110001001101101100110110100111100011010101001001 1111111010111100000110101001101011 Done Cracking....? any help or verification of the data/steps would be greatly appreciated. Regards, >
Dear Chuck and all, I've had the same phenomena as Chuck's. My system information is Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz with CentOS 6.0 64-bit. If you have found out the solution, please help me with this problem. Br _______________________________________________ A51 mailing list [email protected] http://lists.lists.reflextor.com/cgi-bin/mailman/listinfo/a51
