Re: [OmniOS-discuss] LX Zone DTrace

> On Jan 15, 2017, at 2:21 PM, Mini Trader wrote: > > Here is the strace. Which shows the underlying libc call failing. chdir > would have failed if the directory was not there. Maybe a race condition > going on here? Does this now become a Linux bug? > > I've

Re: [OmniOS-discuss] LX Zone DTrace

Here is the strace. Which shows the underlying libc call failing. chdir would have failed if the directory was not there. Maybe a race condition going on here? Does this now become a Linux bug? I've even made a call to pwd in the exception and it does not fail. lstat("ParameterSet",

Re: [OmniOS-discuss] LX Zone DTrace

I just tried on CentOS same error. The directory has to be from LOFS i.e. a ZFS pool. >From OmniOS can you output zfs get all zonefileset and /usr/bin/ls -lV zonedirectory and share your results. On Sat, Jan 14, 2017 at 9:35 AM, Natxo Asenjo wrote: > hi, > > > On Sat,

Re: [OmniOS-discuss] LX Zone DTrace

hi, On Sat, Jan 14, 2017 at 3:16 PM, Mini Trader wrote: > Well the author at my request was able to remove the call to os.getcwd() > which allows the program to operate. > > > If anyone wants to tinker here is an example that will likely break on > someones system. I

Re: [OmniOS-discuss] LX Zone DTrace

Well the author at my request was able to remove the call to os.getcwd() which allows the program to operate. If anyone wants to tinker here is an example that will likely break on someones system. I don't know if this is an LX bug, libc bug, python bug etc. # read a directory, stat all files

Re: [OmniOS-discuss] LX Zone DTrace

Here is the code. It will run just fine with Debian 8.6 or OmniOS. It will fail on the LX zone with Debian. The only way for it to fail is for the stat call to fail and this seems to happen because the system doen't know what directory it is in. The files being looked at are static so not a

Re: [OmniOS-discuss] LX Zone DTrace

Could you provide some of your telemetry and background here? There might be a reasonable explanation, or a quick fix. /dale > On Jan 13, 2017, at 3:12 PM, Mini Trader wrote: > > I have a small program that will reproduce the issue. Where should the bug > be sent?

Re: [OmniOS-discuss] LX Zone DTrace

I have a small program that will reproduce the issue. Where should the bug be sent? It's pretty serious. The system is forgetting the location of the current working directory in a recursive call. On Fri, Jan 13, 2017 at 9:30 AM, Nahum Shalman wrote: > Have you tried

Re: [OmniOS-discuss] LX Zone DTrace

Have you tried simply tracing the lx-syscall probes? On Fri, Jan 13, 2017 at 9:24 AM, Mini Trader wrote: > I followed these instructions prior to my post and my zone would not boot > after doing the mod to add the flag to the file. > > > On Fri, Jan 13, 2017 at 8:55 AM

Re: [OmniOS-discuss] LX Zone DTrace

I followed these instructions prior to my post and my zone would not boot after doing the mod to add the flag to the file. On Fri, Jan 13, 2017 at 8:55 AM Nahum Shalman wrote: > The short answer is yes. > > My experience debugging LX was on SmartOS and there are some notes

Re: [OmniOS-discuss] LX Zone DTrace

The short answer is yes. My experience debugging LX was on SmartOS and there are some notes on https://wiki.smartos.org/display/DOC/LX+Branded+Zones#LXBrandedZones-Debugging Some of the details on that page are Specific to SmartOS, but some of it is generic to LX. -Nahum On Fri, Jan 13, 2017

[OmniOS-discuss] LX Zone DTrace

Is there anything that can be done to trace a program having issues on an LX Zone. I am seeing: OSError: [Errno 2] No such file or directory: Again under certain conditions which I am trying to trace - unfortunately this is a closed source program. Can DTrace be used to help track something