Hi All,

I get these weird errors when I tried to install a fresh beta7.

Warning: require_once(./profiles/managingnews/managingnews.profile) [function.require-once]: failed to open stream: No such file or directory in /var/www/install.php on line 89

Fatal error: require_once() [function.require]: Failed opening required './profiles/managingnews/managingnews.profile' (include_path='.:/usr/share/php:/usr/share/pear') in /var/www/install.php on line 89

Notes

Regular Drupal 6.15 installs fine, multisite setup, Ubuntu server on Linode, fresh database, fresh beta7 download, fresh settings.php file.

Weird!

Thanks

Comments

saltcod’s picture

saltcod commented

This issue is marked beta6, but actually refers to beta7 released today.

i just went right through the process of installing a regular D6.15 site. Worked perfectly. I chose the normal install instead of Managing News at the profiles screen, and things went perfectly.

But when I try to use the managing news profile, I get the above errors. Incidentally, I tried installing a beta6 site with the same result - exact same errors as above. Perhaps it has to do with my multisite setup?

saltcod’s picture

saltcod commented

hurm. I think this may be an issue with [poorly conceived] ubuntu permissions. I'm going to get those amended and report back.

I tried to add a new node at my main site but got a 403 Forbidden error - suggesting a global permissions, unrelated to the managing news install.

stay tuned!

milos.kroulik’s picture

milos.kroulik commented

I think, that beta7 release could be badly built, because it's only falf as big as the previous betas. In my opinion this could mean, that some parts are missing. Just my 5 cents.

alex_b’s picture

alex_b commented

I think, that beta7 release could be badly built, because it's only falf as big as the previous betas.

The reason why the download is smaller is because we slimmed down radically on the OpenLayers library. We rolled our own flavor of it that only includes what Managing News uses.

saltcod: any news? MN beta 7 is working fine over here.

epiraces’s picture

epiraces commented

Hi,

I had a similar issue. Solved by adding increasing the memory limit for PHP in settings.php

Add:

ini_set("memory_limit","32M"); (I actually used way more -> 256M but I'm paranoid)

Once you do it, and before running install again make sure to clear your browser cache.

Hope it helps :-)

saltcod’s picture

saltcod commented

This really is weird. I got the permissions right finally, but I'm still getting that same error. I've got 96MB of memory.

I downloaded a fresh copy of beta7, made a new database, and am able to go right through a normal Drupal install from the opening screen. But, when i try and install MN, I get the error screen.

I'm going to try and remove everything and start from scratch again this afternoon.

epiraces’s picture

epiraces commented

I think I finally got it. My previous post was probably misleading. I tried after that and got the same error. Then I got to a post that mentioned mod_security as an issue for this type of install.

I didn't want to disable mod_security so I added some rules:


SecRuleRemoveById 960010
SecRuleRemoveById 960015
SecRuleRemoveById 960032
SecRuleRemoveById 950107

Two post that have more info:

http://www.convolutedtheory.com/tech/mod_security-and-drupal-62-issues/
http://drupal.org/node/695902

Hope this helps.

alex_b’s picture

alex_b commented

#7 - could you give us some background on these rule modifications?

epiraces’s picture

epiraces commented

The issue is still blurry to me, but it seems that there is a difference if you are using mod_security and mod_security2. It seems that drupal's .htaccess deals fine with the first but that some minor tweaking is required if you are using *2.

I found a post that has some info: http://blog.webhostingdiscussion.net/site-and-server-security/wordpress-... in case someone can help to understand this.

Another potentially useful URL: http://optics.csufresno.edu/~kriehn/fedora/fedora_files/f11/howto/modsec...

I had also issues installing OpenPublish and the lines above solved them too. I'll retry tonight with and without them to make sure that I can replicate the issue.

saltcod’s picture

saltcod commented

Sorry for posting to an old issue, but I'm just able to get back to it now.

I just tried the new Beta9 today with no success [as before]. After much reading on mod_security, I'm not sure that that's the problem. In fact, I'm not even sure if that module is installed. It's not listed in Apache's mods-enabled folder.

I tried various tricks from around the forums about disabling mod_security with .htaccess, but that had no effect. I still get the same error message as above.

Any new insights floating around?

Thanks

Terry

saltcod’s picture

saltcod commented

.....in fact, I just tried a :

apt-get purge libapache-mod-security

and that told me that: Package libapache-mod-security is not installed, so not removed

So I guess that rules out mod_security?

saltcod’s picture

saltcod commented

Sorry to hound on this issue, but with Beta9 I'm getting a new error:

Fatal error: require_once() [function.require]: Failed opening required './profiles/managingnews/managingnews.profile' (include_path='.:/usr/share/php:/usr/share/pear') in /var/www/install.php on line 89

I thought that this might have meant that Pear isn't installed, so I tried to apt-get it, but I get told then that it is installed.

A continuing series of unknown error messages!

Thanks

Terry

alex_b’s picture

alex_b commented
Status: Active » Closed (fixed)

Sorry for not getting back on this but these reports look a lot like issues beyond the actual Managing News application. There must be something fundamentally broken in your set up (permissions?) if the profile file can't be found. I'll set this to fixed now.