-
Notifications
You must be signed in to change notification settings - Fork 37
Error with logs handler caused a panic #70
Comments
Hi @mangobowl, Thanks for your interest in OpenFaaS For us to be able to help you, we will need either the functions you are deploying, or similar ones where you can re-create the issue. faas-swarm hasn't been changed significantly for quite some time, so I suspect this has something to do with the naming of your functions or perhaps something else specific to your environment. If you want a quick resolution, I'd suggest you use OpenFaaS on Kubernetes - with k3s or a managed service like AKS, GKE etc. This is what we recommend for business / work and production use and what we actively support. See the note here -> https://docs.openfaas.com/deployment/ Alex |
/set title: Error with logs handler caused a panic |
Specifically, it looks like you are trying to access logs from the call-stack, is that right? Did you run |
that is really weird, the line that panics is here which suggests that the logs stream was completely empty or a partial load of the logs that doesn't contain the full docker log prefix. Perhaps the cleanest way to change this is to try and reuse their I have an idea on how to handle it |
@alexellis @LucasRoesler This problem is related to a special function log. The steps to reproduce are as follows:
The full docker json-file log of the function is as follows: The api response will terminate at line 127:
The function yml config is as follows: |
I don't understand what is special about line 127 {"log":"2020/06/23 08:00:04 stdout: /home/app/function/handler.py[line:18] - INFO: 99\n","stream":"stdout","time":"2020-06-23T08:00:04.85923018Z"} The API response has a default timeout, is it possible that it terminates there just because of the request timeout? Can you share the fully cli command you used or the curl request you used? |
I got the similar issue. My workaround was trying to remove the function and then redeploy it. And |
Not sure how removing the function could prevent a crash. Can either of you give us full reproduction instructions? |
Expected Behaviour
Faas-swarm works fine.
Current Behaviour
Faas-swarm crashed soon after starting.
Possible Solution
No solution has been found yet (not familiar with golang).
Steps to Reproduce (for bugs)
Context
Your Environment
faas-cli version
):faas-swarm version: 0.8.5
docker version
(e.g. Docker 17.0.05 ):Docker Swarm
Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-142-generic x86_64)
The text was updated successfully, but these errors were encountered: