Any attempt on 3 different ReadyNAS's (just updated to 6.8.0 firmware), to install downloaded App .deb files results in "cannot read property 'childNodes' of undefined" error. Doesn't matter which app I try, always get the same problem. Using 'system/settings/install firmware' button and uploading relevant app .Deb file just downloaded from 'Apps/available apps/install'.

btaroli wrote:I saw this very issue mentioned in the release notes for 6.8 as a known problem that will be addressed in 6.8.1. It just says "apps installed from UI, workaround is to install manually." But given how it's described here, it sounds like you DID download the .deb and install as "upload" in the apps page? IF so, then I'm avoiding 6.8.0 until this is fixed. That's a super nasty problem I'm stunned wasn't caught in beta.If Netgear is relying on Beta testing to find this kind of bug, then their test philosophy is inadaquate. This is simply not they kind of thing you rely on beta testing to find. You cannot expect a random self-selected group of users to install/update every app during a beta test phase. Most will just verify that the already-installed apps still work. Finding this type of error requires a list of reverse compatibility tests. A bad list of requirements yeilds a bad set of tests.

btaroli wrote: That's a super nasty problem I'm stunned wasn't caught in beta. Since it's listed as a known problem, it was either caught in beta or in Netgear's testing. I don't know why they released it with that bug.

Correction: SickBeard App 'shows' its installed, just won't run. Netgear's own UTM connectivity App doesn't show as installed.

I saw this very issue mentioned in the release notes for 6.8 as a known problem that will be addressed in 6.8.1. It just says "apps installed from UI, workaround is to install manually." But given how it's described here, it sounds like you DID download the .deb and install as "upload" in the apps page? IF so, then I'm avoiding 6.8.0 until this is fixed. That's a super nasty problem I'm stunned wasn't caught in beta.

Cannot install Apps on 6.8.0 | NETGEAR Communities

27 Replies

Replies have been turned off for this discussion

kohdee
NETGEAR Expert
Aug 23, 2017
The problem is not really a bug in readynasos -- the bug lies in that the cacti application that one of you were installing (based on one of the comments in this thread earlier) can't fully install itself. Once you have an app that fails to install fully, it holds up other apps from installing properly. readynasos tries to work around some of those problems (which we have greatly improved). There's a log called install_debpkg.log that says what the problem was with installing the application. That can help debug app installation
- btaroli
  Prodigy
  Aug 23, 2017
  kohdee wrote:
  There's a log called install_debpkg.log that says what the problem was with installing the application. That can help debug app installation
  Uh, I thought that file was now deprecated in favor of the system journal. See https://community.netgear.com/t5/Community-Add-ons/How-best-to-diagnose-false-positive-app-upgrade-in-logs/m-p/1299377#M5762
  
  journalctl --identifier=fv-app-install
  - kohdee
    NETGEAR Expert
    Aug 23, 2017
    btaroli wrote:
    
    kohdee wrote:
    
    There's a log called install_debpkg.log that says what the problem was with installing the application. That can help debug app installation
    
    Uh, I thought that file was now deprecated in favor of the system journal. See https://community.netgear.com/t5/Community-Add-ons/How-best-to-diagnose-false-positive-app-upgrade-in-logs/m-p/1299377#M5762
    
    journalctl --identifier=fv-app-install
    
    The install_debpkg.log is a file that is generated when you download the Logs bundle from the UI. Using the journal via journalctl is a backend command. I don't typically advise backend commands. Since you seem to already be familiar with backend commands, You can run apt-get install -yf and it should tell you a bunch of output. Can you copy and paste it into this thread and I can tell you what is going wrong with the installation of your apps?
- philask
  Aspirant
  Aug 23, 2017
  Thanks, so this is our fault?
  - kohdee
    NETGEAR Expert
    Aug 23, 2017
    
    philask wrote:
    
    Thanks, so this is our fault?
    
    No, it is not your fault. Apps are built by package developers. App devs need to update their packages to ensure smooth transitions during upgrade.

philask

Aspirant

Aug 16, 2017

I have the exact same issue with 6.8.0, I can't install or uninstall apps. Looking at dpkg.log it looks like it could be related to cacti.

If I try to uninstall:

2017-08-16 06:30:03 startup packages configure
2017-08-16 06:30:03 configure cacti:all 0.8.8b+dfsg-8+deb8u6 <none>
2017-08-16 06:30:03 status half-configured cacti:all 0.8.8b+dfsg-8+deb8u6

And if I try to install (Plex): (I get the dashboard error Cannot install application plexmediaserver-ros6-binaries. )

