Re: gateway aborted by SIGBUS

["Martin L. Smith" <mls@aps.anl.gov>]

Hi Pete,

I have not seen this in quite a while at APS where I have about 40 gateways
running that are read/write; although I'm using version 2.0.3.0

If your gateways are running under Linux my understanding is that you may want
to increase the stack size limit. I have a comment in my starter file:

# Limit stacksize for Linux to increase number of threads
# 1024 is 204 threads (default)
#  4096 is 512 threads
ulimit -s 4096

As you can see I use 4096 although I'm not sure that this will help especially
if you are not running on Linux.
If this is reproducible the gateway documentation mentions that there
is a command line debug option which may help but I expect that it would slow
things down a bit.

-debug <value> 	
Enter a value between 0-100. 50 gives lots of information, 1 gives a small
amount. For developers.

Marty

peter.leicester@diamond.ac.uk wrote:
> Recently we have had three read/write gateways (version 2.0.4.0) crash at different times with the following error appearing in the gateway log.
>
> PV Gateway Aborted (SIGBUS)
>
> The crashes have all occurred when doing a caput thorough the gateway.
>
> The server option on the gateway causes an immediate restart of the gateway however the restart doesn't seem to cure the problem with the particular PV's we are writing to although read access to all PV's is fine. Manually stopping and restarting the gateway get this back to a working state so presumably the time taken to do the restart manually is significant.
>
> So a couple of questions:
>
> 1) Has anyone else seen this?
> 2) What's the best way to debug this? Presumably as its SIGBUS it has something to do with stack size or byte alignment or similar. So presumably I need to get a core dump. Is there any additional debugging in the gateway I can enable which may help?
>
> Pete Leicester
> Diamond Light Source