[OmniOS-discuss] Supermicro X10DRi-T4+ usable with Illumos?

[qutic development]

Hi,

Is anyone using the Supermicro X10DRi-T4+ with the onboard sata for zfs with 
SmartOS or OmniOSce?

And is the 10Gbit-Driver working with this board?

Thanks!

- Stefan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Problem with upgrade from r151014 to r151022

[qutic development]

Have you done a "pkg update" to get the latest updates from r151014 before 
switching the publisher to r151022?

- Stefan

> Am 29.07.2017 um 12:47 schrieb Даниил Ландау :
> 
> Hello!
> 
> I’m trying to upgrade my small home server with 3 lipkg zones from r151014 to 
> r151022.
> 
> I’ve moved from SunSSH to OpenSSH (in global and all lipkg zones):
> 
> # pkg list |grep ssh
> network/openssh   7.4.1-0.151014 
> i--
> network/openssh-server7.4.1-0.151014 
> i--
> 
> 
> Also I changed publisher to r151022 (in global and lipkg zones also):
> 
> # pkg publisher
> PUBLISHER   TYPE STATUS P LOCATION
> omnios  origin   online F 
> https://pkg.omniti.com/omnios/r151022/
> ms.omniti.com   origin   online F http://pkg.omniti.com/omniti-ms/
> 
> 
> But when I run "pkg update" from global zone or from a lipkg zone I get 
> errors (please see at the end of the message). It looks very strange for me. 
> Did I missed something in upgrade plan or, may be, there are some other 
> issues?
> 
> Thank you for help!
> 
> Daniil
> 
> 
> 
> Creating Plan (Running solver): |
> pkg update: No solution was found to satisfy constraints
> Plan Creation: Package solver has not found a solution to update to latest 
> available versions.
> This may indicate an overly constrained set of packages are installed.
>  
> latest incorporations:
>  
>   pkg://omnios/entire@11,5.11-0.151022:20170511T002513Z
>   
> pkg://omnios/incorporation/jeos/illumos-gate@11,5.11-0.151022:20170510T210757Z
>   
> pkg://omnios/consolidation/osnet/osnet-incorporation@0.5.11,5.11-0.151022:20170510T212740Z
>   
> pkg://omnios/incorporation/jeos/omnios-userland@11,5.11-0.151022:20170511T001737Z
>  
> The following indicates why the system cannot update to the latest version:
>  
>   No suitable version of required package 
> pkg://omnios/consolidation/osnet/osnet-incorporation@0.5.11,5.11-0.151022:20170510T212740Z
>  found:
> Reject:  
> pkg://omnios/consolidation/osnet/osnet-incorporation@0.5.11,5.11-0.151022:20170510T212740Z
> Reason:  A version for 'incorporate' dependency on 
> pkg:/SUNWcs@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/incorporation/jeos/illumos-gate@11,5.11-0.151022:20170510T210757Z
>  found:
> Reject:  
> pkg://omnios/incorporation/jeos/illumos-gate@11,5.11-0.151022:20170510T210757Z
> Reason:  A version for 'incorporate' dependency on 
> pkg:/SUNWcs@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/entire@11,5.11-0.151022:20170511T002513Z found:
> Reject:  pkg://omnios/entire@11,5.11-0.151022:20170511T002513Z
> Reason:  A version for 'require' dependency on 
> pkg:/SUNWcs@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/shell/zsh@5.3.1,5.11-0.151022:20170510T233501Z found:
> Reject:  pkg://omnios/shell/zsh@5.3.1,5.11-0.151022:20170510T233501Z
> Reason:  A version for 'require' dependency on 
> pkg:/SUNWcs@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/system/management/snmp/net-snmp@5.7.3,5.11-0.151022:20170511T003113Z
>  found:
> Reject:  
> pkg://omnios/system/management/snmp/net-snmp@5.7.3,5.11-0.151022:20170511T003113Z
> Reason:  A version for 'require' dependency on 
> pkg:/SUNWcs@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/security/sudo@1.8.7,5.11-0.151022:20170511T001935Z found:
> Reject:  pkg://omnios/security/sudo@1.8.7,5.11-0.151022:20170511T001935Z
> Reason:  A version for 'require' dependency on 
> pkg:/SUNWcs@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/library/libxslt@1.1.29,5.11-0.151022:20170511T003321Z found:
> Reject:  
> pkg://omnios/library/libxslt@1.1.29,5.11-0.151022:20170511T003321Z
> Reason:  A version for 'require' dependency on 
> pkg:/SUNWcs@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/compress/p7zip@16.2,5.11-0.151022:20170510T225314Z found:
> Reject:  pkg://omnios/compress/p7zip@16.2,5.11-0.151022:20170510T225314Z
> Reason:  A version for 'require' dependency on 
> pkg:/SUNWcs@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/compress/gzip@1.8,5.11-0.151022:20170510T233218Z found:
> Reject:  pkg://omnios/compress/gzip@1.8,5.11-0.151022:20170510T233218Z
> Reason:  A version for 'require' dependency on 
> pkg:/system/library@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/system/library/mozilla-nss@3.30.2,5.11-0.151022:20170510T212137Z 
> found:
> Reject:  
> pkg://omnios/system/library/mozilla-nss@3.30.2,5.11-0.151022:20170510T212137Z
> 

