Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update not possible: Out-of-path file extraction #52

Closed
EmJotGeh opened this issue Aug 17, 2021 · 24 comments
Closed

Update not possible: Out-of-path file extraction #52

EmJotGeh opened this issue Aug 17, 2021 · 24 comments
Projects

Comments

@EmJotGeh
Copy link

recognize new version available: 1.5.1
recognize couldn't be updated

recognize new version available: 1.5.2
recognize couldn't be updated

Nextcloud 21.0.4

@GVLLIFESTYLE
Copy link

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
Copy link

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}

@marcelklehr

This comment has been minimized.

@marcelklehr

This comment has been minimized.

@GVLLIFESTYLE
Copy link

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

@marcelklehr
Copy link
Member

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

@hdridder

This comment has been minimized.

@marcelklehr marcelklehr reopened this Aug 20, 2021
@marcelklehr

This comment has been minimized.

@hdridder

This comment has been minimized.

@marcelklehr marcelklehr reopened this Aug 23, 2021
@marcelklehr marcelklehr changed the title Update not possible Update not possible: Out-of-path file extraction Aug 23, 2021
@marcelklehr
Copy link
Member

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

@spicemint

This comment has been minimized.

@DecaTec
Copy link

DecaTec commented Aug 25, 2021

A manual update of the app seems to work.

@spicemint
Copy link

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

@DecaTec
Copy link

DecaTec commented Aug 25, 2021

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.

@vanderheyde
Copy link

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
Copy link
Member

@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
Copy link

@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

@vanderheyde
Copy link

attempted both 1.6 release and 1.5.8 release, same results

@marcelklehr
Copy link
Member

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

@marcelklehr
Copy link
Member

fyi, this appears to be fixed in v22

@KruyKaze

This comment has been minimized.

@marcelklehr

This comment has been minimized.

@Sputnikchen

This comment has been minimized.

@marcelklehr
Copy link
Member

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.)

@nextcloud nextcloud locked as spam and limited conversation to collaborators Aug 26, 2021
@marcelklehr marcelklehr pinned this issue Sep 16, 2021
@marcelklehr marcelklehr added this to In progress in Recognize Sep 29, 2021
Recognize automation moved this from In progress to Done Dec 31, 2021
@marcelklehr marcelklehr unpinned this issue Oct 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Development

No branches or pull requests

9 participants