Starting php5-fpm appears to work, but checking the status immediately shows that it is not running:
[root@server ~]# service php5-fpm start php5-fpm start/running, process 4516 [root@server ~]# service php5-fpm status php5-fpm stop/waiting
Even though I am able to load PHP pages (meaning that PHP-FPM must be running), the status sometimes reports as
It appears that there are processes running, but are these only the worker processes?
ps -aux |grep php www-data 3552 0.0 0.7 338108 14960 ? S 05:43 0:00 php-fpm: pool www www-data 3553 0.0 1.3 338168 27156 ? S 05:43 0:00 php-fpm: pool www www-data 3554 0.0 1.1 337948 23020 ? S 05:43 0:00 php-fpm: pool www www-data 3555 0.0 1.0 334108 20644 ? S 05:43 0:00 php-fpm: pool www www-data 3556 0.0 1.1 337952 23032 ? S 05:43 0:00 php-fpm: pool www
I’m concerned that the master process is not working correctly. There is nothing being reported in the PHP-FPM log though.
[root@server ~]# tail /var/log/php5-fpm.log [03-May-2014 06:19:32] NOTICE: configuration file /etc/php5/fpm/php-fpm.conf test is successful
service php-fpm status misreporting? Or is the master process actually stopped?
UPDATE: Rebooting the server causes PHP-FPM to start on boot and show as running, but issuing the reload or restart command causes it to go into the state described above. In it’s current condition, I have to reboot the server every time I change php.ini. The server is Ubuntu 14.04
I have a download stream over TCP in an application (running on Win2k12).
The problem is that the connection gets closed by the sender because it times out.
I used wireshark to see what happens on 2 different servers (on one server it works ok, on the other it gets timed out).
I have noticed the same behavior on both:
When the download starts, everything seems ok, window size is 64k and remains the same for some time, segments get acknowledged. Then at some point the window size starts to decrease until it is 0. (As far as I know this is ok, the receiver cannot keep up with the sender.) However, there is no ACK or Window update message from the receiver until the entire buffer is read by the app, then a Window update advertises 64k window size again. Then it starts over again. Window size decreases until zero.
This does not seem right for me. As the application reads from the buffer it should have free space in it and a Window update should be sent, so the sender can send the next segment.
The other thing I don’t understand is the behavior on the failing server. This server advertises larger and larger window sizes in every such cycle, in the last cycle before the timeout the window size was ~800 000. The timeout occures because the buffer is not emptied quick enough. But I have no clue why is the window size increasing on this server? Is there a setting on the server to prevent this?
Are my assumptions right, or I misunderstood something about the TCP protocol?
Any ideas to solve this issue is appreciated.
I’ve got many servers and I want them to have the same IP when they do requests via the Internet. So I configured a Squid http proxy server that works well for http requests.
The problem is that it do not works for HTTPS requests (the real IP of my server appears…).
Do you have a solution for that ?
you encrypt and decrypt content with PGP. While it is possible to decrypt the
content encrypted by Cast Iron in the application itself, there are
times when a user might want to encrypt content in Cast Iron but decrypt it in
an external tool or vice versa. This article focuses on these interoperability