• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Kraken didn't load.

Q

Qinsp

2[H]4U
Joined
Jan 7, 2011
Messages
2,154
I had a machine stuck in a "no server" loop, so I deleted a bunch of files from the FAH directory (logs, config, queue, cores) but none that said Kraken or the 6.34 client or any directories.

Do I have to install Kraken from scratch?

How do I tell if the RAMDisk is in operation?

It's folding fine. Puzzling. New record for P8101.
 
lol.

Do you know what thekraken is?

Scorched earth is usually my preferred method as well, but also like to do controlled burns.
 
Code: 
Temperature table:
Node 0	C0:53	C1:53	C2:53	C3:53	C4:53	C5:53	C6:53	C7:53	
Node 1	C0:51	C1:51	C2:51	C3:51	C4:51	C5:51	C6:51	C7:51	
Node 2	C0:55	C1:55	C2:55	C3:55	C4:55	C5:55	C6:55	C7:55	
Node 3	C0:55	C1:55	C2:55	C3:55	C4:55	C5:55	C6:55	C7:55	

Done.
dual6200@dual6200m:~$ ./fahdiag
bash: ./fahdiag: No such file or directory
dual6200@dual6200m:~$ cd $HOME
dual6200@dual6200m:~$ rm -f fahdiag
dual6200@dual6200m:~$ wget https://raw.github.com/team33/fahdiag/released/fahdiag
--2013-04-19 09:09:01--  https://raw.github.com/team33/fahdiag/released/fahdiag
Resolving raw.github.com (raw.github.com)... 199.27.75.133
Connecting to raw.github.com (raw.github.com)|199.27.75.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2247 (2.2K) [text/plain]
Saving to: `fahdiag'

100%[======================================>] 2,247       --.-K/s   in 0.001s  

2013-04-19 09:09:02 (3.90 MB/s) - `fahdiag' saved [2247/2247]

dual6200@dual6200m:~$ chmod +x fahdiag
dual6200@dual6200m:~$ ./fahdiag
fahdiag.sh 0.2
Brought to you by The [H]orde
Copyright (c) 2013
Dave Corfman <davecorfman@gmail.com>
Kris Rusocki <kszysiu@gmail.com>

Detecting FAH directory.
Using /home/dual6200/fah

Hostname: dual6200m
IP: 192.168.0.34

Client running:
dual6200  2839  0.0  0.0 175948  1680 pts/2    Sl+  07:55   0:00 ./fah6 -smp -bigadv

tmpfs:
tmpfs  /home/dual6200/fah  tmpfs  rw,uid=1000,gid=1000  0  0
tmpfs          tmpfs  7.9G  483M  7.4G   7% /home/dual6200/fah
drwxrwxrwt 4 dual6200 dual6200 340 Apr 19 07:57 /home/dual6200/fah

Crontab entry:
00 * * * * fahbackup > /dev/null 2>&1

Restore -- rc.local:
sudo -u dual6200 fahrestore #[H]ardOCP

Backup data:
current
total 494300
-rw-rw-r-- 1 dual6200 dual6200 506163200 Apr 19 09:00 2013-04-19-0900.tar
previous
total 431376
-rw-rw-r-- 1 dual6200 dual6200 441722880 Apr 19 08:00 2013-04-19-0800.tar

Backup-on-shutdown:
-rwxr-xr-x 1 root root 39 Apr  5 08:51 /etc/init.d/fahbackup-rc
lrwxrwxrwx 1 root root 24 Apr  5 08:51 /etc/rc0.d/K10fahbackup-rc -> /etc/init.d/fahbackup-rc
lrwxrwxrwx 1 root root 24 Apr  5 08:51 /etc/rc1.d/K10fahbackup-rc -> /etc/init.d/fahbackup-rc
lrwxrwxrwx 1 root root 24 Apr  5 08:51 /etc/rc6.d/K10fahbackup-rc -> /etc/init.d/fahbackup-rc

Kraken version:
thekraken: The Kraken 0.7-pre15 (compiled Fri Apr  5 08:51:41 PDT 2013 by root@dual6200m)

Kraken wrap:
-rwxr-x--- 1 dual6200 dual6200 6272504 Apr 19 07:57 /home/dual6200/fah/FahCore_a5.exe
-rwxr-xr-x 1 dual6200 dual6200 6272504 Apr  5 08:51 /home/dual6200/fah/thekraken-FahCore_a3.exe
-rwxr-xr-x 1 dual6200 dual6200 6272504 Apr  5 08:51 /home/dual6200/fah/thekraken-FahCore_a4.exe
-rwxr-xr-x 1 dual6200 dual6200 6272504 Apr  5 08:51 /home/dual6200/fah/thekraken-FahCore_a5.exe

Kraken running:
 2866  2868 99.6  27 FahCore_a5.exe
 2866  2872 99.6   8 FahCore_a5.exe
 2866  2873 99.7  31 FahCore_a5.exe
 2866  2874 99.7  21 FahCore_a5.exe
 2866  2875 99.7  22 FahCore_a5.exe
 2866  2876 99.7   0 FahCore_a5.exe
 2866  2877 99.7  17 FahCore_a5.exe
 2866  2878 99.7  26 FahCore_a5.exe
 2866  2879 99.6   6 FahCore_a5.exe
 2866  2880 99.7  28 FahCore_a5.exe
 2866  2881 99.6  15 FahCore_a5.exe
 2866  2882 99.7  30 FahCore_a5.exe
 2866  2883 99.7   2 FahCore_a5.exe
 2866  2884 99.5   3 FahCore_a5.exe
 2866  2885 99.7  29 FahCore_a5.exe
 2866  2886 99.7  19 FahCore_a5.exe
 2866  2887 99.7  13 FahCore_a5.exe
 2866  2888 99.6  12 FahCore_a5.exe
 2866  2889 99.7  20 FahCore_a5.exe
 2866  2890 99.7  18 FahCore_a5.exe
 2866  2891 99.7   7 FahCore_a5.exe
 2866  2892 99.7  23 FahCore_a5.exe
 2866  2893 99.5  14 FahCore_a5.exe
 2866  2894 99.7   5 FahCore_a5.exe
 2866  2895 99.7  16 FahCore_a5.exe
 2866  2896 99.7   2 FahCore_a5.exe
 2866  2897 99.7  25 FahCore_a5.exe
 2866  2898 99.6   1 FahCore_a5.exe
 2866  2899 99.6  11 FahCore_a5.exe
 2866  2900 99.5   4 FahCore_a5.exe
 2866  2901 99.7   9 FahCore_a5.exe
 2866  2902 99.5  10 FahCore_a5.exe

Langouste version:
./fahdiag: line 83: langouste3: command not found

Langouste running:

Langouste -- client.cfg:
username=CrayZ4
team=33
active=no
host=localhost
port=8080

Langouste script version:
md5sum: /home/dual6200/fah/langouste-helper.sh: No such file or directory

Langouste script permission:
ls: cannot access /home/dual6200/fah/langouste-helper.sh: No such file or directory

Langouste -- rc.local:

NUMA -- memory:
/sys/devices/system/node/node0/meminfo:Node 0 MemTotal:        4193320 kB
/sys/devices/system/node/node0/meminfo:Node 0 MemFree:         2766300 kB
/sys/devices/system/node/node1/meminfo:Node 1 MemTotal:        4194304 kB
/sys/devices/system/node/node1/meminfo:Node 1 MemFree:         2933716 kB
/sys/devices/system/node/node2/meminfo:Node 2 MemTotal:        4194304 kB
/sys/devices/system/node/node2/meminfo:Node 2 MemFree:         2767584 kB
/sys/devices/system/node/node3/meminfo:Node 3 MemTotal:        4177920 kB
/sys/devices/system/node/node3/meminfo:Node 3 MemFree:         3214004 kB

Scaling governor: scaling disabled

vmstat -- this will take 10 seconds
32  0      0 11682176  47984 1930000    0    0     0    25 8291  217 89 11  0  0
32  0      0 11683920  47984 1930000    0    0     0     0 8311  347 90 10  0  0
dual6200@dual6200m:~$

I guess it's running, but no console messages. Thanks!
 
If you deleted the cores you will need to wait for the cores to re-download and then you will need to wrap them with the kraken.
 
sc0tty8 said:
lol.

Do you know what thekraken is?

Scorched earth is usually my preferred method as well, but also like to do controlled burns.
Click to expand...

When I said I was clueless, I was not kidding around. :D

ignore.

So be patient. :)
 
It actually isn't.

The fact of FahCore_a5.exe and thekraken-FahCore_a5.exe being of the same size
tells us that core isn't actually wrapped..

Thread list provides additional evidence -- no "thekraken-FahCo" there either.

To fix your issue, do this
Code: 
cd $HOME/fah
thekraken -u
thekraken -w

Then restart your client.

BTW, can you do me a favor? If you have TPC installed, can you run and paste output
of:
Code: 
sudo tpc -htc
 
Last edited:
#1 button pusher reporting for duty.
 
Last edited by a moderator:
I'll let it burn through this job first before making anymore changes. 3.2ghz on $9 copper bricks at 54°C with SE chips. 1.200v. 18:30 TPF on P8101.
 
Last edited:
Then at least run that tpc for me, please.
 
Code: 
Temperature table:
Node 0	C0:53	C1:53	C2:53	C3:53	C4:53	C5:53	C6:53	C7:53	
Node 1	C0:51	C1:51	C2:51	C3:51	C4:51	C5:51	C6:51	C7:51	
Node 2	C0:54	C1:54	C2:54	C3:54	C4:54	C5:54	C6:54	C7:54	
Node 3	C0:54	C1:54	C2:54	C3:54	C4:54	C5:54	C6:54	C7:54	

Done.
dual6200@dual6200m:~$ sudo tpc -htc
TurionPowerControl 0.44-rc2 (export)
Turion Power States Optimization and Control - by blackshard

Hardware Thermal Control Status:

 --- Node 0:
HTC features enabled flag: true. Hardware Thermal Control is enabled.
HTC features currently active (means overheating): false
HTC features has been active (means overheated in past): false
HTC parameters are locked: false
HTC Slew control: by Tctl without Slew register
HTC Limit temperature (equal or above means overheating): 70
HTC Hysteresis temperature (equal or below means no more overheating) : 67
HTC PState Limit: 7

 --- Node 1:
HTC features enabled flag: false. Hardware Thermal Control is disabled.
HTC features currently active (means overheating): false
HTC features has been active (means overheated in past): false
HTC parameters are locked: false
HTC Slew control: by Tctl without Slew register
HTC Limit temperature (equal or above means overheating): 70
HTC Hysteresis temperature (equal or below means no more overheating) : 70
HTC PState Limit: 0

 --- Node 2:
HTC features enabled flag: true. Hardware Thermal Control is enabled.
HTC features currently active (means overheating): false
HTC features has been active (means overheated in past): false
HTC parameters are locked: false
HTC Slew control: by Tctl without Slew register
HTC Limit temperature (equal or above means overheating): 70
HTC Hysteresis temperature (equal or below means no more overheating) : 67
HTC PState Limit: 7

 --- Node 3:
HTC features enabled flag: false. Hardware Thermal Control is disabled.
HTC features currently active (means overheating): false
HTC features has been active (means overheated in past): false
HTC parameters are locked: false
HTC Slew control: by Tctl without Slew register
HTC Limit temperature (equal or above means overheating): 70
HTC Hysteresis temperature (equal or below means no more overheating) : 70
HTC PState Limit: 0


Done.
dual6200@dual6200m:~$

What is that command?
 
Allows us to tell whether CPUs are being (or have been) throttled due to temperature issues.

General examination rule:
1. On G34 one should only check even node numbers (0, 2, 4...)
2. On F / C32 one should check every node

Statuses of interest:
HTC features currently active (means overheating): false
HTC features has been active (means overheated in past): false

If any of these are 'true' -- there's a problem.

It looks like you're ok, though.
 
tear said:
Allows us to tell whether CPUs are being (or have been) throttled due to temperature issues.

General examination rule:
1. On G34 one should only check even node numbers (0, 2, 4...)
2. On F / C32 one should check every node

Statuses of interest:
HTC features currently active (means overheating): false
HTC features has been active (means overheated in past): false

If any of these are 'true' -- there's a problem.

It looks like you're ok, though.
Click to expand...

Thanks a bunch Tear! :cool: I will just do a fresh MI (MuskyInstall) when the job finishes, just to make sure I didn't delete something bad.
 
Umm. I don't believe there's need for such a drastic action.

From fahdiag's output I can see that Kraken seems to be the only item that is out of order.
 
Had this issue on one of my rig. Just do as Tear said.

Unwrap the core (or simply delete core and redownload it). Wrap it .. then run it with autostart.
 
This worked great! :cool: Thanks.

tear said:
It actually isn't.

The fact of FahCore_a5.exe and thekraken-FahCore_a5.exe being of the same size
tells us that core isn't actually wrapped..

Thread list provides additional evidence -- no "thekraken-FahCo" there either.

To fix your issue, do this
Code: 
cd $HOME/fah
thekraken -u
thekraken -w

Then restart your client.
Click to expand...
 
You must log in or register to reply here.
Back
Top