I deploy my project on the battle server and every day I encounter new and new problems ..

I configured a bunch of nginx + uwsgi + web.py

Running the test application, I calmly connect to the database and output the data from it.

But it is impossible to connect from the main application. Even to the test database. Writes

File "/usr/local/lib/python2.7/dist-packages/MySQLdb/connections.py", line 193, in __init__ super(Connection, self).__init__(*args, **kwargs2) OperationalError: (2003, "Can't connect to MySQL server on '127.0.0.1' (111)")

The bd connection file is displayed in a separate python module config.py. Nothing but connections are missing in it ...

How can it be that one application connects and the other does not? How to solve a problem? Help please ... I do not sleep the second week with the setting of the server, already no strength.

The last lines of the log look like this

 170606 0:01:41 InnoDB: Operating system error number 11 in a file operation. InnoDB: Error number 11 means 'Resource temporarily unavailable'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html 170606 0:01:41 InnoDB: Could not open or create data files. 170606 0:01:41 InnoDB: If you tried to add new data files, and it failed here, 170606 0:01:41 InnoDB: you should now edit innodb_data_file_path in my.cnf back 170606 0:01:41 InnoDB: to what it was, and remove the new ibdata files InnoDB c reated 170606 0:01:41 InnoDB: in this failed attempt. InnoDB only wrote those files fu ll of 170606 0:01:41 InnoDB: zeros, but did not yet use them in any way. But be caref ul: do not 170606 0:01:41 InnoDB: remove old data files which contain your precious data! 170606 0:01:41 [ERROR] Plugin 'InnoDB' init function returned error. 170606 0:01:41 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 170606 0:01:41 [ERROR] Unknown/unsupported storage engine: InnoDB 170606 0:01:41 [ERROR] Aborting 170606 0:01:41 [Note] mysqld: Shutdown complete
  • And what do you listen muskl? Port or socket? netstat -nlp | grep mysql && netstat -nlp | grep :3306 netstat -nlp | grep mysql && netstat -nlp | grep :3306 3306 standard port, you can connect both by port and by socket. And what is the status of the service? Run? - Igor Lavrynenko
  • netstat -nlp | grep "mysql\|3306" netstat -nlp | grep "mysql\|3306" - Igor Lavrynenko
  • Thanks for the feedback. netstat -nlp | grep "mysql\|3306" netstat -nlp | grep "mysql\|3306" issued the following tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 28761/mysqld unix 2 [ ACC ] STREAM LISTENING 60608 28761/mysqld /var/run/mysqld/mysqld.sock that, I connect from the test application, everything is OK, I disconnect, run the main one and the hell, and if I connect again to the test application, then everything is OK with the same bd ... There are not enough nerves, more than a year of work on the application and already 2 weeks without sleepy nights in the server setup ... Though on Azure go to ... - Electro Boy
  • Lay out the connection code for your and for the test, you did not forget to specify the port Muskl? - Igor Lavrynenko
  • I copied his copy ... Now applied new access rights and a group with the user www-data and still does not work (( - Electro Boy

0