Re: [OmniOS-discuss] Python conflicts in upgrade from 20 to 22

[qutic development]

I do have the same issues. The upgrade to r151022 fails with the described 
python conflict.

Any hint how to fix it is appreciated :)

> Hello,
>  
> I’m doing upgrade from version 20 to 22 LTS, and when I run pkg updade (after 
> changing Publisher), I’m receiving many conflicts between Python 2.6 and 2.7 
> which prevents me in upgrade.
> Can anyone please help me, how to correctly do upgrade with replacing Python 
> 2.6 with Python 2.7?
>  
> Thank you very much,
> Filip
>  
> 
> pkg update: The requested change to the system attempts to install multiple 
> actions
> for link 'usr/bin/amd64/python-config' with conflicting attributes:
>  
> 1 package delivers 'link path=usr/bin/amd64/python-config 
> target=python2-config':
> pkg://omnios/runtime/python-27@2.7.13,5.11-0.151022:20170511T005259Z
> 1 package delivers 'link path=usr/bin/amd64/python-config 
> target=python2.6-config':
> pkg://omnios/runtime/python-26@2.6.8,5.11-0.151020:20161102T021635Z
>  
> These packages may not be installed together.  Any non-conflicting set may
> be, or the packages must be corrected before they can be installed.
>  
> The following packages all deliver file actions to usr/bin/smtpd.py:
>  
>   pkg://omnios/runtime/python-27@2.7.13,5.11-0.151022:20170511T005259Z
>   pkg://omnios/runtime/python-26@2.6.8,5.11-0.151020:20161102T021635Z
>  
> …and many more
> ---
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

[OmniOS-discuss] No boot after pkg update

[qutic development]

Hi List,

after a pkg update to get the latest r151014 changes (which required a reboot) 
the supermicro server failed to boot with error [1]: 

failed to get ramdisk from boot

Next I tried to boot from an older BEs. This failed too, but with another error 
[2]:

null path
krtld: failed to open ''

Now I tried to create a new boot-archive with the help of an r151014 live-cd 
[3]:

zpool import -f rpool
beadm mount my_be /a
mv /a/platform/i86pc/boot_archive /a/platform/i86pc/boot_archive.bak
mv /a/platform/i86pc/amd64/boot_archive /a/platform/i86pc/amd64/boot_archive.bak
bootadm update-archive -v -R /a
zpool export -f rpool
init 6

But the boot failed with the same error [2]:

null path
krtld: failed to open ''

Does anyone has an idea how to fix this?

Best regards
Stefan

Screenshots of all errors could be found here:

[1] https://owncloud-002.qutic.com/index.php/s/dDODdEXmS1ebWwC
[2] https://owncloud-002.qutic.com/index.php/s/Oy2YfKyZcgfFhcl
[3] https://owncloud-002.qutic.com/index.php/s/4z2j5Od6s5YtxbG

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] OmniOS r151020 is now out!

[qutic development]

> Am 04.11.2016 um 16:26 schrieb Dan McDonald :
> 
> Happy upgrading!

Thanks Dan for this release and all the good work!

Do the LX Zones need an intel processor? Or will it work with amd too?

- Stefan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Tun/Tap device installed but not showing up on OmniOS

[qutic development]

Hi Andries,

> Am 24.10.2016 um 21:04 schrieb Andries Annema :
> 
> I have installed the tun/tap device within the global zone of a r151014 
> machine, but the /dev/tun and /dev/tap devices don't show up. What am I 
> missing here?

I use the following build script to get a working module for r151014:

https://github.com/jfqd/omnios-build/tree/151006/build/tuntap

