Problem Note 64771: The sas-stream microservice (sas-viya-stream-evdm-default) stops running and generates an error
 |  |  |  |  |
Under certain conditions, the sas-stream microservice (sas-viya-stream-evdm-default) might stop running. When this problem occurs, the error messages that are shown below are written to the sas-stream-evdm_year-month-day-hour-minute-second.log file. This file resides in the /opt/sas/viya/config/var/log/stream-evdm/default/ directory on the host that is designated as the [Operations] target in the Ansible inventory file (inventory.ini).
panic: interface conversion: interface {} is nil, not string
gitlab.sas.com/emi/collect/vendor/gitlab.sas.com/emi/common/event/parse.unJavaEv
ent(0xc4216b7140, 0x946dbd, 0x19, 0x864601)
/var/lib/jenkins/workspace/emi_collect_deploy/gopath/src/gitlab.sas.com/emi/col
lect/vendor/gitlab.sas.com/emi/common/event/parse/parser.go:243 +0xa46
gitlab.sas.com/emi/collect/vendor/gitlab.sas.com/emi/common/event/parse.parseJav
aEvent(0xc4240d4000, 0x1c1d, 0x2000, 0x95d610, 0x454f50, 0xc424845a90, 0x42dcee)
/var/lib/jenkins/workspace/emi_collect_deploy/gopath/src/gitlab.sas.com/emi/col
lect/vendor/gitlab.sas.com/emi/common/event/parse/parser.go:94 +0x209
gitlab.sas.com/emi/collect/vendor/gitlab.sas.com/emi/common/event/parse.Event(0x
c4240d4000, 0x1c1d, 0x2000, 0x0, 0x0, 0x0)
/var/lib/jenkins/workspace/emi_collect_deploy/gopath/src/gitlab.sas.com/emi/col
lect/vendor/gitlab.sas.com/emi/common/event/parse/parser.go:26 +0x83
gitlab.sas.com/emi/collect/vendor/gitlab.sas.com/emi/common/event/consumer.(*AMQ
PConsumer).Receive(0xc422bd1030, 0xc42435c540, 0xc42435c5a0)
/var/lib/jenkins/workspace/emi_collect_deploy/gopath/src/gitlab.sas.com/emi/col
lect/vendor/gitlab.sas.com/emi/common/event/consumer/amqpConsumer.go:238 +0x284
created by gitlab.sas.com/emi/collect/stream.consume
/var/lib/jenkins/workspace/emi_collect_deploy/gopath/src/gitlab.sas.com/emi/col
lect/stream/subscribe.go:126 +0x36e
The following symptoms are present when this issue occurs:
- The sas-viya-stream-evdm-default microservice stops running.
- The sas-viya-stream-evdm-default microservice displays the errors that are shown above in the sas-stream-evdm_year-month-day-hour-minute-second.log file.
- In SAS® Environment Manager, the sas-viya-stream-evdm-default microservice shows a red status on the dashboard.
- In SAS Environment Manager, the Machines tab does not show CPU and memory usage.
- If you submit the command /opt/sas/viya/home/bin/sas-ops validate, validation of the sas-stream microservice fails.
The sas-stream microservice reads metric, log, and notification events from RabbitMQ exchanges and writes them to tab-separated values (TSV) files in the data mart. During the time period that sas-viya-stream-evdm-default is stopped, no metric, notification, or log data is collected. When you restart sas-viya-stream-evdm-default, only new metric, notification, and log data (generated after the restart) are collected.
For more information about sas-stream, see SAS® Viya® 3.4 Administration: Operations Infrastructure.
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Viya | Microsoft Windows Server 2012 R2 Datacenter | 3.3 | |||
| Microsoft Windows Server 2012 R2 Std | 3.3 | |||||
| Microsoft Windows Server 2016 | 3.3 | |||||
| Linux for x64 | 3.3 | |||||