Re: [smartos-discuss] Forking a pty

Have you tried running truss -f on the python process? It sounds like something in there might be hanging (and so the master process is stuck waiting and thus never invokes the callback). Truss might help narrow things down. On March 17, 2017 at 8:17:36 PM, David Preece (da...@polymath.tech)

Re: [smartos-discuss] VMs down after upgrading to latest SmartOS

I looks like the smardc/mdata:fetch service might be stuck.  Do you have the logfile for that (/var/svc/log/smartdc-mdata:fetch.log) ? On July 22, 2017 at 6:09:29 PM, John Croix (jcr...@mac.com) wrote: As an update to my own question, build 20170706T001501Z works just fine. It’s only the

Re: [smartos-discuss] node communications topology question

Triton consists of a number of services and agents.  Typically the services run on the head node and agents run on the compute nodes (this is simplifying things a bit) and they communicate over an administrative VLAN.  Typically this communication is between the headnode and the compute notes

RE: [smartos-discuss] Proposed Experimental Setup

All the IPsec utilities are still there (sadly the in.ike bits are still closed source).  You’d likely want to do everything from a zone since there’s nothing setup in a smartos global zone to use them. On August 5, 2017 at 5:27:18 AM, a b (tripivc...@hotmail.com) wrote: While we are on

Re: [smartos-discuss] node communications topology question

Let’s try that again (#$@# touchbar)… Typically you have an administrative VLAN for traffic between the services/agents running on the headnode and compute nodes.  Typically this is going to be between the headnode and the compute nodes than between compute nodes.  Containers can be

Re: [smartos-discuss] Proposed Experimental Setup

from one node to the other). I have set up IPSec in the transport mode with pre-shared key authentication. Will some other setup fail to work? MiroB. - Original Message - From: "Jason King" <jason.brian.k...@gmail.com> To: "a b" <tripivc...@

Re: [smartos-discuss] Problems with low memory (lx zones)

I don’t know if this helps or not, but a better way to think of it is that for every page of memory, the OS wants to make sure there’s somewhere it can go on disk.  For application code, this is easy — it can just re-read the code from the binary (assuming it hasn’t changed) if necessary.  For

Re: [smartos-discuss] USB to RS232 Serial adapters

Might as well shoot off an email with whatever diagnostic messages you have and the version of SmartOS you’re running. While no guarantees someone will be able to help, it can’t hurt either. On May 5, 2017 at 10:27:05 AM, Jeff Goeke-Smith (goeke...@gmail.com) wrote: I'm looking for anybody who

Re: [smartos-discuss] Intel x520-da2 and DAC cables or third party optics?

