[smartos-discuss] SmartOS release-20161208

[Trent Mick]

Hello All,

The latest bi-weekly "release" branch build of SmartOS is up:

curl -C - -O
https://us-east.manta.joyent.com/Joyent_Dev/public/SmartOS/smartos-latest.iso
curl -C - -O
https://us-east.manta.joyent.com/Joyent_Dev/public/SmartOS/smartos-latest-USB.img.bz2
curl -C - -O
https://us-east.manta.joyent.com/Joyent_Dev/public/SmartOS/smartos-latest.vmwarevm.tar.bz2

A generated changelog is here:


https://us-east.manta.joyent.com/Joyent_Dev/public/SmartOS/smartos.html#20161208T003707Z

The full build bits directory, for those interested, is here in Manta:

/Joyent_Dev/public/SmartOS/20161208T003707Z


# General Info

Every second Thursday we roll a "release-MMDD" release branch and
builds for SmartOS (and Triton DataCenter and Manta, as well).

Cheers,
Trent, on behalf of the SmartOS developers
https://smartos.org



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] event ports are broken with FIFOs

[Robert Mustacchi]

On 12/8/16 18:15 , Peter Toth wrote:
> Thanks Robert,
> 
> Have been testing Nginx lately with use eventport;  (source
> http://letsgetdugg.com/2009/04/21/nginx-hidden-performance-option/) on
> SamrtOS and have experienced some abnormal behaviour.
> 
> Mostly this error "port_dissociate() failed (2: No such file or directory)
> while reading upstream, client" but also cases where Nginx stops serving
> content and just hangs.
> 
> Not entirely sure this is the root cause, but after taking "use eventport"
> out of the config everything seem normal again.

It's pretty hard to say whether or not it's related to that. You could
check and see if nginx is using any FIFOs, but that wouldn't relate to
port_disociate behavior. There may just be some bugs in nginx, but hard
to say for certain without more information.

Robert

> On Fri, Dec 9, 2016 at 2:50 PM, Robert Mustacchi  wrote:
> 
>> On 12/8/16 17:42 , Peter Toth wrote:
>>> Anyone knows whether this is affecting recent SmartOS builds
>>> https://www.illumos.org/issues/6524 ?
>>
>> As the bug has not been fixed, it is possible to occur with any SmartOS
>> release. Though it does require a specific user land programs to cause
>> it to happen.
>>
>> Robert
>>
> 
> 


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] event ports are broken with FIFOs

[Peter Toth]

Thanks Robert,

Have been testing Nginx lately with use eventport;  (source
http://letsgetdugg.com/2009/04/21/nginx-hidden-performance-option/) on
SamrtOS and have experienced some abnormal behaviour.

Mostly this error "port_dissociate() failed (2: No such file or directory)
while reading upstream, client" but also cases where Nginx stops serving
content and just hangs.

Not entirely sure this is the root cause, but after taking "use eventport"
out of the config everything seem normal again.



On Fri, Dec 9, 2016 at 2:50 PM, Robert Mustacchi  wrote:

> On 12/8/16 17:42 , Peter Toth wrote:
> > Anyone knows whether this is affecting recent SmartOS builds
> > https://www.illumos.org/issues/6524 ?
> 
> As the bug has not been fixed, it is possible to occur with any SmartOS
> release. Though it does require a specific user land programs to cause
> it to happen.
> 
> Robert
> 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] event ports are broken with FIFOs

[Robert Mustacchi]

On 12/8/16 17:42 , Peter Toth wrote:
> Anyone knows whether this is affecting recent SmartOS builds
> https://www.illumos.org/issues/6524 ?

As the bug has not been fixed, it is possible to occur with any SmartOS
release. Though it does require a specific user land programs to cause
it to happen.

Robert


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] event ports are broken with FIFOs

[Peter Toth]

Anyone knows whether this is affecting recent SmartOS builds
https://www.illumos.org/issues/6524 ?

Thanks
P



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] FLAG DAY: RFD 69 / OS-5783

[Josh Wilsdon]

Hello,

A change has just been pushed to master which introduces a flag day between
smartos-live and illumos-joyent. If you don't build your own platforms, or
if you always make sure to update both illumos-joyent and smartos-live
before building, or if you never use LX you shouldn't need to worry about
this.

If you build your own platforms and don't usually update both smartos-live
and illumos-joyent, you will need to do so the next time you update either
of these if want metadata to work in LX zones. This is because the
platform.xml file for LX zones lives in illumos-joyent while the rest of
the changes here are in smartos-live.

For more information about the change itself, see:

https://github.com/joyent/rfd/blob/master/rfd/0069/README.md

Thanks,
Josh



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] vnc resolution configurable?

[Nahum Shalman]

Wow, resurrecting a thread from 2013 with my email address from my previous
employer. Okay, let's jump in.

