speeding_ant

Any feedback from the email plugin testers?

FYI, SimpleFeatures only uses smartctl for the Disk Health plugin. I agree, I believe Tom has his own implementation for temperature. Not sure why the webGUI is faster - perhaps placebo

V5 plugin or unMenu?

I'll be moving to github with the next major release. Cheers!

Mr. Ant, did you by any chance have time to reproduce those disconnects you were talking about with less than 4095MB of RAM? I'll test in the next week or so.

No need to incorporate the plugin into SF, we just need someone to take the plugin over and maintain it... I helped the guy write the gui for the current APC plugin, and all it really needs is a solid place to store the APC plugin. Anyone? Its missing functionality with APC units that work over Network Management Cards, e.g. AP9619, AP9617 I worked this out a long ways back with JoeL's help (who else right ), I know it's not the majority but having incompleteness is not good (what u dont use today u might want tomorrow). My two Smart-UPS 2200's use network management cards so its a must for me. It's been on the back burner for me until 5.0 Final (true Final). Was that just an updated APC package, or was there more to it?

Latest version of hdparm and smartmontools made a difference to GUI load speed with lots of hard drives, my drive health plugin seems to load a lot faster too. Tom, might be worth including those in the final release - if it's not a big deal.

No need to incorporate the plugin into SF, we just need someone to take the plugin over and maintain it... I helped the guy write the gui for the current APC plugin, and all it really needs is a solid place to store the APC plugin. Anyone?

It should place nice with all plugins (except other email plugins I guess) It also doesn't require the Simple Features base plugin to run.

Hi All, Can I please get some testers for the new mail notification plugin? It uses a bare minimum postfix install, which should only require an email address to configure. You'll need to remove any old email plugins beforehand, including the current SimpleFeatures plugin. Due to the way this type of null client email server works, emails that come from it may go straight to your spam folder. It will require a one-time whitelist of that email via your webmail. This script is meant to be the first rung in the email plugin ladder - SIMPLE. It should work for all, but if you need anything more complex then there are other options (unMenu and the old plugin). It uses Joe.L's email script, with permission from the boss Emails will be sent at the 47th minute of every hour. Cheers https://dl.dropboxusercontent.com/u/86051512/simpleFeatures.email.notifications-1.1.0-noarch-1.plg NOTE: In the Simple Features GUI it currently shows it is not running. This is incorrect. You can verify this by typing: postfix status echo "test" | mail [email protected]

Just for kicks, can you get the same disconnects when you boot that server with less than 4gb ram? Server is configured with 4GB of ram. Do you mean drop it below 4GB and test?

Hi Jowi, I haven't tested, nor will test, older versions of SF against the latest RCs. Current issues are viewable on the google code page, however below are a few examples. • The main page doesn't draw the folder icons on the right. • There is an 'unknown' cause bug, where if you leave the server main page open then you get slower parity sync speeds. Otherwise, I'm happily using it and will continue to. I'm working on a replacement mail plugin right now.

What AFP issues? What does adding the netalk fix for you? I do have a imac that use TimeMachine to save to my unraid. I think it's working fine. I will go confirm now, after reading this. I'm getting random disconnects when dealing with a copy of thousands of files. I've confirmed that Netatalk 2 is the culprit on some other servers I have, Netatalk 3 fixed many issues. I presume the same problems exist with the current version of unRAID. This isn't a deal breaker, as using SMB works just fine for that situation right now. To clarify, Time Machine and AFP works fine for the average home user (like my unRAID server at home).

Happy with the new release! Apart from some AFP issues, which can be resolved when moving to latest netatalk, the FUSE issues have been fixed. Cheers!