Having run into this frustration with VMware + Intel NICs at $JOB-1, I feel your pain :) By default, the ixgbe driver does not allow unsupported SFPs ( https://github.com/joyent/illumos-joyent/blob/master/usr/src/uts/common/io/ixgbe/ixgbe_sw.h#L172). However it does mean there is a driver

Re: [smartos-discuss] service varpd not working

hould also use is_env_string smartos-live: OS-6958 bad comparison introduced with OS-6630 On Fri, May 18, 2018 at 4:11 PM, Jason King <jason.brian.k...@gmail.com> wrote: > What is the last commit in your branch that you built? I’ll try to > recreate this locally. > > > Fro

Re: [smartos-discuss] service varpd not working

What is the last commit in your branch that you built? I’ll try to recreate this locally. From: Youzhong Yang Reply: smartos-discuss@lists.smartos.org Date: May 18, 2018 at 3:04:31

Re: [smartos-discuss] softether vpn

For the SoftEther code changes, I’d suggest looking into libdlpi(3DLPI). It’ll take care of most of the DLPI details for you (including handling both style 1 and style 2 devices — it sounds like it can’t handle style 1 devices — e.g. /dev/net0), it’s also something that’s been around since Solaris

Re: [smartos-discuss] smartos-latest is over a month old?

I have a fix up for review (it looks like it was a strange ksh93 bug w/ it’s builtin implementation of cat), so I’m hopeful we’ll be able to get a release out next week. From: Rob Seastrom Reply: smartos-discuss@lists.smartos.org

Re: [smartos-discuss] Is it Normal?

Is there any configuration settings in ApacheDS dealing with virtual list view (VLV) controls? IIRC the native ldap client uses that control for enumeration of entries (to give the results in chunks). From: k...@protonmail.com Reply:

Re: [smartos-discuss] anyone know a SmartOS friendly Mini-ITX motherboard?

How were you disabling the other cores?  If not doing so from the BIOS, probably the easiest way on SmartOS to do it is to boot w/ kmdb (-kd in the boot args) and when KMDB loads, type ‘use_mp/W 0’ then ‘:c’ to continue.  If might also be useful to include the -v flag as well to see how far

Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself

: Youzhong Yang Reply: Youzhong Yang Date: August 13, 2018 at 9:29:07 AM To: Jason King Cc: smartos-discuss@lists.smartos.org Subject:  Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself Hi Jason, The image that had the issue was a full build, but last night I

Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself

it to hang (though it’ll take a bit to do a full build). From: Youzhong Yang Reply: Youzhong Yang Date: August 13, 2018 at 12:27:52 AM To: Jason King Cc: smartos-discuss@lists.smartos.org Subject:  Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself So your image

Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself

Was that with boot -v?  Are you able to send the system an NMI after it hangs (or get the boot -v output up to the hang)? Prior to OS-7079, the system would start to startup the next CPU before it had completely finished initializing the ‘current’ CPU (which could deadlock depending on which

Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself

it at https://us-east.manta.joyent.com/jbk/OS-7079/platform-20180719T001516Z.{iso,tgz,usb.bz2} If you do, it’d be interesting to see ::cpustack on each core looks like. From: Youzhong Yang Reply: Youzhong Yang Date: August 12, 2018 at 11:58:48 PM To: Jason King Cc: smartos-discuss@lists.smartos.org

Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself

Doh.. the problems of it being late :) .. there should be a ‘public’ in there.  Try https://us-east.manta.joyent.com/jbk/public/OS-7079/platform-20180719T001516Z.iso From: Youzhong Yang Reply: Youzhong Yang Date: August 13, 2018 at 12:12:52 AM To: Jason King Cc: smartos-discuss

Re: [smartos-discuss] anyone know a SmartOS friendly Mini-ITX motherboard?

That Solaris works w/ a single CPU makes me wonder if it might be OS-7079 (still under review/testing so the fix hasn’t been integrated yet). The bug was introduced in 2009 (so it’s very possible Solaris still has this bug), but seems to have been hard enough to hit that it hasn’t been

Re: [smartos-discuss] anyone know a SmartOS friendly Mini-ITX motherboard?

Are there any power management options in the bios? > On Jul 22, 2018, at 8:09 AM, Robert Fisher wrote: > > Thanks for the advice everyone, but nothing is helping. > > Using `use_mp/W 0` makes no difference. It hangs at exactly the same place. > (However, doing this on Solaris 11 allows it

Re: [smartos-discuss] anyone know a SmartOS friendly Mini-ITX motherboard?

If you can, instead of disabling the cores in the BIOS, try to boot -kvd (kmdb w/ debug), and at the kmdb prompt, type “use_mp/W 0” to set use_mp to 0, then “:c” to continue the boot process. From: Robert Fisher Reply: smartos-discuss@lists.smartos.org Date: July 21, 2018 at 5:03:32 PM To: 

Re: [smartos-discuss] anyone know a SmartOS friendly Mini-ITX motherboard?

I do see some options for managing C states. I’d need to confirm when I’m back at work (unfortunately I’m out for the week) for specifics, but ISTR some issues involving them. > On Jul 22, 2018, at 9:23 AM, Robert Fisher wrote: > > ​> Are there any power management options in the bios? > >