|
Girish Posts: 20
8/19/2017
|
Support,
The service was running fine for few days and suddenly got the below messages and had to reboot the server. Can you please help.
blox_opensips-1.0.4-8.x86_64
blox_ministun_client-1.0.4-8.x86_64
blox_security-1.0.4-8.x86_64
blox-rpm-keys-1.0.4-8.x86_64
blox_rtppinhole-1.0.4-8.x86_64
blox_core-1.0.4-8.x86_64
freeblox-1.0.4-8.x86_64
blox_rtpengine-1.0.4-8.x86_64
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15797]: CRITICAL:core:receive_fd: EOF on 30
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15719]: INFO:core:handle_sigs: child process 15763 exited by a signal 11
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15719]: INFO:core:handle_sigs: core was generated
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15719]: INFO:core:handle_sigs: terminating due to SIGCHLD
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15794]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15793]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15790]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15789]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15784]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15783]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15782]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15778]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15741]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15747]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15771]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15748]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15740]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15749]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15770]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15772]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15773]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15758]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15777]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15736]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15739]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15738]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15733]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15734]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15728]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15737]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15797]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15732]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15759]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15729]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15779]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15761]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15760]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15762]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15735]: INFO:core:sig_usr: signal 15 received
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15719]: INFO:core:cleanup: cleanup
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15719]: NOTICE:event_datagram:destroy: destroy module ...
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15719]: INFO:db_mysql:switch_state_to_disconnected: disconnect event for 0x7f9e689592f0
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15719]: INFO:db_mysql:reset_all_statements: reseting all statements on connection: (0x7f9e6895a318) 0x7f9e689592f0
Aug 19 11:55:12 BloXeSBC blox-1-0-4-stable[15719]: INFO:db_mysql:connect_with_retry: re-connected successful for 0x7f9e689592f0
Aug 19 11:56:12 BloXeSBC blox-1-0-4-stable[15719]: CRITICAL:core:sig_alarm_abort: BUG - shutdown timeout triggered, dying...
Aug 19 11:56:37 BloXeSBC rtpengine[15503]: [901a8c25997c3d51-12035180] Closing call due to timeout
Aug 19 11:56:37 BloXeSBC rtpengine[15503]: [901a8c25997c3d51-12035180] Final packet stats:
|
|
|
0
link
|
|
Girish Posts: 20
8/19/2017
|
Sorry the firmware version details are wrong, the below is right
blox-rpm-keys-1.0.5-2.x86_64
blox_rtpengine-1.0.5-2.x86_64
blox_rtppinhole-1.0.5-2.x86_64
blox_ministun_client-1.0.5-2.x86_64
blox_security-1.0.5-2.x86_64
freeblox-1.0.4-8.x86_64
blox_core-1.0.5-2.x86_64
blox_opensips-1.0.5-2.x86_64
|
|
|
0
link
|
|
quan.pt Posts: 7
8/20/2017
|
I have same your problem. I must create a script to detect and restart blox when It happened.
|
|
|
0
link
|
|
bloxsupport1 Posts: 231
8/20/2017
|
Can you please give us the remote access to verify the issue. you can send the details to support@blox.org or you can contact us through skype at "blox.support".
Girish wrote:
Sorry the firmware version details are wrong, the below is right
blox-rpm-keys-1.0.5-2.x86_64
blox_rtpengine-1.0.5-2.x86_64
blox_rtppinhole-1.0.5-2.x86_64
blox_ministun_client-1.0.5-2.x86_64
blox_security-1.0.5-2.x86_64
freeblox-1.0.4-8.x86_64
blox_core-1.0.5-2.x86_64
blox_opensips-1.0.5-2.x86_64
|
|
|
0
link
|
|
Girish Posts: 20
8/21/2017
|
Sure, let me arrange and send it. In the mean time do you need any logs that can be useful to check on the same ?
|
|
|
0
link
|
|
Girish Posts: 20
8/21/2017
|
Sure, let me arrange and send it. In the mean time do you need any logs that can be useful to check on the same ?
|
|
|
0
link
|
|
prateep Posts: 1
8/21/2017
|
hi bloxsupport1,
I am Girish 's colleagues please contact me at Skype id Prateep Prawattiyakul. i will provide remote access to you.
|
|
|
0
link
|
|
quan.pt Posts: 7
8/23/2017
|
Hi Girish,
Can you reslove this problem ?
|
|
|
0
link
|
|
bloxsupport1 Posts: 231
8/23/2017
|
quan.pt wrote:
Hi Girish,
Can you reslove this problem ?
Hello Quan,
please send us the log file after crash /var/log/opensips.log
|
|
|
0
link
|
|
quan.pt Posts: 7
8/25/2017
|
Hello Bloxsupport1,
I have sent you log file.
edited by quan.pt on 8/27/2017
|
|
|
0
link
|