2017-08-16 06:31:09 startup packages configure
2017-08-16 06:31:09 configure cacti:all 0.8.8b+dfsg-8+deb8u6 <none>
2017-08-16 06:31:09 status half-configured cacti:all 0.8.8b+dfsg-8+deb8u6
2017-08-16 06:31:12 startup archives unpack
2017-08-16 06:31:12 install plexmediaserver-ros6-binaries:amd64 <none> 1.8.1.4139-c789b3fbb
2017-08-16 06:31:12 status half-installed plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb
2017-08-16 06:31:44 status unpacked plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb
2017-08-16 06:31:44 status unpacked plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb
2017-08-16 06:31:44 startup packages configure
2017-08-16 06:31:44 configure cacti:all 0.8.8b+dfsg-8+deb8u6 <none>
2017-08-16 06:31:44 status half-configured cacti:all 0.8.8b+dfsg-8+deb8u6
2017-08-16 06:31:44 configure plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb <none>
2017-08-16 06:31:44 status unpacked plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb
2017-08-16 06:31:44 status half-configured plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb
2017-08-16 06:31:53 status installed plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb
2017-08-16 06:31:53 status triggers-pending libc-bin:amd64 2.19-18+deb8u10.netgear1
2017-08-16 06:31:54 trigproc libc-bin:amd64 2.19-18+deb8u10.netgear1 <none>
2017-08-16 06:31:54 status half-configured libc-bin:amd64 2.19-18+deb8u10.netgear1
2017-08-16 06:31:54 status installed libc-bin:amd64 2.19-18+deb8u10.netgear1
2017-08-16 06:31:54 startup packages purge
2017-08-16 06:31:54 status installed plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb
2017-08-16 06:31:54 remove plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb <none>
2017-08-16 06:31:54 status half-configured plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb
2017-08-16 06:31:55 status half-installed plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb
2017-08-16 06:31:55 status triggers-pending libc-bin:amd64 2.19-18+deb8u10.netgear1
2017-08-16 06:31:55 status config-files plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb
2017-08-16 06:31:55 purge plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb <none>
2017-08-16 06:31:55 status config-files plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb
2017-08-16 06:31:57 status config-files plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb
2017-08-16 06:31:57 status config-files plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb
2017-08-16 06:31:58 status config-files plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb
2017-08-16 06:31:58 status config-files plexmediaserver-ros6-binaries:amd64 1.8.1.4139-c789b3fbb
2017-08-16 06:31:58 status not-installed plexmediaserver-ros6-binaries:amd64 <none>
2017-08-16 06:31:58 trigproc libc-bin:amd64 2.19-18+deb8u10.netgear1 <none>
2017-08-16 06:31:58 status half-configured libc-bin:amd64 2.19-18+deb8u10.netgear1
2017-08-16 06:31:58 status installed libc-bin:amd64 2.19-18+deb8u10.netgear1
2017-08-16 06:31:58 startup packages configure
2017-08-16 06:31:58 configure cacti:all 0.8.8b+dfsg-8+deb8u6 <none>
2017-08-16 06:31:58 status half-configured cacti:all 0.8.8b+dfsg-8+deb8u6

btaroli
Prodigy
Aug 17, 2017
I saw this very issue mentioned in the release notes for 6.8 as a known problem that will be addressed in 6.8.1. It just says "apps installed from UI, workaround is to install manually." But given how it's described here, it sounds like you DID download the .deb and install as "upload" in the apps page? IF so, then I'm avoiding 6.8.0 until this is fixed. That's a super nasty problem I'm stunned wasn't caught in beta.
- StephenB
  Guru - Experienced User
  Aug 21, 2017
  btaroli wrote:
  
  That's a super nasty problem I'm stunned wasn't caught in beta.
  
  Since it's listed as a known problem, it was either caught in beta or in Netgear's testing.
  
  I don't know why they released it with that bug.

nglshmn
Tutor
Aug 16, 2017
Correction: SickBeard App 'shows' its installed, just won't run. Netgear's own UTM connectivity App doesn't show as installed.

Forum Discussion

Cannot install Apps on 6.8.0

27 Replies

Related Content

6.8.0 breaks FTP

Cannot Install Apps to ReadyNAS 212 Firmware 6.8.0

R8000 - impossible to install

ReadyNAS 104 [6.8.0] Communication error to NTP & Updates

ReadyNas OS 6.8.0 freezes

NETGEAR Academy

ProSupport for Business