On Thu, Dec 8, 2016 at 3:47 AM, Fred Liu  wrote:

> We noticed that GUI since SL7.2 did not work with the low resolution
> 1024x768 which is the default-detected resolution from SmartOS vnc server.
>

That might have to do with the default amount of video memory QEMU gives
the VM. You may be able to change that with qemu_extra_opts. I've only ever
done that to the QXL device rather than the default VGA device so I don't
know what the variable you'd need to set would be.

Is there a way to configure the vnc to run in higher resolution like
> 1280x1024? And I don't need to hack Linux to forcedly run in higher
> resolution.
>

I think what you're asking is "How do I make all changes on the
SmartOS/QEMU/Client side so that I don't have to make any changes within
the guest OS?"

The first thing I would try to do is force the VNC client to try to connect
at a higher resolution. That might be enough to jolt the X server up to the
higher resolution so that the login UI will be able to render correctly.

Figuring out what arguments to add to qemu_extra_opts is what I would
explore second.



> BTW, is spice stable enough on SmartOS?
>

My old email address which was CCd on your message was from my time at
Elysium Digital which was acquired by Stroz Friedberg[1] in 2015 and which
I left in March of this year (2016).
When I left, ~50 people in that Boston office were still using Spice
enabled VMs (running Fedora as the guest OS) on SmartOS as their primary
work systems every day which they had been doing for years.
I would have argued then that for some value of stable, that counted.

I do not know if that system is still in use, and even if it is, it
probably won't be for much longer.
For a while after I left I was still regularly using a Spice enabled Fedora
VM on my home server for most of my personal stuff.
At this point most of what I was doing on it has been split apart between a
Mac laptop and a Centos 7 LX branded zone on the SmartOS machine.
Which means that the Spice for SmartOS work is currently dormant in terms
of my time and I'm pretty sure no one else is actively developing it.

So it may be somewhat stable, but it's kind of rotting on the vine at this
point.


If anyone out there is using the Spice enabled QEMU code and needs support,
my current employer, OmniTI, is a consulting company and can sell you my
time to work on it.


-Nahum

[1] Stroz Friedberg has since been acquired by Aon


> -Original Message-
> > From: Nahum Shalman [mailto:nshalman-smar...@elys.com]
> > Sent: 星期一, 三月 25, 2013 21:01
> > To: smartos-discuss@lists.smartos.org
> > Cc: Alain O'Dea
> > Subject: Re: [smartos-discuss] Cannot get working VNC Viewer onto KVM
> Zone
> >
> > On 03/23/2013 09:56 PM, Alain O'Dea wrote:
> > > Is SPICE a feasible option here?  I notice the experimental
> > > configuration options for it.  I'm really only looking at having a
> > > console long enough to install the OS and bootstrap a Bomgar session
> > > onto the desktop.
> >
> > Feasible, possibly. Ideal, probably not.
> > In order to use Spice, you need to use an alternate QEMU binary rather
> than
> > the one that ships with the platform.
> > (See http://wiki.smartos.org/display/DOC/Spice+on+SmartOS for details)
> >
> > The benefit of using "my" QEMU is that you can use Spice. The biggest
> down
> > side is that if you run into problems, you're not using the Joyent
> supported
> > QEMU.
> >
> > One option if you're trying to build a fresh image to use later as a
> template that
> > will have SSH already working, you could try using the Spice enabled
> QEMU for
> > the stage of building your image, verify that a fresh boot of that image
> does
> > bring up SSH as desired, then use that image with the platform QEMU.
> >
> > So, order of preference from best to worst from my perspective:
> >Try to get VNC working.
> >Use Spice enabled QEMU for image building, platform QEMU for
> production
> > workload.
> >Use Spice enabled QEMU for building and running in production
> >
> > I do run "my" QEMU in production, but I can't provide support.
> >
> > -Nahum
> >
> > P.S.  I might not-so-secretly be hoping that you'll choose #3 *and* that
> you'll
> > then ask Joyent to support it... A guy can dream.
>



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] UUID is already not 'running' (currently: shutting_down)

[Robert Mustacchi]

On 12/8/16 9:07 , the outsider wrote:
> Hi,
> 
> that didn’t work unfortunately. 
> 
>  
> 
> Also vmadm stop UUID -F did nothing. 
> 
>  
> 
> The zone is a plain SmartOS zone. No special VM. 
> 
>  
> 
> Prstat -z UUID shows:
> 
>PID USERNAME  SIZE   RSS STATE  PRI NICE  TIME  CPU PROCESS/NLWP
> 
>   8405 root   15M 9568K sleep10   0:00:28 0.0% smbd/2
> 
>   4206 root0K0K sleep   60-   0:00:00 0.0% zsched/1
> 
>  
> 
> And cannot kill both processes. (tried pkill from global zone)

