I have updated cli and nginx to use php 7.2 using the follow commands:
sudo apt-get -y install gcc make autoconf libc-dev pkg-config
sudo apt-get -y install libmcrypt-dev
sudo pecl install mcrypt-1.0.1
sudo bash -c "echo extension=/usr/lib/php/20170718/mcrypt.so > /etc/php/7.2/cli/conf.d/mcrypt.ini"
sudo bash -c "echo extension=/usr/lib/php/20190902/mcrypt > /etc/php/7.2/mods-available/mcrypt.ini"
However when I run:
php -i | grep "mcrypt"
I get the following response:
PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php/20190902/mcrypt' (tried: /usr/lib/php/20190902/mcrypt (/usr/lib/php/20190902/mcrypt: cannot open shared object file: No such file or directory), /usr/lib/php/20170718//usr/lib/php/20190902/mcrypt.so (/usr/lib/php/20170718//usr/lib/php/20190902/mcrypt.so: cannot open shared object file: No such file or directory)) in Unknown on line 0
/etc/php/7.2/cli/conf.d/mcrypt.ini
phpinfo() doesn’t display mcrypt info either, I’m guessing for the same reason.
I’ve tried changing the path in /etc/php/7.2/cli/php.ini; ‘extension_dir’ is actually commented out, but if I uncomment it, whatever I update it to, it gets appended to ‘/usr/lib/php/20170718/’.
Why does my system insist on using ‘/usr/lib/php/20170718/’ as the path?
How do I get mcrypt working for cli and nginx?
Subscribe
Share
Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Sign in to AnswerThese answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
HEY I FOUND A SOLUTION firstly Goto /etc/php/7.2/cli/conf.d and /etc/php/7.2/cgi/conf.d and /etc/php/7.2/mods-available and /etc/php/7.2/apache2/conf.d and remove mcrypt.ini from all those folder.And back up mcrypt.ini if u need
this is beacause php 7.2 dosent depend on it
Hello, @ecell100
As you can see from the warning message, the problem is with the actual path of the library:
You can either try running these two commands:
or change the path manually by editing the ini files directly. You can then again test if everything is loaded correctly:
Keep in mind that you need to restart Nginx as well in order to make sure the new library is loaded.
Let me know how it goes.
Regards, Alex