unraid_notify 2.55 [01-01-2010]: Email notifications for unRAID status


Recommended Posts

Sorry for maybe a stupid question but what is the difference between the spin down timer here and the one already in Unraid (4.3), I am sure there is a difference just not sure what it is  ;D

 

I thought my drives already spin down the drives after an 1 hour.

 

Thanks,

Link to comment
  • Replies 235
  • Created
  • Last Reply

Top Posters In This Topic

The spin down timer in unRAID 4.3 uses the drives firmware to spin down the drive (tells the drive to spin itself down after x of inactivity).  The spin down timer in unraid_notify (and unRaid 4.4) monitors disk activity (read and writes) and instructs the drive to spin down, regardless of the firmware. 

 

Why do it this way?  Things like checking the disk temp., smart status, etc. look like activity to the disk firmware, and won't let the drive spin down.  Doing it outside the disk firmware, we only monitor actual reads or writes to the disk, not checks of smart status, etc.

 

In short, if you want to periodically monitor the status of the disk, you can't use the drives firmware (the way unRAID 4.3 does it) for spinning down the drive.

 

Link to comment
  • 4 weeks later...
  • 4 weeks later...

hey guys,

 

I'm pretty sure I've done all the steps but I still can't get any email using my Sympatico account

 

 

Tower login: root

Password:

Linux 2.6.24.4-unRAID.

root@Tower:~# installpkg /boot/unraid_notify-2.20-noarch-unRAID.tgz

  unraid_notify startInstalling package unraid_notify-2.20-noarch-unRAID...

PACKAGE DESCRIPTION:

unraid_notify: unraid_notify  Control scripts for the unRAID server Environment.

unraid_notify:

unraid_notify: Summary:

unraid_notify: The purpose of this script is to check the status of the unRAID

unraid_notify: array by searching the /proc/mdcmd file for known bad states.

unraid_notify:

unraid_notify: Configure options in /boot/config

unraid_notify:

Executing install script for unraid_notify-2.20-noarch-unRAID...

root@Tower:~#    unraid_notify start

unraid_notify started

root@Tower:~#    unraid_notify -d

>

< 220 toip6.srvr.bell.ca ESMTP

> HELO Tower

< 250 toip6.srvr.bell.ca

> AUTH LOGIN

< 503 #5.3.3 AUTH not available

503 #5.3.3 AUTH not available

root@Tower:~# 

 

Any ideas? Thanks

Link to comment
  • 3 weeks later...
  • 2 weeks later...

# Choose the critical disk temp. (in celsius) that will cause unraid_notify to execute an external

# command (like powerdown - see: http://lime-technology.com/wiki/index.php?title=Powerdown_script )

CriticalDiskTemp = 37

CriticalDiskCommand = powerdown

 

 

This should power down my machine when 37 C is reached right?

Does not work if a file is open (like watching a video file). I guess I'm doing something wrong.

The powerdown script is installed and working when executed manually with "powerdown" trough telnet.

 

# Choose the maximum temp. (in celsius) a disk may get before an error will message will be sent.

MaxDiskTemp = 30

 

This does send me an email though.

 

 

Values set low just for testing...

Link to comment
  • 2 weeks later...

I can't get E-mail to work... 

 

root@Tower:~# unraid_notify -d
>
< 220 equipment to accept, transmit, or distribute unsolicited e-mail.
> HELO Tower
< 250 elasmtp-kukur.atl.sa.earthlink.net Hello Tower [209.113.159.130]
> AUTH LOGIN
< 503 AUTH command used when not advertised
503 AUTH command used when not advertised

 

Using stuff from another thread.. I get

 

root@Tower:~# telnet smtpauth.earthlink.net 25
Trying 207.69.189.204...
Connected to smtpauth.earthlink.net (207.69.189.204).
Escape character is '^]'.
220-elasmtp-spurfowl.atl.sa.earthlink.net ESMTP Exim 4.67 #1 Tue, 20 Jan 2009 17:59:36 -0500
220-NO UCE.  EarthLink does not authorize the use of its computers or network
220 equipment to accept, transmit, or distribute unsolicited e-mail.
EHLO
250-elasmtp-spurfowl.atl.sa.earthlink.net Hello  [209.113.159.130]
250-SIZE 14680064
250-PIPELINING
250-AUTH PLAIN LOGIN CRAM-MD5
250-STARTTLS
250 HELP
help
214-Commands supported:
214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP
quit
221 elasmtp-spurfowl.atl.sa.earthlink.net closing connection
Connection closed by foreign host.

 

Where do I go from here?  I'm no smtp expert!  ???

 

I know this works somewhat because I can send through my old netscape e-mail program and I've setup through my backup utility to send mail (acronis)

 

Jim

Link to comment

I removed my username and passwrd and just like I thought..

 

root@Tower:/boot/config# unraid_notify -d
>
< 220 equipment to accept, transmit, or distribute unsolicited e-mail.
> HELO Tower
< 250 elasmtp-banded.atl.sa.earthlink.net Hello Tower [76.119.47.209]
> MAIL FROM: <[email protected]>
< 250 OK
> RCPT TO: <Itdoesnt.work.com>
< 550 Please configure your mail client to use authentication.
550 Please configure your mail client to use authentication.

 

What's next?  any other thoughts?  *pout*

 

 

Link to comment

Do they require SSL? if they do then you need to set the port to 465 and install the socat package.

 

Nope..  My other setups use plain old port 25

 

Probably would not hurt to try with SSL and the socat package.

 

Even if it shows in your other setup as using port 25 it might be using SSL which MAKES it use 465.

Link to comment

Probably would not hurt to try with SSL and the socat package.

 

Even if it shows in your other setup as using port 25 it might be using SSL which MAKES it use 465.

 

I don't think so..  SSL box is un checked.  See pic. 

 

 

Hum, try following some of these settings and make yours similar.  The only thing i can think of is that you need to use your full e-mail address for the username.

 

CRAP! forgot link

 

http://www.ehow.com/how_2175814_setup-earthlink-email-outlook.html

http://www.broadbandreports.com/faq/5718

Link to comment

The problem seems to be that Earthlink appears to reject any authentication from MTAs that use "HELO" instead of "EHLO".

 

This is a simple fix, but unfortunately my unraid server is down right now.

 

The change is in bashmail (/usr/bin/bashmail)

 

Changing line:

mail_chat "HELO $(hostname)"

to:

mail_chat "EHLO $(hostname)"

 

After I get unraid up and running again, I'll release a new unraid_notify.

 

Link to comment

 

Changing line:

mail_chat "HELO $(hostname)"

to:

mail_chat "EHLO $(hostname)"

 

That seems to have worked..

root@Tower:/boot/config# unraid_notify -d
>
< 220 equipment to accept, transmit, or distribute unsolicited e-mail.
> EHLO Tower
< 250 HELP
> AUTH LOGIN
< 334 blah
> moreblash==
< 334 evenmoreblah
> blah
< 235 Authentication succeeded
> MAIL FROM: <[email protected]>
< 250 OK
> RCPT TO: <[email protected]>
< 250 Accepted
> DATA
< 354 Enter message, ending with "." on a line by itself
> .
< 550 Your message does not conform to RFC2822 standard
550 Your message does not conform to RFC2822 standard

 

does this mean I should get a piece of mail?  I haven't yet...

 

Thanks all for the help so far!  I'm close!

 

Link to comment

No.  Unfortunately the mail server is complaining that the message does not conform to RFC2822.

 

I don't have an Earthlink email account to do further testing.  If you trust me, you can PM me your username and password, else I'll have to see if I can find another way to isolate what in the message is triggering the non-compliance issue.

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.