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

oC 9.0 RC1: proc_open required #261

Closed
vanMacG opened this issue Mar 3, 2016 · 10 comments
Closed

oC 9.0 RC1: proc_open required #261

vanMacG opened this issue Mar 3, 2016 · 10 comments
Assignees
Labels
Milestone

Comments

@vanMacG
Copy link

vanMacG commented Mar 3, 2016

The new updater requires proc_open function to be enabled.

On many shared hosters this function is disabled. Is this function really used or only "included" by symfony? Can the updater run without the function or is there a workaround?

owncloud/updater/index.php produces this error:

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 /www/htdocs/w0069a6f/testing/oc9rc1/owncloud/updater/vendor/symfony/process/Process.php:144 Stack trace: #0 /www/htdocs/w0069a6f/testing/oc9rc1/owncloud/updater/src/Utils/OccRunner.php(45): Symfony\Component\Process\Process->__construct('php /www/htdocs...') #1 /www/htdocs/w0069a6f/testing/oc9rc1/owncloud/updater/src/Utils/OccRunner.php(56): Owncloud\Updater\Utils\OccRunner->run('--no-warnings c...') #2 /www/htdocs/w0069a6f/testing/oc9rc1/owncloud/updater/src/Utils/ConfigReader.php(106): Owncloud\Updater\Utils\OccRunner->runJson('config:list --p...') #3 /www/htdocs/w0069a6f/testing/oc9rc1/owncloud/updater/src/Utils/ConfigReader.php(50): Owncloud\Updater\Utils\ConfigReader->load() #4 /www/htdocs/w0069a6f/testing/oc9rc1/owncloud/updater/src/Controller/IndexController.php(96): Owncloud\Updater\Utils\ConfigReader->init() #5 /www/htdocs/ in /www/htdocs/w0069a6f/testing/oc9rc1/owncloud/updater/vendor/symfony/process/Process.php on line 144
@VicDeo
Copy link
Member

VicDeo commented Mar 3, 2016

@vanMacG sadly proc_open is a hard requirement of symfony/process

@karlitschek
Copy link

@VicDeo Can we check for proc_open and show a better error message?
@DeepDiver1975

@vanMacG
Copy link
Author

vanMacG commented Mar 4, 2016

I know that shared hoster are not your favorite hosting solutions for ownCloud, but people do use it. I worry that many will struggle on this...

Nevertheless, when I have to do a manual upgrade, will this work? Aka how does the db get updated? Also with the "new updater" or is this an independent function without proc_open?

@LukasReschke
Copy link
Member

@vanMacG sadly proc_open is a hard requirement of symfony/process

What about http://symfony.com/doc/current/cookbook/console/command_in_controller.html as fallback?

@DeepDiver1975
Copy link
Member

This is why we need owncloud/core#21985

@DeepDiver1975 DeepDiver1975 added this to the 9.1-current milestone Apr 4, 2016
@DeepDiver1975
Copy link
Member

Or we have a shortened processing path for the web updater where the need of interaction using occ is not required.

@VicDeo where is occ required as of today?

@DeepDiver1975 DeepDiver1975 self-assigned this Apr 4, 2016
@VicDeo
Copy link
Member

VicDeo commented Apr 4, 2016

@DeepDiver1975 in short it is used nearly everywhere (except dealing with checkpoints)

@vanMacG
Copy link
Author

vanMacG commented Apr 5, 2016

What doesn't make sense from a users pov is: "There was a web updater which mainly did the job. Now there is a web updater which is just a nice gui for occ-cli?"
I'm sorry for the rough sounding and exaggerating! I don't want to degrade the work which was done here but that's the result for many users on shared hosters... :-/

@DeepDiver1975
Copy link
Member

We have to enhance the web Updater for sure.
Next Version will Focus on this

@PVince81
Copy link
Contributor

PVince81 commented Jul 7, 2016

Closing in favor of owncloud/core#21985 which brings the web executor.

@PVince81 PVince81 closed this as completed Jul 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants