HDD temperature reached in LaCie Cloudbox, safe temp?

[Cubytus]

And it still is marked as spam:

Code: Select all

Content analysis details:   (13.3 points, 5.5 required) pts rule name              description ---- ---------------------- --------------------------------------------------
0.7 DNS_FROM_AHBL_RHSBL    RBL: Envelope sender listed in dnsbl.ahbl.org
3.5 BAYES_99               BODY: Bayesian spam probability is 99 to 100% [score: 1.0000]
4.3 HELO_DYNAMIC_HCC       Relay HELO'd using suspicious hostname (HCC)
4.4 HELO_DYNAMIC_IPADDR2   Relay HELO'd using suspicious hostname (IP addr 2)
0.0 FH_HELO_EQ_D_D_D_D     Helo is d-d-d-d
1.9 TVD_RCVD_IP            TVD_RCVD_IP
0.1 RDNS_DYNAMIC           Delivered to trusted network by host with dynamic-looking rDNS
-1.6 AWL                    AWL: From: address is in the auto white-list
X-Spam-Status: Yes, score=13.3

[Jocko]

Hi Cubytus,

I am lost... In some previous posts you reported the opposite.
And currently, I see nothing else to do.

So replace [$ippub] by your no-ip DNS.

As wrote previously I had also done some other tests with another provider with spam-assasin and I got a very low score.
Please to note, I used as domain ddns.net instead of no-ip.org which is well knew to be used by spammer and hacker. (some month ago, M$ had blocked these addresses on its servers)

[Cubytus]

That's what I did in the previous version, and the spam score was still too high… I don't understand either :thinking It has been years I use these no-ip.org extensions

[Jocko]

Maybe you should read this : http://www.noip.com/blog/2014/06/30/ips ... -takedown/

I believe that your smtp provider takes similar rules to blacklist these domains

[Cubytus]

I misunderstood you....
So there is no reason so that the temp-guard may not run with an auto-wake up.

Maybe you should make another try

Just did. It automatically turned off that night at 4:47 ,but never came back online at 5:47 as it would have been expected.

Interestingly, the time-suspend.txt file contains the value "0", and not "60", as expected.

Code: Select all

-rw-r--r--  1 root   root         1 2015-08-20 04:48 time-suspend.txt

Listing shows it hasn't been touched by the reboot at 11:25.

But temp-alert.sh "lost" its time value command upon manual reboot.

Code: Select all

#!/bin/sh
/usr/bin/php /etc/api/nasapi.php mrvlNotify 5 55 1 00:D0:4B:94:3C:26 0
touch /etc/wolenable
/bin/sync
/sbin/rebootd-spd


By the way, /etc/wolenable doesn't exist. Maybe that's why it doesn't work using the script, but does when manually put in automatic wake-up WoL?

[Jocko]

Hi Cubytus,

But temp-alert.sh "lost" its time value command upon manual reboot.

This is the expected behaviour, temp-alert.sh is overwritten in accordance with the nas database. Then your custom line is removed.
attached a file to fix it. So copy the file daemonfunc_tempguard_commit.finc in the folder /etc/finc.

Currently the suspend time is 60, you can change it by editing the line 79

Code: Select all

fwrite($fp,"echo 60 > /etc/time-suspend.txt\n");

By the way, /etc/wolenable doesn't exist.

This is the expected behaviour. Please to note that temp-alert.sh creates this file

Code: Select all

touch /etc/wolenable

Interestingly, the time-suspend.txt file contains the value "0", and not "60", as expected.

This seems to be also the expected behaviour: wol-fvdw-sl resets it and note this last modified time is 1' after the NAS turned off at 4:47.

It automatically turned off that night at 4:47 ,but never came back online at 5:47 as it would have been expected

This is really amazing and I have no explanation :scratch

[Cubytus]

Ok, I replaced said file with the updated version, corrected temp-alert.sh. I guess I'll just wait for it to overheat again (shouldn't take too long, unfortunately). Would there be a trace somewhere in the logs when it fails to restart? If the CPU and RAM stay active?

[Cubytus]

Update: after a particularly hot night, the NAS stopped at 3:11, and resumed activity at 4:12. Success!

[Jocko]

Nice :thumbup