Problem Note 59329: SAS® Metadata Server becomes unresponsive or crashes with an AccessViolation error
During normal run time, the SAS Metadata Server might encounter an AccessViolation error, which results in the server becoming unresponsive. Once the server has entered the unresponsive state, the metadata server process itself must be stopped and then restarted in order to restore service.
The problem occurs randomly with no previous warning. A metadata server encountering such a problem might be able to run for several days or weeks in between occurrences of the issue.
In order to confirm that your issue matches the one documented here, look in the SAS-configuration-directory/SASMeta/MetadataServer/Logs/SASMeta_MetadataServer_date_hostname_pid.log file for a stack trace similar to this one:
2015-12-16T16:14:07,307 ERROR [788896265] 3184:myuser - AccessViolation (6) encountered in CONTEXT 1F45710E using cookie 24.
2015-12-16T16:14:07,674 ERROR [788896265] 3184:myuser - /opt/sashome/SASFoundation/9.4/sasexe/tkiomsvc.so(tktracex+0x2e) [0x7f46d9ec204e]
/opt/sashome/SASFoundation/9.4/sasexe/tkiomsvc.so(+0xce09) [0x7f46d9e47e09]
/opt/sashome/SASFoundation/9.4/sasexe/tkmk.so(bktExcept+0x62) [0x7f46f4492ed2]
/opt/sashome/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7f46f4493514]
/lib64/libpthread.so.0() [0x34b860f500]
/opt/sashome/SASFoundation/9.4/sasexe/tkmk.so(skm_unlink+0x35) [0x7f46f44a5e35]
/opt/sashome/SASFoundation/9.4/sasexe/tkmk.so(skmMemAlloc+0x183) [0x7f46f44a3cc3]
/opt/sashome/SASFoundation/9.4/sasexe/tkmk.so(skmMemRealloc+0x1da) [0x7f46f44a27aa]
/opt/sashome/SASFoundation/9.4/sasexe/tkoms.so(omssmiie+0x7f) [0x7f46c8d8646f]
/opt/sashome/SASFoundation/9.4/sasexe/tkoms.so(FOMSsecuritymanagerBuildExplicitCredentialItems+0x4dd) [0x7f46c8d168ad]
/opt/sashome/SASFoundation/9.4/sasexe/tkoms.so(FOMSsecuritymanagerBuildCredentialsForContext+0x400) [0x7f46c8d12ee0]
/opt/sashome/SASFoundation/9.4/sasexe/tkomi.so(secGetAuthorizationsForObjects+0x52c) [0x7f46c9f00a4c]
/opt/sashome/SASFoundation/9.4/sasexe/tkomi.so(+0x1e0409) [0x7f46c9de1409]
/opt/sashome/SASFoundation/9.4/sasexe/tkomi.so(+0x2115a5) [0x7f46c9e125a5]
/opt/sashome/SASFoundation/9.4/sasexe/tkiompeb.so(+0x1d707) [0x7f468ebe9707]
/opt/sashome/SASFoundation/9.4/sasexe/tkiompeb.so(clientDispatch+0xa95) [0x7f468ebe3765]
/opt/sashome/SASFoundation/9.4/sasexe/tkiomsvc.so(svcPuddleMain+0x442) [0x7f46d9e60f42]
/opt/sashome/SASFoundation/9.4/sasexe/tkepdl.so(+0x2fbe) [0x7f46d953efbe]
/opt/sashome/SASFoundation/9.4/sasexe/tkmk.so(sktMain+0x94) [0x7f46f4491154]
/opt/sashome/SASFoundation/9.4/sasexe/tkmk.so(bktMain+0x69) [0x7f46f4492d39]
/lib64/libpthread.so.0() [0x34b8607851]
/lib64/libc.so.6(clone+0x6d) [0x34b7ee85ad]
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| SAS System | SAS Metadata Server | Linux for x64 | 9.4 | 9.4_M4 | | 9.4 TS1M4 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2016-11-29 15:41:17 |
| Date Created: | 2016-11-11 12:57:24 |
