The MU forums have moved to WordPress.org

File does not exist error in apache error_log (3 posts)

  1. craig777
    Member
    Posted 14 years ago #

    Fresh install when trying to access admin login link. The page shows with no css styling and error is found in apache error_log below :

    [Fri Jul 03 09:35:38 2009] [error] [client 161.117.117.47] File does not exist: /usr/local/apache_blog/htdocs/wordpress-mu/wp-admin/css/colors-fresh.css/, referer: http://161.117.126.76/wordpress-mu/wp-login.php
    [Fri Jul 03 09:35:38 2009] [error] [client 161.117.117.47] File does not exist: /usr/local/apache_blog/htdocs/wordpress-mu/wp-admin/css/login.css/, referer: http://161.117.126.76/wordpress-mu/wp-login.php

    Someone has had simliar error but no resolution was posted that I could find. I have confirmed that rewrite is atleast running. Added lines to create rewrite debug log in httpd.conf. I can see that it is hitting the rewrite rules defined in .htaccess which is in the /htdocs/wordpress-mu directory :

    161.117.117.47 - - [03/Jul/2009:09:35:38 +1000] [161.117.126.76/sid#59e160][rid#7a2138/initial] (3) [perdir /usr/local/apache_blog/htdocs/wordpress-mu/] add path info postfix: /usr/local/apache_blog/htdocs/wordpress-mu/wp-admin/css/login.css -> /usr/local/apache_blog/htdocs/wordpress-mu/wp-admin/css/login.css/
    161.117.117.47 - - [03/Jul/2009:09:35:38 +1000] [161.117.126.76/sid#59e160][rid#7a2138/initial] (3) [perdir /usr/local/apache_blog/htdocs/wordpress-mu/] strip per-dir prefix: /usr/local/apache_blog/htdocs/wordpress-mu/wp-admin/css/login.css/ -> wp-admin/css/login.css/
    161.117.117.47 - - [03/Jul/2009:09:35:38 +1000] [161.117.126.76/sid#59e160][rid#7a2138/initial] (3) [perdir /usr/local/apache_blog/htdocs/wordpress-mu/] applying pattern '^(.*/)?files/$' to uri 'wp-admin/css/login.css/'
    161.117.117.47 - - [03/Jul/2009:09:35:38 +1000] [161.117.126.76/sid#59e160][rid#7a2138/initial] (3) [perdir /usr/local/apache_blog/htdocs/wordpress-mu/] add path info postfix: /usr/local/apache_blog/htdocs/wordpress-mu/wp-admin/css/login.css -> /usr/local/apache_blog/htdocs/wordpress-mu/wp-admin/css/login.css/
    161.117.117.47 - - [03/Jul/2009:09:35:38 +1000] [161.117.126.76/sid#59e160][rid#7a2138/initial] (3) [perdir /usr/local/apache_blog/htdocs/wordpress-mu/] strip per-dir prefix: /usr/local/apache_blog/htdocs/wordpress-mu/wp-admin/css/login.css/ -> wp-admin/css/login.css/
    161.117.117.47 - - [03/Jul/2009:09:35:38 +1000] [161.117.126.76/sid#59e160][rid#7a2138/initial] (3) [perdir /usr/local/apache_blog/htdocs/wordpress-mu/] applying pattern '^(.*/)?files/(.*)' to uri 'wp-admin/css/login.css/'
    161.117.117.47 - - [03/Jul/2009:09:35:38 +1000] [161.117.126.76/sid#59e160][rid#7a2138/initial] (3) [perdir /usr/local/apache_blog/htdocs/wordpress-mu/] add path info postfix: /usr/local/apache_blog/htdocs/wordpress-mu/wp-admin/css/login.css -> /usr/local/apache_blog/htdocs/wordpress-mu/wp-admin/css/login.css/
    161.117.117.47 - - [03/Jul/2009:09:35:38 +1000] [161.117.126.76/sid#59e160][rid#7a2138/initial] (3) [perdir /usr/local/apache_blog/htdocs/wordpress-mu/] strip per-dir prefix: /usr/local/apache_blog/htdocs/wordpress-mu/wp-admin/css/login.css/ -> wp-admin/css/login.css/
    161.117.117.47 - - [03/Jul/2009:09:35:38 +1000] [161.117.126.76/sid#59e160][rid#7a2138/initial] (3) [perdir /usr/local/apache_blog/htdocs/wordpress-mu/] applying pattern '^(.+)$' to uri 'wp-admin/css/login.css/'
    161.117.117.47 - - [03/Jul/2009:09:35:38 +1000] [161.117.126.76/sid#59e160][rid#7a2138/initial] (4) [perdir /usr/local/apache_blog/htdocs/wordpress-mu/] RewriteCond: input='/wordpress-mu/wp-admin/css/login.css/' pattern='^.*/wp-admin$' => not-matched
    161.117.117.47 - - [03/Jul/2009:09:35:38 +1000] [161.117.126.76/sid#59e160][rid#7a2138/initial] (3) [perdir /usr/local/apache_blog/htdocs/wordpress-mu/] add path info postfix: /usr/local/apache_blog/htdocs/wordpress-mu/wp-admin/css/login.css -> /usr/local/apache_blog/htdocs/wordpress-mu/wp-admin/css/login.css/
    161.117.117.47 - - [03/Jul/2009:09:35:38 +1000] [161.117.126.76/sid#59e160][rid#7a2138/initial] (3) [perdir /usr/local/apache_blog/htdocs/wordpress-mu/] strip per-dir prefix: /usr/local/apache_blog/htdocs/wordpress-mu/wp-admin/css/login.css/ -> wp-admin/css/login.css/
    161.117.117.47 - - [03/Jul/2009:09:35:38 +1000] [161.117.126.76/sid#59e160][rid#7a2138/initial] (3) [perdir /usr/local/apache_blog/htdocs/wordpress-mu/] applying pattern '.' to uri 'wp-admin/css/login.css/'
    161.117.117.47 - - [03/Jul/2009:09:35:38 +1000] [161.117.126.76/sid#59e160][rid#7a2138/initial] (4) [perdir /usr/local/apache_blog/htdocs/wordpress-mu/] RewriteCond: input='/usr/local/apache_blog/htdocs/wordpress-mu/wp-admin/css/login.css' pattern='-f' => matched
    161.117.117.47 - - [03/Jul/2009:09:35:38 +1000] [161.117.126.76/sid#59e160][rid#7a2138/initial] (1) [perdir /usr/local/apache_blog/htdocs/wordpress-mu/] pass through /usr/local/apache_blog/htdocs/wordpress-mu/wp-admin/css/login.css

    Any ideas ?

  2. craig777
    Member
    Posted 14 years ago #

    For those that had a simliar problem it was due to an incorrect sitename in the wodpress mu table

    mysql> select option_value from wp_2_options where option_name='siteurl';
    +----------------------------------------------+
    | option_value |
    +----------------------------------------------+
    | http://161.117.126.76/wordpress-mu/index.php |
    +----------------------------------------------+
    1 row in set (0.00 sec)

    The fix is to set to remove the index.php.

    mysql> update wp_2_options set option_value='http://161.117.126.76/wordpress-mu/' where option_name='siteurl';
    Query OK, 1 row affected (0.00 sec)
    Rows matched: 1 Changed: 1 Warnings: 0

    mysql> commit;
    Query OK, 0 rows affected (0.00 sec)

    When I first tried to install wordpress mu there was issues with it connecting to the database. I didnt have GRANT privileges setup properly for the user. Not sure if this caused the above issue. Hope it helps someone.

  3. skadaha
    Member
    Posted 14 years ago #

    Hope it helps someone.

    It helped me. thanks!

    Note: perhaps this case should be considered in the admin interface - i.e. updating the base url should be possible through an admin setting? or perhaps simply a check the DOMAIN_CURRENT_SITE matches the option_value above.

About this Topic

  • Started 14 years ago by craig777
  • Latest reply from skadaha