Module 'SourceGuardian' already loaded error after PHP 5.3.4 to 5.3.6 update

[luigidelgado]

Hi. After upgrading the software in my WHM I've been having this error repetead several times... I don't know how to solve it I have checked PHP config no SourceGuardina is loaded:

[01-Apr-2011 03:31:01] PHP Warning: Module 'SourceGuardian' already loaded in Unknown on line 0
[01-Apr-2011 03:31:01] PHP Warning: Module 'SourceGuardian' already loaded in Unknown on line 0
[01-Apr-2011 03:32:01] PHP Warning: Module 'SourceGuardian' already loaded in Unknown on line 0
[01-Apr-2011 03:32:01] PHP Warning: Module 'SourceGuardian' already loaded in Unknown on line 0
[01-Apr-2011 03:33:01] PHP Warning: Module 'SourceGuardian' already loaded in Unknown on line 0
[01-Apr-2011 03:33:01] PHP Warning: Module 'SourceGuardian' already loaded in Unknown on line 0
[01-Apr-2011 03:34:01] PHP Warning: Module 'SourceGuardian' already loaded in Unknown on line 0
[01-Apr-2011 03:34:01] PHP Warning: Module 'SourceGuardian' already loaded in Unknown on line 0
[01-Apr-2011 03:35:01] PHP Warning: Module 'SourceGuardian' already loaded in Unknown on line 0
[01-Apr-2011 03:35:01] PHP Warning: Module 'SourceGuardian' already loaded in Unknown on line 0...

and going and going... looks like every minute, two times, it is trying to load that... I dont Get it...

This appears in the error log of one of the hosted domains.

[cPanelTristan]

Are you using suPHP and does that account have its own php.ini file that might be listing that in it? Also, even when SourceGuardian is installed on a machine I tested, it doesn't show any lines in the php.ini file on a grep of it:

grep -i guard /usr/local/lib/php.ini

I do show entries on a php -i check though:

php -i | grep -i guardian

This returns:

# php -i | grep guardian
sourceguardian.restrict_unencoded => 0 => 0

The actual way to check if SourceGuardian is installed is this way:

# php -m | grep -i guardian
SourceGuardian

[luigidelgado]

Thank you Tristan,
suPHP is Enabled for 5.x, the php.ini file in the user account does not call any SourceGuardian...

my php.ini doesnt recall anything as you say...
my php -i shows:

SourceGuardian Loader Support => enabled
SourceGuardian Loader Version => 8.2
SourceGuardian Loader Build Number => 0x00000011
sourceguardian.restrict_unencoded => 0 => 0

I have checked and none of the users in the server needs SourceGuardian, how can I disable it?

[cPanelTristan]

Luis, you should be able to do the following to uninstall it:

/scripts/phpextensionmgr uninstall SourceGuardian

After running that command, you can again try to check if it shows in php -i on a grep for it.

[luigidelgado]

Thanks Tristan... I'll check... I don't know why is happening this... I try to kkep my server as lean as possible.
I will make a double check my clients site (it's strange its calling it but not needing it) and if not, I will uninstall it.

BTW it's incredible how this thread has been already indexed by Google in the SERP's

(search: disabling sourceguardian cpanel)

[cPanelTristan]

I've been amazed with the speed of the results for our forum being indexed in Google as well.

[luigidelgado]

Tristan....
I FOUND IT.
In fact I now recall a similar problem I had before... may be a bug or something similar... the extension for calling sourceguardian got duplicated in the file just after the end of the php.ini:

; Local Variables:
; tab-width: 4
; End:
extension="ixed.5.3.lin"

Last month just after using the php configuration editor in cPanel for editing memory limits I had the same problem with extensions appeareang at the end:

extension = "suhosin.so"
extension = "pdo.so"
extension = "pdo_sqlite.so"
extension = "sqlite.so"
extension = "pdo_mysql.so"

The problem has to do with the the quotes "" Somehow, maybe Magic Quotes or semthing but I had to edit the php.ini manually to remove the extension after the end of the file and PROBLEM SOLVED.

[cPanelTristan]

There are a couple of cases in our system about php.ini being edited in WHM > PHP Configuration Editor adding duplicate entries, so this is likely related to those cases. For the time being, I highly suggest editing the file manually only. The cases are 46972 and 47683, respectively. You can review our change log at Change Logs location to see when the cases are referenced as released into a set version.

You can see the existing cPanel versions for each tier at Downloads - cPanel Inc. location.

[luigidelgado]

Great Tristan.
Thanks for your assistance.