Ovidiu Zaharia
|
qad crash - Process 421917 (qad) terminated SIGSEGV code=1
|
Ovidiu Zaharia
07/17/2018 11:46 AM
post118962
|
qad crash - Process 421917 (qad) terminated SIGSEGV code=1
Hello,
I was experimenting with qad (anomaly Detection) module which is a native module in QNX for a while and despite the fact
that the documentation is very "spartanic" on qnx.com and internet in general, the command crashes after some 5 min
when active.Several reboots didn't help. The nly thing which helped (for a while) was reflashing the whole OS, but then
after 5-6 min of activity the error message (memory segmentation fault?) came again.
My questions:
1.) Is it a known bug and is someone also experiencing this?
2.) Are there some solutions available?
3.) I would also need to know how can this help me monitor my system from the security point of view?
I use
QNX 7.0 on a A53 ARM processor
Here is the command (for ref)
# qad /root/conf/qad.conf
Here is the error message
Process 421917 (qad) terminated SIGSEGV code=1 fltno=11 ip=00000000100cdd04(/usr/bin/qad@ServerInfo+0x000000000000282c)
mapaddr=0000000000005d04. ref=000000003f31fa6f
Memory fault (core dumped)
Here is the qad.conf - pretty much as the example available
{
"buf_size": 64,
"win_size": 8,
"mon_list": [
{
"id": "proc/boot/random",
"type": 2,
"desc": "Proc monitored: proc/boot/random",
"win_size": 8,
"notify": 1
},
{
"id": "proc/boot/qconn",
"type": 2,
"desc": "Proc monitored: proc/boot/qconn",
"win_size": 8,
"notify": 1
}
],
"exc_list": [
],
"prof_path": "/opt",
"notify": 1,
"normal_wait": 180
}
|
|
|