Plugin changes with 6.11?

[PeterB]

I have a couple of plugins which I created years ago, to run dovecot and mpop on my unRAID server.  I say 'years ago' - the dates on the files are from 2012 - 2014!  If I remember correctly that was when unRAID went to 64 bit!

 

They have been running without change and without problem for eight years.

 

Last night I upgraded to unRAID 6.11 and those two plugins no longer startup.

 

The output is as follows:

Quote

root@Tower:/boot/config/plugins# ls dove*
dovecot-2.2.13-x86_64-4pb.plg
root@Tower:/boot/config/plugins# plugin install dovecot-2.2.13-x86_64-4pb.plg
plugin: installing: dovecot-2.2.13-x86_64-4pb.plg
Executing hook script: pre_plugin_checks
plugin: XML file doesn't exist or xml parse error
Executing hook script: post_plugin_checks
sh: -c: line 1: unexpected EOF while looking for matching `''
sh: -c: line 2: syntax error: unexpected end of file
root@Tower:/boot/config/plugins# 
 

 

I have reverted to unRAID 6.10.3 and the plugins run again.

 

Other plugins I have created still run in 6.11

 

What has changed in 6.11 and what do I need to do to make my plugins fully compatible?

 

Documentation on the plugin system is still seriously lacking!

[primeval_god]

Try using an online xml validator on your plugin source. I had a similar issue with a plugin I maintain. I dont know anything for sure but it seems like they may have tightened up the XML validation for the .plg. For me I needed to use a XML escape character in place of a character in one of my inline bash scripts.

[Squid]

The format of the .plg hasn't changed  As mentioned, the xml doesn't have valid syntax

[PeterB]

Thanks for the responses.

I've put my .plg through two xml validators (w3schools & xmlvalidation.com) both of which report that the file has no errors.

Can anyone recommend a validator which will identify the problem?

 

What are these pre_plugin_checks and post_plugin_checks?

 

These lines after the post_plugin_checks, in particular, suggest, to me, that the file (or whatever is being checked) is empty:

sh: -c: line 1: unexpected EOF while looking for matching `''
sh: -c: line 2: syntax error: unexpected end of file

[PeterB]

11 hours ago, Squid said:

The format of the .plg hasn't changed  As mentioned, the xml doesn't have valid syntax

Not according to the validators I've tried, and something has changed since reverting to 6.10.3 makes the problem go away!

[Squid]

Then post the .plg  There has been zero changes to the specification for .plg's that would break anything from 6.10 -> 6.11, and since 6.0 only additional optional attributes have been added as time goes forward.  

 

pre and post plugin checks are mainly used as hooks for CA so that it knows what's going on.  Nothing strange happening in them

 

[olea]

I got this problem too. After a lot of tests I found plugin requires a full path argument and not a relative one. In the case of OP:

 

plugin install /boot/config/plugins/dovecot-2.2.13-x86_64-4pb.plg

 

and not

 

cd /boot/config/plugins/
plugin install dovecot-2.2.13-x86_64-4pb.plg

 

¯\_(ツ)_/¯