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

500: Internal server error , expect blob.data.ndim == 4 #12

Closed
jmozah opened this issue Mar 20, 2015 · 6 comments
Closed

500: Internal server error , expect blob.data.ndim == 4 #12

jmozah opened this issue Mar 20, 2015 · 6 comments
Labels

Comments

@jmozah
Copy link

jmozah commented Mar 20, 2015

Hi

When testing a trained model (stock AlexNet) using a single image... i get "500: internal server error", Assertion failed: expect blob.data.ndim == 4.

@lukeyeager
Copy link
Member

To clarify, you are looking at a trained model, choosing a model snapshot with epoch=x, giving either an image URL or selecting one locally, and clicking on "Test one image," right? And then you get this error?

That's strange, that shouldn't happen. I see in #10 that you may have some conflicting version of caffe on your system. Is it possible that you're linking against a different version of caffe than NVIDIA's fork? This commit is the biggest difference between NVIDIA/caffe and BVLC/caffe at the moment, and it looks like it may be related to the error that you're seeing.

@jmozah
Copy link
Author

jmozah commented Mar 20, 2015

Iam running stock caffe in the server ... Thanks for the commit pointer... I will dig more and respond back

Sent from my iPhone

On 20-Mar-2015, at 10:23 pm, Luke Yeager notifications@github.com wrote:

To clarify, you are looking at a trained model, choosing a model snapshot with epoch=x, giving either an image URL or selecting one locally, and clicking on "Test one image," right? And then you get this error?

That's strange, that shouldn't happen. I see in #10 that you may have some conflicting version of caffe on your system. Is it possible that you're linking against a different version of caffe than NVIDIA's fork? This commit is the biggest difference between NVIDIA/caffe and BVLC/caffe at the moment, and it looks like it may be related to the error that you're seeing.


Reply to this email directly or view it on GitHub.

@lukeyeager
Copy link
Member

I am running stock caffe

Well then that's probably your problem right there. As laid out in the README, you need to use the NVIDIA/caffe fork.

@cjtonde
Copy link

cjtonde commented Mar 21, 2015

@jmozah I had the same issue.
@lukeyeager I tried your solution. I had used stock caffe version with the digits so I switched to NVIDIA/caffe version and that fixed the issue.

@zdx3578
Copy link

zdx3578 commented Mar 28, 2015

500 ParseError 2:1 : Message type "caffe.NetParameter" has no field named "layer".

this error is also caffe version ; caffe version should nvidia/caffe fork.

@lukeyeager
Copy link
Member

@zdx3578, see my response to your issue in #39. Your problem is not related to @jmozah's.

I'm closing this issue as it seems to be fixed by building from the NVIDIA/caffe fork.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants