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" ...
Please start from the beginning with a chronological list of what you have done and what the problems are. Include version number(s) of NAS firmware, systems you are using to try and access it, and specific error messages and/or log entries. Your current message is the equivalent of "my car doesn't run, please tell me why".
One possibility is that your installation of a progam via SSH has overwritten a critical NAS system file with a newer version that is not supported in your firmware version. Another is that your program filled up the OS partition (though you would likely have other errors as well if that were it). But without specifics of what has happened, these are no more than outright guesses. Factory default may be your only solution. So if you don't have a current backup (as you should), then now is the time to think about how you will create and maintain one.
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 :)
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 TeamHey
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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
