As I don't read .Net log files with much understanding, I need to have you unravel it... The salient points being:
1. Our Tech guys replaced a UPS, during which a few machines were moved around, but the Production box and monitoring box stayed up. I'm guessing they powered down a network machine...
2. The Server.log.00000.log file around that time starts showing "The remote procedure call failed" messages from each of the three remote servers SQL Response is monitoring.
3. A mixture of COMException and SQLException incidents occurred in the ProcessMonitor, SqlServerMonitor, SqlClockMonitor and a whole bunch more...
4. This "barfing" continued from 2008-02-25 20:14:43.4615 to 2008-02-25 20:20:11.7854 (6 minutes worth) until:
2008-02-25 20:20:11.7854|Fatal|*** A fatal unexpected condition occurred. The application will now shut down. *** Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
RedGate.SqlResponse.Common.ConfigurableThreadPool+WorkerExecutionException
at RedGate.SqlResponse.Common.ConfigurableThreadPool.a(Exception )
at RedGate.SqlResponse.Common.ConfigurableThreadPool.a.b()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
5. One of the servers being monitored is the server on which the Repository resides, so it's not like the Service had nothing left to monitor...
Naturally when I came in this morning I couldn't connect to the Repository as it was dead, despite the connections having been restored to all monitored servers.
The log file is about 100K so I don't think posting it here would be beneficial - if you need it, please provide an email adress I can post it to...
Hi PDinCA,
1. Our Tech guys replaced a UPS, during which a few machines were moved around, but the Production box and monitoring box stayed up. I'm guessing they powered down a network machine... 2. The Server.log.00000.log file around that time starts showing "The remote procedure call failed" messages from each of the three remote servers SQL Response is monitoring. 3. A mixture of COMException and SQLException incidents occurred in the ProcessMonitor, SqlServerMonitor, SqlClockMonitor and a whole bunch more... 4. This "barfing" continued from 2008-02-25 20:14:43.4615 to 2008-02-25 20:20:11.7854 (6 minutes worth) until:
5. One of the servers being monitored is the server on which the Repository resides, so it's not like the Service had nothing left to monitor...Naturally when I came in this morning I couldn't connect to the Repository as it was dead, despite the connections having been restored to all monitored servers.
The log file is about 100K so I don't think posting it here would be beneficial - if you need it, please provide an email adress I can post it to...