Hi Kosala, The most common time that Homestead hits a signal 6 (SIGABRT) is when Monit detects that it is not responding to polls, and attempts to stop it.
The first thing to check is whether that is what we are seeing here. You can check that by looking in /var/log/monit.log at the time when you saw the signal 6. If Monit is not the culprit, then we should figure out where the application hit the signal. You can do that by installing debug symbols (installing the homestead-dbg package) that you will have built at the same time as your homestead package. That will include more information in the crash dump. If Monit is the culprit, hopefully the logs will explain why. If not, I’m happy to help. Yours, Chris From: Clearwater [mailto:[email protected]] On Behalf Of Kosala Sent: 03 August 2016 09:22 To: [email protected] Subject: [Project Clearwater] Signal 6 caught Hi team, I got homestead following url https://github.com/Metaswitch/homestead/blob/dev/docs/development.md. Then I made a deb package following isntructions. Then I installed deb packages on all in one clearwater image. The I registered two clients Zoiper and Jitsi. I can make calls between them. Issue is, when i check log files in /var/log/homestead, I can see "Signal 6 caught" Basic stack dump: /usr/share/clearwater/bin/homestead[0x49336d] /usr/share/clearwater/bin/homestead[0x49452d] /usr/share/clearwater/bin/homestead[0x4aa47c] /lib/x86_64-linux-gnu/libc.so.6(+0x36cb0)[0x7ff647b1acb0] /lib/x86_64-linux-gnu/libpthread.so.0(sem_wait+0x2e)[0x7ff64909a66e] /usr/share/clearwater/bin/homestead[0x41cdcf] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7ff647b05f45] /usr/share/clearwater/bin/homestead[0x41dc6c] I am just wondering if this can be solved? Many Thanks, Kosala
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
