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

Updater failed - The Process class relies on proc_open, which is not available on your PHP installation #337

Closed
Rouzax opened this issue Jul 7, 2016 · 5 comments

Comments

@Rouzax
Copy link

Rouzax commented Jul 7, 2016

Steps to reproduce

  1. goto xxx.yyy/updater/

Expected behaviour

Show the updater

Actual behaviour

Gives an error

Server configuration

Operating system:

Web server:

Database:
Mysql
PHP version:
5.6

Nextcloud version: (see Nextcloud admin page)
Nextcloud 9.0.50 (stable)

Updated from an older Nextcloud/ownCloud or fresh install:
Upgrade from OC

Where did you install Nextcloud from:
tar

Signing status (Nextcloud 9.0 and above):

Signing status

No errors have been found.

List of activated apps:

App list

If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder

The content of config/config.php:

Config report

If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder

or 

Insert your config.php content here
(Without the database password, passwordsalt and secret)

Are you using external storage, if yes which one: local/smb/sftp/...
no

Are you using encryption:
no

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
no


Fatal error: Uncaught exception 'Symfony\Component\Process\Exception\RuntimeException' with message 'The Process class relies on proc_open, which is not available on your PHP installation.' in /home/xxx/public_html/_cloud/updater/vendor/symfony/process/Process.php:144 Stack trace: #0 /home/xxx/public_html/_cloud/updater/src/Utils/OccRunner.php(45): Symfony\Component\Process\Process->__construct('php /home/xxx/...') #1 /home/xxx/public_html/_cloud/updater/src/Utils/OccRunner.php(56): Owncloud\Updater\Utils\OccRunner->run('config:list --p...') #2 /home/xxx/public_html/_cloud/updater/src/Utils/ConfigReader.php(106): Owncloud\Updater\Utils\OccRunner->runJson('config:list --p...') #3 /home/xxx/public_html/_cloud/updater/src/Utils/ConfigReader.php(50): Owncloud\Updater\Utils\ConfigReader->load() #4 /home/xxx/public_html/_cloud/updater/src/Controller/IndexController.php(96): Owncloud\Updater\Utils\ConfigReader->init() #5 /home/xxx/public_html/_cloud/updater/src/Controller/IndexController.php(70): Owncloud\Updater\Control in /home/xxx/public_html/_cloud/updater/vendor/symfony/process/Process.php on line 144
@MorrisJobke
Copy link
Member

@LukasReschke Caused by the old updater ...

@karlitschek Another argument to move to the new version ;)

@LukasReschke
Copy link
Member

🙈 🙉 🙊

@MorrisJobke
Copy link
Member

@Rouzax This is the old updater, that only works if you have this method available. This should also be listed in the admin settings check. Sadly we can't do much here for the old updater and we wrote a new one, that is a lot simpler and doesn't require this method anymore. Feel free to test it. See https://help.nextcloud.com/t/test-our-new-work-in-progress-upgrader-script/1214 for more details

@karlitschek
Copy link
Member

@MorrisJobke Agreed. I'm just not sure we we still have the time to bring this into shape for the next release. Aka. Add the needed features and do testing. I suggest to do this for the next one.

@MorrisJobke
Copy link
Member

@MorrisJobke Agreed. I'm just not sure we we still have the time to bring this into shape for the next release. Aka. Add the needed features and do testing. I suggest to do this for the next one.

Therefore we only show this when a "I'm super sure to use this, because it is still in beta" config switch was set ;) Then eager people can set it and try the new updater without copying files around. And on the other side we are safe, because it is not enabled by default :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants