News from Snort
-
Hi Bill,
I do not expect a solution to this, it is only for fun: I got exits when Snort updates with signal 11 and signal 10 but since last update I got something new: exit with signal 4! (I uninstall Snort and reinstall it just to be shure there is everything in place) Snort works as expected but its very strange all this.
Have a fine Weekend,
fireodo -
@fireodo said in News from Snort:
Hi Bill,
I do not expect a solution to this, it is only for fun: I got exits when Snort updates with signal 11 and signal 10 but since last update I got something new: exit with signal 4! (I uninstall Snort and reinstall it just to be shure there is everything in place) Snort works as expected but its very strange all this.
Have a fine Weekend,
fireodoI assume you are running Snort on an ARM platform such as SG-1000, SG-1100 or SG-3100? If so, unfortunately I'm not surprised at those errors. Signal 4 is "illegal instruction".
-
@bmeeks said in News from Snort:
@fireodo said in News from Snort:
I assume you are running Snort on an ARM platform such as SG-1000, SG-1100 or SG-3100? If so, unfortunately I'm not surprised at those errors.
No, as stated in my signature its a amd64 Architecture.
Signal 4 is "illegal instruction".
I know.
My post maybe underlines what we have discussed here:
https://forum.netgate.com/topic/154580/snort-exit-with-signal-10-or-11-when-doing-certain-updatesKind regards,
fireodo -
@fireodo said in News from Snort:
@bmeeks said in News from Snort:
@fireodo said in News from Snort:
I assume you are running Snort on an ARM platform such as SG-1000, SG-1100 or SG-3100? If so, unfortunately I'm not surprised at those errors.
No, as stated in my signature its a amd64 Architecture.
Signal 4 is "illegal instruction".
I know.
My post maybe underlines what we have discussed here:
https://forum.netgate.com/topic/154580/snort-exit-with-signal-10-or-11-when-doing-certain-updatesKind regards,
fireodoSorry, I missed the hardware specs. An illegal instruction basically can come from only two sources. Either the compiler (which is very unlikely) or memory corruption (much more likely). That signal error literally means the CPU fetched an instruction opcode from memory that did not match any of the defined instructions available for the CPU. The most likely reason for that happening is the memory location returned bogus data. That's where I would look first, by running a full memory hardware diagnostic if you have one.
-
@bmeeks said in News from Snort:
@fireodo said in News from Snort:
@bmeeks said in News from Snort:
@fireodo said in News from Snort:
That's where I would look first, by running a full memory hardware diagnostic if you have one.No issues (after running memtest86+) and all back to normal (I mean exit on signal 11
)Thanks anyway for your time and all the best,
fireodo
