By dare2bfree on

warning: require_once(modules/system/system.admin.inc) [function.require-once]: failed to open stream: No such file or directory in /var/www/virt/dev.fija.org/htdocs/includes/menu.inc on line 344.

I had 6.2 installed and it was working ok. I ended up having to leave the project alone for a couple of months and recently got back to it. When I signed in and tried to access the administer section I get the above error.

Can someone please tell me in plain english what it means and more importantly... how to fix it?

Thank you in advance!

⋅ Categories: Drupal 6.x

Comments

vm’s picture

vm commented

Using the error message as a search term here on drupal.org it seems that others who've had this problem found themselves missing files needed by drupal to run correctly.

considering you're using 6.2 and the latest release is 6.6 I'd consider upgrading or starting over using the latest release to insure you are most secure and bug free.

dare2bfree’s picture

dare2bfree commented

Thanks for the suggestion, but I have searched. I will try again with different terms to see what I may have missed though.

I did try 6.6 since it was available and it was worse. I had a whole page of errors that were similar. It wouldn't even run the install script. So I deleted it and put my restored my stuff from a backup I made to at least get me to where I could see something other than errors.

WorldFallz’s picture

WorldFallz commented

Sometimes finding the right words in an error message that will yield results can be difficult. I usually have pretty good success with a small quoted part of the error message and the line number. In this case, there's a bunch of links. Hopefully, you've not seen those yet and one of them will help.

===
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime." - Lao Tzu
"God helps those who help themselves." - Ben Franklin
"Search is your best friend." - Worldfallz

vm’s picture

vm commented

I didn't mean that you should search, I was stating I searched.

without knowing what those errors were with 6.6 it's hard to help.

using an insecure build of drupal will bring about more pain and frustration than working with the errors you were getting. Some of the security fixes that went into core between 6.2 and 6.6 are very important and not using 6.6 leaves you open to XSS exploits.

gpk’s picture

gpk commented

1. On your server, PHP's include_path setting doesn't include the current directory of the active script
2. Sometimes Drupal attempts to include a PHP file without unambiguously specifying its location (#296194: Some includes are not anchored).

Given that that bug is still languishing in the issue queue the workaround is to add the characters ".:" (minus the quotes) to the include_path. If your server is running PHP as CGI you may be able to do this in a custom php.ini file; otherwise adding

ini_set('include_path', '.:' . ini_get('include_path'));

to the bottom of your settings.php file should do the trick, assuming the server is running *nix.

gpk
----
www.alexoria.co.uk

gpk
----
www.alexoria.co.uk

dare2bfree’s picture

dare2bfree commented

Great! That fixed it.

Since this got 6.2 working, I went ahead and tried the upgrade to 6.6 again since the errors were similar. It fixed the errors I was getting with 6.6 as well. So now I'm up with 6.6 and all the updates.

Thanks guys!

gpk’s picture

gpk commented

Probably your host had modified their php.ini and more especially the include_path setting. It's quite unusualy not to include the script's current directory though. You might want to have a word with them.

gpk
----
www.alexoria.co.uk

gpk
----
www.alexoria.co.uk