Hello;

I know this tool is not developed anymore /and all discussions dried out about 3-4 months ago - but those still using it, perhaps can assist with a setup question.

 

I just installed  checksum suite, and it complained of inotifywait not installed.

 

After going back and forth several times (because I already had Nerdpack installed), i discovered that Inotify needed to be set to monitor directories. I configured it, but then none of those directories I've set in the confguration menu, made it into the config file. That stayed sample.conf, and if I deleted it, it got recreated again upon starting inotify docker.

I then edited renamed sample.conf to inotify.conf, and entered all the directories. Since the default command directive  - present in the sample - didn't make sense, I commented it out.

I restarted inotify, but it died right away, since it was missing the command directive.

I figured the command has to point to checksum suite somehow, but it is not obvious.

Anyone caring to point me in the right direction?

Thank you!

Hello;

I know this tool is not developed anymore /and all discussions dried out about 3-4 months ago - but those still using it, perhaps can assist with a setup question.

 

I just installed  checksum suite, and it complained of inotifywait not installed.

 

After going back and forth several times (because I already had Nerdpack installed), i discovered that Inotify needed to be set to monitor directories. I configured it, but then none of those directories I've set in the confguration menu, made it into the config file. That stayed sample.conf, and if I deleted it, it got recreated again upon starting inotify docker.

I then edited renamed sample.conf to inotify.conf, and entered all the directories. Since the default command directive  - present in the sample - didn't make sense, I commented it out.

I restarted inotify, but it died right away, since it was missing the command directive.

I figured the command has to point to checksum suite somehow, but it is not obvious.

Anyone caring to point me in the right direction?

Thank you!

All of the comments regarding sample.conf are presumably all part of inotifywait.  IIRC all you have to do is use NerdPack plugin to install inotifywait, and then run checksum, and set up the directories there.  Checksum makes a copy of inotifywait (so that it can enable / disable it no problems)

That was fast!

Thank you for your reply. Essentially that's what I did. But nothing happened with inotifywait config file.

Again - steps I've taken:

- already had the NerdPak installed, long time ago. It also was up-to-date.

- today I just installed checksum suite. It complained about inotifywait not running right after installation.

- I thought NerdPak doesn't have inotify tools, and added the plugin again, but nothing happened, since it was already installed.  I could perhaps have uninstalled it, and reinstalled.

- then I went to checsum (Create/Monitor settings) and started adding directories in the setup, such as /dir1 .../mnt/user/pictures; /dir2 .... /mnt/user/Education etc.

- At the top of the page however I continue to have "Monitor Status: inotifywait NOT installed"

- In docker dashboard, Inotify-command is not running. If I start it manually, it complains that the conf file I created is missing the command directive (which is true, because I commented it out when I edited manually the conf file). Inotify otherwise did not pick -up any config from checksum.

 

Thanks again for your help.

hg

 

 

 

You have to tell nerd pack to install inotifywait in its settinfs

 

Sent from my LG-D852 using Tapatalk

 

 

Aha! got it now! Thanks so much!

 

I didn't realized that the nerd pack was downloaded but not installed. I just turned on all the tools in the pack and inotify among them.

Went back to checksum added one more directory in the configuration, and this time it didn't complain about inotifywait anymore. It just asked me to restart the monitor, and I did, and it appears that now it started: Monitor Status: Running Checksum Calculations Idle Verifier Status: Idle

Now one last question: do I need to start a manual checksum first, or will it do it alone? - not finding any checksum (this is the first time it is running).

 

Much appreciated.

 

Next time there's a change to a monitored folder it will create everything within it

 

Sent from my LG-D852 using Tapatalk

 

 

Perfect. Thank you!

Squid great plugin, thank you.

 

Have some question,

 

when i rename file in monitored share no scan command received,

but when open file with nano without editing scan command received.

 

is it ok?

Squid great plugin, thank you.

 

Have some question,

 

when i rename file in monitored share no scan command received,

but when open file with nano without editing scan command received.

 

is it ok?

Since this would have affected me (the rename) (good catch -> never noticed it) I've fixed it... Updated to 2016.08.26

 

As far as editing in nano with no changes being made and a scan being issued, its because nano opens files in rewrite mode.  Once the file is closed, the only way to tell if the file was actually changed is for a scan to take place  (since the filemtimes don't actually change, no actual update of the hash will take place)

wow fast response, work like a charm 

seems no catch for delete event

Deletes don't matter.  The entry in the hash file will still exist.  If the file gets recreated then the hash will get updated automatically

 

Sent from my LG-D852 using Tapatalk

 

 

@Squid:

Thank you very much for developing this great plugin. I'm still using it to get the corz compatible hash files directly without having to copy them every time I export from bonienls plug.

 

I have little problem though:

Nov 27 18:44:03 lafiel crond[1564]: failed parsing crontab for user root: /usr/local/emhttp/plugins/checksum/scripts/verifyShare.php "/mnt/user/Anime" &>/dev/null 2>&1
Nov 27 18:44:03 lafiel crond[1564]: failed parsing crontab for user root: /usr/local/emhttp/plugins/checksum/scripts/verifyShare.php "/mnt/user/Filme" &>/dev/null 2>&1
Nov 27 18:44:03 lafiel crond[1564]: failed parsing crontab for user root: /usr/local/emhttp/plugins/checksum/scripts/verifyShare.php "/mnt/user/Multimedia" &>/dev/null 2>&1
Nov 27 18:44:03 lafiel crond[1564]: failed parsing crontab for user root: /usr/local/emhttp/plugins/checksum/scripts/verifyShare.php "/mnt/user/SecDrive" &>/dev/null 2>&1

 

I get this error messages in my log. And they seem to be related to this plugin. Is there any way to remove them?

 

cheers

 

Slrg

@Squid:

Thank you very much for developing this great plugin. I'm still using it to get the corz compatible hash files directly without having to copy them every time I export from bonienls plug.

 

I have little problem though:

Nov 27 18:44:03 lafiel crond[1564]: failed parsing crontab for user root: /usr/local/emhttp/plugins/checksum/scripts/verifyShare.php "/mnt/user/Anime" &>/dev/null 2>&1
Nov 27 18:44:03 lafiel crond[1564]: failed parsing crontab for user root: /usr/local/emhttp/plugins/checksum/scripts/verifyShare.php "/mnt/user/Filme" &>/dev/null 2>&1
Nov 27 18:44:03 lafiel crond[1564]: failed parsing crontab for user root: /usr/local/emhttp/plugins/checksum/scripts/verifyShare.php "/mnt/user/Multimedia" &>/dev/null 2>&1
Nov 27 18:44:03 lafiel crond[1564]: failed parsing crontab for user root: /usr/local/emhttp/plugins/checksum/scripts/verifyShare.php "/mnt/user/SecDrive" &>/dev/null 2>&1

 

I get this error messages in my log. And they seem to be related to this plugin. Is there any way to remove them?

 

cheers

 

Slrg

What's the output of

crontab -l

 

Try just changing the verify time settings in the plugin for those shares.

crontab -l shows:

# If you don't want the output of a cron job mailed to you, you have to direct
# any output to /dev/null.  We'll do this here since these jobs should run
# properly on a newly installed system.  If a script fails, run-parts will
# mail a notice to root.
#
# Run the hourly, daily, weekly, and monthly cron jobs.
# Jobs that need different timing may be entered into the crontab as before,
# but most really don't need greater granularity than this.  If the exact
# times of the hourly, daily, weekly, and monthly cron jobs do not suit your
# needs, feel free to adjust them.
#
# Run hourly cron jobs at 47 minutes after the hour:
47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null
#
# Run daily cron jobs at 4:40 every day:
40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null
#
# Run weekly cron jobs at 4:30 on the first day of the week:
30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null
#
# Run monthly cron jobs at 4:20 on the first day of the month:
20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null
/usr/local/emhttp/plugins/checksum/scripts/verifyShare.php "/mnt/user/Anime" &>/dev/null 2>&1
/usr/local/emhttp/plugins/checksum/scripts/verifyShare.php "/mnt/user/Filme" &>/dev/null 2>&1
/usr/local/emhttp/plugins/checksum/scripts/verifyShare.php "/mnt/user/FilmeMarco" &>/dev/null 2>&1
/usr/local/emhttp/plugins/checksum/scripts/verifyShare.php "/mnt/user/Multimedia" &>/dev/null 2>&1
/usr/local/emhttp/plugins/checksum/scripts/verifyShare.php "/mnt/user/SecDrive" &>/dev/null 2>&1

The share verification shedules are set to never. If I change them to run again, the errors vanish. If I disable them (set them to never) the jobs seem to get added to the crontab without times instead of removing them completely. This causes the cron errors in the log.

For now I'll manually remove them via crontab -e. This needs to  be done after every reboot however. It would be cool if you can fix this in a future version. Take your time. I know you are not actively developing this anymore.

For now I'll manually remove them via crontab -e. This needs to  be done after every reboot however. It would be cool if you can fix this in a future version. Take your time. I know you are not actively developing this anymore.

I'm amazed that I missed that one way back when    Check for updates 

I know that feeling from some of my development projects. It works fine now. Thank you very much for the fix! It is a great plugin.

FYI - now iNotify is built-in to 6.3, the plugin no longer detects it.

 

SR

Hadn't noticed.  The scripts however still seem to work as they've been generating hashes for me.  I'll check it out

 

Sent from my LG-D852 using Tapatalk

 

 

That was quick...

 

After looking a bit deeper it does appear that the monitor is working, although I get the "iNotify NOT installed" pop-up when accessing the settings, and the monitor status shows as not installed.

 

SR

That was quick...

 

After looking a bit deeper it does appear that the monitor is working, although I get the "iNotify NOT installed" pop-up when accessing the settings, and the monitor status shows as not installed.

 

SR

Works fine on my systems (6.3.1)  I don't have NerdPack installed, and can still hit Checksum's GUI without any complaints about inotify not being installed 

Oh well...

 

No biggy, it is working despite the error and I don't access the settings enough for it to be really annoying.

 

I know you're not really supporting this anymore, so thanks for looking.

 

SR

Oh well...

 

No biggy, it is working despite the error and I don't access the settings enough for it to be really annoying.

 

I know you're not really supporting this anymore, so thanks for looking.

 

SR

This is odds on why you're seeing the error: http://lime-technology.com/forum/index.php?topic=44989.msg541991#msg541991  You installed and subsequently removed the Dynamix File Integrity plugin.

Hi, I'm aware that you're no longer working on this anymore, but I was just wondering if there's a way to set a single global checksum file in the share root instead of in each folder, like what can be done with corz.
I love the ability to read corz checksums, and I thought I'd ask before moving to something like running a vm. I already have ~30TB of hashes, so doing them again isn't something I'm considering.

Edited April 26, 20179 yr by Coffee_Aluminum

No, the plugin doesn't have an option to create hashes with paths.  I'm not 100% sure if I programmed it to recognize paths in the hash files on scheduled verifications either....

2 minutes ago, Squid said:

No, the plugin doesn't have an option to create hashes with paths.  I'm not 100% sure if I programmed it to recognize paths in the hash files on scheduled verifications either....

No worries, thanks for the super-quick reply!