Hi all,
has anyone experience with segfaults on AWS Hana ver. 68? Today I see these in the system log:
Feb 6 06:32:38 imdbhdb ec2: Unable to retreive user-data
Feb 6 06:32:38 imdbhdb ec2: Failed to retreive ec2-ami-tools from S3
Feb 6 06:32:38 imdbhdb ec2: Unable to update ec2-ami-tools
Feb 6 06:32:39 imdbhdb su: (to hdbadm) root on /dev/console
Feb 6 06:32:41 imdbhdb kernel: [ 47.288386] sapstartsrv[4600]: segfault at 14 ip 0000000000a16c2f sp 00007fffe516b2d0 error 4 in sapstartsrv[400000+ab5000]
Feb 6 06:32:41 imdbhdb kernel: [ 47.304006] sapstartsrv[4601]: segfault at 14 ip 0000000000a16c2f sp 00007fffbb543310 error 4 in sapstartsrv[400000+ab5000]
Feb 6 06:32:42 imdbhdb SAPHDB_00[4596]: SAP Service SAPHDB_00 successfully started.
Feb 6 06:32:43 imdbhdb kernel: [ 49.452189] sapstart[4673]: segfault at 13 ip 00000000004304ff sp 00007fff54bb9c30 error 4 in sapstart[400000+84000]
...
Feb 6 07:17:51 imdbhdb kernel: [ 2757.683629] sapstartsrv[5270]: segfault at 14 ip 0000000000a16c2f sp 00007fff8d85d670 error 4 in sapstartsrv[400000+ab5000]
Feb 6 07:17:51 imdbhdb /usr/sbin/cron[5274]: (CRON) STARTUP (V5.0)
Feb 6 07:17:52 imdbhdb kernel: [ 2757.708436] sapstartsrv[5273]: segfault at 14 ip 0000000000a16c2f sp 00007fff2fde8780 error 4 in sapstartsrv[400000+ab5000]
and Hana does not start properly. This happens from time to time, it seems to have something to do with ec2-ami-tools, as this "retreive" (sic) always happens right before.
Cheers,
-- Micha