6 minutes ago, bortsampson89 said:

patching file sbin/mover
Hunk #1 FAILED at 72.
1 out of 1 hunk FAILED -- saving rejects to file sbin/mover.rej


Failed to install patch 20250128204439-pr271.patch Aborting

I get this error when installing the latest patches for 7.0. I'm 99% sure it's because I use the mover fine tuning plugin. It seems the like other patches worked, so I will ignore. 

 

Thanks for pointing this out. If the mover tuning plugin has already modified this file then this will generate an error. Should be ok to ignore, need to see if we can improve this 

Getting an error notification from Fix Common Plugins that this plugin isn't installed, then having the patch name itself being Unraid 7.0 1.0.0 (???), then having the patch installs error out repeatedly isn't exactly instilling a lot of confidence. 

 

Edited January 30, 20251 yr by FACENC

Would you kindly provide instruction for installing this plugin without Community Applications?

the pinned post at the top of every page lets you install CA on OS versions <6.12 and then the patch plugin

44 minutes ago, FACENC said:

Getting an error notification from Fix Common Plugins that this plugin isn't installed, then having the patch name itself being Unraid 7.0 1.0.0 (???), then having the patch installs error out repeatedly isn't exactly instilling a lot of confidence. 

 

The reason for the failure is because you have the mover tuning plugin installed which (against best practices) modifies one of those files that are being patched.   
 

We’re shortly going to release an update that will address this, but the failure is due to mover tuning and not the patch (or the plugin)

3 minutes ago, Squid said:

the pinned post at the top of every page lets you install CA on OS versions <6.12 and then the patch plugin

 

Sorry, what I meant is that I don't want the Community Applications plugin.  I'd like to know how to install the Unraid Patch Plugin without using Community Applications.

2 minutes ago, tkohhh said:

 

Sorry, what I meant is that I don't want the Community Applications plugin.  I'd like to know how to install the Unraid Patch Plugin without using Community Applications.

 

Paste this URL into Plugins, Install Plugin

https://raw.githubusercontent.com/unraid/unraid.patch/refs/heads/main/plugins/unraid.patch.plg

 

Just now, Squid said:

 

Paste this URL into Plugins, Install Plugin

https://raw.githubusercontent.com/unraid/unraid.patch/refs/heads/main/plugins/unraid.patch.plg

 

Awesome, thank you!  Is there a reason why this information isn't more readily available?

 

I mean absolutely no disrespect to you for the work you've done developing CA, but it's just not how I like to interact with my server.  It feels strange to me that Limetech/Unraid seem to take for granted that all users have CA installed.

 

In any case, thanks for the URL!

2 minutes ago, tkohhh said:

Awesome, thank you!  Is there a reason why this information isn't more readily available?

 

Because generally CA is how you install any applications, especially plugins.  That way you only are able to install stuff that has been vetted, is compatible etc.

 

After CA being in existence for almost 10 years, nobody really publishes any URLs for plugins, or for template repositories anymore.

Love the ability to address things quicker and outside of a normal patch window.  Small ask, is it possible to update the version number in someway in the header so that its easy to tell what version I'm on.  This will also make support in the discord easier.  Thanks!

We just need to be able to talk about them in a manner that makes sense.

Edited January 30, 20251 yr by smdion

4 hours ago, smdion said:

Love the ability to address things quicker and outside of a normal patch window.  Small ask, is it possible to update the version number in someway in the header so that its easy to tell what version I'm on.  This will also make support in the discord easier.  Thanks!

We just need to be able to talk about them in a manner that makes sense.

 

Thanks for the feedback. We definitely considered this but any way we changed the version number (either by incrementing it or by tacking on characters) brings its own set of problems that outweighed any benefit. Users who need this information can visit Tools > Unraid Patch, and people providing support can look at the diagnostics (it is in the syslog, and on 7 you can look at system\installed_patches.txt in the diags)

Automatic install who on earth thought this was ok?, If I wanted that I would just run windows.

 

Will have to remove this and not install in future, hopefully it wont be automatically pushed on us.

2 hours ago, ljm42 said:

 

Thanks for the feedback. We definitely considered this but any way we changed the version number (either by incrementing it or by tacking on characters) brings its own set of problems that outweighed any benefit. Users who need this information can visit Tools > Unraid Patch, and people providing support can look at the diagnostics (it is in the syslog, and on 7 you can look at system\installed_patches.txt in the diags)

Thanks for the response.  Is the patch version number that is inside the patch plugin consistent across major/minor versions?  Just trying to think of a human way to talk through stuff without listing out every fix.

 

My sysadmin brain just likes to go "okay, I'm on the current version cuz I see I'm 7.0.0 and patch 1.0.0.", instead of comparing a list of bug fixes.

Edited January 31, 20251 yr by smdion

3 hours ago, Cexitime said:

Automatic install who on earth thought this was ok?

I think they wanted to get the plug-in out in a simplified state to push a CVE patch as soon as it was possible (and with so many people being so update and reboot averse, it was probably for the best), now that that is out of the way they are working on updating this (still optional) plug-in to add some more controls.

 

I suspect some toggles for auto install or manual install will be added very quickly.
Preferably with an option to auto install major CVEs but manually install minor bugfixes and patches.

Will be cool to see in the Page of Unraid Patch, that i have already installed latest/number version of patch or something like this ,

Installed the patch on v7.0 but in the Page of Unraid Patch it still shows v1.0 and button to install it etc ...

1 hour ago, Faceman said:

with so many people being so update and reboot averse

Wonder why that is...

 

1 hour ago, Faceman said:

still optional

For now.

Hello,

 

Attempting to install the below set of 'patches' via the Unraid Patch plugin:

 

Generated the following error:

 

Immediately retried the same process and received the below error:

 

Rebooted unRAID Server and retried the process, received the following error:

 

(Reviewed the 'Unraid Patch' Support Forum and saw some issues with the Mover Tuning Plugin.)

 

Removed the Mover Tuning Plugin:

 

Retried applying patches and received the following error:

(Diagnostics attached.)

 

Please advise.

 

Thanks.

littlebox-diagnostics-20250131-0935.zip

Edited January 31, 20251 yr by PPH
Added diagnostics file.

A reboot would have been necessary.  We are popping out an update to the plugin in a couple of minutes

On today's update the issue with mover tuning is mitigated.

 

During a reboot of the server, the patch plugin will install first before any other plugin.  This allows it to patch the files as set by the OS instead of attempting to patch a file which has been modified (or replaced) by another plugin (eg: Mover Tuning)

 

If a patch fails to install via the GUI, then a reboot will be suggested to perform.

Do you have an ETA for an update where the user can manually install the patches or ignore them? Thank you for your work!

 

Using mover-tuning 

Saw the new patch plugin update install failed.

Rebooted as it told me to do.

Went to plugins and there was a new update for it again,

try to update same error about reboot.

Will try rebooting again.

Ok second reboot got it to update 🤷‍♂️

Hi @Squid,

 

Updated to latest version of unRAID Patch plugin and also rebooted my Server.

 

Plugin now working without issue:

 

 

Thanks for your help.

47 minutes ago, Jaycedk said:

Went to plugins and there was a new update for it again,

 

Yeah, that was my bad.  @ljm42 and myself went through a ton of testing yesterday via a different .plg file and when I did the release this morning, muscle memory dictated that I simply updated the changelog and MD5 in the "normal" plg file and not the one which we were testing -> hence the need for the quick second release.

@Squid Thanks for the clarification 👍