Question

After "sudo apt-get upgrade" phpmyadmin doesn't work, how can I fix it?

  • Posted on June 24, 2014
  • ionutzbfAsked by ionutzbf

After “sudo apt-get upgrade” phpmyadmin doesn’t work, how can I fix it? - I have installed “LEMP on Ubuntu 14.04” not other installs


Submit an answer

This textbox defaults to using Markdown to format your 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 or Sign Up to Answer

These 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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Ran into same problem. I just edited my /etc/php5/fpm/pool.d/www.conf file.

Set

listen.owner = www-data  
listen.group = www-data 
listen.mode = 0660 

Restarted php5-fpm.

Logs showed 2014/06/24 20:04:25 [crit] 2223#0: *10547 connect() to unix:/var/run/php5-fpm.sock failed (13: Permission denied) while connecting to upstream, client: <snip>

Update (Nice we can edit the posts now)

Looking into this more closely it looks like it fixes bug CVE-2014-0185 incorrect socket permissions.

CVE-2014-0185

The default PHP FPM socket permission has been changed from 0666
to 0660 to mitigate a security vulnerability (CVE-2014-0185) in PHP
FPM that allowed any local user to run a PHP code under the active
user of FPM process via crafted FastCGI client.

The default Debian setup now correctly sets the listen.owner and
listen.group to www-data:www-data in default php-fpm.conf.  If you
have more FPM instances or a webserver not running under www-data
user you need to adjust the configuration of FPM pools in
/etc/php5/fpm/pool.d/ so the accessing process has rights to
access the socket.

I had a similar error after php update.

  1. Go to /var/run

cd /var/run

#sudo chmod 666 php5-fpm.sock 2.Enjoy!

Are you seeing any output in the Nginx error log? Run: <pre> tail -n25 /var/log/nginx/error.log </pre>

What packages were upgraded?