9.10 Stable reports syscall inotify_init1 not implemented

[Tim1962]

Hi, I upgraded from 9.3 to 9.10Stable without problem (well it didn't seem to reboot til I did it) on a HP Microserver.

However since then I am getting daily email reports of daily security run output which AFAIK never reported before. Mainly I have pretty standard config plus Crashplan and Owncloud and not much else.

a. what does it mean (to a layman)?
b. how do I resolve it?

TIA
Tim


nas.local kernel log messages:
linux: pid 15679 (java): syscall inotify_init1 not implemented
linux: pid 17785 (java): syscall inotify_init1 not implemented
linux: pid 21935 (java): syscall inotify_init1 not implemented
linux: pid 23888 (java): syscall inotify_init1 not implemented
linux: pid 25821 (java): syscall inotify_init1 not implemented
linux: pid 27737 (java): syscall inotify_init1 not implemented
linux: pid 29640 (java): syscall inotify_init1 not implemented
linux: pid 31573 (java): syscall inotify_init1 not implemented
linux: pid 33470 (java): syscall inotify_init1 not implemented
linux: pid 35433 (java): syscall inotify_init1 not implemented
linux: pid 39165 (java): syscall inotify_init1 not implemented
linux: pid 41040 (java): syscall inotify_init1 not implemented
linux: pid 44776 (java): syscall inotify_init1 not implemented
linux: pid 46707 (java): syscall inotify_init1 not implemented
linux: pid 48610 (java): syscall inotify_init1 not implemented
linux: pid 50552 (java): syscall inotify_init1 not implemented
linux: pid 52483 (java): syscall inotify_init1 not implemented
linux: pid 54383 (java): syscall inotify_init1 not implemented
linux: pid 56307 (java): syscall inotify_init1 not implemented
linux: pid 58209 (java): syscall inotify_init1 not implemented
linux: pid 60140 (java): syscall inotify_init1 not implemented
linux: pid 62018 (java): syscall inotify_init1 not implemented
linux: pid 63996 (java): syscall inotify_init1 not implemented
linux: pid 67717 (java): syscall inotify_init1 not implemented
linux: pid 69601 (java): syscall inotify_init1 not implemented
linux: pid 71540 (java): syscall inotify_init1 not implemented
linux: pid 73442 (java): syscall inotify_init1 not implemented
linux: pid 75334 (java): syscall inotify_init1 not implemented
linux: pid 77265 (java): syscall inotify_init1 not implemented
linux: pid 79201 (java): syscall inotify_init1 not implemented
linux: pid 81088 (java): syscall inotify_init1 not implemented
linux: pid 83055 (java): syscall inotify_init1 not implemented
linux: pid 86801 (java): syscall inotify_init1 not implemented
linux: pid 89048 (java): syscall inotify_init1 not implemented
linux: pid 90930 (java): syscall inotify_init1 not implemented
linux: pid 92921 (java): syscall inotify_init1 not implemented
linux: pid 94827 (java): syscall inotify_init1 not implemented
linux: pid 96794 (java): syscall inotify_init1 not implemented
linux: pid 98693 (java): syscall inotify_init1 not implemented
linux: pid 729 (java): syscall inotify_init1 not implemented
linux: pid 2688 (java): syscall inotify_init1 not implemented

Checking for packages with security vulnerabilities:
pcre-8.38

 

[dlavigne]

You can ignore it: https://forums.freenas.org/index.ph...on-into-a-jail-freenas-9-2.19868/#post-112341.

 

[Tim1962]

Thankyou. I'll see if I can ignore it

 

[inpowers]

Hi Tim

How did you go with the log messages.
I just updated to 9.10 as you have done and now I am getting the same messages every day.
I have Crashplan running and it seem to be still working but I received a message from Crashplan today stating that I have not backed up in the last three days.
I have checked both the PC and freenas and all looks fine.

 

[SweetAndLow]

You can try to unchecked the watch directory or backup on change settings in crashplan. Only scheduled backups work with freebsd.

 

[inpowers]

Hi SweetAndLow
Is this on the PC being backed up or on the Code42 Crashplan site?

Thanks

 

[SweetAndLow]

The setting is on the freenas crashplan application. Connect to the crashplan jail with the client app and try to turn off that setting.

 

[Tim1962]

Hi Sorry, my internet has been off for the last 3d and a right hassle to sort. I haven't even thought about it as a result and probably wont for a couple of weeks, sorry

 

[inpowers]

Hi SweetAndLow
Now when you say the crashplan client app is that the one on the web site not the PC being backed up?
As I do not have a paid version of crashplan.
I have looked into the setting on the crashplan web site the watch directory is greyed out.
And as for the crashplan on my PC I can't find that setting.

Regards

 

[Kuro Houou]

Did this ever get resolved? I just built a new FreeNAS server (9.11 u2 and now 9.11 u3) and re-installed CrashPlan on it and pointed it to my old backup which worked fine. But as soon as it started backing up new data I noticed all the same errors that the original poster saw. They happen every 2 minutes! On top of that the CrashPlan client on my Windows box crashes shortly after I open it. The two aren't exactly related as the error messages occur even if I don't have the Windows client up. My guess is some error is occurring on the backend dropping the connection for the Windows client and causing it to crash. I thought maybe it was something wrong with my install or config, so I delete the jail and did a complete re-install and still the exact same issue. I tried the suggestion of disabling "watch file system in real time", but that did not help any.