Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
disk_event_handler: disk event handler called for change
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2017-02-15
08:09 AM
2017-02-15
08:09 AM
Starting yesterday morning, several of these pop up in the syslog every few minutes:
# cat /ReadyNAS-Volume/rsyslog/syslog ... Feb 14 11:42:04 Netgear-RN202 disk_event_handler: disk event handler called for change
And I see disk_event_handler here:
# which disk_event_handler /usr/bin/disk_event_handler
I've tried rebooting, stopping & restarting antivirus scanning, a volume defrag, volume scrub and volume balance, but it continues unabated.
This is an RN202 running the latest 6.6.1.
Any idea what's causing this?
Solved! Go to Solution.
Model: RN202|ReadyNAS 202
Message 1 of 4
Labels:
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2017-02-16
02:27 PM
2017-02-16
02:27 PM
Solved. On a whim I did this:
# service webmin stop
and the messages stopped.
Not even sure whether I'll keep webmin around - I was evaluating it. What's especially odd is that several days had elapsed between installing it and when the messages started, but whatever. 🙂
Message 3 of 4
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2017-02-16
07:28 AM
2017-02-16
07:28 AM
Re: disk_event_handler: disk event handler called for change
Since then I've run a disk test (took about 6 hours) that didn't find anything, and the "disk event handler called for change" messages continue.
/usr/bin/disk_event_handler is just a link to rnutil, but the latter is a poorly documented utility.
Usually I'm pretty good at digging into stuff like this, but so far come up empty.
Any suggestions out there?
Message 2 of 4
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2017-02-16
02:27 PM
2017-02-16
02:27 PM
Solved. On a whim I did this:
# service webmin stop
and the messages stopped.
Not even sure whether I'll keep webmin around - I was evaluating it. What's especially odd is that several days had elapsed between installing it and when the messages started, but whatever. 🙂
Message 3 of 4
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2017-02-16
02:28 PM