After config, "Failed opening '/tmp/tpl_0_7_0_7... .php' for inclusion".

List overview All Threads
Download

newer

older

move upload directory into database

Enotif + Eauthent 2.00/CVS for CVS...

Erik Hermansen

13 Dec 2004 13 Dec '04

12:35 a.m.

I copied MediaWiki 1.3.8 files over to my web-accessible dir. I created a MySQL database and user. I ran the Config\index.php page and it reported back with no errors. I looked at the new database and it is populated with tables from the config script. Everything looked good at that point. Then I browsed to the top-level page of the wiki, and got this error: Warning: Failed opening '/tmp/tpl_0_7_0_7d90f7cef16f0e547fab72ff18d4b4a1.php' for inclusion (include_path='.:/home/httpd/vhosts/mydomain.com/httpdocs/mediawiki:/hom…) in /home/httpd/vhosts/mydomain.com/httpdocs/mediawiki/PHPTAL-NP-0.7.0/libs/PHPTAL/Template.php on line 430 [pear_error: message="Template function 'tpl_0_7_0_7d90f7cef16f0e547fab72ff18d4b4a1' not found (template source : /home/httpd/vhosts/mydomain.com/httpdocs/mediawiki/templates/xhtml_slim.pt" code=0 mode=return level=notice prefix="" info=""] The file that it complains about is in fact present at "/tmp/tpl_0_7_0_7d90f7cef16f0e547fab72ff18d4b4a1.php". And I'm not sure how MediaWiki works, but this file must have been created by running the PHPs since I didn't put it there. This leads me to believe that the PHP should have permissions to read from that file. So what's wrong here? I apologize if I am asking something that has come up before. I tried to find an existing answer to this, since I am not doing anything very unusual and it seems like it must be something that lots of people would run into. But unfortunately I couldn't find anything on it. -Erik

Show replies by date

Brion Vibber

13 Dec 13 Dec

12:59 a.m.

New subject: [Mediawiki-l] After config, "Failed opening '/tmp/tpl_0_7_0_7... .php' for inclusion".

On Dec 12, 2004, at 4:35 PM, Erik Hermansen wrote:

...

Everything looked good at that point. Then I browsed to the top-level page of the wiki, and got this error: Warning: Failed opening '/tmp/tpl_0_7_0_7d90f7cef16f0e547fab72ff18d4b4a1.php' for inclusion

Give 1.4beta3 a try; it no longer uses the PHPTal template system and doesn't depend on using a compiled template written to /tmp. -- brion vibber (brion @ pobox.com)

Erik Hermansen

1:42 a.m.

New subject: [Mediawiki-l] After config, "Failed opening '/tmp/tpl_0_7_0_7... .php' for inclusion".

At 04:59 PM 12/12/2004 -0800, Brion Vibber wrote:

...

On Dec 12, 2004, at 4:35 PM, Erik Hermansen wrote:

Everything looked good at that point. Then I browsed to the top-level page of the wiki, and got this error: Warning: Failed opening '/tmp/tpl_0_7_0_7d90f7cef16f0e547fab72ff18d4b4a1.php' for inclusion

Give 1.4beta3 a try; it no longer uses the PHPTal template system and doesn't depend on using a compiled template written to /tmp.

Brion, 1.4beta3 does seem to work now. Thank you very much for your quick reply. During setup of 1.4beta3 I had three warnings like this: Warning: open_basedir restriction in effect. File is in wrong directory in /home/httpd/vhosts/mydomain.com/httpdocs/mediawiki/maintenance/updaters.inc on line 9 ...yet, the setup seemed to complete without problems, and I can access my freshly set up mediawiki without trouble. This warning seems like it may have been related to my previous problems with 1.3. My theory is that the PHP code was failing to access a file in /tmp because of the open_basedir restriction. Since the warnings appeared during 1.4beta3 setup, it makes me think I might have some other problems down the road and might need to remove the "open_basedir" restriction (don't want to). >>shrug<< Anyhow, thanks again. -Erik

Denny Schierz

12:05 p.m.

New subject: [Mediawiki-l] After config, "Failed opening '/tmp/tpl_0_7_0_7... .php' for inclusion".

hi, Am Sonntag, den 12.12.2004, 17:42 -0800 schrieb Erik Hermansen:

...

Since the warnings appeared during 1.4beta3 setup, it makes me think I might have some other problems down the road and might need to remove the "open_basedir" restriction (don't want to). >>shrug<<

i strongly recommend, that you change your apache(virtual) config like this: php_admin_flag engine on php_admin_value open_basedir "/home/httpd/userFoo/websites/domain.foo/htdocs:/home/httpd/userFoo/websites/domain.foo/tmp:." php_admin_value upload_tmp_dir /home/httpd/userFoo/websites/domain.foo/tmp php_admin_value session.save_path /home/httpd/userFoo/websites/domain.foo/tmp After that, you're a bit safer :-), don't let write apache to /tmp cu denny -- Denny Schierz <cuall(a)gmx.de>

Erik Hermansen

14 Dec 14 Dec

10:36 p.m.

New subject: [Mediawiki-l] After config, "Failed opening '/tmp/tpl_0_7_0_7... .php' for inclusion".

At 01:05 PM 12/13/2004 +0100, Denny Schierz wrote:

...

hi, Am Sonntag, den 12.12.2004, 17:42 -0800 schrieb Erik Hermansen:

Since the warnings appeared during 1.4beta3 setup, it makes me think I might have some other problems down the road and might need to remove the "open_basedir" restriction (don't want to). >>shrug<<

Jamie Bliss

15 Dec 15 Dec

12:29 a.m.

New subject: [Mediawiki-l] After config, "Failed opening '/tmp/tpl_0_7_0_7... .php' for inclusion".

That's possible, but I think that uploads (through the interface) goto the images directory. I believe that the tmp directory is just for PHPTAL, and I know the specific file is PHPTAL cache file. On Tue, 14 Dec 2004 14:36:18 -0800, Erik Hermansen <erikh(a)caravelgames.net> wrote:

...

At 01:05 PM 12/13/2004 +0100, Denny Schierz wrote:

hi, Am Sonntag, den 12.12.2004, 17:42 -0800 schrieb Erik Hermansen:

Since the warnings appeared during 1.4beta3 setup, it makes me think I might have some other problems down the road and might need to remove the "open_basedir" restriction (don't want to). >>shrug<<

Ah, but both the stable and latest versions of mediawiki seem to need to write to /tmp. Your advice is probably good, but I don't know how to reconcile it with this. Is the worry that an attacker would upload something to /tmp and execute it? -Erik _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l

-- ------------------------------------------------------------------- http://endeavour.zapto.org/astro73/ Thank you to JosephM for inviting me to Gmail!

Erik Hermansen

12:41 a.m.

New subject: [Mediawiki-l] After config, "Failed opening '/tmp/tpl_0_7_0_7... .php' for inclusion".

At 07:29 PM 12/14/2004 -0500, Jamie Bliss wrote:

...

That's possible, but I think that uploads (through the interface) goto the images directory. I believe that the tmp directory is just for PHPTAL, and I know the specific file is PHPTAL cache file.

After I installed 1.4, it wrote files in "\tmp" prefixed with "sess_". They contained mediawiki login names and maybe a few other things. This might just be how PHP stores session variables--not sure. -Erik

Brion Vibber

12:59 a.m.

New subject: [Mediawiki-l] After config, "Failed opening '/tmp/tpl_0_7_0_7... .php' for inclusion".

On Dec 14, 2004, at 4:41 PM, Erik Hermansen wrote:

...

That's just how PHP stores session variables. You can change the directory in php.ini. (If using memcached, we also have a module to store sessions in memcached.) PHP's safe_mode, open_basedir etc settings should not affect session files as far as I know (and should thus be a good way to keep one user's scripts from snarfing another's session files). PHP may also store uploaded files temporarily in /tmp, again this is configurable in php.ini. I'm less sure about whether open_basedir would affect it. I've taken a quick grep through 1.4, and the only place I see /tmp being explicitly used outside of the test suites is in diff merging, where it tries to shell out to diff3. None of this should trigger on an include statement in the installer... -- brion vibber (brion @ pobox.com)

Erik Hermansen

1:44 a.m.

New subject: [Mediawiki-l] After config, "Failed opening '/tmp/tpl_0_7_0_7... .php' for inclusion".

At 04:59 PM 12/14/2004 -0800, Brion Vibber wrote:

...

On Dec 14, 2004, at 4:41 PM, Erik Hermansen wrote:

Interesting.

...

PHP may also store uploaded files temporarily in /tmp, again this is configurable in php.ini. I'm less sure about whether open_basedir would affect it. I've taken a quick grep through 1.4, and the only place I see /tmp being explicitly used outside of the test suites is in diff merging, where it tries to shell out to diff3. None of this should trigger on an include statement in the installer...

I've conferred with another guy that works on the site, and his experience with some other software on the same server matches mine. We have some kind of intermittent file permissions problem that began after this big update of our server management software (Plesk 7). The symptom is that when PHP creates a file, sometimes the owner of the file won't be given permissions. Whether or not the PHP-created file gets correct permissions seems to be random. Knowing this, it explains why the 1.3 installation didn't work. The template file was created by mediawiki, and for some @!@#! reason the permissions for the owner to read/write were not set when the file was created. I'm not going to throw this burden on the list since it isn't a problem specific to mediawiki. But it does explain why 1.3 wouldn't work for me and some other problems I'm having in 1.4 that I haven't described on the list. It seems possible to me that this same file permissions problem is a cause of the open_basedir warnings coming up during 1.4 installation, but I'm not sure. I don't recommend troubleshooting that any further until I can fix this irritating not-mediawiki-related problem which might be responsible. If the warnings are still there after that, then maybe it is worth looking into further. -Erik

Brion Vibber

14 Dec 14 Dec

2:05 a.m.

New subject: [Mediawiki-l] After config, "Failed opening '/tmp/tpl_0_7_0_7... .php' for inclusion".

On Dec 12, 2004, at 5:42 PM, Erik Hermansen wrote:

...

Brion, 1.4beta3 does seem to work now. Thank you very much for your quick reply.

Great!

...

During setup of 1.4beta3 I had three warnings like this: Warning: open_basedir restriction in effect. File is in wrong directory in /home/httpd/vhosts/mydomain.com/httpdocs/mediawiki/maintenance/ updaters.inc on line 9

Line 9 is: require_once 'convertLinks.inc'; That's kind of a weird error... What's open_basedir actually set to? (If it's an administrative imposition, try phpinfo() or ini_get() if they haven't been disabled to check the setting.) -- brion vibber (brion @ pobox.com)

Erik Hermansen

9:44 p.m.

New subject: [Mediawiki-l] After config, "Failed opening '/tmp/tpl_0_7_0_7... .php' for inclusion".

At 06:05 PM 12/13/2004 -0800, Brion Vibber wrote:

...

On Dec 12, 2004, at 5:42 PM, Erik Hermansen wrote:

Line 9 is: require_once 'convertLinks.inc'; That's kind of a weird error...

I have to point out there were two more warnings just like this but on different lines. Unfortunately, I'd need to reinstall to see which exact lines they were. If it seems particularly valuable, I don't mind doing it later.

...

What's open_basedir actually set to?

It is set to the top-level directory of documents served by Apache for this particular virtual domain. Now that I look at it, I also see that "tmp" is included, which probably rules out my earlier explanation for why 1.3 wouldn't install. Let me know if I can do anything to narrow down the cause of the warnings. It seems it would be better to avoid reporting them if they are benign or give a more specific warning if they aren't. -Erik

7077

days inactive

7079

days old

mediawiki-l@lists.wikimedia.org

Manage subscription

10 comments

4 participants

tags (0)

participants (4)

Brion Vibber
Denny Schierz
Erik Hermansen
Jamie Bliss