I'd rather have a simple "fixed" solution than not have a more complex one ... but I understand your concern. That would simply be a very easy way to minimize what Tom would have to do to provide the capability. In perhaps 5 minutes you can (a) create a GMail account; (b) set a filter to automatically put ALL incoming mail except for one specific sender directly into the trash; and © forward mail from the approved sender to any address of your choice. I just did that for grins .. and it took me less than 3 minutes Actually, by far the simplest solution is to create a Postfix mail server. It involves 3MB worth of binaries, and an automated setup to make sure it's sending from a valid hostname. Once this is done, providing unRAID has access to the internet, it will just send email to wherever you want. It would come from: root@tower (or whatever your hostname is). This is usually what the other NAS products do, and it makes sense. It requires no additional setting up. Postfix is used around the world, it is highly tested, and it just works. You'd limit the setup so it will only receive email from itself (127.0.0.1). I'm in the middle of a test phase for this now. Sounds great ... hopefully you can create a nice simple package for those of us who just want a very easy-to-use solution that will send alerts for key events in UnRAID [Although I'm sure the next "discussion" will be just what is a "key event" -- some of use just want drive failure notifications; others probably want e-mails for just about anything that changes ] That's the aim, make it as simple as possible.

I'd rather have a simple "fixed" solution than not have a more complex one ... but I understand your concern. That would simply be a very easy way to minimize what Tom would have to do to provide the capability. In perhaps 5 minutes you can (a) create a GMail account; (b) set a filter to automatically put ALL incoming mail except for one specific sender directly into the trash; and © forward mail from the approved sender to any address of your choice. I just did that for grins .. and it took me less than 3 minutes Actually, by far the simplest solution is to create a Postfix mail server. It involves 3MB worth of binaries, and an automated setup to make sure it's sending from a valid hostname. Once this is done, providing unRAID has access to the internet, it will just send email to wherever you want. It would come from: root@tower (or whatever your hostname is). This is usually what the other NAS products do, and it makes sense. It requires no additional setting up. Postfix is used around the world, it is highly tested, and it just works. You'd limit the setup so it will only receive email from itself (127.0.0.1). I'm in the middle of a test phase for this now.

Hi All, Yes, I'm waiting for the final version of unRAID before doing any further work on SimpleFeatures. There have been a lot of reports of SF bugs, a lot of which are not caused by SF. Of course, there are a lot of bugs introduced due to somewhat relaxed code revisions and checking from myself and the other contributor (who has disappeared, thanks...). I'm waiting to ensure unRAID development is stable before giving it a proper spank. The next version will have a lot of code ripped out, simplified, and tested thoroughly. I'm in the middle of rebuilding the email notifications plugin - compiling postfix to replace ssmtp (no need to reroute emails through gmail, and complexities with ssl etc). The current version of SimpleFeatures is working with the latest RC however, due to some changes in unRAID, some modifications to the GUI will not be shown. Cheers Andrew

I'll rest after some reports that this bug is fixed I thought netatalk update was next? There's no rest for the weary. Too right.

Testing now - will let you know how it goes.

Just check mine and it is fine using stock web GUI. You using stock or simple features? Reason I ask is that last couple of rc's I've found simple features to be a bit unstable so I removed it. Will revisit post final one a new version comes out. Sent from my Nexus 4 using Tapatalk 2 It's unlikely to be Simple Features. SF will either run, or not run. There may be display bugs introduced because Tom has changed something that hasn't been changed in my code yet, but Simple Features base package cannot introduce instability as it basically runs off the same code and in the same manner as the stock GUI. Cheers

Interesting, I guess they just need slow and cheap storage. Object storage I guess...

I wonder how you interface with the storage.. are they presented as LUNs, FC?

Can you briefly share what you have seen/detected with the "transport endpoint not connected", thanks. The error message is just a symptom that the 'shfs' process has terminated. I have to have plex running a scan and then run a 'find /mnt/user' in a couple windows and once in a while it will fail. But there is nothing output - no syslog messages, no error messages, nothing. Latest run had 'valgrind' watching the process and it has made it through a couple plex scans without failing, and when I terminate the process valgrind shows no memory leaks whatsoever. Another user gets it to fail running rsync, so that's next... This almost sounds like a malloc failure rather then a leak. In the past I've experienced issues with a massive rsync across a huge filesystem would cause OOM errors. Perhaps you need a filesystem with tons and tons of files. Also consider if the end user is running the dir_cache tool, which continually traverses the filesystems with a find. Correct. I run into this issue consistently and have sent many emails to Tom in the past regarding this problem. Currently an unRAID server is sitting in the corner collecting dust, would love to see it up and running again for its intended purpose (nearline archive).

pair.com, great service too.

I don't think there's a reason why you can't use SMB2 for TimeMachine. SMB1 I can understand as TimeMachine requires hard links.