segmentation fault in rasserver causes oid operator failures

[beccati@…]

Following the two discussions on the mailing list [1] [2] that seem to be strictly related I open this ticket to keep track and gather info.

[1] ​http://groups.google.com/group/rasdaman-dev/browse_thread/thread/ac8324f9c09d0a4c/cce6409251be3ebe
[2] ​http://groups.google.com/group/rasdaman-dev/browse_thread/thread/2fbbe0842583cbc0/8b5d9d4c91065629

Here follows log excerpt and problem description, ongoing operations were rasgeo insert to a non existing collection that should have been followed by an update.

—- KERNEL LOG —-
Feb 28 12:42:26 ras-dev-dar kernel: rasserver[15480]: segfault at 0 ip 00000000004c089b sp 00007fff9ef3bc80 error 4 in rasserver[400000+1a8000]

—- rasmgr.001504.log —-
[2012-02-28 12:42:26] client request from 192.168.0.115: 'get server'…ok
rasdaman server process with pid 15480 has terminated.
Error: rasdaman server N1, pid 15480 terminated illegally, reason: uncaught signal 11
[2012-02-28 12:42:26] starting server N1, executable /usr/local/rasdaman8.3/bin/rasserver; pid 19987…[2012-02-28 12:42:27] client request from 192.168.0.115: 'get server'…ok

—- N1.015480.log (last entries) —-
[2012-02-28 12:42:26] request from 192.168.0.115
Request: 'insert MDD', type 'GreyCube', domain [0:0,0:0,0:0], cell length 1, 1 bytes…ok
[2012-02-28 12:42:26] request completed in 356 usecs.

PerformanceTimer: RnpRasDaManComm :: request = 366 usecs

[2012-02-28 12:42:26] request from 192.168.0.115
Request: 'insert tile'…insertTile created new TransTile (Array), changing endianness…

—- N1.019987.log (repeated insert, should have been an update —-
[…]
[2012-02-28 12:42:56] request from 192.168.0.115
Request: 'insert into none_TEST_32630_1000 values marray x in [0:0,0:0,149941:149941] values 0c'…parsing…checking semantics…evaluating…ok
[2012-02-28 12:42:56] request completed in 5703 usecs.

—- oid(t) output —-
rasql: rasdaman query tool v1.0, rasdaman v8 — generated on 31.01.2012 17:14:19.
opening database RASBASE at localhost:7001...ok
Executing retrieval query…ok
Query result collection has 2 element(s):

Result element 1: 2.37934e-317
Result element 2: 2.37934e-317

rasql done.

Restarting the server N1 via rascontrol solves the oid issue