In this situation, it was the auth.log file that was taking up all the free space. So, the short term fixup is to clear out space on the file system.
– Possible system/services corruption if a critical file/configuration file was in the process of being written to disk when the partition became full.Īll three are ‘bad things’ in the IT world. – System logging facilities will fail (due to no space to write logs) – Services will start failing (including services for UAG). Once that happens, several things will be seen: Auth.log had grown to 6.8GB and filled up the root partition. Checking through the filesystem for large files – we found it in \var\log. The volume \dev\sda2 was at 100% and killed the system. Fortunately, the customer was running a pair of UAG’s with a load balancer in front – so business wasn’t impacted (they had less than 1000 Horizon users).Īfter continuing basic troubleshooting the answer came in the form of: df -h. I hopped on to a zoom session with our customer and got a Webconsole session to the UAG1 appliance.įirst check, ran: netstat -ano and noted there were no listeners for ports 443, 6443 or 9443 so it was pretty much dead in the water. It was noteworthy that their UAG1 went down and the load balancer shifted the traffic to UAG2, but UAG2 failed about 2 hours later. They had already rebooted them a couple of times to try and get it back in service. Both were pingable, but neither were serving clients and the administrators could not get to the Management Interface (port 9443). Worked a case with a customer recently for a pair of UAG v.2103 servers that were down.
0 kommentar(er)
