Posted by Grant E Foraker on January 23, 2019 at 06:02:53: Uploaded files: 2
In Reply to: Comet time outs posted by Grant Foraker on December 27, 2018 at 07:06:34:
Problem resolved in a weird and mysterious way. How else???
Back about the 10th, I retro'd to Comet 512 but the time outs persisted. 517 had just come out so I installed that. No joy :) So, I'm thinking, how about Sever 18.2. The AV didn't like SecSrvUI.exe. Maybe something else is wrong with 18.2.
On the night of Monday the 14th, I retro'd to 18.0. Planned on running PINGINFO the next morning to see if the failures would go away and the timeouts stop. Tuesday 2:15 AM, the main transformer to the whole PacShip facility shorted out. The UPS shut down all the virtual servers properly about 5 AM and then shut down the physical servers. Power wasn't restored until 3 PM. On Wednesday, I got back to PINGINFO. RAN CLEAN!!!!. No calls from users, especially the poor guy who was crashing twice a day.
So, says I to myself, I need some additional testing so I can send the results to CometWoman. Saturday, I installed 18.1 and ran PININFO for about 20 hours. See screen shot. All the PC's left on had 0% errors. Aha, problem must have been with 18.2. Installed 18.2 on Sunday afternoon. Ran PINGINFO. No errors. Left 18.2 in place. Ran PINGINFO on Monday from 7 AM - 2 PM. Except for people coming in late or leaving early and a DNS glitch necessitating reboots, 18.2 is running fine.
So, what happened to fix the mess??? My guess is the total power shutdown reset something, somewhere. Maybe the NIC settings on the primary and secondary physical servers. The NIC settings on the virtual servers had been checked and they'd been rebooted multiple times for patches, etc.
Post a Followup
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.