Nextgen filling error logs and killing server

@bobcatou – What are you seeing under Gallery > Overview | Site Details tab for the Server Settings?

Also, can you work with your web hosting service to address this specific issue: PHP Warning: is_dir(): open_basedir restriction in effect. File(/) is not within the allowed path(s)

I suspect that is the problem more than anything else at the moment.

Thanks!

– Cais.

Thanks Cais,

I’m not going be able to look at those settings until Friday. Kind of a long story but when Nextgen is activated, it will create that warning hundreds of thousand of times. Literally increasing the error log by about 1gb every 15 to 30 seconds. Be that this is on a shared host, it crashes other sites

The local host in town is smallish setup and can’t get back to me about it until Friday.

I don’t quite understand what the warning means?
Warning: is_dir(): open_basedir restriction in effect. File(/) is not within the allowed path(s)

Is this a permission issue? Could a permission have been changed on the server so not to allow part of your plugin to work, thus hitting us with the loop of warnings? I’m trying to figure out what I can talk to the host about that might resolve this. The website owner really likes your plugin and doesn’t want to give it up.

Thank you for your input.

Bryan

Hi Cais,

I heard back from my host and he tells me that the warning is stating that the plugin wants access to (/) which I believe is the root directory of the server and they don’t allow that. I admit that seems odd.

I’m going to check the server settings this afternoon on Nextgen (as you suggested) and maybe I will learn more.

I did find another ticket here with the same issue, but the user never said if he resolved the issue and how. https://www.ads-software.com/support/topic/nextgen-gallery-is_dir-open_basedir-restriction?replies=15

Thanks
Bryan

@bobcatou – Unfortunately there is not much we can do if the hosting service does not provide access to the WordPress root installation folder (which appears to be what you are describing as their response).

You are welcome to send us a Bug Report (https://imagely.com/report-bug/ … please reference this topic) so we can get a better look under the page at your site but if the above is true we may only at best be able to confirm what you have already stated.

Please include as many details as you can about your site and the issue at hand so we can move on this as fast as possible.

Thanks!

– Cais.

I TOTALLY understand that. I might still keep you posted, if that is okay but I am thinking I am going to have to work with the host on this.

Thanks for your time.
Bryan

@bobcatou – Absolutely! Please let us know what you can get sorted out with your web host on this.

Thanks!

– Cais.

This is very strange. I activated Nextgen on Friday to pull the server info like you said. The error log didn’t go crazy again in size. In fact it only increased by 1mb all weekend long with Nextgen activated.

I don’t know if the host was doing something then stopped or if there was a DDOS attack somehow.

Regardless, it isn’t creating Gigabytes of errors in a matter of minutes anymore. I’m hoping my host investigates further but as far as I am concerned right now, I consider this resolved, “Tentatively”

Thanks

@bobcatou – Thanks for the update!

– Cais.

The plugin is attempting to access the servers root folder /, which of course it should never be allowed access to. Are there settings for the plugin that need to be changed to the domains webroot e.g. /var/www/vhosts/domain.com/httpdocs ?

@dgwalsh – The plugin is looking for access to the WordPress root installation folder (which in many cases is the root folder of the domain).

You can use the “domain’s webroot” in some cases such as template paths although generally it is not necessary to be that specific.

For anything else it might be best to start your own topic.

Thanks!

– Cais.

I’m experiencing the same issue as Bryan and am unwilling to grant ‘/’ on the open base directory configuration. ‘/’ refers to the root of the server in this instance, not wordpress httpdocs root like ‘/var/www/domain/’. Server logs are ballooning with the same symptom. Is there a constant to define a path that can be defined as a workaround?

@jsnrkd – Although I suspect more a server environment issue, please start your own topic so we can try to help you with your specific issue on your specific site.

See https://make.www.ads-software.com/support/handbook/forum-welcome/#post-in-the-best-place

Thanks!

– Cais.