Bill H Posted February 4, 2008 Report Share Posted February 4, 2008 We have been using PBXNSIP for about 9 months now and have never experienced a system crash. Version: 2.1.6.2433 (Win32) and also when we used the previous version. 2.1.5.???? Everything else in the server works OK during the crash and the PBXNSIP service re-starts again OK. Since 1/3/08 we have had several crashes as indicated in the list below. Type Date Time Source Category Event User Computer Error 1/3/2008 09:34:17 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/31/2008 09:48:51 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/31/2008 10:24:44 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/11/2008 10:32:54 AM Service Control Manager None 7031 N/A PBXNSIP Error 2/4/2008 10:34:08 AM Service Control Manager None 7031 N/A PBXNSIP Error 2/4/2008 10:43:59 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/5/2008 11:00:10 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/30/2008 11:06:43 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/11/2008 11:24:39 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/5/2008 11:29:58 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/18/2008 02:36:33 PM Service Control Manager None 7031 N/A PBXNSIP Error 1/4/2008 04:15:35 PM Service Control Manager None 7031 N/A PBXNSIP Error 1/31/2008 04:17:22 PM Service Control Manager None 7031 N/A PBXNSIP Error 1/18/2008 04:32:31 PM Service Control Manager None 7031 N/A PBXNSIP There seems to be a pattern based on the cluster of failures at different times, but I don't know if this means anything. I looked at the pbxlog, but it isn't time stamped so I could not get any meaninful info from it. Is there a way to get the last message sent before it crashed? Any ideas as to why it fails? Bill H Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 4, 2008 Report Share Posted February 4, 2008 Error 1/03/2008 09:34:17 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/04/2008 04:15:35 PM Service Control Manager None 7031 N/A PBXNSIP Error 1/05/2008 11:00:10 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/05/2008 11:29:58 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/11/2008 10:32:54 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/11/2008 11:24:39 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/18/2008 02:36:33 PM Service Control Manager None 7031 N/A PBXNSIP Error 1/18/2008 04:32:31 PM Service Control Manager None 7031 N/A PBXNSIP Error 1/30/2008 11:06:43 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/31/2008 09:48:51 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/31/2008 10:24:44 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/31/2008 04:17:22 PM Service Control Manager None 7031 N/A PBXNSIP Error 2/04/2008 10:34:08 AM Service Control Manager None 7031 N/A PBXNSIP Error 2/04/2008 10:43:59 AM Service Control Manager None 7031 N/A PBXNSIP Whow. THe first thing that comes to my mind would be memory. Is there any way that you can monitor how much memory the process took? The patterns above look to me like it is working for about a week, then it crashes (restarts) and then goes into a weekly cycle. Quote Link to comment Share on other sites More sharing options...
Bill H Posted February 4, 2008 Author Report Share Posted February 4, 2008 Error 1/03/2008 09:34:17 AM Service Control Manager None 7031 N/A PBXNSIPError 1/04/2008 04:15:35 PM Service Control Manager None 7031 N/A PBXNSIP Error 1/05/2008 11:00:10 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/05/2008 11:29:58 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/11/2008 10:32:54 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/11/2008 11:24:39 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/18/2008 02:36:33 PM Service Control Manager None 7031 N/A PBXNSIP Error 1/18/2008 04:32:31 PM Service Control Manager None 7031 N/A PBXNSIP Error 1/30/2008 11:06:43 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/31/2008 09:48:51 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/31/2008 10:24:44 AM Service Control Manager None 7031 N/A PBXNSIP Error 1/31/2008 04:17:22 PM Service Control Manager None 7031 N/A PBXNSIP Error 2/04/2008 10:34:08 AM Service Control Manager None 7031 N/A PBXNSIP Error 2/04/2008 10:43:59 AM Service Control Manager None 7031 N/A PBXNSIP Whow. THe first thing that comes to my mind would be memory. Is there any way that you can monitor how much memory the process took? The patterns above look to me like it is working for about a week, then it crashes (restarts) and then goes into a weekly cycle. ----------- We have 4 gigabytes in the server and are not running any other programs on a regular basis. We are running the needed processes for Windows to operate. Could it be a memory Leak? Accumulating memory over a week and then goes bad? The Task Manager says it is usin 84.016K of memory for PBXNSIP. Is this the method you suggest or is there something better? Task Manager also reports over 16 million handles, that seems high to me. Bill H Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 4, 2008 Report Share Posted February 4, 2008 Task Manager also reports over 16 million handles, that seems high to me. That sounds extremly high to me. Does that number go down after a restart of the service? Quote Link to comment Share on other sites More sharing options...
ap_6200 Posted February 4, 2008 Report Share Posted February 4, 2008 Version: 2.1.6.2433 (Win32) and also when we used the previous version. 2.1.5.???? Was this version posted for beta testing? Quote Link to comment Share on other sites More sharing options...
ap_6200 Posted February 4, 2008 Report Share Posted February 4, 2008 Was this version posted for beta testing? I'm also getting reports of DTMF issues on certain automated systems: I tested with 2.0.3.1715 and it works fine.. But with the latest release of 2.1.5 I get the following errors: [8] 20080204154855: No codec available for sending [8] 20080204154855: Last message repeated 45 times [9] 20080204154855: Resolve 9916807: udp 10.15.237.246 1240 [8] 20080204154855: No codec available for sending [8] 20080204154855: Last message repeated 6 times [9] 20080204154855: Resolve 9916808: udp 15.10.174.19 5060 [8] 20080204154855: No codec available for sending [8] 20080204154855: Last message repeated 12 times [9] 20080204154855: Resolve 9916809: udp 15.10.174.19 5060 [8] 20080204154855: No codec available for sending [8] 20080204154856: Last message repeated 58 times [9] 20080204154856: Resolve 9916810: udp 10.15.237.138 10283 [8] 20080204154856: No codec available for sending [8] 20080204154856: Last message repeated 32 times [9] 20080204154856: Resolve 9916811: udp 10.15.237.234 49161 [8] 20080204154856: No codec available for sending [8] 20080204154856: Last message repeated 61 times [8] 20080204154856: SNMP: Received unknown object identifier 06082b06010201010300 [8] 20080204154856: No codec available for sending [8] 20080204154856: Last message repeated 14 times [9] 20080204154856: Resolve 9916812: udp 10.15.236.70 4217 [8] 20080204154856: No codec available for sending [8] 20080204154857: Last message repeated 49 times [9] 20080204154857: Resolve 9916813: udp 15.10.174.19 5060 [8] 20080204154857: No codec available for sending [8] 20080204154857: Last message repeated 12 times [9] 20080204154857: Resolve 9916814: udp 10.15.236.162 16626 [8] 20080204154857: No codec available for sending [8] 20080204154857: Last message repeated 9 times [9] 20080204154857: Resolve 9916815: udp 15.10.174.19 5060 [8] 20080204154857: No codec available for sending [8] 20080204154857: Last message repeated 42 times [9] 20080204154857: Resolve 9916816: udp 15.10.174.19 5060 [8] 20080204154857: No codec available for sending [8] 20080204154857: Last message repeated 17 times [9] 20080204154857: Resolve 9916817: udp 10.15.237.138 10229 [9] 20080204154857: Resolve 9916818: udp 10.15.237.138 10244 [8] 20080204154857: No codec available for sending [8] 20080204154857: Last message repeated 6 times [9] 20080204154857: Resolve 9916819: udp 15.10.174.19 5060 [8] 20080204154857: No codec available for sending [8] 20080204154857: Last message repeated 21 times [9] 20080204154857: Resolve 9916820: udp 10.15.237.138 10238 [8] 20080204154857: No codec available for sending Please advise quickly. Thanks! Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 5, 2008 Report Share Posted February 5, 2008 [8] 20080204154855: No codec available for sending That is caused by the fact that many devices cannot deal properly with multiple codecs in the SDP answer. 2.1.6 should improve this (if not fix this). Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.