[SOLVED] Minor script errors on boot caused by unknown plugin

[weirdcrap]

Decided to dive straight into beta 35 (from stable) with my backup server to get ahead of any issues I might encounter as my backup and main are configured very similarly.

 

I've noticed two innocuous errors on the monitor attached to the server. They don't show up in the logs anywhere that I can find and there is nothing preceding or following them.

 

I rebooted into safe mode and those two lines don't appear. So it has something to do with a plugin, but I'm not sure how to go about figuring out which one. I poked through the beta threads and tried some searching but didn't see this mentioned anywhere else yet.

 

I haven't noticed any lost or broken functionality yet, so they appear to be harmless but I would feel better knowing where they are coming from and what if any damage it may cause.

 

Diagnostics:

void-diagnostics-20201203-1515.zip

Edited December 4, 2020 by weirdcrap

[trurl]

Looks like many of your plugins are not up-to-date. Take care of that and see what happens.

[weirdcrap]

7 minutes ago, trurl said:

Looks like many of your plugins are not up-to-date. Take care of that and see what happens.

The update checker in UnRAID disagrees with you. I assumed I was all good. How do I tell which are out of date if I can't trust the updater?

 

EDIT: I even have automatic weekly plugin updates turned on in Squid's plugin.

Edited December 3, 2020 by weirdcrap

[trurl]

Looks like you're right, I just thought some of them should have newer dates than that.

 

 

[weirdcrap]

1 minute ago, trurl said:

Looks like you're right, I just thought some of them should have newer dates than that.

 

 

I did remove Docgyver's SSH and denyhosts plugins after the beta update as they were quite old and I saw the SSH changes made in beta 25.

 

I initially thought they might be my problem but even after removing those and rebooting this persisted.

[Squid]

It's actually UD.  First time I've turned on my monitor in about a year and the same thing is there. @dlandon

[weirdcrap]

9 minutes ago, Squid said:

It's actually UD.  First time I've turned on my monitor in about a year and the same thing is there. @dlandon

Nice, how did you figure this out? Something in my diags?

[Squid]

That way that I did it was to look at all the .plgs within /boot/config/plugins and see which code section was long enough to hit a line 87 and then copied / pasted that section and saw that line 87 contained an ==, then uninstalled the plugin rebooted and saw the error didn't reappear.

 

The way most people would have done it is uninstall one by one followed by a reboot and see when the error disappeared.

[dlandon]

1 hour ago, Squid said:

It's actually UD.  First time I've turned on my monitor in about a year and the same thing is there. @dlandon

Got it.  Fixed in the next release.

[Squid]

1 hour ago, trurl said:

Looks like you're right, I just thought some of them should have newer dates than that.

 

Forgivable.  When was the last time CA didn't have an update for this long?

[weirdcrap]

1 hour ago, Squid said:

That way that I did it was to look at all the .plgs within /boot/config/plugins and see which code section was long enough to hit a line 87 and then copied / pasted that section and saw that line 87 contained an ==, then uninstalled the plugin rebooted and saw the error didn't reappear.

 

The way most people would have done it is uninstall one by one followed by a reboot and see when the error disappeared.

Oh yeah I thought about trying to dig through the PLGs myself but I didn't really know what I was looking for so I figured asking would be quicker. I'd just have a million questions about the PLGs instead lol.

 

@dlandon thank you for the quick fix! Glad it wasn't anything serious.

[DuRunyu]

This may be a problem of "Unassigned Devices" 2020.11.28c, there will be no such prompt after uninstalling