HDD temperature reached in LaCie Cloudbox, safe temp?

[Cubytus]

Yes that is and with the next version apache server will use also SHA256-signed SSL certificate instead of SHA1 SSL certificate (deprecated)

:thumbup

1/ Can you post your temp-alert.sh

I was about to do that by logging with ssh, but unexpectedly triggered the previous issue I was having. The root password that has been reset to the default using the cron job, is unrecognised. To reproduce: 1- change root password to a custom one 2- reset it using the one-time cron job 3- let the drive go to sleep from overheat. Temperature limit was set at 55.

The alert emails still get the spam marker quite often, despite what you tried to make it more "acceptable" to email servers. Header of the latest shows:

Code: Select all

Content analysis details:   (11.4 points, 5.5 required) pts rule name              description ---- ---------------------- -------------------------------------------------- 0.7 DNS_FROM_AHBL_RHSBL    RBL: Envelope sender listed in dnsbl.ahbl.org 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.0 BAYES_50               BODY: Bayesian spam probability is 40 to 60% [score: 0.4469] 0.1 RDNS_DYNAMIC           Delivered to trusted network by host with dynamic-looking rDNS -0.0 AWL                    AWL: From: address is in the auto white-list
X-Spam-Status: Yes, score=11.4


temp-alert.sh is:

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
echo 60 > /etc/time-suspend.txt
/bin/sync
/sbin/rebootd-spd

2/ check if the nas succeeds to auto-wake-up after 5min
- in putty do

echo 5 > /etc/time-suspend.txt

- Go to the shutdown/restart menu and do a standby with WoL

Did just that. The NAS didn't wake up after 5 minutes, as expected.Well it did, but removed the line

Code: Select all

echo 60 > /etc/time-suspend.txt

after reboot.

I verified the temp-alert.sh file after boot, since the temp guard is started on boot.

[Jocko]

4.3 HELO_DYNAMIC_HCC Relay HELO'd using suspicious hostname (HCC) 4.4 HELO_DYNAMIC_IPADDR2 Relay HELO'd using suspicious hostname

This confirm what I wrote previously :

Replacing the DDNS in the EHLO by [$ippub], it still doesn't trigger spam marking.

So for your smtp server, use public IP is the best as if you use your DDNS you get an high spam score.

So you need to use your public IP in the HELO command.

2d point :
your alert script it is ok but I wanted the file to check if you use Linux encoding for breakline or windows encoding. Can you check this on your side (for all lines of your script).

Well it did, but removed the line
Code:
echo 60 > /etc/time-suspend.txt

after reboot.

My goal was not to check the feature at this level but at a lower level which allows to check the new binary independently with the temp-guard daemon and its shell script.
So can you do a standby wol with an auto wakeup after 5 minutes.

[Cubytus]

Well, it did wake up after I clicked "NAS standby WoL", after 5 minutes, although the process was a bit slow. Should I try again with 60 min? It still doesn't explain why it failed to wake up after 60 mins.

[Jocko]

Hi Cubytus,

Thank you for this last test.

Now, we can be sure that the new wol-fvdw-sl binary runs nice on your NAS.

It still doesn't explain why it failed to wake up after 60 mins.

As temp-guard daemon is the same and only temp-alert.sh is new with the line echo yy > /etc/time-suspend.txt, the issue is here.

Can you attach your shell script file?

and the output of

Code: Select all

ls -l /etc/temp-alert.sh

[Cubytus]

I have the script:

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
echo 60 > /etc/time-suspend.txt
/bin/sync
/sbin/rebootd-spd

Then the output is:

Code: Select all

-rwxrwxrwx  1 nobody nobody 162 2015-08-13 08:33 /etc/temp-alert.sh

[Jocko]

Cubytus,

my asking was to attach the file because there is no shell syntax error with your file but I suspect an error with the breakline encoding.

[Jocko]

I made a test

I added a windows break-line (\r\n) instead of a linux break-line (\n) with the line

Code: Select all

echo 60 > /etc/time-suspend.txt

as it is the only line you had edited after enabling the temp guard daemon.

In this case, the file time-suspend.txt does not contain the standby value !

Code: Select all

root@Acrab:/etc # sh -x temp-alert.sh
+ /usr/bin/php /etc/api/nasapi.php mrvlNotify 5 60 1 xxxxxxxxxxxxxxxxxxxxxx 5
0+ touch /etc/wolenable
+ echo 60
+ /bin/sync
root@Acrab:/etc # cat /etc/time-suspend.txt

root@Acrab:/etc #


(I disabled rebootd-spd)

Then wol-fvdw-sl waits only for waking up the NAS to receive a magic packet!

I am now pretty sure that you have this issue.

2d point :
your alert script it is ok but I wanted the file to check if you use Linux encoding for breakline or windows encoding. Can you check this on your side (for all lines of your script).

[Cubytus]

temp-alert.sh.zip

Here it is.

[Jocko]

:scratch
This version is fully ok.

So there is no reason that it does not work (wol binary ok; shell script ok and no change for the temp guard daemon) and nothing else to deepen.

[Cubytus]

Maybe a functionality in the CloudBox that prevents it to return to an active state after too long a wait time? When the sleep state is so deep that an ordinary command can't wake it up?