Closed rolinux closed 4 years ago
Also in Tools -> Database -> Recording DB Analysis triggers Unexpected Error The Server responded with a status code of 400.
So instead of passing in a path, you have a volume and pass that in? How does the volume get passed around the cluster?
It is a single host cluster
. I tried with direct volumes and still the same. Even using docker directly (outside the kubernetest) I get the same 'Unexpected Error The Server responded with a status code of 400.'
Is it possible this is just somehow the weird :3.10.8
issues? Can you try on :3.10.6
?
Ended up running in docker (not kubernetes) with image 3.10.4 (as on the original host). Had to reset 2 cameras and downgrade firmware to get it working.
I spent too much time to try again :(
@rolinux, did you ever got this working? I'm running into exactly the same problem..
@rolinux, did you ever got this working? I'm running into exactly the same problem..
Did you manage to solve the issue? I'm having the same issue.
Nope. Ended up buying the Cloudkey Gen2
@rolinux, did you ever got this working? I'm running into exactly the same problem..
Did you manage to solve the issue? I'm having the same issue.
Did YOU ever end up figuring this out? I'm also stuck here...
This is more of a cry for help than a bug with the image as I've spend the last few days trying to debug why the docker image worked in docker on my old host but after migration when trying to use Kubernetes and Volumes is not able to see the path or record anything.
I can see the live cameras, connect to the cloud and make see the old recordings but not able to record new ones.
The K8s namespace:
The folder inside the container:
There are 2 volumes in the deployment:
I can provide the full code for the StorageClass, PersistentVolume, PersistenVolumeClaim, Deployment and so on.
Unsure if the problem is both the volumes or only the path to record.
The logs:
The Deployment is:
The
192.168.3.9
is for the VLAN where the cameras run.Thank you