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,
ok... agree - Sorry. I assumed it´s a general issue.
We are talking about an RN 316 with Firmware 6.7.5
during Firmware 6,7.4 - one month ago - the Installation of the Application LogAnalyzer was done and failed.
the LogAnalyzer never run.
A uninstallation of the application failed.
Update Firmware to 6.7.5.
Installation of ReadyNAS Surveillance - failed also.
Reboot the system. Deinstallation of ReadyNAS Surveillance - ok.
Deinstallation of LogAnalyzer also okay.
SSH failed.
Reboot. SSH starts. SMB Failed.
argh...
and that is the acutal status.
in the Systemd-Journal log i find entry´s like:
Jul 18 16:14:45 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 18 16:15:01 nas-gmn cron[3030]: (*system*) WRONG FILE OWNER (/etc/crontab)
Jul 18 16:15:01 nas-gmn cron[3030]: (*system*frontview-volumeschedule) WRONG FILE OWNER (/etc/cron.d/frontview-volumeschedule)
Jul 18 16:15:01 nas-gmn cron[3030]: (*system*poweroff) WRONG FILE OWNER (/etc/cron.d/poweroff)
Jul 18 16:15:01 nas-gmn cron[3030]: (*system*spindown) WRONG FILE OWNER (/etc/cron.d/spindown)
Jul 18 16:16:01 nas-gmn cron[3030]: (*system*) WRONG FILE OWNER (/etc/crontab)
Jul 18 16:16:01 nas-gmn cron[3030]: (*system*frontview-volumeschedule) WRONG FILE OWNER (/etc/cron.d/frontview-volumeschedule)
Jul 18 16:16:01 nas-gmn cron[3030]: (*system*poweroff) WRONG FILE OWNER (/etc/cron.d/poweroff)
Jul 18 16:16:01 nas-gmn cron[3030]: (*system*spindown) WRONG FILE OWNER (/etc/cron.d/spindown)
Jul 18 16:17:01 nas-gmn cron[3030]: (*system*) WRONG FILE OWNER (/etc/crontab)
Jul 18 16:17:01 nas-gmn cron[3030]: (*system*frontview-volumeschedule) WRONG FILE OWNER (/etc/cron.d/frontview-volumeschedule)
Jul 18 16:17:01 nas-gmn cron[3030]: (*system*poweroff) WRONG FILE OWNER (/etc/cron.d/poweroff)
Jul 18 16:17:01 nas-gmn cron[3030]: (*system*spindown) WRONG FILE OWNER (/etc/cron.d/spindown)
Jul 18 16:17:38 nas-gmn dbus[2976]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Jul 18 16:17:38 nas-gmn dbus[2976]: [system] Activated service 'org.opensuse.Snapper' failed: The permission of the setuid helper is not correct
Jul 18 16:17:38 nas-gmn readynasd[3193]: Failure (org.freedesktop.DBus.Error.Spawn.PermissionsInvalid).
And regarding the error "the permission of the xxx" - in combination with LogAnalyzer, I found a lot of (Forum) entries - therefore my assumption this is an general issue.
Hope the "issue" of my car is now more clear :)
Thanks in advance
Regards
Giuseppe
Definately not a general case issue. It certainly appears that system file permissions got changed in the SSH install process. I would suggest an OS re-install (which, unlike a factory default, does not wipe your data), but I am concerned that the wrong owner issues will cause problems with that process and make things worse. Best to have a Netgear person comment on that.
Hey
thanks for your feedback.
But it occours on the LogAnalyzer installation.
And as I read - in other post - it´s not only a single issue.
Well.
let´s see if I get a official reply :)
Without Factory default :)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
