Update not possible: Out-of-path file extraction about recognize

[marcelklehr]

Fixed in dec7e58

[DecaTec]

what other manual way is there besides what i tried? i also tried the webinterface, same issue

Move the recognize folder out of the apps folder. Next, download the release archive from the release page and unpack it in the apps folder. Then chown -R www-data:www-data /var/www/nextcloud/apps/recognize.
After that, the upgrade is done in the browser.

[marcelklehr]

Hi, sorry for your troubles and thank you for reporting! The new version seems to have some toothing problems. I'll investigate and release patches soon.

[marcelklehr]

It seems I cannot circumvent this bug, so I've reopened it here and over here: nextcloud/server#26708

[vanderheyde]

attempted both 1.6 release and 1.5.8 release, same results

[GVLLIFESTYLE]

yap exactly.
and if you try to reinstall you receive this error:
Could not extract app recognize: Out-of-path file extraction {/tmp/oc_tmp_T0cTMU-folder/recognize/node_modules/@tensorflow/tfjs-node-gpu/deps/lib/libtensorflow.so.2 --> libtensorflow.so.2.5.0}

[hdridder]

Same problem here: Message":"Could not extract app recognize: Out-of-path file extraction {/volume1/@tmp/oc_tmp_aYHmf1-folder/recognize/node_modules/@tensorflow/tfjs-node-gpu/deps/lib/libtensorflow.so.2 --> libtensorflow.so.2.5.0}

[GVLLIFESTYLE]

When will you push it to the nextcloud store?
Their is still the old version avialable.

[marcelklehr]

New version is available now. Let me know if there are additional issues ♥️

[hdridder]

Thanks. Upgrade from the GUI failed. On the commandline it reports:

# sudo -u http php74 /var/www/nextcloud/occ app:update recognize
Nextcloud is in maintenance mode - no apps have been loaded

recognize new version available: 1.5.3
/volume1/web/nextcloud/apps/recognize/bin/node-v14.17.4-linux-armv7l: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory
recognize updated

Despite the error message recognize is now reported to be on version 1.5.3
The library reported in the error does exist on the filesystem

# ls -l /volume1/web/nextcloud/apps/recognize/bin/node-v14.17.4-linux-armv7l
-rwxr-xr-x 1 http http 67904012 Aug 20 20:06 /volume1/web/nextcloud/apps/recognize/bin/node-v14.17.4-linux-armv7l

[marcelklehr]

@hdridder Are you running on armv7l? The library reported missing is libatomic.so.1

[hdridder]

Yes it is armv71 on a synology DS214÷

[spicemint]

I just tried to install the app on 21.0.4, raspbian:
sudo -u www-data /usr/bin/php /var/www/nextcloud/occ app:install recognize Error: Could not extract app recognize: Out-of-path file extraction {/tmp/oc_tmp_pofTyG-folder/recognize/node_modules/@tensorflow/tfjs-node-gpu/deps/lib/libtensorflow.so.2 --> libtensorflow.so.2.5.0}

[DecaTec]

A manual update of the app seems to work.

[spicemint]

A manual update of the app seems to work.

what other manual way is there besides what i tried? i also tried the webinterface, same issue

[vanderheyde]

Trying DecaTec's solution showed a 'Saving of node binary failed' message. I had to put the old recognize folder back and manually turn the maintenance mode off in config.php

   "message":{
      "Exception":"Exception",
      "Message":"Saving of node binary failed",
      "Code":0,
      "Trace":[
         {
            "file":"/var/www/nextcloud/apps/recognize/lib/Migration/RegisterBinary.php",
            "line":55,
            "function":"downloadBinary",
            "class":"OCA\\Recognize\\Migration\\RegisterBinary",
            "type":"->",
            "args":[
               "v14.17.4",
               "arm64"
            ]
         },
         {
            "file":"/var/www/nextcloud/lib/private/Repair.php",
            "line":118,
            "function":"run",
            "class":"OCA\\Recognize\\Migration\\RegisterBinary",
            "type":"->",
            "args":[
               {
                  "__class__":"OC\\Repair"
               }
            ]
         },
         {
            "file":"/var/www/nextcloud/lib/private/legacy/OC_App.php",
            "line":1062,
            "function":"run",
            "class":"OC\\Repair",
            "type":"->",
            "args":[
               
            ]
         },
         {
            "file":"/var/www/nextcloud/lib/private/legacy/OC_App.php",
            "line":1004,
            "function":"executeRepairSteps",
            "class":"OC_App",
            "type":"::",
            "args":[
               "*** sensitive parameter replaced ***",
               {
                  "step":"OCA\\Recognize\\Migration\\RegisterBinary"
               }
            ]
         },
         {
            "file":"/var/www/nextcloud/lib/private/Updater.php",
            "line":340,
            "function":"updateApp",
            "class":"OC_App",
            "type":"::",
            "args":[
               "*** sensitive parameters replaced ***"
            ]
         },
         {
            "file":"/var/www/nextcloud/lib/private/Updater.php",
            "line":260,
            "function":"doAppUpgrade",
            "class":"OC\\Updater",
            "type":"->",
            "args":[
               
            ]
         },
         {
            "file":"/var/www/nextcloud/lib/private/Updater.php",
            "line":132,
            "function":"doUpgrade",
            "class":"OC\\Updater",
            "type":"->",
            "args":[
               "21.0.4.1",
               "21.0.4.1"
            ]
         },
         {
            "file":"/var/www/nextcloud/core/ajax/update.php",
            "line":214,
            "function":"upgrade",
            "class":"OC\\Updater",
            "type":"->",
            "args":[
               
            ]
         }
      ],
      "File":"/var/www/nextcloud/apps/recognize/lib/Migration/RegisterBinary.php",
      "Line":104,
      "CustomMessage":"--"
   }

[marcelklehr]

@vanderheyde Make sure you chown to the right user. It should be the user of your http server (the one you use for running occ).

[vanderheyde]

@vanderheyde Make sure you chown to the right user. It should be the user of your http server (the one you use for running occ).

I did. Also attempted to update via commandline with same result:

/var/www/nextcloud/apps$ chown -R www-data:www-data recognize/
/var/www/nextcloud/apps$ cd ..
/var/www/nextcloud$ sudo -u www-data php ./occ upgrade
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Setting log level to debug
Turned on maintenance mode
Updating database schema
Updated database
Updating <recognize> ...
Exception: Saving of node binary failed
Update failed
Maintenance mode is kept active
Resetting log level

[marcelklehr]

I guess, then you'll have to wait until this issue is fixed :/

[marcelklehr]

fyi, this appears to be fixed in v22

[KruyKaze]

1.6 does not seem to be available in the store . Is it a package size issue?

…

On Thu, Aug 26, 2021, 02:36 Marcel Klehr ***@***.***> wrote: fyi, this appears to be fixed in v22 <nextcloud/3rdparty@a711d70> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#52 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAARFYN4QYJJMV2JDC6ZOFTT6X4KNANCNFSM5CK2J76A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

[marcelklehr]

Is it a package size issue?

Yep, I'm working on it :)

[Sputnikchen]

Not working since version 1.5.8:
Nextcloud 21.0.3
Recognize 1.6.3
TensorFlow 2.5.0 {/usr/lib/libtensorflow.so.2 -> libtensorflow.so.2.5.0}
sudo -u www-data php ./occ app:install recognize
Error: Could not extract app recognize: Out-of-path file extraction {/tmp/oc_tmp_UhJNSO-folder/recognize/node_modules/@tensorflow/tfjs-node/deps/lib/libtensorflow.so.2 --> libtensorflow.so.2.5.0}

[marcelklehr]

To be clear: This is a bug in nextcloud < 22 that I cannot circumvent without bloating up the bundle causing the appstore to reject the bundle. (I have tried.)