search

NetSys / bess

BESS: Berkeley Extensible Software Switch
Other
313 stars 156 forks source link

BESS daemon response - errno=19 (ENODEV: No such device) #867

Closed omzmarlon closed 5 years ago

omzmarlon commented 6 years ago

I am running this script in BESS ctl but get a no such device error:

image

image

I am not sure how to debug this, I was under the impression that using PMDPort would automatically create a virtual device for you. But it is not found.

Any ideas how to fix this?

Thank you!

omzmarlon commented 5 years ago

Issue resolved. It seems creating a virtual device using PMDPort will create a socket file in the specified location. And after that if you want to re-run the script again you have to run "daemon reset" which will delete the created socket file for you (or you can delete them manually). If the sock file is already created at the specified location, this "device not found" error will return (which sounds weird, because the device file is actually there, but it reports "not found").

It seems only "daemon reset" does the right job of cleaning socket files. If you run "daemon stop" and then "daemon start" the socket file won't be cleaned. Intuitively, "daemon stop" + "daemon start" = "daemon reset" to me