On 12/28/2011 04:10 PM, Patrick Mullaney wrote: > I am using sles11sp1. My kernel is 2.6.32.49-0.3-default. > > I tried the packages that came with sles11sp1 as a start and ran into the > issue. I am currently using > my own build of open-iscsi-2.0-872 and I have tried building from head of > the git repo, > both with the same result. > > I have been able to get this to work under the same kernel and versions on > the host machine as > opposed to in the lxc container. I suspect that the af_netlink code is > refusing the connection because > the connection is initiated in the container(perhaps its a capabilities > issue but that is just a guess at this point).
Yeah, sounds like a reasonable guess. I am not exactly sure what is in the SLES kernel. Could you run a patch with some debugging, so we can check where exactly it is failing in the netlink code. What version of lxc are you using? Does it come with SLES or did you download it from sourceforge? > > On Wed, Dec 28, 2011 at 3:36 AM, Mike Christie <[email protected]> wrote: > >> On 12/22/2011 04:44 PM, pmullaney wrote: >>> Hi all, >>> >>> Running into problems running under lxc. I am running iscsid in the >>> container and when it >>> attempts to connect to the netlink iscsi socket it is getting a >>> connection refused(111) and >>> the following in the log: >>> >>> sendmsg: bug? ctrl_fd 5 >>> >>> which causes iscsid to exit. >>> >>> Any thoughts on what could be wrong? >>> >> >> The iscsi netlink code never returns 111/ECONNREFUSED. >> >> It looks like the netlink code will return this when the netlink socket >> is not setup. >> >> What kernel are you using? What iscsi modules? Did they come with your >> kernel? >> > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
