Re: bg.php.net mirror site deactivated
| From: | Gabor Hojtsy | Date: | Mon, 11 Sep 2006 14:25:15 +0000 |
| Subject: | Re: bg.php.net mirror site deactivated | ||
| References: | 1 2 | Groups: | php.mirrors |
| Request: | Send a blank email to php-mirrors+get-32488@lists.php.net to get a copy of this message | ||
Hi,
The error message itself explicitly states that the problem *is* that the mirror setup is unchanged. Please compare your mirror setup (all aspects) with the current one suggested on /mirroring.php. The errordocument is surely not right, as the error message suggests.
Gabor
On Mon, 11 Sep 2006, Bulgaria Online - Assen Totin wrote:
Hi, I see no problem with bg.php.net: the server setup is unchanhed; the mirror is running and is serving content. It was last updated last night: [root@rhett /storage/php]# ls -lt | head total 1221drwxrwxr-x 29 root nobody 928 Sep 11 02:32 manual drwxr-xr-x 2 root root 824 Sep 11 02:31 include -rw-r--r-- 1 root root 9241 Sep 11 02:31 mirrorkit.tgz drwxr-xr-x 4 root root 312 Sep 11 02:31 backend drwxr-xr-x 7 root root 1280 Sep 11 02:27 images drwxr-xr-x 3 root root 1168 Sep 11 02:27 distributions -rw-r--r-- 1 root root 2132 Sep 10 22:26 cvsup.php -rw-r--r-- 1 root root 13415 Sep 10 22:26 mirroring.php -rw-r--r-- 1 root root 20671 Sep 10 21:44 index.php If you believe a problem persists, please, advise so. Best regards, Assen Totin Development Manager php-mirrors@lists.php.net writes:the PHP.net mirror site maintained by you for three or more days now, *or* have found a permanent fatal error in your mirror setup. Therefore our bot automatically disabled your listing as an official PHP.net mirror site. The last error message stored for your mirror is: invalid data received (probably improper ErrorHandler) Please correct the problem or reply to this mail with your questions, if you think that the problem is not on your side. Your mirror will be kept disabled until the error is fixed. Mail sent out by the PHP.net automatic mirror site monitoring systemHi! Our automatic mirror site check was unable to reach