If you can't kill them, that means that they're stuck waiting for
something to happen. Most likely zsched is blocked on smbd. What you
should do next is run the following:

mdb -ke '0t8405::pid2proc | ::walk thread | ::findstack -v'

Robert



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] UUID is already not 'running' (currently: shutting_down)

[the outsider]

Hi,

that didn’t work unfortunately. 

 

Also vmadm stop UUID -F did nothing. 

 

The zone is a plain SmartOS zone. No special VM. 

 

Prstat -z UUID shows:

   PID USERNAME  SIZE   RSS STATE  PRI NICE  TIME  CPU PROCESS/NLWP

  8405 root   15M 9568K sleep10   0:00:28 0.0% smbd/2

  4206 root0K0K sleep   60-   0:00:00 0.0% zsched/1

 

And cannot kill both processes. (tried pkill from global zone)

 

Zone is still responding to ping but SSH and login are down. 

 

 

 

 

 

Van: Mark Creamer [mailto:white...@gmail.com] 
Verzonden: donderdag 8 december 2016 16:22
Aan: smartos-discuss@lists.smartos.org
Onderwerp: Re: [smartos-discuss] UUID is already not 'running' (currently: 
shutting_down)

 

Last time this happened to me I used zoneadm -z [UUID] halt

 

and then after it was finally down I started it using vmadm as normal.

 

On Thu, Dec 8, 2016 at 9:50 AM, the outsider  > wrote:

I tied to reboot a zone, but after a while it didn’t seem to reboot. So I did 
reboot from within the zone. 

But after almost half an hour the zone is still in shutting down state and 
can’t be touched in any way. 

 

What is the best thing to do now? 

(yes, I will grab some coffee. But how to get this zone rebooted and up again? 
) 





 

-- 

Mark


smartos-discuss |   
Archives   
|   Modify Your Subscription

  

 




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] UUID is already not 'running' (currently: shutting_down)

[Mark Creamer]

Last time this happened to me I used zoneadm -z [UUID] halt

and then after it was finally down I started it using vmadm as normal.

On Thu, Dec 8, 2016 at 9:50 AM, the outsider 
wrote:

> I tied to reboot a zone, but after a while it didn’t seem to reboot. So I
> did reboot from within the zone.
>
> But after almost half an hour the zone is still in shutting down state and
> can’t be touched in any way.
>
>
>
> What is the best thing to do now?
>
> (yes, I will grab some coffee. But how to get this zone rebooted and up
> again? )
>
> *smartos-discuss* | Archives
> 
>  |
> Modify
> 
> Your Subscription 
>



-- 
Mark



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] vnc resolution configurable?

[Fred Liu]

Hi,

We noticed that GUI since SL7.2 did not work with the low resolution 1024x768 
which is the default-detected resolution from SmartOS vnc server.
Is there a way to configure the vnc to run in higher resolution like 1280x1024? 
And I don't need to hack Linux to forcedly run in higher resolution.

BTW, is spice stable enough on SmartOS?


Thanks.

Fred
> -Original Message-
> From: Nahum Shalman [mailto:nshalman-smar...@elys.com]
> Sent: 星期一, 三月 25, 2013 21:01
> To: smartos-discuss@lists.smartos.org
> Cc: Alain O'Dea
> Subject: Re: [smartos-discuss] Cannot get working VNC Viewer onto KVM Zone
> 
> On 03/23/2013 09:56 PM, Alain O'Dea wrote:
> > Is SPICE a feasible option here?  I notice the experimental
> > configuration options for it.  I'm really only looking at having a
> > console long enough to install the OS and bootstrap a Bomgar session
> > onto the desktop.
> 
> Feasible, possibly. Ideal, probably not.
> In order to use Spice, you need to use an alternate QEMU binary rather than
> the one that ships with the platform.
> (See http://wiki.smartos.org/display/DOC/Spice+on+SmartOS for details)
> 
> The benefit of using "my" QEMU is that you can use Spice. The biggest down
> side is that if you run into problems, you're not using the Joyent supported
> QEMU.
> 
> One option if you're trying to build a fresh image to use later as a template 
> that
> will have SSH already working, you could try using the Spice enabled QEMU for
> the stage of building your image, verify that a fresh boot of that image does
> bring up SSH as desired, then use that image with the platform QEMU.
> 
> So, order of preference from best to worst from my perspective:
>Try to get VNC working.
>Use Spice enabled QEMU for image building, platform QEMU for production
> workload.
>Use Spice enabled QEMU for building and running in production
> 
> I do run "my" QEMU in production, but I can't provide support.
> 
> -Nahum
> 
> P.S.  I might not-so-secretly be hoping that you'll choose #3 *and* that 
> you'll
> then ask Joyent to support it... A guy can dream.
> 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com