ispCP - Board - Support
Ignoring users php.ini - Printable Version

+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: Usage (/forum-34.html)
+--- Thread: Ignoring users php.ini (/thread-7352.html)



Ignoring users php.ini - Schokobecher - 08-02-2009 01:48 AM

Hey Folks,
It's the real first problem I experience with IspCP.
Apache2 (or IspCP, I really don't know) keeps suddenly ignoring my php.ini for customer domains.

Example:
I had enabled phpinfo on my domain tile44.org
and it states:
"Loaded Configuration File /var/www/fcgi/tile44.org/php5/php.ini "

But even after I changed disable_funtions to include phpinfo, I still get the phpinfo page.

On the other hand I tried changing the open_basedir on another domain, but it keeps complaining that open_basedir is still in effect.
Then I tried to enable phpinfo, but all I got was:

Warning: phpinfo() has been disabled for security reasons in /var/www/virtual/cavewiki.org/htdocs/info.php on line 2

It's goes total random.
I also tried editing the master php.ini (/var/www/fcgi/master/php5/php.ini) but it had no effect for the other domains.

The strange thing is, that I can delete the php.inis and Apache does not complain about them.

So anyone got a clue on this?

€: System is a Debian Lenny with 1.0.0 Updated Smile


RE: Ignoring users php.ini - kurgans - 08-02-2009 02:04 AM

Have you restarted apache after making changes on php.ini?


RE: Ignoring users php.ini - Schokobecher - 08-02-2009 02:10 AM

I'm sorry that I didn't said that so directly.
Yeah I did.
Millions of times.


RE: Ignoring users php.ini - kurgans - 08-02-2009 02:28 AM

Have you done the modification correctly and should work.
I have never had this problem, I think it may be some configuration problems.

I would restore the configuration and return to try again the changes in php.ini in domains not in master.


http://www.isp-control.net/documentation/howto/ispcp/regenerate_config


RE: Ignoring users php.ini - Schokobecher - 08-02-2009 02:45 AM

So I regenerated all Configs, but the php.ini didn't change at all.
-> Query OK, 0 rows affected (0.00 sec)


Result:
Problem still exists.

€:
http://www.isp-control.net/forum/thread-2844.html
Had a similar Problems (but that was RC3)

kinda bugs me


RE: Ignoring users php.ini - kilburn - 08-02-2009 10:43 AM

Are you using fastcgi, fcgid or mod_php?


RE: Ignoring users php.ini - Schokobecher - 08-02-2009 12:08 PM

PHP 5.2.6-1+lenny3 with Suhosin-Patch 0.9.6.2 (cgi-fcgi)
so it should be FastCGI (If I'm correct Smile )


RE: Ignoring users php.ini - MasterTH - 08-02-2009 02:56 PM

for recreation of the php.ini u have to delete the php.ini in /var/www/fcgi/domain.tld/...
then follow the howto regenerate the config-files and the php.ini will be created again.


RE: Ignoring users php.ini - theprincy - 08-14-2009 09:28 AM

hi, i have the same problem

this is a /master/php.ini

Code:
; This directive allows you to disable certain functions for security reasons.
; It receives a comma-delimited list of function names. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
;disable_functions = show_source, system, shell_exec, passthru, exec, phpinfo, shell, symlink
;disable_functions = dl, passthru, system, exec, shell_exec
disable_functions =

this is a revlab.net/php.ini


Code:
; This directive allows you to disable certain functions for security reasons.
; It receives a comma-delimited list of function names. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
;disable_functions = show_source, system, shell_exec, passthru, exec, phpinfo, shell, symlink
;disable_functions = dl, passthru, system, exec, shell_exec
disable_functions =

i have reloaded infinty apache but nothing change

http://revlab.net/info.php
I do not know where to look ... more
after restarting the server it worked ...


RE: Ignoring users php.ini - Schokobecher - 09-22-2009 08:34 AM

Try restarting your server.
I don't know why, but it works!
(event it's been above a month, maybe someone got the same problem again.)