[Plugin] Parity Check Tuning


Recommended Posts

Released version that displays version number of plugin that is running in the plugin's GUI pages (top right).

 

This is to help with a recent report where it appears that the version of the plugin showing as installed in the syslog did not agree with what was showing on the Plugins tab.  Makes it easier to check the version actually running which should help with support going forward.

  • Thanks 1
Link to comment
  • 4 weeks later...
  • 2 weeks later...

I am seeing this over and over in my system log.

How do I resolve?

 

Nov 17 14:57:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Nov 17 14:57:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Nov 17 15:12:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Nov 17 15:12:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Nov 17 15:27:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Nov 17 15:27:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null

Link to comment
8 hours ago, a12vman said:

I am seeing this over and over in my system log.

How do I resolve

What version of the plugin are you using?   There was a bug of this sort some time ago but this should not happen with any recent release.

 

You may find that going into the plugin’s settings and making any change and then hitting Apply may fix things as that causes the cron settings to be regenerated.  

 

BTW:  if you have the latest version of the plugin installed you will see the version number displayed at the top right of the plugins settings.

Link to comment

My Version is 2021.10.10

 

I went into the parity tuning config. Changed my interval from Monthly to Yearly and clicked apply.  The I changed it from Yearly to Monthly and clicked apply.

 

I am still getting these messages in my SysLog:

 

Nov 18 05:48:11 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Nov 18 05:48:11 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Nov 18 05:49:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Nov 18 05:49:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Nov 18 05:56:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Nov 18 05:56:01 MediaTower crond[2014]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null

Link to comment

not sure why you might be seeing this when as far as I know you are the only one.   I need to see why it is happening for you.


to help me look further can you please let me have the .cfg and the .cron files from the plugin’s folder on the flash drive?   If possible I would not mind also a copy of your system’s diagnostics taken after you change a setting in the plugin.   Even better if you can have enabled the Testing mode logging option enable in the plugin’s settings as this will give me more information in the diagnostics.

 

in addition have you managed to reboot the server so that it confirms there is nothing being cached by Unraid in RAM.

Link to comment
  • 1 month later...

Hi @itimpi, a Happy New Year to you. 

Here's a strange one...

 

EDIT: IGNORE THIS....

 

Parity check started (as scheduled) at 02:30 this morning (reported as 02:31 in Unraid and email

Paused at 09:00 this morning (as scheduled) and reported correctly in Unraid and email (so 6 hours 30 minutes roughly)

 

Unraid reports Parity History with a runtime of :

    Elapsed time: 15 hours, 44 minutes (paused) <---- seems very strange

    Current position: 3.52 TB (58.7 %)  <---- seems completely normal

The plugin reports "Version: 2021.10.10"

 

Is there anything that you would like to see?  I have not seen this strange elapsed time report before.   I shall allow the second part of the check to run tonight and let you know what happens.

I am not too worried, if I am honest, but I thought you would like to have the possible bug report.

Take care,

Les.

 

EDIT: So Elapsed time includes the run time and the paused time.  I had not appreciated that, and had thought it only included the active time spent checking parity.  My apologies.

Edited by S80_UK
Link to comment

Unraid has had problems getting times (and speeds) correct when there are pauses involved.

 

the plug-in takes account of this in the messages it generates (as opposed to the ones Unraid generates), and also in the history record written on completion.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.