AllWorx 8.0.9.5 Going down everyday for 1 week.
Posted: Mon Aug 17, 2015 8:50 am
We have an Allworx 48X system
Last week our logs started getting full with BLFPacket error that eventually would bring down our system.
Call could not complete, phones would not register and eventually we could not even log into the server and would have to pull the plug on the system just to get back in.
8.0.8.6:utilString.c,43] 0076903c 0041fdf0 0041a4e4 0041a6cc 0042fd6c 00593d08 007f9838 007f9804
08/12/2015 09:53:12am tBlf: +++ IEC [8.0.8.6:blfPacket.c,5252] 0041fe14 0041a4e4 0041a6cc 0042fd6c 00593d08 007f9838 007f9804
08/12/2015 09:53:12am tBlf: +++ IEC [8.0.8.6:blfPacket.c,5176] 0041fc78 0041a4e4 0041a6cc 0042fd6c 00593d08 007f9838 007f9804
08/12/2015 09:53:12am tBlf: +++ IEC [8.0.8.6:blfPacket.c,1149] 0041fc88 0041a4e4 0041a6cc 0042fd6c 00593d08 007f9838 007f9804
08/12/2015 09:53:12am tBlf: +++ IEC [8.0.8.6:blfNet.c,1224] 0041a66c 0041a6cc 0042fd6c 00593d08 007f9838 007f9804
08/12/2015 09:53:12am tBlf: +++ IEC [8.0.8.6:blfNet.c,1107] 0041a6e4 0042fd6c 00593d08 007f9838 007f9804
08/12/2015 09:53:13am tBlf: +++ IEC [8.0.8.6:utilString.c,43] 0076903c 0041fdf0 0041a4e4 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:13am tBlf: +++ IEC [8.0.8.6:blfPacket.c,5252] 0041fe14 0041a4e4 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:13am tBlf: +++ IEC [8.0.8.6:blfPacket.c,5176] 0041fc78 0041a4e4 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:13am tBlf: +++ IEC [8.0.8.6:blfPacket.c,1149] 0041fc88 0041a4e4 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:13am tBlf: +++ IEC [8.0.8.6:blfNet.c,1224] 0041a66c 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:13am tBlf: +++ IEC [8.0.8.6:blfThread.c,766] 0042fc54 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:13am tBlf: +++ IEC [8.0.8.6:blfThread.c,420] 0043054c 00593d08 007f9838 007f9804
08/12/2015 09:53:16am tBlf: +++ IEC [8.0.8.6:utilString.c,43] 0076903c 0041fdf0 0041a4e4 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:16am tBlf: +++ IEC [8.0.8.6:blfPacket.c,5252] 0041fe14 0041a4e4 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:16am tBlf: +++ IEC [8.0.8.6:blfPacket.c,5176] 0041fc78 0041a4e4 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:16am tBlf: +++ IEC [8.0.8.6:blfPacket.c,1149] 0041fc88 0041a4e4 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:16am tBlf: +++ IEC [8.0.8.6:blfNet.c,1224] 0041a66c 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:16am tBlf: +++ IEC [8.0.8.6:blfThread.c,766] 0042fc54 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:16am tBlf: +++ IEC [8.0.8.6:blfThread.c,420] 0043054c 00593d08 007f9838 007f9804
Allworx engineers asked us to apply the new patch 2 days before it's release 8.0.9.5, this seemed to solve the TBLF errors but our troubles continued
Tsip errors and a host of others that continued to bring our system completely down. Allworx has been at a loss to figure this situation out. We are told their top people are looking at everything but it's amazing to me how the have no idea what could be causing these problems.
Has anyone else had any similar issues?
Last week our logs started getting full with BLFPacket error that eventually would bring down our system.
Call could not complete, phones would not register and eventually we could not even log into the server and would have to pull the plug on the system just to get back in.
8.0.8.6:utilString.c,43] 0076903c 0041fdf0 0041a4e4 0041a6cc 0042fd6c 00593d08 007f9838 007f9804
08/12/2015 09:53:12am tBlf: +++ IEC [8.0.8.6:blfPacket.c,5252] 0041fe14 0041a4e4 0041a6cc 0042fd6c 00593d08 007f9838 007f9804
08/12/2015 09:53:12am tBlf: +++ IEC [8.0.8.6:blfPacket.c,5176] 0041fc78 0041a4e4 0041a6cc 0042fd6c 00593d08 007f9838 007f9804
08/12/2015 09:53:12am tBlf: +++ IEC [8.0.8.6:blfPacket.c,1149] 0041fc88 0041a4e4 0041a6cc 0042fd6c 00593d08 007f9838 007f9804
08/12/2015 09:53:12am tBlf: +++ IEC [8.0.8.6:blfNet.c,1224] 0041a66c 0041a6cc 0042fd6c 00593d08 007f9838 007f9804
08/12/2015 09:53:12am tBlf: +++ IEC [8.0.8.6:blfNet.c,1107] 0041a6e4 0042fd6c 00593d08 007f9838 007f9804
08/12/2015 09:53:13am tBlf: +++ IEC [8.0.8.6:utilString.c,43] 0076903c 0041fdf0 0041a4e4 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:13am tBlf: +++ IEC [8.0.8.6:blfPacket.c,5252] 0041fe14 0041a4e4 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:13am tBlf: +++ IEC [8.0.8.6:blfPacket.c,5176] 0041fc78 0041a4e4 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:13am tBlf: +++ IEC [8.0.8.6:blfPacket.c,1149] 0041fc88 0041a4e4 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:13am tBlf: +++ IEC [8.0.8.6:blfNet.c,1224] 0041a66c 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:13am tBlf: +++ IEC [8.0.8.6:blfThread.c,766] 0042fc54 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:13am tBlf: +++ IEC [8.0.8.6:blfThread.c,420] 0043054c 00593d08 007f9838 007f9804
08/12/2015 09:53:16am tBlf: +++ IEC [8.0.8.6:utilString.c,43] 0076903c 0041fdf0 0041a4e4 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:16am tBlf: +++ IEC [8.0.8.6:blfPacket.c,5252] 0041fe14 0041a4e4 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:16am tBlf: +++ IEC [8.0.8.6:blfPacket.c,5176] 0041fc78 0041a4e4 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:16am tBlf: +++ IEC [8.0.8.6:blfPacket.c,1149] 0041fc88 0041a4e4 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:16am tBlf: +++ IEC [8.0.8.6:blfNet.c,1224] 0041a66c 0042fbdc 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:16am tBlf: +++ IEC [8.0.8.6:blfThread.c,766] 0042fc54 00430534 00593d08 007f9838 007f9804
08/12/2015 09:53:16am tBlf: +++ IEC [8.0.8.6:blfThread.c,420] 0043054c 00593d08 007f9838 007f9804
Allworx engineers asked us to apply the new patch 2 days before it's release 8.0.9.5, this seemed to solve the TBLF errors but our troubles continued
Tsip errors and a host of others that continued to bring our system completely down. Allworx has been at a loss to figure this situation out. We are told their top people are looking at everything but it's amazing to me how the have no idea what could be causing these problems.
Has anyone else had any similar issues?