Topic: [SOLVED] PHP Encryption on two SME7.3 servers

[logan]

Good day,

some background:
I have two SME 7.3 servers running. One is for me as an IT member to play with and learn etc while the other is the main server used by the company. The main server is primarily maintained by someone else. Both are basically the same regarding versions and updates etc.

On my playing server, after must struggle i managed to get mcrypt to be added as a module for PHP and all php code using mcrypt on this server works fine.
The process of installation was "yum localintal libmhash....rpm libmcrypt....rpm php-mcrypt...rpm php-mhash...rpm" then reboot and YAY all was fine. The rpms were downloaded from net.
Phpinfo() shows "/etc/php.d/mcrypt.ini, /etc/php.d/mhash.ini" in the "additional .ini files parsed" section.

My problem is that i ran the same rpms in the same way on the main server. All files seem to have been added where they should be but phponfo() on this server does not show "/etc/php.d/mcrypt.ini, /etc/php.d/mhash.ini" and thus the same working php code copied from the test server does not work.
There is one thing during the "installation" process that bothers me, and that is a reply from server during install of the php-.....rpm files. The reply is 'httpd' is not a valid service name. But i have no idea what that means.

I have compared location of files on both servers as well as all templates etc and both are the same.
I am unsure what direction to move in from here, any help would be greatly appreciated! i think i am simply missing something but not sure what?

PS maybe this would be the correct question:
Is there any way i can check that the PHP is checking/using the installed mcrypt and mhash modules? I think something like this was done automatically on the play server but not on the main server.

Thank you,
David

----------------------

EDIT:
I think i should be dragged behind the chemical shed and be shot for stupidity!

in order to get everything working i had to expand the php.ini and httpd templates

Code: [Select]

expand-template /etc/httpd/cpnf/httpd.conf
expand-template /etc/php.ini
/etc/init.d/httpd-e-smith restart


[raem]

logan

I think i should be dragged behind the chemical shed and be shot for stupidity!
in order to get everything working i had to expand the php.ini and httpd templates

That's why everyone should have a test server.

[logan]

hehe
I do fully agree with you!

[william_syd]

logan

That's why everyone should have a test server.

And with that test server should be clear, concise documentation detailing every step taken to achieve a particular outcome.

[logan]

Once again, agreed, but i must say from experience i have learned that documentation of a practical level takes some 'skill' and not many people have that! (including me)

hmmm a question then: what would be best, having electronic documentation or keeping everything in paper and files?