Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rasa in docker - tensorflow error "invalid opcode" #1639

Closed
trstn70 opened this issue Jan 23, 2019 · 3 comments
Closed

rasa in docker - tensorflow error "invalid opcode" #1639

trstn70 opened this issue Jan 23, 2019 · 3 comments
Labels
status:more-details-needed Waiting for the user to provide more details / stacktraces / answer a question

Comments

@trstn70
Copy link

trstn70 commented Jan 23, 2019

I'm using this repository: https://github.com/sasastarcevic/rasa-core-and-nlu-docker-compose

Rasa NLU version:
The Repo uses image tag "latest" as it is not defined. The Dockerfile executes "pip install rasa_core". This seems to be the newest Version as of today.

Operating system:
Debian 9 VM on Proxmox

Issue:
the rasa container is being perodically restartet and i see a tensionflow error in the logs:

Jan 23 10:53:39 lxvm165-113 kernel: [ 7357.922165] traps: python[20676] trap invalid opcode ip:7f5368d55250 sp:7ffcd9265c20 error:0
Jan 23 10:53:39 lxvm165-113 kernel: [ 7357.922193]  in libtensorflow_framework.so[7f53688c6000+c88000]
@akelad
Copy link
Contributor

akelad commented Jan 24, 2019

Thanks for raising this issue, @MetcalfeTom will get back to you about it soon.

@MetcalfeTom
Copy link
Contributor

Hmm this one's a little mysterious, I've been doing some researching and it seems to be due to an incompatibility between the OS and the tensorflow binary

As a first pass at a solution, could you try again using a different tensorflow binary (or perhaps even by compiling one from source) and get back to us with your results

@MetcalfeTom MetcalfeTom added the status:more-details-needed Waiting for the user to provide more details / stacktraces / answer a question label Jan 28, 2019
@no-response
Copy link

no-response bot commented Feb 11, 2019

This issue has been automatically closed because there has been no response to our request for more information from the original author. Without this, we don't have enough information to help you. Please comment below with the requested information if you still need help.

@no-response no-response bot closed this as completed Feb 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:more-details-needed Waiting for the user to provide more details / stacktraces / answer a question
Projects
None yet
Development

No branches or pull requests

3 participants