dlandon

While I was testing the rc versions, one of the later rc's broke it and I can't believe how much I missed it. This sucker saved my bacon many times. With the new capability LT has given me, it is now much better because I can do a per share recycle bin. The old way of doing it globally meant the recycle bin was on for every share in the system. No one mentioned anything, but even SMB/NFS shares mounted with UD would have a recycle bin. Not a great way to do things.

The older version is compatible with 6.1 through 6.2.

I put a link to the previous version of the plugin on the OP that can be used to manually install the old version.

If the plugin already got updated, then the autoupdate backup of the .plg is the only way to go back. The current .plg will reference the most recent .txz (not to mention that CA won't even display the plugin unless you enable Show Incompatible Apps within CA settings) The backup plg that AutoUpdate makes will reference an older dated txz (and md5) and will still install assuming that you haven't deleted old txz's from github Besides, its the first time I've had the chance to flog that little feature of AutoUpdate (and been thinking about getting rid of it) All of old versions are left on github.

You can continue to use it. If you try to update it, the new version will error out with a version error and the old version will stay.

Can't he just reinstall it with ca?

Wow. That's esoteric.

OK, so that's normal. Any advise on the "missing csrf_token"? Apparently, it is caused by ANY browser window that was opened (and is still open) before your last reboot. And, apparently, it can be on any computer or device and not necessarily the computer that is displaying the error. There is a difference between missing csrf_token and wrong csrf_token. The missing csrf_token means the post does not have the csrf_token defined. This is a coding issue in the plugin. A wrong csrf_token means the csrf_token passed in is the wrong value. The wrong csrf_token is generally from a stale token from a webgui being open during a reboot. It would pass the old value because the csrf_token is re-genereated on each boot. - Missing csrf_token is a programming problem. - Wrong csrf_token is from a stale value being used and can be fixed by refreshing the page in the open browser.

Both plugins have been updated to handle these errors. It looks like you don't have the latest versions installed. The latest version of UD is 2017.02.04.

Dan, respectfully, please don't terminate the previous version, there will be users who stay with older versions, that's just the way it is, probably always will be. Just a note about the term 'deprecate', when you say something is deprecated, you aren't saying it's terminated, you are saying it's still available and completely usable, but that there's another option that is now preferred over it. For example, Microsoft would say that Windows 7 is deprecated in favor of Windows 10. Many users would disagree, and continue using it. I would prefer that auto update be turned off for the previous version, so that the Recycle Bin still works for all users, no matter what version they decide to use. I updated my post based on your comments to better reflect the situation as it could have been misleading the way it was originally written. The old version will not be removed even if the user tries to upgrade the plugin.

If a user of an older version tries to upgrade, the plugin will fail with a version incompatibility message and leave the old version in place. I don't see any issue here. A new user should use 6.3 and not an older version so a new install of the plugin will be the latest version. You will notice that LT has removed all versions of the OS but version 6.3 from the downloads available on the LimeTech website. Tom is fairly insistent that due to security issues, that users upgrade to 6.3. This is why I decided to drop backwards compatibility. I do not want to support two versions in any way. It is not necessary and it's time to move on. I've already spent MANY hours getting the new version up and running. If someone feels that I absolutely have to do this or they'll explode, how about a contribution?

Yes. Remove the old recycle bin and then use CA to get the latest version. You can do this either before or do this after the update.

The existing recycle bin does not work on the 6.3 final release. I have updated it for 6.3 final, but it will not be backwards compatible because of changes in 6.3 to accommodate other features that broke the recycle bin. This required the recycle bin to be rewritten. The previous version will be deprecated fail to update, so it will not be removed. It will continue to work without any issues. The advantages of the new recycle bin are: - True per share recycle bins. You can specify shares to exclude. - You can optionally exclude all UD devices, or on a per UD share. I will complete testing this weekend and release an updated version.

Post on the fix common problems post for help with install problems. The issue with the disk cache settings is they are setup for small amounts of ram memory and are too large for large amounts of ram memory in a lot of unPAID systems because they are set as a percentage of total memory.

Could this be your problem? Beautiful response from TOM! This could very well be my issue and let me tell you why I think so.. Since updating to the new rc9 there have been a few serious unrelated issues occurring on my server so I now keep the logging window open at all times to monitor events. After the updates to UD & PreClear Disks, I rebooted my server, but left my logging window open. I also launched my IMPI Viewer to monitor reboot routine. When unRAID OS returned, I mounted disks and refreshed the logging window, once refreshed, log events began popping in including errors. Since then, I've uninstalled both plugins, rebooted and the like, but errors wont go away. I use firefox primarily if that matters. *Update* Uninstalled UD plugin, booted into safe mode and got the following csrf errors, see 18:02:35. I also included full syslog from Safe Mode boot Feb 2 18:02:29 Tower kernel: br0: port 1(eth0) entered blocking state Feb 2 18:02:29 Tower kernel: br0: port 1(eth0) entered forwarding state Feb 2 18:02:31 Tower ntpd[1724]: Listen normally on 3 br0 192.168.1.25:123 Feb 2 18:02:31 Tower ntpd[1724]: new interface(s) found: waking up resolver Feb 2 18:02:35 Tower root: error: webGui/include/ProcessStatus.php: wrong csrf_token Feb 2 18:02:36 Tower root: error: webGui/include/ProcessStatus.php: wrong csrf_token Feb 2 18:02:36 Tower emhttp: shcmd (18): rmmod md-mod |& logger Feb 2 18:02:36 Tower kernel: md: unRAID driver removed Feb 2 18:02:36 Tower emhttp: shcmd (19): modprobe md-mod super=/boot/config/super.dat |& logger Feb 2 18:02:36 Tower kernel: md: unRAID driver 2.7.1 installed Feb 2 18:02:36 Tower emhttp: Pro key detected, GUID: 058F-6387-0000-000079010148 FILE: /boot/config/Pro.key ***Bump*** Anymore on this, or am I stuck? If you booted in safe mode, this has to relate to unRAID and not plugins. I would post this on the rc9 release post along with your diagnostics. As Tom has said, the wrong csrf_token is from a stale csrf_token that can happen from a web page needing to be refreshed.

Click the 'Help' button and read. You should find the answer there.

I posted on the rc9 post and this is Tom's response: Could this be your problem?

Hey thanks for the tip... At work currently, but I can remote into my Home PC in a bit and try both tips out and report back later. Hey thanks again!! In the meantime, post the /flash/config/plugins/unassigned.devices*.cfg files. The best I can come up with is there is something about your configuration that is causing a problem. Another idea that is a little easier. Remove the UD plugin and then delete the /flash/config/plugins/unassigned.devices folder. When UD is uninstalled, the configuration files and scripts are left. Removing these would give you a clean install with no devices configured.

It appears the csrf errors are occurring when the UD plugin is installed and then whenever the flash drive is imported. I also see a csrf error related to a dynamix.plg beta or test version. Check and see if you have a dynamix.plg file in /flash/config/pligins/ and remove it. Can you boot in the safe mode and install UD and see if the errors occur then?

UD has been updated to handle the csrf errors generated in 6.3-rc9. What are you doing when these errors occur? I may have missed something. gfjardim has also updated the preclear plugin. Both plugins work for me. Double check to be sure you have the latest versions.

Install the Tips and Tweaks plugin and adjust networking and disk caching. These have caused issues for some. Read the help for information on what to adjust. Also read the Tips and Tweaks posts for ideas.

0,12

I understand what you are saying. I didn't realize that OSX wasn't supported. Based on that you are right, your work should stay here and does not really apply to Windows or Linux. As I said, I'm not an OSX guy.

I see some posting their XML settings to show how they are assigning CPUs. It is very confusing and to some they might feel they need to edit the XML directly and not use the VM editor. My suggestion is to show the thread pairs you are assigning and not the XML results as I have done in the OP. We also need to see your total thread pairs. For example: Thread pairs in system. 0,4 1,5 2,6 3,7 CPU assignment to VM: 1,5 2,6 3,7 Emulator pin: 0,4 This way we can see your system architecture and how you are assigning the CPUs. I've seen other posts where a person only shows their XML CPU assignments when they have 16 or more threads and it's difficult to understand their architecture without reverse engineering. I very strongly discourage editing the XML file directly. There is generally no need to edit the XML file and the VM editor should be used. If you do not know what you are doing, you can create real problems directly editing the XML.

I am not an OSX guy so I don't visit this thread. It was pointed out to me by someone that there was a discussion going on here about CPU pinning to VMs. Your test results are interesting, but contrary in some cases to what seems logical on how to assign CPUs to VMs. You seem to be concentrating on raw horse power and not dealing with latency in a VM. While that is interesting in some cases, it may not apply to real world operation of a VM, like streaming video and audio. I am assuming your VMs are OSX. Most of the VM applications on unRAID are Windows or Linux, not OSX. OSX may deal with hyperthread processors differently than Windows or Linux. I started a post here http://lime-technology.com/forum/index.php?topic=49051.0 to discuss the topic so we could provide some guidance to those having issues in VMs or wanting to tweak their VMs. My main focus was for those having latency issues in VMs that are used in media serving/hosting applications. This is not a criticism of what you have done, but it seems by your posts that you are editing the XML file directly. I see this all the time and highly discourage this practice. Using the VM editor is best. Let it set up all the XML file parameters. There are other parameters that need to be set in the XML like cores and thread assignments. These should not be done manually. I will encourage LT to give us a way with the VM editor to do the emulator pinning, but they are concentrating on the 6.3 release and need to release it for the security updates. If you feel you have some contribution to VM pinning and assignment, post on the topic I started and I will make changes to my OP and update it as we get more experience with CPU pinning and assignment. That way we can keep the information in one place and make it easier for those wanting to experiment with it. It has also been mentioned to me that a video describing VM tuning would be a good idea, but we need to be sure the video incorporates good information. There are many things in unRAID that can affect a VM. Many of the newer builds have large amounts of memory and I have found in my case with 32MB of memory that I had to tweak some disk buffering very low to achieve smooth operation of the VM. My mouse was getting stuck and then jumping all over the place. There is a plugin called Tips and Tweaks that allows adjusting disk buffering. Networking can also affect VMs.