I upgraded my production server from V 12.x to 13.2-RELEASE-p10 and the from PHP 7.x to php81-8.1.27
This was to match my development server. I've got new server hardware, and will take that and a new development server to V14 in about 2 months.
I had the usual issues with PHP extensions, and a server I wrote in PHP that has a TCP port open would create a port, and then it had a PHP error and terminated. I got to the point where nothing in the system was causing PHP errors, but then server would not take connections. The output of sockstat looked like this (lots of lines cut out for clarity and space). Addresses change to protect the innocent.
Had 28 of these, the last one CONN STATE was CLOSING. There were also a number of active web sockets that were up and running. I could not figure out how to close these down with sockstat, so I decided to reboot with a
.
The ssh connection closed, but the server never went down. Apache was still up. I'm guessing a rc.d or other shutdown mechanism also could not figure out how to close the TCP connections. I've called the hosting site, they will power cycle the machine. It's an older machine, hence the new hardware that is in the queue. During a reboot to do the major update on the OS, it tossed a disk so I'm down to two. Getting the new machine up and installing it just went to the top of the priority list.
Any ideas on how to deal with this should it happen again ? Any insight in to what happened would be appreciated. The sever I wrote has been up and running for 3 years with no issues, but it's clear I need to figure out how to handle this situation going forward. Note also the server file is owned by root, is that why there are the ???? everywhere ? Would it be better to have something else own it ?
thanks in advance.
This was to match my development server. I've got new server hardware, and will take that and a new development server to V14 in about 2 months.
I had the usual issues with PHP extensions, and a server I wrote in PHP that has a TCP port open would create a port, and then it had a PHP error and terminated. I got to the point where nothing in the system was causing PHP errors, but then server would not take connections. The output of sockstat looked like this (lots of lines cut out for clarity and space). Addresses change to protect the innocent.
Code:
root@mymachine # sockstat -P tcp -s
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS PATH STATE CONN STATE
www httpd 37880 3 tcp6 *:80 *:* LISTEN
www httpd 37880 4 tcp4 *:80 *:* LISTEN
? ? ? ? tcp4 10.55.55:55:111 192.55.55.55:22333 TIME_WAIT
Had 28 of these, the last one CONN STATE was CLOSING. There were also a number of active web sockets that were up and running. I could not figure out how to close these down with sockstat, so I decided to reboot with a
shutdown -r now
..
The ssh connection closed, but the server never went down. Apache was still up. I'm guessing a rc.d or other shutdown mechanism also could not figure out how to close the TCP connections. I've called the hosting site, they will power cycle the machine. It's an older machine, hence the new hardware that is in the queue. During a reboot to do the major update on the OS, it tossed a disk so I'm down to two. Getting the new machine up and installing it just went to the top of the priority list.
Any ideas on how to deal with this should it happen again ? Any insight in to what happened would be appreciated. The sever I wrote has been up and running for 3 years with no issues, but it's clear I need to figure out how to handle this situation going forward. Note also the server file is owned by root, is that why there are the ???? everywhere ? Would it be better to have something else own it ?
thanks in advance.