New answers tagged timeout
If it's available or can be installed, take a look at netcat. You could do something like this. On the server run: nc -l 31415 On the client run: nc -w 5400 <server> 31415 You can change the port number to anything you like, just make sure you can reach it from where you are testing. A timeout of 90 minutes (-w 5400) is set in the example ...
You can also add the settings suggested by others as defaults in your ~/.ssh/config file, so you don't have to pass them to ssh every time you initiate a connection: nano ~/.ssh/config and add: TCPKeepAlive=no ServerAliveInterval=15
It turns out that the solutions is as simple as specifying a larger timeout. It does matter which timeout though (there are several timeout switches for SqlPackage.exe and it's neither the connection timeout specifiable in a connection string), it's CommandTimeout. The below modified command won't fail even with a bacpac containing a large number of tables ...
You have probably problem with persistent Zabbix DB connections. Tune also your TCP stack - see hints for persistent connections http://www.slideshare.net/Severalnines/haproxy-mysql-slides
Let's just stick to the documentation and take notes: The most common reason for the MySQL server has gone away error is that the server timed out and closed the connection. Connection is closed if mysqld receives larger or out-of-order packet. You might want to twick max_allowed_packet variable. Set it some what larger than what it is. Is your ...
If you distrust the application, you can set a slow log in order to log each request that lasts more than N seconds (on fpm) by adding on your fpm pool configuration (default location tends to be (debian): /etc/php5/fpm/pool.d/www.conf) slowlog = /path/to/slow.log request_slowlog_timeout = Ns change the N with amount of seconds you want, get it lower ...
Top 50 recent answers are included