- Stefan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] ZPOOL disk performance on Supermicro with LSI 9300-8i

[qutic development]

> Am 23.06.2016 um 01:06 schrieb Josh Barton :
> 
> Any ideas why the HP is so much faster? It just has one Smart Array 
> Controller which I didn’t think would be faster than JBOD

Could you please provide a few more information about the servers? CPU speed, 
cores, RAM, etc?

OmniOS tuned or all raw installations? All the same OmniOS version?

- Stefan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] kstat zone memory

[qutic development]

> Am 09.05.2016 um 03:33 schrieb Dan McDonald :
> 
> This also means it's available in the current stable, r151018.  You must be 
> running LTS, or old-stable (r151016), Stefan.

Thx Dan, 

running TLS on all boxes. So no free command in zones for now, but I did a pull 
request for the core dump issue:

https://github.com/wiedi/free/pull/1

- Stefan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Wiki is slightly broken

[qutic development]

> Am 25.04.2016 um 16:09 schrieb Eric Sproul :
> 
> If you are using a plugin like HTTPS Everywhere, you'll need to set an
> exception for http://omnios.omniti.com

Thanks Eric for your clarification.

Would it be possible to get the omnios page and all repos https only?

- Stefan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] https://pkg.omniti.com (was: SECURITY UPDATE FOR OpenSSL & Perl; plus other fixes)

[qutic development]

> Am 02.03.2016 um 12:52 schrieb Ben Summers :
> 
> I believe this was measured. pkg makes lots of small requests and doesn't 
> appear to be very clever with session management.
> 
> What results did you get when you benchmarked it?

Sorry my answer shouldn´t sound that harsh. We do have our own pkg-Server over 
https with a tls-terminating loadbalancer and request times are mostly under 
20ms.

>> Yes signed packages are fine, but not my case. As you now your county is 
>> taking a full take - on all they can get!
> Which country?

Great Britain

> I found OmniTI to be really open to making security improvements, and I'm 
> sure they would be very interested in learning about your specific concerns.

Thank you for pointing that out. I would be happy to get direct feedback.

- Stefan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] https://pkg.omniti.com (was: SECURITY UPDATE FOR OpenSSL & Perl; plus other fixes)

[qutic development]

> Am 02.03.2016 um 12:08 schrieb Ben Summers :
> 
> This was rejected previously due to the significant additional latency of 
> https.


Please, please do not spread myth from the last century. This is not true!
Add a proper tls-termination in front and you are good to go.

> Now that packages are signed properly, you don't need https to assure 
> integrity of the software.


Yes signed packages are fine, but not my case. As you now your county is taking 
a full take - on all they can get!

> If you wish to avoid disclosing your updates to passive observers, you could 
> use a local mirror.


Yes I could be, but that does not make the internet a better and more secure 
place!

- Stefan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] https://pkg.omniti.com (was: SECURITY UPDATE FOR OpenSSL & Perl; plus other fixes)

[qutic development]

Hi Dan,

> Am 01.03.2016 um 21:23 schrieb Dan McDonald :
> 
> We're working out the best course of forward action.  That people still *use* 
> SSLv2 post-2010 amazes me, but apparently I shouldn't be amazed.

I would like to connect via https to the omnios repos under pkg.omniti.com.

Would that be possible in the near future?

- Stefan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Extending the installer

[qutic development]

> Am 26.02.2016 um 23:53 schrieb PÁSZTOR György 
> :
> 
> I am not against improving the system.
> But this is a server distro. 

I am so happy that there is no "gui" in any way (like in debian) to configure 
an omnios server on startup.

If it is an extra script, which can be started manually, all would be fine.

- Stefan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] "pkg update" NOW for KVM security fixes!

[qutic development]

Hi Dan,

> "pkg update" is your friend for LTS (r151014) and Stable (r151016). 

will this fix be part of r151006 LTS as well?

- Stefan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Apache for OmniOS r151016?

[qutic development]

> The omniti-ms repository is the only IPS repository I have found with apache 
> in it.  SFE on SourceForge does not appear to have any spec files for apache. 
>  I assume that this is because SFE has primarily targeted Oracle Solaris and 
> OpenIndiana, which already come with apache.

You may wanna use our ips-server [1]. Build with and for r151006 LTS and tested 
successfully with r151014 as well. Build scripts could be found on github [2].

- Stefan

[1] https://ips.qutic.com
[2] https://github.com/jfqd/omnios-build
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss