-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
[Bug]: flood of errors is_file(): open_basedir restriction in effect. File(/proc/cpuinfo) after 25 > 26 update #37921
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Thanks. Mind to try:
|
In serverinfo we are using
To read /proc/cpuinfo every time we need a preview generator is a bit weird. |
Sure, but I just hate |
I understand. It was just a suggestion. If you prefer to check open_basedir go ahead. The runtime check for the number of cores is weird anyway. It's unlikely to change ;) |
Agree. |
That seems to work. I'm not getting new errors. I cannot say something usefull about performance. This is a very small setup, around 10 users, < 100 documents. |
Regarding this:
NC isn't using |
OK, I'll tell them. From the forum topic linked above I understand that you can disable it if you have access to php.ini, but we don't. In Directadmin I don't see an option to disable it. Probably only an admin can. The same with cPanel at another provider where I'm hosting a website. |
Yes, open_basedir is controlled by administrators in shared hosting environments. And if you're using shared hosting, you're going to have a far lower level of access to the server and the control panel capabilities. You're stuck with whatever you can do within the confines of the access the provider chooses to give you the ability to do and whatever they consider a "standard" configuration internally. Control panels (e.g. Directadmin/cPanel) aren't the issue per se - you can install them on your own VPS (versus shared web hosting) if you like - and enjoy full access to do as you please. :-) |
So the elegant solution by @solracsf did not make it through review. It worked for us although I got the feeling that viewing folders got a little slower.
Isn't that the underlying problem that needs to be fixed? Some more thoughts: I'm running Nextcloud on my own server at home but also on shared hosting for 2 associations. This kind of usage is in the official documentation and the 'web installer' I used is promoted on nextcloud.com. Also, many hosting providers offer Installatron, which probably also runs the web installer. I assume this installer checks for some requirements for Nextcloud. In fact we do get some warnings about missing PHP extensions required for certain functionality. But nothing about IMHO it is important to make and keep Nextcloud working on shared hosting with some basic functionality. It helps 'spread the word'. It has worked fine for us so far and it made at least one member get a commercial Nextcloud solution for his company. |
Hi, still occurs in Nexcloud 26.0.2. |
Have the issue still in version 27.0.1. |
Me too. Have this Issue since v26.0.0. Yesterday i updated to v27.0.1. Is still there. |
looks like it will be only fixed in nc 28. |
Bug description
After updating Nextcloud server from 25.0.6 to 26.0 every activity results in an error in the log like:
This never occurred before the update (installed may 2022)
Steps to reproduce
Expected behavior
Clean log or only warnings
Installation method
Community Web installer on a VPS or web space
Nextcloud Server version
26
Operating system
RHEL/CentOS
PHP engine version
PHP 8.1
Web server
Other
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
Updated to a major version (ex. 22.2.3 to 23.0.1)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
See this forum topic.
This has similarities with #27759 but that one is closed, was generated by a different .php and was about different directories so IMHO this a new bug.
Like on most shared hosting we cannot edit php.ini but the DirectAdmin panel allowed us to add /proc/cpuinfo to the open_basedir. I still believe this should not be needed.
Opinions I heard/read, but I'm no developer, so I cannot judge:
In the forum topic mentioned above:
On php.net:
The text was updated successfully, but these errors were encountered: