[BlueOnyx:25497] Re: Open_basedir error

[Ken Marcus]

Have the script print to screen the file location it is trying to open.
Compare that to the allowed / open basedir directories.
Or check the ownership and permissions of the file you are trying to
delete.

Ken Marcus
Precision Web Hosting, Inc.


On Wed, Jul 6, 2022 at 8:32 AM Colin Jack <colin at mainline.co.uk> wrote:

> We have a customer who is suddenly getting open_basedir errors on their
> vsite:
>
>
>
> PHP Warning:  unlink(): open_basedir restriction in effect. File() is not
> within the allowed path(s):
> (/var/lib/php/session/:/usr/sausalito/configs/php/:/tmp/:/home/solarspeed/php-5.4/share/pear:/home/.sites/28/site1/)
> in /home/.sites/28/site1/web/1/phserial/remove-record.php on line 23,
> referer:
>
>
>
> The file in question is a PDF that is written to the phserial folder which
> it does correctly and is then supposed to delete it.
>
>
>
> // DELETE PDF
>
> unlink($row[file]);
>
> echo "<p>You have deleted the crate, the components and the pdf.</p>";
>
>
>
> This is on an old 5207R running PHP 5 … I know … very old but this is
> in-house and not exposed to the internet! 😊
>
>
>
> The question is why are they now seeing an open_basedir error when the
> file in question is in the allowed path and is not creating an error when
> it is written.
>
>
>
> This has been running fine for years.
>
>
>
> Any ideas would be great.
>
>
>
> Thanks
>
>
>
> Colin
>
>
>
>
>
>
>
>
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at mail.blueonyx.it
> http://mail.blueonyx.it/mailman/listinfo/blueonyx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20220706/c8a27ce0/attachment.html>