NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNas 6.x SSH / SMB Crash
Hey.... It seems that this is a neverending topic. Also on our System SSH is not starting anymore. Deinstallation of Log Analyzer- the installtion never work probably - with a reboot.... "solve" ...
Hello GiuseppeMa,
It does appear then you did encounter trouble uninstalling and re-installing several add on's after upgrading to the latest firmware which was cause by permission problem. An OS re-install may help address the concern. You may also try the beta firmware 6.8.0.
Regards,
Marty_M
NETGEAR Community Team
Hey
It seems that the installation crash some "main settings"....
I can´t believe that factory default should be the only solution.
No - good - ideas?
system-journal.log
Jul 20 14:09:00 nas-gmn systemd[1]: Configuration file /lib/systemd/system/tracker-miner-fs.service is marked world-writable. Please remove world writability permission bits. Proceeding anyway.
Jul 20 14:09:00 nas-gmn systemd[1]: Configuration file /lib/systemd/system/tracker-extract.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Jul 20 14:09:00 nas-gmn systemd[1]: Configuration file /lib/systemd/system/tracker-extract.service is marked world-writable. Please remove world writability permission bits. Proceeding anyway.
Jul 20 14:09:00 nas-gmn systemd[1]: Configuration file /lib/systemd/system/tracker-store.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Jul 20 14:09:00 nas-gmn systemd[1]: Configuration file /lib/systemd/system/tracker-store.service is marked world-writable. Please remove world writability permission bits. Proceeding anyway.
Jul 20 14:09:00 nas-gmn systemd[1]: Configuration file /lib/systemd/system/tracker-dbus-session.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Jul 20 14:09:00 nas-gmn systemd[1]: Configuration file /lib/systemd/system/tracker-dbus-session.service is marked world-writable. Please remove world writability permission bits. Proceeding anyway.
Jul 20 14:09:00 nas-gmn systemd[1]: Configuration file /lib/systemd/system/tracker-miner-fs.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Jul 20 14:09:00 nas-gmn systemd[1]: Configuration file /lib/systemd/system/tracker-miner-fs.service is marked world-writable. Please remove world writability permission bits. Proceeding anyway.
Jul 20 14:09:00 nas-gmn systemd[1]: Configuration file /lib/systemd/system/tracker-miner-fs.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Jul 20 14:09:00 nas-gmn systemd[1]: Configuration file /lib/systemd/system/tracker-miner-fs.service is marked world-writable. Please remove world writability permission bits. Proceeding anyway.
Jul 20 14:09:00 nas-gmn dbus[2976]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Jul 20 14:09:00 nas-gmn dbus[2976]: [system] Activated service 'org.opensuse.Snapper' failed: The permission of the setuid helper is not correct
Jul 20 14:09:00 nas-gmn readynasd[3193]: Failure (org.freedesktop.DBus.Error.Spawn.PermissionsInvalid).
Jul 20 14:09:01 nas-gmn cron[3030]: (*system*) WRONG FILE OWNER (/etc/crontab)
Jul 20 14:09:01 nas-gmn cron[3030]: (*system*frontview-volumeschedule) WRONG FILE OWNER (/etc/cron.d/frontview-volumeschedule)
Jul 20 14:09:01 nas-gmn cron[3030]: (*system*poweroff) WRONG FILE OWNER (/etc/cron.d/poweroff)
Jul 20 14:09:01 nas-gmn cron[3030]: (*system*spindown) WRONG FILE OWNER (/etc/cron.d/spindown)
Jul 20 14:09:03 nas-gmn readynasd[3193]: sysctl: reading key "net.ipv6.conf.all.stable_secret"
Jul 20 14:09:03 nas-gmn readynasd[3193]: sysctl: reading key "net.ipv6.conf.bond0.stable_secret"
Jul 20 14:09:03 nas-gmn readynasd[3193]: sysctl: reading key "net.ipv6.conf.default.stable_secret"
Jul 20 14:09:03 nas-gmn readynasd[3193]: sysctl: reading key "net.ipv6.conf.eth0.stable_secret"
Jul 20 14:09:03 nas-gmn readynasd[3193]: sysctl: reading key "net.ipv6.conf.eth1.stable_secret"
Jul 20 14:09:03 nas-gmn readynasd[3193]: sysctl: reading key "net.ipv6.conf.lo.stable_secret"
An OS re-install is not the same thing as a factory default. The re-install does not wipe out your data. But it does overwrite most system files, so that could fix the issue. Note that the re-install will set the network to use DHCP and the admin password back to the default.
Same problem here, loganalyzer, and I'm afraid it happened 2 times, 3er time to reinstall everything...
At least now I know the problem.
ReadyNAs 6.8.1
That APP should be removed as it is incompatible and causes big problems.
It is possible that the version of the app is not yet compatible with the ReadyNAS OS6 firmware version. In any case that the app is not yet compatible with the new firmware, it is the
developer that should update their app and submit it to Netgear.
Regards,
Marty_M
NETGEAR Community Team
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
