open_basedir restriction error in BackWPup when using SymLinks
-
Hi,
for certain reasons I’m using SymLinks in the WP root directory, which refer to log folders outside my webspace. The problem I’m now having is, that BackWPup creates the error message “RuntimeException: SplFileInfo::isDir(): open_basedir restriction in effect” in the log of a backup job and the job is cancelled while BackWPup was creating the file & folder list. The reason for this is quite clear, because of the SymLinks referring are to a location outside the open_basedir. Also this should not (and cannot) be changed due to security reasons.
The point is: Why is BackWPup treating this as a fatal error and stops progressing? I think if there is a link to any location outside the basedir range, this should not block creating the backup. Just a warning and progressing would be fair enough.
The funny thing is, that I already excluded these folders before I moved them outside my webspace and replacing them with a SymLink. Now, after having these SymLinks, I also do not see anything in the Files tab of the job settings. I think the PHP for the job settings stops exactly at the same problem.
Please could you stop treating this as a fatal error and ignore all folders and files, which creates this open_basedir restriction error? I think that would really be the right way to handle such PHP errors.
Thanks a lot in advance,
Armin
-
@duongcuong96,
I just realized your reply here and tested this in my environment. What now works is that the php of the backend does not crash anymore. But I still have the issue that the backup script crashes, when it tries to create the folder list:[26-Dec-2017 12:52:41] WARNUNG: realpath(): open_basedir restriction in effect. File(/www/htdocs/(...)/logs) is not within the allowed path(s): (/www/htdocs/(...)/:/tmp:/usr/bin:/www/htdocs/(...):/bin:/usr/local/bin:/usr/share/php:/dev/urandom)[26-Dec-2017 12:52:41] FEHLER: Ausnahme eingefangen in RuntimeException: SplFileInfo::isDir(): open_basedir restriction in effect. File(/www/htdocs/(...)/logs) is not within the allowed path(s): (/www/htdocs/(...)/:/tmp:/usr/bin:/www/htdocs/(...):/bin:/usr/local/bin:/usr/share/php:/dev/urandom)I already tried to exclude in different ways, but no success at all.
Any ideas? I still think the backup script should capture this php error and could create a warning instead of stop at all.
Rgds,
ArminNo, this does not help. The issue I have is not related to the dir, where the backup should be stored. The issue relates to some symlinks inside my WP installation, which refer to folders outside the open_basedir restriction. I need these links for some security reasons.
I just made some debugging analysis and found the solution! The difficulty here is that e.g. the isLink() method already tries to access the properties of the target in case of a sym link and an open_basedir exception already occurs. Here is my solution, which I have tested on V3.4.4:
In class-jobtype-file.php change line 417 to
if ( $file->isDot() || ! @is_readable( $file->getPathname() )) {In class-job.php add the following code after line 1734:
if ( ! @is_readable( $file->getPathname() )) { $this->log( sprintf( _x( 'File or link "%s" is not readable', 'File or link name', 'backwpup' ), $file->getPathname() ), E_USER_WARNING ); continue; }This now works fine for me.
Rgds,
Armin
The topic ‘open_basedir restriction error in BackWPup when using SymLinks’ is closed to new replies.
