From paladinemishakal at gmail.com Thu Nov 2 09:56:15 2017 From: paladinemishakal at gmail.com (Lawrence Giam) Date: Thu, 2 Nov 2017 17:56:15 +0800 Subject: [OmniOS-discuss] OmniOS R151014 hardware support Message-ID: Hi All, I know that OmniOS R151014 is old but I still have to use it. I am looking at running OmniOS on top of ESXi 5.5 or 6. I would like to know if illumos support the new Intel Xeon Scalable and also Intel C620 chipset? I am stuck at choosing either a Dell PowerEdge R530 or PowerEdge R740. Thanks & Regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: From danmcd at kebe.com Thu Nov 2 13:13:04 2017 From: danmcd at kebe.com (Dan McDonald) Date: Thu, 2 Nov 2017 09:13:04 -0400 Subject: [OmniOS-discuss] OmniOS R151014 hardware support In-Reply-To: References: Message-ID: > On Nov 2, 2017, at 5:56 AM, Lawrence Giam wrote: > > Hi All, > > I know that OmniOS R151014 is old but I still have to use it. I am looking at running OmniOS on top of ESXi 5.5 or 6. I have to ask, why do you have to use '014? What specific thing is tying you to it? I can't think of anything rational that isn't old hardware. > I would like to know if illumos support the new Intel Xeon Scalable and also Intel C620 chipset? I believe '014 supports the C620 chipset (620 is an older one, Sandy Bridge era, IIRC). > I am stuck at choosing either a Dell PowerEdge R530 or PowerEdge R740. R530 should be fine with '014 (modulo some possible edge-cases). Not sure about the R740 with 014, though. Seriously, if you're getting new HW, what's to stop you from upgrading OmniOS? Dan From danmcd at kebe.com Sat Nov 4 19:35:45 2017 From: danmcd at kebe.com (Dan McDonald) Date: Sat, 4 Nov 2017 15:35:45 -0400 Subject: [OmniOS-discuss] Just enough X? Message-ID: <8C1911E6-7922-4E87-B2F2-BCC8F73B4FCB@kebe.com> I apologize in advance for asking the community this in lieu of figuring it out myself. I wish to run "Just enough X" on OmniOS to run twm and xterm. Basically, I'd like console windows for all of my zones readily available. I used to do this when I ran OI on my home server, and occasionally I miss that functionality. Please PLEASE do not turn this into a thread about window managers and, "WTF do you want to use twm, Dan?" Any reasonable window manager can be swapped in for TWM, but I know TWM is simple and lightweight. I'm thinking it's either pkgsrc, or an alternate IPS publisher exists. Either works, but I'd like to hear from folks who've actually done it, if any exist. Thanks, Dan From bfriesen at simple.dallas.tx.us Sat Nov 4 20:04:47 2017 From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn) Date: Sat, 4 Nov 2017 15:04:47 -0500 (CDT) Subject: [OmniOS-discuss] Just enough X? In-Reply-To: <8C1911E6-7922-4E87-B2F2-BCC8F73B4FCB@kebe.com> References: <8C1911E6-7922-4E87-B2F2-BCC8F73B4FCB@kebe.com> Message-ID: On Sat, 4 Nov 2017, Dan McDonald wrote: > I apologize in advance for asking the community this in lieu of figuring it out myself. > > I wish to run "Just enough X" on OmniOS to run twm and xterm. > Basically, I'd like console windows for all of my zones readily > available. I used to do this when I ran OI on my home server, and > occasionally I miss that functionality. Please PLEASE do not turn > this into a thread about window managers and, "WTF do you want to > use twm, Dan?" Any reasonable window manager can be swapped in for > TWM, but I know TWM is simple and lightweight. > > I'm thinking it's either pkgsrc, or an alternate IPS publisher > exists. Either works, but I'd like to hear from folks who've > actually done it, if any exist. I have X11 (without twm installed) from pkgsrc which is enough to run and compile X11 programs. It is not clear to me if you want the server-side of X11, or want to use XDM, or if X11-client only is ok. These seem to be the applicable packages according to pkgin: GraphicsMagick-1.3.25 X application for displaying and manipulating images bigreqsproto-1.1.2 BigReqs extension headers from modular Xorg X11 libICE-1.0.9 Inter Client Exchange (ICE) library for X libSM-1.2.2 X Session Management Library libX11-1.6.4 Base X libraries from modular Xorg X11 libXau-1.0.8 Authorization Protocol for X from X.org libXaw-1.0.13 X Athena Widgets Library from modular Xorg X11 libXdamage-1.1.4 Xdamage extension (Library) libXdmcp-1.1.2 X Display Manager Control Protocol library from X.org libXext-1.3.3 X Extension library libXfixes-5.0.3 Xfixes library and extension of X RandR from modular X.org libXft-2.3.2 Library for configuring and customizing font access libXi-1.7.8 X Input extension library libXmu-1.1.2 X Miscellaneous Utilities library libXpm-3.5.12 X PixMap Library from modular Xorg X11 libXrender-0.9.10 X Render Library libXt-1.1.5 X Toolkit Intrinsics library libXxf86vm-1.1.4 Library for the XFree86-VidMode X extension libpciaccess-0.13.4nb1 PCI access utility library from X.org libxcb-1.12 X protocol C-language Binding motif-2.3.4nb7 LGPLed Motif toolkit for the X Window System videoproto-2.3.3 Video extension headers from modular X.org X11 xauth-1.0.9 X authentication utility xextproto-7.3.0 XExt extension headers from X.org xproto-7.0.31 X protocol and ancillary headers from Xorg X11 xterm-327 Latest terminal emulator for the X Window System I have seen screen shots of graphical native desktops running on "OmniOS" so some people have taken it that far. Bob -- Bob Friesenhahn bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From danmcd at kebe.com Sat Nov 4 20:14:40 2017 From: danmcd at kebe.com (Dan McDonald) Date: Sat, 4 Nov 2017 16:14:40 -0400 Subject: [OmniOS-discuss] Just enough X? In-Reply-To: References: <8C1911E6-7922-4E87-B2F2-BCC8F73B4FCB@kebe.com> Message-ID: <8FAF4459-F053-49FE-8D75-B1FF59D0E527@kebe.com> > On Nov 4, 2017, at 4:04 PM, Bob Friesenhahn wrote: > > I have X11 (without twm installed) from pkgsrc which is enough to run and compile X11 programs. It is not clear to me if you want the server-side of X11, or want to use XDM, or if X11-client only is ok. Sorry, I should've been clear. i want the server-side of X11. I have a 1920x1200 monitor KVM'ed to my home server. When I switch to it, I'd like to see all of the consoles for my zones (including global). Dan From tobi at oetiker.ch Mon Nov 6 10:55:05 2017 From: tobi at oetiker.ch (Tobias Oetiker) Date: Mon, 6 Nov 2017 11:55:05 +0100 (CET) Subject: [OmniOS-discuss] ANNOUNCEMENT: OmniOS Community Edition r151024 Message-ID: <341809893.242698.1509965705656.JavaMail.zimbra@oetiker.ch> OmniOS Community Edition R151024 -------------------------------- After 4 months of intense development, the OmniOS Community Edition Association is proud to announce the availability of the first Community release of OmniOS; version r151024. The release is on schedule (https://www.omniosce.org/schedule) coming 6 months after the final OmniTI release of OmniOS back in May. This new release adds several key improvements to the lx-zones facility allowing for lightweight virtualization of GNU/Linux in an illumos environment, better zone resource management, new hardware support and all the latest updates from upstream illumos; userland packages have also been brought right up-to-date. The underlying build system for OmniOS has been enhanced to make builds and ongoing maintenance easier; for example the total build time has been more than halved, and the addition of automated testing minimises the chance for regressions due to updates. Release notes for the new update are can be found at https://omniosce.org/releasenotes and upgrade instructions are at https://omniosce.org/upgrade The web site for OmniOS Community Edition has been updated with all the latest information, including new information for deployment, operation and development of OmniOS systems. OmniOS is an enterprise level operating system with long-term support and large release overlaps to allow for validation prior to deployment of new releases. Many organizations rely on OmniOS driven servers for their core storage and virtualization environments. As such they want to ensure the continued development and support of the OmniOS illumos distribution. It is now possible to support the work that goes into maintaining the OS by becoming an OmniOS patron, either with a recurring donation or a one time payment (https://omniosce.org/patron) About OmniOS - OmniOS is an Enterprise level illumos-based Operating System with superb lightweight virtualization support through zones as well as full hardware virtualization via integrated kvm support. Native ZFS support provides highly reliable storage options of nearly unlimited capacity. With dtrace it is possible to instrument virtually any part of the OS to provide highly precise debugging information to resolve performance issues and software failures. About OmniOS Community Edition Association - The OmniOS Community Edition Association has taken up development and care of OmniOS since Summer 2017 after OmniTI announced their withdrawal from the project. OmniOSce Association Aarweg 17, 4600 Olten, Switzerland info at omniosce.org From david.ledger at ivdcs.co.uk Mon Nov 6 11:53:37 2017 From: david.ledger at ivdcs.co.uk (David Ledger) Date: Mon, 06 Nov 2017 11:53:37 +0000 Subject: [OmniOS-discuss] Java on Intel/OmniOS Message-ID: I gather that Oracle have said that they will stop releasing Java for non-Sparc open-Solaris based systems. Does this affect many people? Is there anyone ?large? enough to influence this decision? (Like the US Navy was with HP and VMS). My interest is for continued use of Atlasssian products on OmniOS. David From jdg117 at elvis.arl.psu.edu Mon Nov 6 23:25:38 2017 From: jdg117 at elvis.arl.psu.edu (John D Groenveld) Date: Mon, 06 Nov 2017 18:25:38 -0500 Subject: [OmniOS-discuss] Java on Intel/OmniOS In-Reply-To: Your message of "Mon, 06 Nov 2017 11:53:37 GMT." References: Message-ID: <201711062325.vA6NPcAm011747@elvis.arl.psu.edu> In message , David Ledger wri tes: >Navy was with HP and VMS). My interest is for continued use of >Atlasssian products on OmniOS. Looks like someone has had success running Atlassian with OpenJDK: John groenveld at acm.org From mir at miras.org Mon Nov 6 23:55:41 2017 From: mir at miras.org (Michael Rasmussen) Date: Tue, 7 Nov 2017 00:55:41 +0100 Subject: [OmniOS-discuss] Java on Intel/OmniOS In-Reply-To: <201711062325.vA6NPcAm011747@elvis.arl.psu.edu> References: <201711062325.vA6NPcAm011747@elvis.arl.psu.edu> Message-ID: <20171107005541.5a90eefd@sleipner.datanom.net> On Mon, 06 Nov 2017 18:25:38 -0500 John D Groenveld wrote: > > Looks like someone has had success running Atlassian > with OpenJDK: > > At work we run our jira installation on RHEL 7 using the provided OpenJDK 8.0 from Redhat. Using OpenJDK is certified on all Atlassian products. -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- /usr/games/fortune -es says: Disease can be cured; fate is incurable. -- Chinese proverb -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From jdg117 at elvis.arl.psu.edu Tue Nov 7 00:50:01 2017 From: jdg117 at elvis.arl.psu.edu (John D Groenveld) Date: Mon, 06 Nov 2017 19:50:01 -0500 Subject: [OmniOS-discuss] Java on Intel/OmniOS In-Reply-To: Your message of "Tue, 07 Nov 2017 00:55:41 +0100." <20171107005541.5a90eefd@sleipner.datanom.net> References: <201711062325.vA6NPcAm011747@elvis.arl.psu.edu> <20171107005541.5a90eefd@sleipner.datanom.net> Message-ID: <201711070050.vA70o17a012107@elvis.arl.psu.edu> In message <20171107005541.5a90eefd at sleipner.datanom.net>, Michael Rasmussen wr ites: >At work we run our jira installation on RHEL 7 using the provided >OpenJDK 8.0 from Redhat. Using OpenJDK is certified on all Atlassian >products. Very cool. Anyone got a good OpenJDK 8 build recipe for OmniOS? John groenveld at acm.org From danmcd at kebe.com Tue Nov 7 15:11:07 2017 From: danmcd at kebe.com (Dan McDonald) Date: Tue, 7 Nov 2017 10:11:07 -0500 Subject: [OmniOS-discuss] PERL booleans? References: <201711070441.vA74fnQP006297@nowhere.kebe.com> Message-ID: <01134039-06DF-4C4B-813F-7883F78A2865@kebe.com> I upgraded my HDC to OmniOSce r151024, and did some nightly builds. After re-rewhacking PERL_VERS, I managed to get a MOSTLY clean build save for: > Begin forwarded message: > > From: Dan McDonald > Subject: Nightly i386 Build of illumos-gate Failed. > Date: November 6, 2017 at 11:41:49 PM EST > To: danmcd at nowhere.kebe.com > > > ==== Nightly distributed build started: Mon Nov 6 22:34:21 EST 2017 ==== > ==== Nightly distributed build completed: Mon Nov 6 23:41:49 EST 2017 ==== > > ==== Total build time ==== > > real 1:07:28 > > ==== Build environment ==== > > /usr/bin/uname > SunOS nowhere 5.11 omnios-r151024-c2a1589567 i86pc i386 i86pc > ==== Build warnings (non-DEBUG) ==== > > WARNING: The token "BOOL" is deprecated; use "BOOLEAN" instead > WARNING: The token "BOOL" is deprecated; use "BOOLEAN" instead > WARNING: The token "BOOL" is deprecated; use "BOOLEAN" instead > WARNING: The token "BOOL" is deprecated; use "BOOLEAN" instead > WARNING: The token "BOOL" is deprecated; use "BOOLEAN" instead > WARNING: The token "BOOL" is deprecated; use "BOOLEAN" instead > WARNING: The token "BOOL" is deprecated; use "BOOLEAN" instead > WARNING: The token "BOOL" is deprecated; use "BOOLEAN" instead > WARNING: The token "BOOL" is deprecated; use "BOOLEAN" instead > WARNING: The token "BOOL" is deprecated; use "BOOLEAN" instead > > ==== Elapsed build time (non-DEBUG) ==== The file $SRC/cmd/hal/hald/hald_marshal.list uses "BOOL" and under an updated glib (which is in the new OmniOS) should be "BOOLEAN". OmniOS has this fix now: commit f1311a377c43d15cc090269298266c6daacb47ac Author: citrus-it Date: Wed Sep 20 07:59:04 2017 +0000 Replace deprecated glob marshal BOOL with BOOLEAN I was curious if anyone who's not building on OmniOS has tried making this change? It should be a NOP on SmartOS because we don't use or even manifest hald. Thanks, Dan From peter.tribble at gmail.com Tue Nov 7 15:17:58 2017 From: peter.tribble at gmail.com (Peter Tribble) Date: Tue, 7 Nov 2017 15:17:58 +0000 Subject: [OmniOS-discuss] Fwd: Java on Intel/OmniOS In-Reply-To: References: <201711062325.vA6NPcAm011747@elvis.arl.psu.edu> <20171107005541.5a90eefd@sleipner.datanom.net> <201711070050.vA70o17a012107@elvis.arl.psu.edu> Message-ID: Forwrding to the list, as it doesn't seem to be setting reply-to. ---------- Forwarded message ---------- From: Peter Tribble Date: Tue, Nov 7, 2017 at 3:15 PM Subject: Re: [OmniOS-discuss] Java on Intel/OmniOS To: John D Groenveld On Tue, Nov 7, 2017 at 12:50 AM, John D Groenveld wrote: > In message <20171107005541.5a90eefd at sleipner.datanom.net>, Michael > Rasmussen wr > ites: > >At work we run our jira installation on RHEL 7 using the provided > >OpenJDK 8.0 from Redhat. Using OpenJDK is certified on all Atlassian > >products. > > Very cool. > Anyone got a good OpenJDK 8 build recipe for OmniOS? > I sent one to the list about a year ago. Here it is, updated for a more recent jdk update: So the following should work. Apart from the benefit in OmniOS having a current JDK, I wanted to be sure we could build from scratch just in case the Oracle binaries stopped working for any reason. This is on a vanilla r151014, updated to current. I'm Primary Administrator and the java bootstrap is the java7 that ships with omnios. If you build with Studio then it's a little easier as that's assumed to be the compiler on SunOS (OI have a patched openjdk that uses gcc). To get the sources: wget http://hg.openjdk.java.net/jdk8u/jdk8u/archive/jdk8u141-b15.tar.bz2 foreach file ( corba hotspot jaxp jaxws langtools jdk nashorn ) wget http://hg.openjdk.java.net/jdk8u/jdk8u/${file}/archive/ jdk8u141-b15.tar.bz2 -O ${file}-jdk8u141-b15.tar.bz2 end bzcat jdk8u141-b15.tar.bz2 | tar xf - mv jdk8u-jdk8u141-b15 openjdk8u141 foreach file ( corba hotspot jaxp jaxws langtools jdk nashorn ) bzcat ${file}-jdk8u141-b15.tar.bz2 | tar xf - mv ${file}-jdk8u141-b15 openjdk8u141/$file end Install the 64-bit pkgsrc bootstrap https://pkgsrc.joyent.com/install-on-illumos/ Install appropriate pkgsrc and omnios packages. There was a little trial and error to get this list... pfexec pkg install developer/build/gnu-make system/header system/header/header-audio developer/macro/cpp developer/object-file developer/gnu-binutils pfexec pkg install sunstudio12.1 pfexec /opt/local/bin/pkgin -y update pfexec /opt/local/bin/pkgin -y install libX11 libXrender renderproto libXext libXtst libXt xproto xextproto inputproto kbproto cups freetype2 Fix up some errant stupidities: pfexec mv /usr/bin/gobjcopy /usr/bin/not-gobjcopy-honestly pfexec ln -s /opt/local/include/X11 /usr/include pfexec ln -s /opt/local/lib/libX11.so* /usr/lib/amd64 pfexec ln -s /opt/local/lib/libXext.so* /usr/lib/amd64 pfexec ln -s /opt/local/lib/libXrender.so* /usr/lib/amd64 [Note: the gobjcopy thing is the only true magic here. You don't need the X11 symlinks for configure, but the build will fail as it doesn't seem to pass along the locations of the X11 libs and includes correctly.] cd to the openjdk8u141 directory from your download. env PATH=/opt/sunstudio12.1/bin:/usr/bin:/usr/sbin bash ./configure --with-milestone=fcs --with-update-version=141 --with-build-number=b15 --enable-unlimited-crypto --x-includes=/opt/local/include --x-libraries=/opt/local/lib --with-cups=/opt/local --with-freetype-include=/opt/local/include/freetype2 --with-freetype-lib=/opt/local/lib env PATH=/opt/sunstudio12.1/bin:/usr/bin:/usr/sbin gmake all and the built image is in build/solaris-x86_64-normal-server-release/images/j2sdk-image Then there's a little tinkering with sunpkcs11-solaris.cfg, and you'll need a full copy of cacerts, but otherwise you should be good to go. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From omnios at citrus-it.net Tue Nov 7 15:26:36 2017 From: omnios at citrus-it.net (Andy Fiddaman) Date: Tue, 7 Nov 2017 15:26:36 +0000 (UTC) Subject: [OmniOS-discuss] PERL booleans? In-Reply-To: <01134039-06DF-4C4B-813F-7883F78A2865@kebe.com> References: <201711070441.vA74fnQP006297@nowhere.kebe.com> <01134039-06DF-4C4B-813F-7883F78A2865@kebe.com> Message-ID: On Tue, 7 Nov 2017, Dan McDonald wrote: ; I upgraded my HDC to OmniOSce r151024, and did some nightly builds. After re-rewhacking PERL_VERS, I managed to get a MOSTLY clean build save for: ; ; > ==== Build warnings (non-DEBUG) ==== ; > ; > WARNING: The token "BOOL" is deprecated; use "BOOLEAN" instead ; ; The file $SRC/cmd/hal/hald/hald_marshal.list uses "BOOL" and under an updated glib (which is in the new OmniOS) should be "BOOLEAN". Note that BOOL was deprecated a long, long time ago in glib. I haven't been able to find an exact reference but it's showing up as deprecated in the documentation from 15 years ago. Glib recently rewrote the marshal generator in python and now it emits these deprecation warnings, hence the change in output. Andy -- Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and Wales | Company number 4899123 From omnios at citrus-it.net Tue Nov 7 16:00:58 2017 From: omnios at citrus-it.net (Andy Fiddaman) Date: Tue, 7 Nov 2017 16:00:58 +0000 (UTC) Subject: [OmniOS-discuss] PERL booleans? In-Reply-To: <3954E563-CA04-42ED-9BE4-4813580102C1@joyent.com> References: <201711070441.vA74fnQP006297@nowhere.kebe.com> <01134039-06DF-4C4B-813F-7883F78A2865@kebe.com> <3954E563-CA04-42ED-9BE4-4813580102C1@joyent.com> Message-ID: On Tue, 7 Nov 2017, Dan McDonald wrote: ; ; > On Nov 7, 2017, at 10:26 AM, Andy Fiddaman wrote: ; > ; > Note that BOOL was deprecated a long, long time ago in glib. I haven't been ; > able to find an exact reference but it's showing up as deprecated in the ; > documentation from 15 years ago. ; ; So it sounds like if this change is upstreamed nobody with older build environments will care? ; ; If I'm right, would you please file an illumos issue to push that upstream. I'll be reviewer #1. If nobody objects in the next day or two, I'll start the upstream process. It's on our upstream candidate list but the dust is still settling from the release. Thanks, Andy -- Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and Wales | Company number 4899123 From jstockett at molalla.com Wed Nov 8 19:46:04 2017 From: jstockett at molalla.com (Jeff Stockett) Date: Wed, 8 Nov 2017 19:46:04 +0000 Subject: [OmniOS-discuss] wiki problems at omniti Message-ID: <39463ca9b1b2437b934e80f4ed3ba3c3@molalla.com> I've got a few servers still running r151020 I was going to upgrade - but the wiki/download link seems to have a problem: Proxy Error The proxy server could not handle the request GET /wiki.php/Installation. Reason: Error during SSL Handshake with remote server Is this a permanent thing or just temporary? Is there a way to upgrade to omniosCE without first upgrading to R151022? -------------- next part -------------- An HTML attachment was scrubbed... URL: From alka at hfg-gmuend.de Wed Nov 8 20:00:19 2017 From: alka at hfg-gmuend.de (=?UTF-8?Q?G=c3=bcnther_Alka?=) Date: Wed, 8 Nov 2017 21:00:19 +0100 Subject: [OmniOS-discuss] wiki problems at omniti In-Reply-To: <39463ca9b1b2437b934e80f4ed3ba3c3@molalla.com> References: <39463ca9b1b2437b934e80f4ed3ba3c3@molalla.com> Message-ID: It seems that only the wiki is down, repos are working so you can update. You may do it according to my HowTo http://www.napp-it.org/doc/downloads/setup_napp-it_os.pdf chapter 2.2 Gea @napp-it.org Am 08.11.2017 um 20:46 schrieb Jeff Stockett: > > I?ve got a few servers still running r151020 I was going to upgrade ? > but the wiki/download link seems to have a problem: > > > Proxy Error > > The proxy server could not handle the request > /GET?/wiki.php/Installation > /. > > Reason: *Error during SSL Handshake with remote server* > > Is this a permanent thing or just temporary?? Is there a way to > upgrade to omniosCE without first upgrading to R151022? > > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From omnios at citrus-it.net Wed Nov 8 21:34:38 2017 From: omnios at citrus-it.net (Andy Fiddaman) Date: Wed, 8 Nov 2017 21:34:38 +0000 (UTC) Subject: [OmniOS-discuss] wiki problems at omniti In-Reply-To: <39463ca9b1b2437b934e80f4ed3ba3c3@molalla.com> References: <39463ca9b1b2437b934e80f4ed3ba3c3@molalla.com> Message-ID: On Wed, 8 Nov 2017, Jeff Stockett wrote: ; I've got a few servers still running r151020 I was going to upgrade - but the wiki/download link seems to have a problem: ; Proxy Error ; The proxy server could not handle the request GET /wiki.php/Installation. ; ; Reason: Error during SSL Handshake with remote server ; Is this a permanent thing or just temporary? Is there a way to upgrade to omniosCE without first upgrading to R151022? Our import of the OmniTI wiki is up at http://wiki.omniosce.org/ It's safest to go via OmniTI r151022 since that's the process that we have tested. Andy -- Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and Wales | Company number 4899123 From jstockett at molalla.com Wed Nov 8 23:59:22 2017 From: jstockett at molalla.com (Jeff Stockett) Date: Wed, 8 Nov 2017 23:59:22 +0000 Subject: [OmniOS-discuss] wiki problems at omniti In-Reply-To: References: <39463ca9b1b2437b934e80f4ed3ba3c3@molalla.com> Message-ID: <15f9e00fd9a1488f9f7cfc304f91fd65@molalla.com> Thanks Gea and Andy - combining bits and pieces from both resources I was able to get everything updated to r151022y. From: OmniOS-discuss [mailto:omnios-discuss-bounces at lists.omniti.com] On Behalf Of G?nther Alka Sent: Wednesday, November 8, 2017 12:00 PM To: omnios-discuss at lists.omniti.com Subject: Re: [OmniOS-discuss] wiki problems at omniti It seems that only the wiki is down, repos are working so you can update. You may do it according to my HowTo http://www.napp-it.org/doc/downloads/setup_napp-it_os.pdf chapter 2.2 Gea @napp-it.org Am 08.11.2017 um 20:46 schrieb Jeff Stockett: I've got a few servers still running r151020 I was going to upgrade - but the wiki/download link seems to have a problem: Proxy Error The proxy server could not handle the request GET /wiki.php/Installation. Reason: Error during SSL Handshake with remote server Is this a permanent thing or just temporary? Is there a way to upgrade to omniosCE without first upgrading to R151022? _______________________________________________ OmniOS-discuss mailing list OmniOS-discuss at lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From mailinglists at qutic.com Thu Nov 9 07:40:16 2017 From: mailinglists at qutic.com (qutic development) Date: Thu, 9 Nov 2017 08:40:16 +0100 Subject: [OmniOS-discuss] Supermicro X10DRi-T4+ usable with Illumos? Message-ID: <99E41DFF-F171-45B1-85DE-CC9114E1EFCC@qutic.com> 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 From paladinemishakal at gmail.com Thu Nov 9 08:59:56 2017 From: paladinemishakal at gmail.com (Lawrence Giam) Date: Thu, 9 Nov 2017 16:59:56 +0800 Subject: [OmniOS-discuss] Installation problem with OmniOSce R151022s Message-ID: Hi All, I am trying to install OmniOSce R151022s and am facing problem with the installer. In OmniOS R151014, I have already use this method to install OmniOS to a partition on a disk which is: 1. Boot to OmniOS R151014 installer ISO 2. Drop to shell and use format to create a partition on the target disk. 3. Exit the shell and use the installer menu to install OmniOS. In OmniOSce R151022s, I found that it doesn't work anymore so this is what I do 1. Boot to OmniOSce R151022s installer ISO, let it boot to the Multi User using the Loader. 2. At the OmniOSce installer menu, select number 3. 3. Use format to create a partition on the target disk. 4. Run the command: zpool create -f rpool c3t0d0p0. 5. Exit the shell and then select number 2 to install the OS to my preconfigured rpool. 6. The installer run and then show unable to activate boot environment. This is the messages that appears on the console: Welcome to the OmniOSce installation menu 1 Find disks, create rpool, and install OmniOSce 2 Install OmniOSce straight on to a preconfigured rpool 3 Shell (for manual rpool creation) 4 Terminal type (currently sun-color) 5 Reboot 6 Halt Please enter a number [1]: 3 To return to the main menu, exit the shell bash--4.4# zpool create -f rpool c3t0d0s0 cannot open '/dev/dsk/c3t0d0s0': I/O error bash--4.4# format Available Disk Selections: 0. c0t5000C500A54A1C52d0 /scsi_vhci/disk at g5000c500a54a1c52 .... 12. c3t0d0 /pci at 0,0/pci8086,7270 at 1f,2/disk at 0,0 13. c3t1d0 /pci at 0,0/pci8086,7270 at 1f,2/disk at 1,0 Specify disk (enter its number): 12 selecting c3t0d0 [disk formatted] No Solaris fdisk partition found. format> fdisk No fdisk table exists. The default partition for the disk is: a 100% "SOLARIS System" partition Type "y" to accept the default partition, otherwise type "n" to edit the partition table. n Total disk size is 39869 cylinders Cylinder size is 12544 (512 byte) blocks Cylinders Partition Status Type Start End Length % ========= ====== ============ ===== === ====== === 1 Active Solaris2 1 5581 5581 14 Enter Selection: 6 format> partition partition> print Current partition table (original): Total disk cylinders available: 5579 + 2 (reserved cylinders) Part Tag Flag Cylinders Size Blocks 0 unassigned wm 0 0 (0/0/0) 0 1 unassigned wm 0 0 (0/0/0) 0 2 backup wm 0 - 5578 33.37GB (5579/0/0) 69982976 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 unassigned wm 0 0 (0/0/0) 0 7 unassigned wm 0 0 (0/0/0) 0 8 boot wm 0 - 0 6.12MB (1/0/0) 12544 9 unassigned wm 0 0 (0/0/0) 0 partition> quit format> quit bash-4.4# zpool create -f rpool c3t0d0p0 bash-4.4# exit Welcome to the OmniOSce installation menu 1 Find disks, create rpool, and install OmniOSce 2 Install OmniOSce straight on to a preconfigured rpool 3 Shell (for manual rpool creation) 4 Terminal type (currently sun-color) 5 Reboot 6 Halt Please enter a number [1]: 2 Installing from ZFS image /root/*.zfs.bz2 Please enter a hostname or press RETURN if you want [omniosce]: sgarch01test Please enter a hostname or press RETURN if you want [sgarch01test]: Please identify a location so that time zone rules can be set correclty. Please select a continent or ocean. #? 5 <-- Asia #? 40 <-- Singapore The following information has been given: Singapore Therefore TZ='Singapore' will be used. Local time is now: Thu Nov 9 04:12:46 +08 2017 Universal Time is now: Wed Nov 8 20:12:46 UTC 2017 Is the above information OK? 1) Yes 2) No #? 1 <-- If select No, it will repeat the TZ selection Here is the TZ value again, this time on standard output: Singapore [2017/11/09-04:13:30] Receiving image: /root/kayak_r151022s.zfs.bz2 libshare SMF initialization problem: entity not found [2017/11/09-04:14:17] Cleaning up boot environment Mounted successfully on: '/mnt' [2017/11/09-04:14:17] Setting BE UUID: cbee238c-f5ec-c3cd-d787-c6603ed18ac1 [2017/11/09-04:14:17] Setting hostname: sgarch01test [2017/11/09-04:14:17] Setting timezone: Singapore [2017/11/09-04:14:17] Setting language: C [2017/11/09-04:14:17] Making boot environment bootable Unable to activate omnios. Error installing boot files. NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT rpool 238G 628M 237G - 0% 0% 1.00x ONLINE - c3t0d0p0 238G 628M 237G - 0% 0% BE Active Mountpoint Space Policy Created omnios R /mnt 626M static 2017-11-09 04:13 rpool now has a working and mounted boot environment, per above. Once back at the main menu, you can configure the initial system settings, reboot, or enter the shell to modify your new BE before its first boot. Press RETURN to go back to the menu: Questions: 1. The BSD Loader take more than 5 minutes to load, is this normal? The OmniOS installer does not take that long to boot. 2. How do we install OmniOSce to a partition on a disk instead of using the whole disk? Thanks & Regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: From omnios at citrus-it.net Thu Nov 9 10:41:49 2017 From: omnios at citrus-it.net (Andy Fiddaman) Date: Thu, 9 Nov 2017 10:41:49 +0000 (UTC) Subject: [OmniOS-discuss] Installation problem with OmniOSce R151022s In-Reply-To: References: Message-ID: On Thu, 9 Nov 2017, Lawrence Giam wrote: ; Hi All, ; ; I am trying to install OmniOSce R151022s and am facing problem with the ; installer. ; ... snip ... ; 4. Run the command: zpool create -f rpool c3t0d0p0. ... snip ... ; Questions: ; 1. The BSD Loader take more than 5 minutes to load, is this normal? The ; OmniOS installer does not take that long to boot. Not in my experience except from a USB drive. It is loading a lot of data since the miniroot now includes the ZFS stream. ; 2. How do we install OmniOSce to a partition on a disk instead of using the ; whole disk? You are confusing the partition table in the disk's MBR with the VTOC label used by Solaris. You should not be creating a zpool using the ...p0 device. Try this after having created the partition in fdisk: # Force re-genration of the VTOC. # This will result in slice 2 being set up properly to span the entire # partition. prtvtoc -h /dev/rdsk/c3t0d0s2 | awk '$1==8{print}' \ | fmthard -s - /dev/rdsk/c3t0d0s2 # Now add slice 0 covering the whole partition # The same as slice 2 except tagged as root and mountable. # (you can do this interactively via format or run this) fmthard -d `prtvtoc -h /dev/rdsk/c3t0d0s2 \ | awk '$1==2{printf("0:2:00:%d:%d\n",$4,$5)}'` /dev/rdsk/c3t0d0s2 # Check echo -e 'p\np' | format c3t0d0 You should see that slice 0 is flagged as root and spans the entire partition # Create zpool zpool create -f rpool c3t0d0s0 Proceed to option 2 in the menu as before. I've just tested this with OmniOSce r151024. HTH, Andy -- Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and Wales | Company number 4899123 From alka at hfg-gmuend.de Thu Nov 9 12:34:16 2017 From: alka at hfg-gmuend.de (Guenther Alka) Date: Thu, 9 Nov 2017 13:34:16 +0100 Subject: [OmniOS-discuss] Supermicro X10DRi-T4+ usable with Illumos? In-Reply-To: <99E41DFF-F171-45B1-85DE-CC9114E1EFCC@qutic.com> References: <99E41DFF-F171-45B1-85DE-CC9114E1EFCC@qutic.com> Message-ID: I have not tried thisvery special board but would expect X540: supported 6 x Sata by Intel PCH: supported 4 x Sata by SCU: *not supported* Gea @napp-it.org Am 09.11.2017 um 08:40 schrieb 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 at lists.omniti.com > http://lists.omniti.com/mailman -------------- next part -------------- An HTML attachment was scrubbed... URL: From peter.tribble at gmail.com Thu Nov 9 13:08:54 2017 From: peter.tribble at gmail.com (Peter Tribble) Date: Thu, 9 Nov 2017 13:08:54 +0000 Subject: [OmniOS-discuss] Supermicro X10DRi-T4+ usable with Illumos? In-Reply-To: <99E41DFF-F171-45B1-85DE-CC9114E1EFCC@qutic.com> References: <99E41DFF-F171-45B1-85DE-CC9114E1EFCC@qutic.com> Message-ID: On Thu, Nov 9, 2017 at 7:40 AM, qutic development wrote: > Hi, > > Is anyone using the Supermicro X10DRi-T4+ with the onboard sata for zfs > with SmartOS or OmniOSce? > We've got that board in production, works very well. We're not using the onboard SATA, though. Most chassis options have more drive slots than you can use with the onboard SATA, so we connect the drives via LSI cards. (We do have an X10SRi-F, which has the same C612 chipset, and use the onboard SATA for that.) The one thing to be careful of is the chassis, and whether it has expanders or whether it's direct attach. We have the SC216BAC-R920LPB, which is direct attach. And is the 10Gbit-Driver working with this board? > The driver works. We're only at 1G, as we don't need any more right now. But people on this list have reported using this at 10G. Overall, I would say this is a pretty good choice of board for illumos/omnios. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mailinglists at qutic.com Thu Nov 9 16:06:34 2017 From: mailinglists at qutic.com (qutic development) Date: Thu, 9 Nov 2017 17:06:34 +0100 Subject: [OmniOS-discuss] Supermicro X10DRi-T4+ usable with Illumos? In-Reply-To: References: <99E41DFF-F171-45B1-85DE-CC9114E1EFCC@qutic.com> Message-ID: <51239498-7865-425F-8BC6-0A7AEE067644@qutic.com> Hi Gea, Peter, thanks a lot for your for your input! So I can purchase the board without stomachache :) - Stefan From lists at mcintyreweb.com Fri Nov 10 05:07:48 2017 From: lists at mcintyreweb.com (Hugh McIntyre) Date: Thu, 9 Nov 2017 21:07:48 -0800 Subject: [OmniOS-discuss] r151104 to r151022 upgrade problem due to library/security/openssl Message-ID: <7362b16d-e53e-dbd4-eac9-26b75e462901@mcintyreweb.com> I have an old backup server at home which I'm trying to finally upgrade from r151014 to r151022 and then OmniOSCE. There are no zones. I have followed the instructions under https://www.omniosce.org/legacy/upgrade_to_r151022.html, including "pkg update" before switching publisher, then set-publisher to r151022, and removing all ms/omniti.com and perl.omniti.com packages after initial problems. But it still fails. In case it makes a difference, ca-bundle and SunSSH->OpenSSH were already upgraded some time ago. The blockage seems to be because of "library/security/openssl". I am mainly trying "pkg update" but if I try the entire incorporation the error message seems to say it's a failing because I already have a newer version of the openssl package (and the newer openssl package fails other dependencies such as SUNWcs): # pkg update -v pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z Creating Plan (Solver setup): | pkg update: No matching version of entire can be installed: Reject: pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z Reason: All versions matching 'require' dependency pkg:/library/security/openssl at 1.0.2,5.11-0.151022 are rejected Reject: pkg://omnios/library/security/openssl at 1.0.2.11,5.11-0.151022:20170510T232316Z Reason: Newer version pkg://omnios/library/security/openssl at 1.0.2.13,5.11-0.151014:20171107T161725Z is already installed Reject: pkg://omnios/library/security/openssl at 1.0.2.13,5.11-0.151014:20171107T161725Z Reason: All versions matching 'require' dependency pkg:/SUNWcs at 0.5.11,5.11-0.151014 are rejected Reject: pkg://omnios/SUNWcs at 0.5.11,5.11-0.151014:20170301T162827Z Reason: All versions matching 'require' dependency pkg:/library/security/trousers at 0.3.8,5.11-0.151014 are rejected Reject: pkg://omnios/library/security/trousers at 0.3.8,5.11-0.151014:20150505T003526Z Reason: All versions matching 'require' dependency pkg:/library/security/openssl at 1.0.2,5.11 are rejected Excluded by proposed incorporation 'incorporation/jeos/omnios-userland' Reject: pkg://omnios/library/security/trousers at 0.3.8,5.11-0.151022:20170510T212349Z Reason: All versions matching 'require' dependency pkg:/library/security/openssl at 1.0.2,5.11 are rejected Excluded by proposed incorporation 'consolidation/osnet/osnet-incorporation' Excluded by proposed incorporation 'incorporation/jeos/illumos-gate' Reject: pkg://omnios/SUNWcs at 0.5.11,5.11-0.151022:20170510T212740Z Reason: All versions matching 'require' dependency pkg:/library/security/trousers at 0.3.8,5.11-0.151022 are rejected Excluded by proposed incorporation 'incorporation/jeos/omnios-userland' Am I stuck needing a clean re-install, or is there a way to upgrade this box? Hugh. From omnios at citrus-it.net Fri Nov 10 10:46:23 2017 From: omnios at citrus-it.net (Andy Fiddaman) Date: Fri, 10 Nov 2017 10:46:23 +0000 (UTC) Subject: [OmniOS-discuss] r151104 to r151022 upgrade problem due to library/security/openssl In-Reply-To: <7362b16d-e53e-dbd4-eac9-26b75e462901@mcintyreweb.com> References: <7362b16d-e53e-dbd4-eac9-26b75e462901@mcintyreweb.com> Message-ID: On Thu, 9 Nov 2017, Hugh McIntyre wrote: ; ; I have an old backup server at home which I'm trying to finally upgrade from ; r151014 to r151022 and then OmniOSCE. There are no zones. ; ; I have followed the instructions under ; https://www.omniosce.org/legacy/upgrade_to_r151022.html, including "pkg ; update" before switching publisher, then set-publisher to r151022, and ; removing all ms/omniti.com and perl.omniti.com packages after initial ; problems. But it still fails. In case it makes a difference, ca-bundle and ; SunSSH->OpenSSH were already upgraded some time ago. ... snip ... ; ; Am I stuck needing a clean re-install, or is there a way to upgrade this box? The first thing I would try is uninstalling the entire and omnios-userland packages and then doing a full update. # pkg uninstall entire omnios-userland # pkg update --be-name=xxxxx # init 6 # pkg install entire omnios-userland Removing omnios-userland removes the specific version constraints but as it is a dependency of entire you need to (temporarily) remove both. The re-installation after reboot may fail depending on what the exact cause of your problem is in which case leave them uninstalled until you have completed the move to OmniOSce and then they should work. If you want to chat as you work through this, come on over to the lobby at https://gitter.im/omniosorg/Lobby Andy -- Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and Wales | Company number 4899123 From lists at mcintyreweb.com Fri Nov 10 21:31:16 2017 From: lists at mcintyreweb.com (lists at mcintyreweb.com) Date: Fri, 10 Nov 2017 13:31:16 -0800 Subject: [OmniOS-discuss] r151104 to r151022 upgrade problem due to library/security/openssl In-Reply-To: References: <7362b16d-e53e-dbd4-eac9-26b75e462901@mcintyreweb.com> Message-ID: <1510349476.1262081.1168647696.0FAB559B@webmail.messagingengine.com> OK, I will try this. Just so I understand though, I assume removing omnios-userland and entire only removes these top level incorporation meta-packages and not, for example, remove all of the actual user level commands in child packages? I guess I will have to find out if I then get package conflicts attempting to add the new entire/userland back in later. Thanks, Hugh. On Fri, Nov 10, 2017, at 02:46 AM, Andy Fiddaman wrote: > On Thu, 9 Nov 2017, Hugh McIntyre wrote: > > ; > ; I have an old backup server at home which I'm trying to finally upgrade > from > ; r151014 to r151022 and then OmniOSCE. There are no zones. > ; > ; I have followed the instructions under > ; https://www.omniosce.org/legacy/upgrade_to_r151022.html, including "pkg > ; update" before switching publisher, then set-publisher to r151022, and > ; removing all ms/omniti.com and perl.omniti.com packages after initial > ; problems. But it still fails. In case it makes a difference, > ca-bundle and > ; SunSSH->OpenSSH were already upgraded some time ago. > ... snip ... > ; > ; Am I stuck needing a clean re-install, or is there a way to upgrade > this box? > > The first thing I would try is uninstalling the entire and > omnios-userland > packages and then doing a full update. > > # pkg uninstall entire omnios-userland > # pkg update --be-name=xxxxx > # init 6 > # pkg install entire omnios-userland > > Removing omnios-userland removes the specific version constraints but as > it > is a dependency of entire you need to (temporarily) remove both. > > The re-installation after reboot may fail depending on what the exact > cause of your problem is in which case leave them uninstalled until you > have completed the move to OmniOSce and then they should work. > > If you want to chat as you work through this, come on over to the lobby > at https://gitter.im/omniosorg/Lobby > > Andy > > -- > Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk > Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ > Registered in England and Wales | Company number 4899123 > From lists at mcintyreweb.com Sat Nov 11 08:18:57 2017 From: lists at mcintyreweb.com (Hugh McIntyre) Date: Sat, 11 Nov 2017 00:18:57 -0800 Subject: [OmniOS-discuss] r151104 to r151022 upgrade problem due to library/security/openssl In-Reply-To: References: <7362b16d-e53e-dbd4-eac9-26b75e462901@mcintyreweb.com> Message-ID: <0f77125f-4ae0-41e7-9abe-95b2c9302da4@mcintyreweb.com> Thanks, this works. As you guessed, the first re-install after boot failed with conflicts, but after moving to OmniOSCE r151022 the second upgrade seems to have succeeded. Hugh. On 11/10/17 2:46 AM, Andy Fiddaman wrote: > On Thu, 9 Nov 2017, Hugh McIntyre wrote: > > ; > ; I have an old backup server at home which I'm trying to finally upgrade from > ; r151014 to r151022 and then OmniOSCE. There are no zones. > ; > ; I have followed the instructions under > ; https://www.omniosce.org/legacy/upgrade_to_r151022.html, including "pkg > ; update" before switching publisher, then set-publisher to r151022, and > ; removing all ms/omniti.com and perl.omniti.com packages after initial > ; problems. But it still fails. In case it makes a difference, ca-bundle and > ; SunSSH->OpenSSH were already upgraded some time ago. > ... snip ... > ; > ; Am I stuck needing a clean re-install, or is there a way to upgrade this box? > > The first thing I would try is uninstalling the entire and omnios-userland > packages and then doing a full update. > > # pkg uninstall entire omnios-userland > # pkg update --be-name=xxxxx > # init 6 > # pkg install entire omnios-userland > > Removing omnios-userland removes the specific version constraints but as it > is a dependency of entire you need to (temporarily) remove both. > > The re-installation after reboot may fail depending on what the exact > cause of your problem is in which case leave them uninstalled until you > have completed the move to OmniOSce and then they should work. > > If you want to chat as you work through this, come on over to the lobby > at https://gitter.im/omniosorg/Lobby > > Andy > From robert at omniti.com Sun Nov 12 18:08:46 2017 From: robert at omniti.com (Robert Treat) Date: Sun, 12 Nov 2017 13:08:46 -0500 Subject: [OmniOS-discuss] wiki problems at omniti In-Reply-To: <15f9e00fd9a1488f9f7cfc304f91fd65@molalla.com> References: <39463ca9b1b2437b934e80f4ed3ba3c3@molalla.com> <15f9e00fd9a1488f9f7cfc304f91fd65@molalla.com> Message-ID: Just to circle back, this should be fixed, but let us know if you see any other issues. Robert Treat On Wed, Nov 8, 2017 at 6:59 PM, Jeff Stockett wrote: > Thanks Gea and Andy ? combining bits and pieces from both resources I was > able to get everything updated to r151022y. > > > > *From:* OmniOS-discuss [mailto:omnios-discuss-bounces at lists.omniti.com] *On > Behalf Of *G?nther Alka > *Sent:* Wednesday, November 8, 2017 12:00 PM > *To:* omnios-discuss at lists.omniti.com > *Subject:* Re: [OmniOS-discuss] wiki problems at omniti > > > > It seems that only the wiki is down, repos are working > so you can update. > > You may do it according to my HowTo > http://www.napp-it.org/doc/downloads/setup_napp-it_os.pdf > chapter 2.2 > > Gea > @napp-it.org > > > > Am 08.11.2017 um 20:46 schrieb Jeff Stockett: > > I?ve got a few servers still running r151020 I was going to upgrade ? but > the wiki/download link seems to have a problem: > Proxy Error > > The proxy server could not handle the request *GET /wiki.php/Installation > *. > > Reason: *Error during SSL Handshake with remote server* > > Is this a permanent thing or just temporary? Is there a way to upgrade to > omniosCE without first upgrading to R151022? > > > > > _______________________________________________ > > OmniOS-discuss mailing list > > OmniOS-discuss at lists.omniti.com > > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > > > -- > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdg117 at elvis.arl.psu.edu Mon Nov 13 16:15:16 2017 From: jdg117 at elvis.arl.psu.edu (John D Groenveld) Date: Mon, 13 Nov 2017 11:15:16 -0500 Subject: [OmniOS-discuss] Fwd: Java on Intel/OmniOS In-Reply-To: Your message of "Tue, 07 Nov 2017 15:17:58 GMT." References: <201711062325.vA6NPcAm011747@elvis.arl.psu.edu> <20171107005541.5a90eefd@sleipner.datanom.net> <201711070050.vA70o17a012107@elvis.arl.psu.edu> Message-ID: <201711131615.vADGFGr0005737@elvis.arl.psu.edu> In message , Peter Tribble writes: >I sent one to the list about a year ago. Here it is, updated for a more >recent jdk update: Thank you. Its a bummer OpenJDK8 doesn't support headless builds as I have no need for the GUI, but I think I can get away with building with-x and then not deploying those dependencies. John groenveld at acm.org From stephan.budach at jvm.de Tue Nov 14 14:16:21 2017 From: stephan.budach at jvm.de (Stephan Budach) Date: Tue, 14 Nov 2017 15:16:21 +0100 (CET) Subject: [OmniOS-discuss] 2TB vs 4TB NVMe drives? In-Reply-To: <1962784242.3310.1510663907559.JavaMail.stephan.budach@stephan.budach.jvm.de> Message-ID: <1058615334.3360.1510668976623.JavaMail.stephan.budach@stephan.budach.jvm.de> Hi, we are planning on purchasing a Supermicro NVMe server with 48 .U2 slots. I intended to initially load it with 24 x 2TB DC P4500, leaving 24 slots empty. Now? I've been also offered an Intel chassis with only 24 slots and thus the offer also included the 4TB P4500s. Just without thinking very long, I instinctively wayed towards the 2TB drives, mainly for the reason, that should a drive really fail, I'd have of course a longer resilver at hand, usind 4TB NVMe drives. Which ones would you choose? Thanks, Stephan -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5546 bytes Desc: not available URL: From bfriesen at simple.dallas.tx.us Tue Nov 14 14:44:33 2017 From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn) Date: Tue, 14 Nov 2017 08:44:33 -0600 (CST) Subject: [OmniOS-discuss] 2TB vs 4TB NVMe drives? In-Reply-To: <1058615334.3360.1510668976623.JavaMail.stephan.budach@stephan.budach.jvm.de> References: <1058615334.3360.1510668976623.JavaMail.stephan.budach@stephan.budach.jvm.de> Message-ID: On Tue, 14 Nov 2017, Stephan Budach wrote: > we are planning on purchasing a Supermicro NVMe server with 48 .U2 > slots. I intended to initially load it with 24 x 2TB DC P4500, > leaving 24 slots empty. > > > Now? I've been also offered an Intel chassis with only 24 slots and > thus the offer also included the 4TB P4500s. Just without thinking > very long, I instinctively wayed towards the 2TB drives, mainly for > the reason, that should a drive really fail, I'd have of course a > longer resilver at hand, usind 4TB NVMe drives. > > > Which ones would you choose? Assuming that OmniOS works with these devices at all, from a power consumption, heat, complexity, and reliability standpoint, the larger devices appear to be a win (1/2 the power and 2X the MTBF for the same storage capacity). Resilver time is important but NVMe drives do not have the rotational latency and seek time issues of rotating media so resilver time should not be such an issue and there should only be a factor of 2 difference in resilver time. A consideration is what zfs pool configuration you would be putting on these drives. For throughput, more devices and more vdevs is better. It sounds like you would initially (and perhaps forever) have the same number of devices. Are you planning to use zfs mirrors, or raidz2/raidz3? What about dedicated zfs intent log devices? If synchronous writes are important to you, dedicated zfs intent log devices should still help with pool performance and long-term health by deferring writes to the vdevs so writes can be larger and more sequential. Bob -- Bob Friesenhahn bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From stephan.budach at jvm.de Tue Nov 14 15:54:04 2017 From: stephan.budach at jvm.de (Stephan Budach) Date: Tue, 14 Nov 2017 16:54:04 +0100 (CET) Subject: [OmniOS-discuss] 2TB vs 4TB NVMe drives? In-Reply-To: References: <1058615334.3360.1510668976623.JavaMail.stephan.budach@stephan.budach.jvm.de> Message-ID: <2146177661.3422.1510674841833.JavaMail.stephan.budach@stephan.budach.jvm.de> Hi Bob, ----- Urspr?ngliche Mail ----- > Von: "Bob Friesenhahn" > An: "Stephan Budach" > CC: "omnios-discuss" > Gesendet: Dienstag, 14. November 2017 15:44:33 > Betreff: Re: [OmniOS-discuss] 2TB vs 4TB NVMe drives? > > On Tue, 14 Nov 2017, Stephan Budach wrote: > > > we are planning on purchasing a Supermicro NVMe server with 48 .U2 > > slots. I intended to initially load it with 24 x 2TB DC P4500, > > leaving 24 slots empty. > > > > > > Now? I've been also offered an Intel chassis with only 24 slots and > > thus the offer also included the 4TB P4500s. Just without thinking > > very long, I instinctively wayed towards the 2TB drives, mainly for > > the reason, that should a drive really fail, I'd have of course a > > longer resilver at hand, usind 4TB NVMe drives. > > > > > > Which ones would you choose? > > Assuming that OmniOS works with these devices at all, from a power > consumption, heat, complexity, and reliability standpoint, the larger > devices appear to be a win (1/2 the power and 2X the MTBF for the > same > storage capacity). Resilver time is important but NVMe drives do not > have the rotational latency and seek time issues of rotating media so > resilver time should not be such an issue and there should only be a > factor of 2 difference in resilver time. > > A consideration is what zfs pool configuration you would be putting > on > these drives. For throughput, more devices and more vdevs is better. > It sounds like you would initially (and perhaps forever) have the > same > number of devices. > > Are you planning to use zfs mirrors, or raidz2/raidz3? What about > dedicated zfs intent log devices? If synchronous writes are > important > to you, dedicated zfs intent log devices should still help with pool > performance and long-term health by deferring writes to the vdevs so > writes can be larger and more sequential. > Afaik, all the hardware is in the Illumos HCL, so this config should run fine under omniOS. This setup is intended to replace my current ZFS-HA storage pools and it will be configured with zfs mirrors only, where the mirror vdevs will be built on iSCSI LUNs from "raw" devices, as much as you can get raw devices served by COMSTAR. So, we will have these boxes serving each NVMe as a LUN to the RSF-1 nodes, which then will host 2 zpools of 6 mirror vdevs each. From thsoe zpools, the RSF-1 nodes will serve NFS to our Oracle VM cluster servers. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5546 bytes Desc: not available URL: From jstockett at molalla.com Tue Nov 14 16:20:21 2017 From: jstockett at molalla.com (Jeff Stockett) Date: Tue, 14 Nov 2017 16:20:21 +0000 Subject: [OmniOS-discuss] 2TB vs 4TB NVMe drives? In-Reply-To: <1058615334.3360.1510668976623.JavaMail.stephan.budach@stephan.budach.jvm.de> References: <1962784242.3310.1510663907559.JavaMail.stephan.budach@stephan.budach.jvm.de> <1058615334.3360.1510668976623.JavaMail.stephan.budach@stephan.budach.jvm.de> Message-ID: Yes ? definitely let the list know how/if it all works ? I?ve been eyeballing the EPYC based TN70A-B8026 which is 2U and 24 hotswap NVMe that are direct attached. I think the supermicro ones are all going to be via PLX PCI expanders since Intel doesn?t have enough PCI express lanes even in 2P for 24x more less 48x not that it probably matters that much. FWIW, Phoronix reviewed this Tyan system, and couldn?t get OmniOS (r151122CE I think) to see the nvme drives ? but I don?t know how hard he tried nor do I know what kind of drives they sent him for review. https://www.phoronix.com/scan.php?page=article&item=amd-epyc-bsd&num=1 From: OmniOS-discuss [mailto:omnios-discuss-bounces at lists.omniti.com] On Behalf Of Stephan Budach Sent: Tuesday, November 14, 2017 6:16 AM To: omnios-discuss Subject: [OmniOS-discuss] 2TB vs 4TB NVMe drives? Hi, we are planning on purchasing a Supermicro NVMe server with 48 .U2 slots. I intended to initially load it with 24 x 2TB DC P4500, leaving 24 slots empty. Now? I've been also offered an Intel chassis with only 24 slots and thus the offer also included the 4TB P4500s. Just without thinking very long, I instinctively wayed towards the 2TB drives, mainly for the reason, that should a drive really fail, I'd have of course a longer resilver at hand, usind 4TB NVMe drives. Which ones would you choose? Thanks, Stephan -------------- next part -------------- An HTML attachment was scrubbed... URL: From paladinemishakal at gmail.com Wed Nov 15 04:39:27 2017 From: paladinemishakal at gmail.com (Lawrence Giam) Date: Wed, 15 Nov 2017 12:39:27 +0800 Subject: [OmniOS-discuss] Installation problem with OmniOSce R151022s In-Reply-To: References: Message-ID: Hi Andy, Thanks for the help, I got it to work as instructed. Cheers!!! On Thu, Nov 9, 2017 at 6:41 PM, Andy Fiddaman wrote: > On Thu, 9 Nov 2017, Lawrence Giam wrote: > > ; Hi All, > ; > ; I am trying to install OmniOSce R151022s and am facing problem with the > ; installer. > ; > ... snip ... > ; 4. Run the command: zpool create -f rpool c3t0d0p0. > ... snip ... > ; Questions: > > ; 1. The BSD Loader take more than 5 minutes to load, is this normal? The > ; OmniOS installer does not take that long to boot. > > Not in my experience except from a USB drive. It is loading a lot of data > since the miniroot now includes the ZFS stream. > > ; 2. How do we install OmniOSce to a partition on a disk instead of using > the > ; whole disk? > > You are confusing the partition table in the disk's MBR with the VTOC label > used by Solaris. You should not be creating a zpool using the ...p0 device. > > Try this after having created the partition in fdisk: > > # Force re-genration of the VTOC. > # This will result in slice 2 being set up properly to span the entire > # partition. > prtvtoc -h /dev/rdsk/c3t0d0s2 | awk '$1==8{print}' \ > | fmthard -s - /dev/rdsk/c3t0d0s2 > > # Now add slice 0 covering the whole partition > # The same as slice 2 except tagged as root and mountable. > # (you can do this interactively via format or run this) > > fmthard -d `prtvtoc -h /dev/rdsk/c3t0d0s2 \ > | awk '$1==2{printf("0:2:00:%d:%d\n",$4,$5)}'` /dev/rdsk/c3t0d0s2 > > # Check > echo -e 'p\np' | format c3t0d0 > > You should see that slice 0 is flagged as root and spans the entire > partition > > # Create zpool > zpool create -f rpool c3t0d0s0 > > Proceed to option 2 in the menu as before. > > I've just tested this with OmniOSce r151024. > > HTH, > > Andy > > -- > Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk > Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ > Registered in England and Wales | Company number 4899123 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From natxo.asenjo at gmail.com Sun Nov 19 18:17:32 2017 From: natxo.asenjo at gmail.com (Natxo Asenjo) Date: Sun, 19 Nov 2017 19:17:32 +0100 Subject: [OmniOS-discuss] crash after upgrading to 151024 Message-ID: hi, I upgraded our home nas from the old stable ce to the new stable one. The process went ok, but after rebooting it has crashed twice: this is the info I can see with fmpdump: # fmdump -Vp -u 95f72642-1099-ca7a-f1ca-952f0f5a9906 TIME UUID SUNW-MSG-ID Nov 19 2017 18:01:08.485243000 95f72642-1099-ca7a-f1ca-952f0f5a9906 SUNOS-8000-KL TIME CLASS ENA Nov 19 18:01:08.3130 ireport.os.sunos.panic.dump_available 0x0000000000000000 Nov 19 18:00:19.3332 ireport.os.sunos.panic.dump_pending_on_device 0x0000000000000000 nvlist version: 0 version = 0x0 class = list.suspect uuid = 95f72642-1099-ca7a-f1ca-952f0f5a9906 code = SUNOS-8000-KL diag-time = 1511110868 390045 de = fmd:///module/software-diagnosis fault-list-sz = 0x1 fault-list = (array of embedded nvlists) (start fault-list[0]) nvlist version: 0 version = 0x0 class = defect.sunos.kernel.panic certainty = 0x64 asru = sw:///:path=/var/crash/unknown/.95f72642-1099-ca7a-f1ca-952f0f5a9906 resource = sw:///:path=/var/crash/unknown/.95f72642-1099-ca7a-f1ca-952f0f5a9906 savecore-succcess = 1 dump-dir = /var/crash/unknown dump-files = vmdump.1 os-instance-uuid = 95f72642-1099-ca7a-f1ca-952f0f5a9906 panicstr = BAD TRAP: type=e (#pf Page fault) rp=ffffff0016065cc0 addr=0 occurred in module "unix" due to a NULL pointer dereference panicstack = unix:die+df () | unix:trap+e08 () | unix:_cmntrap+e6 () | unix:strncpy+28 () | lx_brand:lx_prctl+48a () | lx_brand:lx_syscall_enter+16f () | unix:brand_sys_syscall+1bd () | crashtime = 1511110541 panic-time = Sun Nov 19 17:55:41 2017 CET (end fault-list[0]) fault-status = 0x1 severity = Major __ttl = 0x1 __tod = 0x5a11b8d4 0x1cec3878 The first time it crashed after re-attaching a ipkg zone, and the second time after I started a vmware vm hosted in a nfs share on the omnios host. I have the dumped crash files, I do not know if anyone could take a look at them. This is a microserver HP proliant N40L, and has been rock stable for 4 years, so maybe the hardware is at fault, obviously. I have not started any ipkg zone or any vm and now the host is running stable. Thanks in advance. -- Groeten, natxo -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdg117 at elvis.arl.psu.edu Sun Nov 19 18:35:01 2017 From: jdg117 at elvis.arl.psu.edu (John D Groenveld) Date: Sun, 19 Nov 2017 13:35:01 -0500 Subject: [OmniOS-discuss] crash after upgrading to 151024 In-Reply-To: Your message of "Sun, 19 Nov 2017 19:17:32 +0100." References: Message-ID: <201711191835.vAJIZ1nj012025@elvis.arl.psu.edu> In message , Natxo Asenjo writes: >The first time it crashed after re-attaching a ipkg zone, and the second >time after I started a vmware vm hosted in a nfs share on the omnios host. If the crashdumps are inconsistent, then I suspect hardware issue, possibly an invasion of dusty bunnies. Break out the compressed air and reseat all of your socketed connections. John groenveld at acm.org From omnios at citrus-it.net Sun Nov 19 21:22:07 2017 From: omnios at citrus-it.net (Andy Fiddaman) Date: Sun, 19 Nov 2017 21:22:07 +0000 (UTC) Subject: [OmniOS-discuss] crash after upgrading to 151024 In-Reply-To: References: Message-ID: On Sun, 19 Nov 2017, Natxo Asenjo wrote: ; hi, ; ; I upgraded our home nas from the old stable ce to the new stable one. The ; process went ok, but after rebooting it has crashed twice: ; ; panicstack = unix:die+df () | unix:trap+e08 () | ; unix:_cmntrap+e6 () | unix:strncpy+28 () | lx_brand:lx_prctl+48a () | ; lx_brand:lx_syscall_enter+16f () | unix:brand_sys_syscall+1bd () | This looks like a bug in the lx support in r151024 with a commit that came in fairly recently (so wouldn't have been in r151022). Send me the crash dump as per the private email I've sent you but I think I can see where this is (and the problem) just from the above. The crash dump will confirm and then we'll get it fixed in the next r151024 update. Andy -- Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and Wales | Company number 4899123 From serge.fonville at gmail.com Mon Nov 20 17:26:01 2017 From: serge.fonville at gmail.com (Serge Fonville) Date: Mon, 20 Nov 2017 18:26:01 +0100 Subject: [OmniOS-discuss] ERROR: Could not update attaching zone Message-ID: Hi, When I tried to attach a zone I got the following errors: > zoneadm -z web01 attach > Log File: /var/tmp/web01.attach_log.olaaFy Attach Path: /export/zones/web01/root Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 Installing: Using pre-existing data in zonepath Cache: Using /var/pkg/publisher. Updating non-global zone: Output follows Evaluation: Packages in zone web01 are out of sync with the global zone. To proceed, retry with the -u flag. Result: Attach Failed. With the log file containing: [Mon Nov 20 18:02:28 CET 2017] Log File: /var/tmp/web01.attach_log.olaaFy [Mon Nov 20 18:02:32 CET 2017] Attach Path: /export/zones/web01/root [Mon Nov 20 18:02:32 CET 2017] Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 [Mon Nov 20 18:02:32 CET 2017] existing [Mon Nov 20 18:02:32 CET 2017] Installing: Using pre-existing data in zonepath [Mon Nov 20 18:02:32 CET 2017] Sanity Check: Passed. Looks like an OpenSolaris system. pkg: Search performance is degraded. Run 'pkg rebuild-index' to improve search speed. [Mon Nov 20 18:02:39 CET 2017] Cache: Using /var/pkg/publisher. [Mon Nov 20 18:02:39 CET 2017] Updating non-global zone: Output follows pkg install: Invalid child image publisher configuration. Child image publisher configuration must be a superset of the parent image publisher configuration. Please update the child publisher configuration to match the parent. If the child image is a zone this can be done automatically by detaching and attaching the zone. The parent image has the following enabled publishers: PUBLISHER 0: omnios PUBLISHER 1: ms.omniti.com The child image has the following enabled publishers: PUBLISHER 0: omnios [Mon Nov 20 18:02:42 CET 2017] Evaluation: Packages in zone web01 are out of sync with the global zone. To proceed, retry with the -u flag. [Mon Nov 20 18:02:44 CET 2017] Result: Attach Failed. So I try to run it with -u > zoneadm -z web01 attach -u > Log File: /var/tmp/web01.attach_log.TNaqaR Attach Path: /export/zones/web01/root Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 Installing: Using pre-existing data in zonepath Cache: Using /var/pkg/publisher. Updating non-global zone: Output follows ERROR: Could not update attaching zone Result: Attach Failed. With the log file containing: [Mon Nov 20 18:20:23 CET 2017] Log File: /var/tmp/web01.attach_log.TNaqaR [Mon Nov 20 18:20:27 CET 2017] Attach Path: /export/zones/web01/root [Mon Nov 20 18:20:27 CET 2017] Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 [Mon Nov 20 18:20:27 CET 2017] existing [Mon Nov 20 18:20:27 CET 2017] Installing: Using pre-existing data in zonepath [Mon Nov 20 18:20:27 CET 2017] Sanity Check: Passed. Looks like an OpenSolaris system. [Mon Nov 20 18:20:31 CET 2017] Cache: Using /var/pkg/publisher. [Mon Nov 20 18:20:31 CET 2017] Updating non-global zone: Output follows pkg install: Invalid child image publisher configuration. Child image publisher configuration must be a superset of the parent image publisher configuration. Please update the child publisher configuration to match the parent. If the child image is a zone this can be done automatically by detaching and attaching the zone. The parent image has the following enabled publishers: PUBLISHER 0: omnios PUBLISHER 1: ms.omniti.com The child image has the following enabled publishers: PUBLISHER 0: omnios [Mon Nov 20 18:20:35 CET 2017] ERROR: Could not update attaching zone [Mon Nov 20 18:20:36 CET 2017] Result: Attach Failed. On global zone: > pkg publisher > PUBLISHER TYPE STATUS P LOCATION omnios origin online F https://pkg.omniosce.org/r151022/core/ Any help in resolving this greatly appreciated!! Thanks in advance!! Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl -------------- next part -------------- An HTML attachment was scrubbed... URL: From lkateley at kateley.com Mon Nov 20 17:39:40 2017 From: lkateley at kateley.com (Linda Kateley) Date: Mon, 20 Nov 2017 11:39:40 -0600 Subject: [OmniOS-discuss] ERROR: Could not update attaching zone In-Reply-To: References: Message-ID: <2ade304c-8833-5d41-1f36-ba25bed87f3c@kateley.com> I had that recently... just made sure I patched both sides identically before moving On 11/20/17 11:26 AM, Serge Fonville wrote: > Hi, > > When I tried to attach a zone I got the following errors: > > zoneadm -z web01 attach > > Log File: /var/tmp/web01.attach_log.olaaFy > ?????????????? Attach Path: /export/zones/web01/root > ??????? Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 > > ??????????????? Installing: Using pre-existing data in zonepath > ???????????????????? Cache: Using /var/pkg/publisher. > ? Updating non-global zone: Output follows > > ??????????????? Evaluation: Packages in zone web01 are out of sync > with the global zone. To proceed, retry with the -u flag. > ??????????????????? Result: Attach Failed. > With the log file containing: > [Mon Nov 20 18:02:28 CET 2017] Log File: /var/tmp/web01.attach_log.olaaFy > [Mon Nov 20 18:02:32 CET 2017]??????????????? Attach Path: > /export/zones/web01/root > [Mon Nov 20 18:02:32 CET 2017]???????? Attach ZFS Dataset: > rpool/export/zones/web01/ROOT/zbe-9 > > [Mon Nov 20 18:02:32 CET 2017] existing > [Mon Nov 20 18:02:32 CET 2017]???????????????? Installing: Using > pre-existing data in zonepath > [Mon Nov 20 18:02:32 CET 2017]?? Sanity Check: Passed. Looks like an > OpenSolaris system. > pkg: Search performance is degraded. > Run 'pkg rebuild-index' to improve search speed. > [Mon Nov 20 18:02:39 CET 2017]????????????????????? Cache: Using > /var/pkg/publisher. > [Mon Nov 20 18:02:39 CET 2017]?? Updating non-global zone: Output follows > > > pkg install: Invalid child image publisher configuration. Child image > publisher > configuration must be a superset of the parent image publisher > configuration. > Please update the child publisher configuration to match the parent.? > If the > child image is a zone this can be done automatically by detaching and > attaching the zone. > > The parent image has the following enabled publishers: > ??? PUBLISHER 0: omnios > ??? PUBLISHER 1: ms.omniti.com > > The child image has the following enabled publishers: > ??? PUBLISHER 0: omnios > [Mon Nov 20 18:02:42 CET 2017] > ??????????????? Evaluation: Packages in zone web01 are out of sync > with the global zone. To proceed, retry with the -u flag. > [Mon Nov 20 18:02:44 CET 2017]???????????????????? Result: Attach Failed. > > So I try to run? it with -u > > zoneadm -z web01 attach -u > > ?Log File: /var/tmp/web01.attach_log.TNaqaR > ?????????????? Attach Path: /export/zones/web01/root > ??????? Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 > > ??????????????? Installing: Using pre-existing data in zonepath > ???????????????????? Cache: Using /var/pkg/publisher. > ? Updating non-global zone: Output follows > ERROR: Could not update attaching zone > ??????????????????? Result: Attach Failed. > > With the log file containing: > [Mon Nov 20 18:20:23 CET 2017] Log File: /var/tmp/web01.attach_log.TNaqaR > [Mon Nov 20 18:20:27 CET 2017]??????????????? Attach Path: > /export/zones/web01/root > [Mon Nov 20 18:20:27 CET 2017]???????? Attach ZFS Dataset: > rpool/export/zones/web01/ROOT/zbe-9 > > [Mon Nov 20 18:20:27 CET 2017] existing > [Mon Nov 20 18:20:27 CET 2017]???????????????? Installing: Using > pre-existing data in zonepath > [Mon Nov 20 18:20:27 CET 2017]?? Sanity Check: Passed. Looks like an > OpenSolaris system. > [Mon Nov 20 18:20:31 CET 2017]????????????????????? Cache: Using > /var/pkg/publisher. > [Mon Nov 20 18:20:31 CET 2017]?? Updating non-global zone: Output follows > > > pkg install: Invalid child image publisher configuration. Child image > publisher > configuration must be a superset of the parent image publisher > configuration. > Please update the child publisher configuration to match the parent.? > If the > child image is a zone this can be done automatically by detaching and > attaching the zone. > > The parent image has the following enabled publishers: > ??? PUBLISHER 0: omnios > ??? PUBLISHER 1: ms.omniti.com > > The child image has the following enabled publishers: > ??? PUBLISHER 0: omnios > [Mon Nov 20 18:20:35 CET 2017] ERROR: Could not update attaching zone > [Mon Nov 20 18:20:36 CET 2017]???????????????????? Result: Attach Failed. > > On global zone: > > pkg publisher > > PUBLISHER?????????????????? TYPE???? STATUS P LOCATION > omnios????????????????????? origin?? online F > https://pkg.omniosce.org/r151022/core/ > > Any help in resolving this greatly appreciated!! > > Thanks in advance!! > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From serge.fonville at gmail.com Mon Nov 20 17:55:18 2017 From: serge.fonville at gmail.com (Serge Fonville) Date: Mon, 20 Nov 2017 18:55:18 +0100 Subject: [OmniOS-discuss] ERROR: Could not update attaching zone In-Reply-To: <2ade304c-8833-5d41-1f36-ba25bed87f3c@kateley.com> References: <2ade304c-8833-5d41-1f36-ba25bed87f3c@kateley.com> Message-ID: So, that means you know how to solve it :D!! Awesome, your input is greatly appreciated!!! Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-20 18:39 GMT+01:00 Linda Kateley : > I had that recently... just made sure I patched both sides identically > before moving > > On 11/20/17 11:26 AM, Serge Fonville wrote: > > Hi, > > When I tried to attach a zone I got the following errors: > >> zoneadm -z web01 attach >> > Log File: /var/tmp/web01.attach_log.olaaFy > Attach Path: /export/zones/web01/root > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 > > Installing: Using pre-existing data in zonepath > Cache: Using /var/pkg/publisher. > Updating non-global zone: Output follows > > Evaluation: Packages in zone web01 are out of sync with > the global zone. To proceed, retry with the -u flag. > Result: Attach Failed. > With the log file containing: > [Mon Nov 20 18:02:28 CET 2017] Log File: /var/tmp/web01.attach_log.olaaFy > [Mon Nov 20 18:02:32 CET 2017] Attach Path: > /export/zones/web01/root > [Mon Nov 20 18:02:32 CET 2017] Attach ZFS Dataset: > rpool/export/zones/web01/ROOT/zbe-9 > > [Mon Nov 20 18:02:32 CET 2017] existing > [Mon Nov 20 18:02:32 CET 2017] Installing: Using > pre-existing data in zonepath > [Mon Nov 20 18:02:32 CET 2017] Sanity Check: Passed. Looks like an > OpenSolaris system. > pkg: Search performance is degraded. > Run 'pkg rebuild-index' to improve search speed. > [Mon Nov 20 18:02:39 CET 2017] Cache: Using > /var/pkg/publisher. > [Mon Nov 20 18:02:39 CET 2017] Updating non-global zone: Output follows > > > pkg install: Invalid child image publisher configuration. Child image > publisher > configuration must be a superset of the parent image publisher > configuration. > Please update the child publisher configuration to match the parent. If > the > child image is a zone this can be done automatically by detaching and > attaching the zone. > > The parent image has the following enabled publishers: > PUBLISHER 0: omnios > PUBLISHER 1: ms.omniti.com > > The child image has the following enabled publishers: > PUBLISHER 0: omnios > [Mon Nov 20 18:02:42 CET 2017] > Evaluation: Packages in zone web01 are out of sync with > the global zone. To proceed, retry with the -u flag. > [Mon Nov 20 18:02:44 CET 2017] Result: Attach Failed. > > So I try to run it with -u > >> zoneadm -z web01 attach -u >> > Log File: /var/tmp/web01.attach_log.TNaqaR > Attach Path: /export/zones/web01/root > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 > > Installing: Using pre-existing data in zonepath > Cache: Using /var/pkg/publisher. > Updating non-global zone: Output follows > ERROR: Could not update attaching zone > Result: Attach Failed. > > With the log file containing: > [Mon Nov 20 18:20:23 CET 2017] Log File: /var/tmp/web01.attach_log.TNaqaR > [Mon Nov 20 18:20:27 CET 2017] Attach Path: > /export/zones/web01/root > [Mon Nov 20 18:20:27 CET 2017] Attach ZFS Dataset: > rpool/export/zones/web01/ROOT/zbe-9 > > [Mon Nov 20 18:20:27 CET 2017] existing > [Mon Nov 20 18:20:27 CET 2017] Installing: Using > pre-existing data in zonepath > [Mon Nov 20 18:20:27 CET 2017] Sanity Check: Passed. Looks like an > OpenSolaris system. > [Mon Nov 20 18:20:31 CET 2017] Cache: Using > /var/pkg/publisher. > [Mon Nov 20 18:20:31 CET 2017] Updating non-global zone: Output follows > > > pkg install: Invalid child image publisher configuration. Child image > publisher > configuration must be a superset of the parent image publisher > configuration. > Please update the child publisher configuration to match the parent. If > the > child image is a zone this can be done automatically by detaching and > attaching the zone. > > The parent image has the following enabled publishers: > PUBLISHER 0: omnios > PUBLISHER 1: ms.omniti.com > > The child image has the following enabled publishers: > PUBLISHER 0: omnios > [Mon Nov 20 18:20:35 CET 2017] ERROR: Could not update attaching zone > [Mon Nov 20 18:20:36 CET 2017] Result: Attach Failed. > > On global zone: > >> pkg publisher >> > PUBLISHER TYPE STATUS P LOCATION > omnios origin online F https://pkg.omniosce.org/ > r151022/core/ > > Any help in resolving this greatly appreciated!! > > Thanks in advance!! > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > > _______________________________________________ > OmniOS-discuss mailing listOmniOS-discuss at lists.omniti.comhttp://lists.omniti.com/mailman/listinfo/omnios-discuss > > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hasslerd at gmx.li Mon Nov 20 18:02:38 2017 From: hasslerd at gmx.li (Dominik Hassler) Date: Mon, 20 Nov 2017 19:02:38 +0100 Subject: [OmniOS-discuss] ERROR: Could not update attaching zone In-Reply-To: References: Message-ID: <13fd6003-e2de-4cc7-dbba-309e063cc31e@gmx.li> > Child image publisher configuration must be a superset of the parent image publisher configuration. your NGZ is lacking the ms.omniti.com publisher which you have set for the GZ. after doing a: # pkg -R /export/zones/web01/root set-publisher -g http://pkg.omniti.com/omniti-ms/ ms.omniti.com attaching the zone should work. On 11/20/2017 06:26 PM, Serge Fonville wrote: > Hi, > > When I tried to attach a zone I got the following errors: > > zoneadm -z web01 attach > > Log File: /var/tmp/web01.attach_log.olaaFy > ?????????????? Attach Path: /export/zones/web01/root > ??????? Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 > > ??????????????? Installing: Using pre-existing data in zonepath > ???????????????????? Cache: Using /var/pkg/publisher. > ? Updating non-global zone: Output follows > > ??????????????? Evaluation: Packages in zone web01 are out of sync with > the global zone. To proceed, retry with the -u flag. > ??????????????????? Result: Attach Failed. > With the log file containing: > [Mon Nov 20 18:02:28 CET 2017] Log File: /var/tmp/web01.attach_log.olaaFy > [Mon Nov 20 18:02:32 CET 2017]??????????????? Attach Path: > /export/zones/web01/root > [Mon Nov 20 18:02:32 CET 2017]???????? Attach ZFS Dataset: > rpool/export/zones/web01/ROOT/zbe-9 > > [Mon Nov 20 18:02:32 CET 2017] existing > [Mon Nov 20 18:02:32 CET 2017]???????????????? Installing: Using > pre-existing data in zonepath > [Mon Nov 20 18:02:32 CET 2017]?? Sanity Check: Passed.? Looks like an > OpenSolaris system. > pkg: Search performance is degraded. > Run 'pkg rebuild-index' to improve search speed. > [Mon Nov 20 18:02:39 CET 2017]????????????????????? Cache: Using > /var/pkg/publisher. > [Mon Nov 20 18:02:39 CET 2017]?? Updating non-global zone: Output follows > > > pkg install: Invalid child image publisher configuration.? Child image > publisher > configuration must be a superset of the parent image publisher > configuration. > Please update the child publisher configuration to match the parent.? If the > child image is a zone this can be done automatically by detaching and > attaching the zone. > > The parent image has the following enabled publishers: > ??? PUBLISHER 0: omnios > ??? PUBLISHER 1: ms.omniti.com > > The child image has the following enabled publishers: > ??? PUBLISHER 0: omnios > [Mon Nov 20 18:02:42 CET 2017] > ??????????????? Evaluation: Packages in zone web01 are out of sync with > the global zone. To proceed, retry with the -u flag. > [Mon Nov 20 18:02:44 CET 2017]???????????????????? Result: Attach Failed. > > So I try to run? it with -u > > zoneadm -z web01 attach -u > > ?Log File: /var/tmp/web01.attach_log.TNaqaR > ?????????????? Attach Path: /export/zones/web01/root > ??????? Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 > > ??????????????? Installing: Using pre-existing data in zonepath > ???????????????????? Cache: Using /var/pkg/publisher. > ? Updating non-global zone: Output follows > ERROR: Could not update attaching zone > ??????????????????? Result: Attach Failed. > > With the log file containing: > [Mon Nov 20 18:20:23 CET 2017] Log File: /var/tmp/web01.attach_log.TNaqaR > [Mon Nov 20 18:20:27 CET 2017]??????????????? Attach Path: > /export/zones/web01/root > [Mon Nov 20 18:20:27 CET 2017]???????? Attach ZFS Dataset: > rpool/export/zones/web01/ROOT/zbe-9 > > [Mon Nov 20 18:20:27 CET 2017] existing > [Mon Nov 20 18:20:27 CET 2017]???????????????? Installing: Using > pre-existing data in zonepath > [Mon Nov 20 18:20:27 CET 2017]?? Sanity Check: Passed.? Looks like an > OpenSolaris system. > [Mon Nov 20 18:20:31 CET 2017]????????????????????? Cache: Using > /var/pkg/publisher. > [Mon Nov 20 18:20:31 CET 2017]?? Updating non-global zone: Output follows > > > pkg install: Invalid child image publisher configuration.? Child image > publisher > configuration must be a superset of the parent image publisher > configuration. > Please update the child publisher configuration to match the parent.? If the > child image is a zone this can be done automatically by detaching and > attaching the zone. > > The parent image has the following enabled publishers: > ??? PUBLISHER 0: omnios > ??? PUBLISHER 1: ms.omniti.com > > The child image has the following enabled publishers: > ??? PUBLISHER 0: omnios > [Mon Nov 20 18:20:35 CET 2017] ERROR: Could not update attaching zone > [Mon Nov 20 18:20:36 CET 2017]???????????????????? Result: Attach Failed. > > On global zone: > > pkg publisher > > PUBLISHER?????????????????? TYPE???? STATUS P LOCATION > omnios????????????????????? origin?? online F > https://pkg.omniosce.org/r151022/core/ > > Any help in resolving this greatly appreciated!! > > Thanks in advance!! > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > From serge.fonville at gmail.com Tue Nov 21 05:10:07 2017 From: serge.fonville at gmail.com (Serge Fonville) Date: Tue, 21 Nov 2017 06:10:07 +0100 Subject: [OmniOS-discuss] ERROR: Could not update attaching zone In-Reply-To: <13fd6003-e2de-4cc7-dbba-309e063cc31e@gmx.li> References: <13fd6003-e2de-4cc7-dbba-309e063cc31e@gmx.li> Message-ID: So how do I see it in the GZ, because pkg publisher does not output it when I execute it on the GZ? Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-20 19:02 GMT+01:00 Dominik Hassler : > > Child image publisher configuration must be a superset of the parent > image publisher configuration. > > your NGZ is lacking the ms.omniti.com publisher which you have set for > the GZ. > > after doing a: > # pkg -R /export/zones/web01/root set-publisher -g > http://pkg.omniti.com/omniti-ms/ ms.omniti.com > > attaching the zone should work. > > On 11/20/2017 06:26 PM, Serge Fonville wrote: > > Hi, > > > > When I tried to attach a zone I got the following errors: > > > > zoneadm -z web01 attach > > > > Log File: /var/tmp/web01.attach_log.olaaFy > > Attach Path: /export/zones/web01/root > > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 > > > > Installing: Using pre-existing data in zonepath > > Cache: Using /var/pkg/publisher. > > Updating non-global zone: Output follows > > > > Evaluation: Packages in zone web01 are out of sync with > > the global zone. To proceed, retry with the -u flag. > > Result: Attach Failed. > > With the log file containing: > > [Mon Nov 20 18:02:28 CET 2017] Log File: /var/tmp/web01.attach_log. > olaaFy > > [Mon Nov 20 18:02:32 CET 2017] Attach Path: > > /export/zones/web01/root > > [Mon Nov 20 18:02:32 CET 2017] Attach ZFS Dataset: > > rpool/export/zones/web01/ROOT/zbe-9 > > > > [Mon Nov 20 18:02:32 CET 2017] existing > > [Mon Nov 20 18:02:32 CET 2017] Installing: Using > > pre-existing data in zonepath > > [Mon Nov 20 18:02:32 CET 2017] Sanity Check: Passed. Looks like an > > OpenSolaris system. > > pkg: Search performance is degraded. > > Run 'pkg rebuild-index' to improve search speed. > > [Mon Nov 20 18:02:39 CET 2017] Cache: Using > > /var/pkg/publisher. > > [Mon Nov 20 18:02:39 CET 2017] Updating non-global zone: Output follows > > > > > > pkg install: Invalid child image publisher configuration. Child image > > publisher > > configuration must be a superset of the parent image publisher > > configuration. > > Please update the child publisher configuration to match the parent. If > the > > child image is a zone this can be done automatically by detaching and > > attaching the zone. > > > > The parent image has the following enabled publishers: > > PUBLISHER 0: omnios > > PUBLISHER 1: ms.omniti.com > > > > The child image has the following enabled publishers: > > PUBLISHER 0: omnios > > [Mon Nov 20 18:02:42 CET 2017] > > Evaluation: Packages in zone web01 are out of sync with > > the global zone. To proceed, retry with the -u flag. > > [Mon Nov 20 18:02:44 CET 2017] Result: Attach Failed. > > > > So I try to run it with -u > > > > zoneadm -z web01 attach -u > > > > Log File: /var/tmp/web01.attach_log.TNaqaR > > Attach Path: /export/zones/web01/root > > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 > > > > Installing: Using pre-existing data in zonepath > > Cache: Using /var/pkg/publisher. > > Updating non-global zone: Output follows > > ERROR: Could not update attaching zone > > Result: Attach Failed. > > > > With the log file containing: > > [Mon Nov 20 18:20:23 CET 2017] Log File: /var/tmp/web01.attach_log. > TNaqaR > > [Mon Nov 20 18:20:27 CET 2017] Attach Path: > > /export/zones/web01/root > > [Mon Nov 20 18:20:27 CET 2017] Attach ZFS Dataset: > > rpool/export/zones/web01/ROOT/zbe-9 > > > > [Mon Nov 20 18:20:27 CET 2017] existing > > [Mon Nov 20 18:20:27 CET 2017] Installing: Using > > pre-existing data in zonepath > > [Mon Nov 20 18:20:27 CET 2017] Sanity Check: Passed. Looks like an > > OpenSolaris system. > > [Mon Nov 20 18:20:31 CET 2017] Cache: Using > > /var/pkg/publisher. > > [Mon Nov 20 18:20:31 CET 2017] Updating non-global zone: Output follows > > > > > > pkg install: Invalid child image publisher configuration. Child image > > publisher > > configuration must be a superset of the parent image publisher > > configuration. > > Please update the child publisher configuration to match the parent. If > the > > child image is a zone this can be done automatically by detaching and > > attaching the zone. > > > > The parent image has the following enabled publishers: > > PUBLISHER 0: omnios > > PUBLISHER 1: ms.omniti.com > > > > The child image has the following enabled publishers: > > PUBLISHER 0: omnios > > [Mon Nov 20 18:20:35 CET 2017] ERROR: Could not update attaching zone > > [Mon Nov 20 18:20:36 CET 2017] Result: Attach Failed. > > > > On global zone: > > > > pkg publisher > > > > PUBLISHER TYPE STATUS P LOCATION > > omnios origin online F > > https://pkg.omniosce.org/r151022/core/ > > > > Any help in resolving this greatly appreciated!! > > > > Thanks in advance!! > > > > Kind regards/met vriendelijke groet, > > > > Serge Fonville > > > > http://www.sergefonville.nl > > > > > > _______________________________________________ > > OmniOS-discuss mailing list > > OmniOS-discuss at lists.omniti.com > > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From serge.fonville at gmail.com Tue Nov 21 05:11:44 2017 From: serge.fonville at gmail.com (Serge Fonville) Date: Tue, 21 Nov 2017 06:11:44 +0100 Subject: [OmniOS-discuss] ERROR: Could not update attaching zone In-Reply-To: References: <13fd6003-e2de-4cc7-dbba-309e063cc31e@gmx.li> Message-ID: Also, since I had to remove it when I upgraded, I was under the impression it was gone everywhere, since pkg publisher does not show it on any other zone (including the GZ). Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-21 6:10 GMT+01:00 Serge Fonville : > So how do I see it in the GZ, because pkg publisher does not output it > when I execute it on the GZ? > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > 2017-11-20 19:02 GMT+01:00 Dominik Hassler : > >> > Child image publisher configuration must be a superset of the parent >> image publisher configuration. >> >> your NGZ is lacking the ms.omniti.com publisher which you have set for >> the GZ. >> >> after doing a: >> # pkg -R /export/zones/web01/root set-publisher -g >> http://pkg.omniti.com/omniti-ms/ ms.omniti.com >> >> attaching the zone should work. >> >> On 11/20/2017 06:26 PM, Serge Fonville wrote: >> > Hi, >> > >> > When I tried to attach a zone I got the following errors: >> > >> > zoneadm -z web01 attach >> > >> > Log File: /var/tmp/web01.attach_log.olaaFy >> > Attach Path: /export/zones/web01/root >> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >> > >> > Installing: Using pre-existing data in zonepath >> > Cache: Using /var/pkg/publisher. >> > Updating non-global zone: Output follows >> > >> > Evaluation: Packages in zone web01 are out of sync with >> > the global zone. To proceed, retry with the -u flag. >> > Result: Attach Failed. >> > With the log file containing: >> > [Mon Nov 20 18:02:28 CET 2017] Log File: /var/tmp/web01.attach_log.olaa >> Fy >> > [Mon Nov 20 18:02:32 CET 2017] Attach Path: >> > /export/zones/web01/root >> > [Mon Nov 20 18:02:32 CET 2017] Attach ZFS Dataset: >> > rpool/export/zones/web01/ROOT/zbe-9 >> > >> > [Mon Nov 20 18:02:32 CET 2017] existing >> > [Mon Nov 20 18:02:32 CET 2017] Installing: Using >> > pre-existing data in zonepath >> > [Mon Nov 20 18:02:32 CET 2017] Sanity Check: Passed. Looks like an >> > OpenSolaris system. >> > pkg: Search performance is degraded. >> > Run 'pkg rebuild-index' to improve search speed. >> > [Mon Nov 20 18:02:39 CET 2017] Cache: Using >> > /var/pkg/publisher. >> > [Mon Nov 20 18:02:39 CET 2017] Updating non-global zone: Output >> follows >> > >> > >> > pkg install: Invalid child image publisher configuration. Child image >> > publisher >> > configuration must be a superset of the parent image publisher >> > configuration. >> > Please update the child publisher configuration to match the parent. >> If the >> > child image is a zone this can be done automatically by detaching and >> > attaching the zone. >> > >> > The parent image has the following enabled publishers: >> > PUBLISHER 0: omnios >> > PUBLISHER 1: ms.omniti.com >> > >> > The child image has the following enabled publishers: >> > PUBLISHER 0: omnios >> > [Mon Nov 20 18:02:42 CET 2017] >> > Evaluation: Packages in zone web01 are out of sync with >> > the global zone. To proceed, retry with the -u flag. >> > [Mon Nov 20 18:02:44 CET 2017] Result: Attach >> Failed. >> > >> > So I try to run it with -u >> > >> > zoneadm -z web01 attach -u >> > >> > Log File: /var/tmp/web01.attach_log.TNaqaR >> > Attach Path: /export/zones/web01/root >> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >> > >> > Installing: Using pre-existing data in zonepath >> > Cache: Using /var/pkg/publisher. >> > Updating non-global zone: Output follows >> > ERROR: Could not update attaching zone >> > Result: Attach Failed. >> > >> > With the log file containing: >> > [Mon Nov 20 18:20:23 CET 2017] Log File: /var/tmp/web01.attach_log.TNaq >> aR >> > [Mon Nov 20 18:20:27 CET 2017] Attach Path: >> > /export/zones/web01/root >> > [Mon Nov 20 18:20:27 CET 2017] Attach ZFS Dataset: >> > rpool/export/zones/web01/ROOT/zbe-9 >> > >> > [Mon Nov 20 18:20:27 CET 2017] existing >> > [Mon Nov 20 18:20:27 CET 2017] Installing: Using >> > pre-existing data in zonepath >> > [Mon Nov 20 18:20:27 CET 2017] Sanity Check: Passed. Looks like an >> > OpenSolaris system. >> > [Mon Nov 20 18:20:31 CET 2017] Cache: Using >> > /var/pkg/publisher. >> > [Mon Nov 20 18:20:31 CET 2017] Updating non-global zone: Output >> follows >> > >> > >> > pkg install: Invalid child image publisher configuration. Child image >> > publisher >> > configuration must be a superset of the parent image publisher >> > configuration. >> > Please update the child publisher configuration to match the parent. >> If the >> > child image is a zone this can be done automatically by detaching and >> > attaching the zone. >> > >> > The parent image has the following enabled publishers: >> > PUBLISHER 0: omnios >> > PUBLISHER 1: ms.omniti.com >> > >> > The child image has the following enabled publishers: >> > PUBLISHER 0: omnios >> > [Mon Nov 20 18:20:35 CET 2017] ERROR: Could not update attaching zone >> > [Mon Nov 20 18:20:36 CET 2017] Result: Attach >> Failed. >> > >> > On global zone: >> > >> > pkg publisher >> > >> > PUBLISHER TYPE STATUS P LOCATION >> > omnios origin online F >> > https://pkg.omniosce.org/r151022/core/ >> > >> > Any help in resolving this greatly appreciated!! >> > >> > Thanks in advance!! >> > >> > Kind regards/met vriendelijke groet, >> > >> > Serge Fonville >> > >> > http://www.sergefonville.nl >> > >> > >> > _______________________________________________ >> > OmniOS-discuss mailing list >> > OmniOS-discuss at lists.omniti.com >> > http://lists.omniti.com/mailman/listinfo/omnios-discuss >> > >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From serge.fonville at gmail.com Tue Nov 21 06:08:37 2017 From: serge.fonville at gmail.com (Serge Fonville) Date: Tue, 21 Nov 2017 07:08:37 +0100 Subject: [OmniOS-discuss] ERROR: Could not update attaching zone In-Reply-To: References: <13fd6003-e2de-4cc7-dbba-309e063cc31e@gmx.li> Message-ID: After having rebooted the server, I am now no longer able to logon to the server, the console shows messages it cannot mount the filesystem. because its directory is not empty, since the zone is in configured/detached state, how do I tell the system not to try to mount it? Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-21 6:11 GMT+01:00 Serge Fonville : > Also, since I had to remove it when I upgraded, I was under the impression > it was gone everywhere, since pkg publisher does not show it on any other > zone (including the GZ). > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > 2017-11-21 6:10 GMT+01:00 Serge Fonville : > >> So how do I see it in the GZ, because pkg publisher does not output it >> when I execute it on the GZ? >> >> Kind regards/met vriendelijke groet, >> >> Serge Fonville >> >> http://www.sergefonville.nl >> >> 2017-11-20 19:02 GMT+01:00 Dominik Hassler : >> >>> > Child image publisher configuration must be a superset of the parent >>> image publisher configuration. >>> >>> your NGZ is lacking the ms.omniti.com publisher which you have set for >>> the GZ. >>> >>> after doing a: >>> # pkg -R /export/zones/web01/root set-publisher -g >>> http://pkg.omniti.com/omniti-ms/ ms.omniti.com >>> >>> attaching the zone should work. >>> >>> On 11/20/2017 06:26 PM, Serge Fonville wrote: >>> > Hi, >>> > >>> > When I tried to attach a zone I got the following errors: >>> > >>> > zoneadm -z web01 attach >>> > >>> > Log File: /var/tmp/web01.attach_log.olaaFy >>> > Attach Path: /export/zones/web01/root >>> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >>> > >>> > Installing: Using pre-existing data in zonepath >>> > Cache: Using /var/pkg/publisher. >>> > Updating non-global zone: Output follows >>> > >>> > Evaluation: Packages in zone web01 are out of sync with >>> > the global zone. To proceed, retry with the -u flag. >>> > Result: Attach Failed. >>> > With the log file containing: >>> > [Mon Nov 20 18:02:28 CET 2017] Log File: /var/tmp/web01.attach_log.olaa >>> Fy >>> > [Mon Nov 20 18:02:32 CET 2017] Attach Path: >>> > /export/zones/web01/root >>> > [Mon Nov 20 18:02:32 CET 2017] Attach ZFS Dataset: >>> > rpool/export/zones/web01/ROOT/zbe-9 >>> > >>> > [Mon Nov 20 18:02:32 CET 2017] existing >>> > [Mon Nov 20 18:02:32 CET 2017] Installing: Using >>> > pre-existing data in zonepath >>> > [Mon Nov 20 18:02:32 CET 2017] Sanity Check: Passed. Looks like an >>> > OpenSolaris system. >>> > pkg: Search performance is degraded. >>> > Run 'pkg rebuild-index' to improve search speed. >>> > [Mon Nov 20 18:02:39 CET 2017] Cache: Using >>> > /var/pkg/publisher. >>> > [Mon Nov 20 18:02:39 CET 2017] Updating non-global zone: Output >>> follows >>> > >>> > >>> > pkg install: Invalid child image publisher configuration. Child image >>> > publisher >>> > configuration must be a superset of the parent image publisher >>> > configuration. >>> > Please update the child publisher configuration to match the parent. >>> If the >>> > child image is a zone this can be done automatically by detaching and >>> > attaching the zone. >>> > >>> > The parent image has the following enabled publishers: >>> > PUBLISHER 0: omnios >>> > PUBLISHER 1: ms.omniti.com >>> > >>> > The child image has the following enabled publishers: >>> > PUBLISHER 0: omnios >>> > [Mon Nov 20 18:02:42 CET 2017] >>> > Evaluation: Packages in zone web01 are out of sync with >>> > the global zone. To proceed, retry with the -u flag. >>> > [Mon Nov 20 18:02:44 CET 2017] Result: Attach >>> Failed. >>> > >>> > So I try to run it with -u >>> > >>> > zoneadm -z web01 attach -u >>> > >>> > Log File: /var/tmp/web01.attach_log.TNaqaR >>> > Attach Path: /export/zones/web01/root >>> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >>> > >>> > Installing: Using pre-existing data in zonepath >>> > Cache: Using /var/pkg/publisher. >>> > Updating non-global zone: Output follows >>> > ERROR: Could not update attaching zone >>> > Result: Attach Failed. >>> > >>> > With the log file containing: >>> > [Mon Nov 20 18:20:23 CET 2017] Log File: /var/tmp/web01.attach_log.TNaq >>> aR >>> > [Mon Nov 20 18:20:27 CET 2017] Attach Path: >>> > /export/zones/web01/root >>> > [Mon Nov 20 18:20:27 CET 2017] Attach ZFS Dataset: >>> > rpool/export/zones/web01/ROOT/zbe-9 >>> > >>> > [Mon Nov 20 18:20:27 CET 2017] existing >>> > [Mon Nov 20 18:20:27 CET 2017] Installing: Using >>> > pre-existing data in zonepath >>> > [Mon Nov 20 18:20:27 CET 2017] Sanity Check: Passed. Looks like an >>> > OpenSolaris system. >>> > [Mon Nov 20 18:20:31 CET 2017] Cache: Using >>> > /var/pkg/publisher. >>> > [Mon Nov 20 18:20:31 CET 2017] Updating non-global zone: Output >>> follows >>> > >>> > >>> > pkg install: Invalid child image publisher configuration. Child image >>> > publisher >>> > configuration must be a superset of the parent image publisher >>> > configuration. >>> > Please update the child publisher configuration to match the parent. >>> If the >>> > child image is a zone this can be done automatically by detaching and >>> > attaching the zone. >>> > >>> > The parent image has the following enabled publishers: >>> > PUBLISHER 0: omnios >>> > PUBLISHER 1: ms.omniti.com >>> > >>> > The child image has the following enabled publishers: >>> > PUBLISHER 0: omnios >>> > [Mon Nov 20 18:20:35 CET 2017] ERROR: Could not update attaching zone >>> > [Mon Nov 20 18:20:36 CET 2017] Result: Attach >>> Failed. >>> > >>> > On global zone: >>> > >>> > pkg publisher >>> > >>> > PUBLISHER TYPE STATUS P LOCATION >>> > omnios origin online F >>> > https://pkg.omniosce.org/r151022/core/ >>> > >>> > Any help in resolving this greatly appreciated!! >>> > >>> > Thanks in advance!! >>> > >>> > Kind regards/met vriendelijke groet, >>> > >>> > Serge Fonville >>> > >>> > http://www.sergefonville.nl >>> > >>> > >>> > _______________________________________________ >>> > OmniOS-discuss mailing list >>> > OmniOS-discuss at lists.omniti.com >>> > http://lists.omniti.com/mailman/listinfo/omnios-discuss >>> > >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From serge.fonville at gmail.com Tue Nov 21 06:54:06 2017 From: serge.fonville at gmail.com (Serge Fonville) Date: Tue, 21 Nov 2017 07:54:06 +0100 Subject: [OmniOS-discuss] ERROR: Could not update attaching zone In-Reply-To: References: <13fd6003-e2de-4cc7-dbba-309e063cc31e@gmx.li> Message-ID: After having updated the canmount property to noauto of the filesystem, the system now boots again. Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-21 7:08 GMT+01:00 Serge Fonville : > After having rebooted the server, I am now no longer able to logon to the > server, the console shows messages it cannot mount the filesystem. because > its directory is not empty, since the zone is in configured/detached state, > how do I tell the system not to try to mount it? > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > 2017-11-21 6:11 GMT+01:00 Serge Fonville : > >> Also, since I had to remove it when I upgraded, I was under the >> impression it was gone everywhere, since pkg publisher does not show it on >> any other zone (including the GZ). >> >> Kind regards/met vriendelijke groet, >> >> Serge Fonville >> >> http://www.sergefonville.nl >> >> 2017-11-21 6:10 GMT+01:00 Serge Fonville : >> >>> So how do I see it in the GZ, because pkg publisher does not output it >>> when I execute it on the GZ? >>> >>> Kind regards/met vriendelijke groet, >>> >>> Serge Fonville >>> >>> http://www.sergefonville.nl >>> >>> 2017-11-20 19:02 GMT+01:00 Dominik Hassler : >>> >>>> > Child image publisher configuration must be a superset of the parent >>>> image publisher configuration. >>>> >>>> your NGZ is lacking the ms.omniti.com publisher which you have set for >>>> the GZ. >>>> >>>> after doing a: >>>> # pkg -R /export/zones/web01/root set-publisher -g >>>> http://pkg.omniti.com/omniti-ms/ ms.omniti.com >>>> >>>> attaching the zone should work. >>>> >>>> On 11/20/2017 06:26 PM, Serge Fonville wrote: >>>> > Hi, >>>> > >>>> > When I tried to attach a zone I got the following errors: >>>> > >>>> > zoneadm -z web01 attach >>>> > >>>> > Log File: /var/tmp/web01.attach_log.olaaFy >>>> > Attach Path: /export/zones/web01/root >>>> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >>>> > >>>> > Installing: Using pre-existing data in zonepath >>>> > Cache: Using /var/pkg/publisher. >>>> > Updating non-global zone: Output follows >>>> > >>>> > Evaluation: Packages in zone web01 are out of sync >>>> with >>>> > the global zone. To proceed, retry with the -u flag. >>>> > Result: Attach Failed. >>>> > With the log file containing: >>>> > [Mon Nov 20 18:02:28 CET 2017] Log File: >>>> /var/tmp/web01.attach_log.olaaFy >>>> > [Mon Nov 20 18:02:32 CET 2017] Attach Path: >>>> > /export/zones/web01/root >>>> > [Mon Nov 20 18:02:32 CET 2017] Attach ZFS Dataset: >>>> > rpool/export/zones/web01/ROOT/zbe-9 >>>> > >>>> > [Mon Nov 20 18:02:32 CET 2017] existing >>>> > [Mon Nov 20 18:02:32 CET 2017] Installing: Using >>>> > pre-existing data in zonepath >>>> > [Mon Nov 20 18:02:32 CET 2017] Sanity Check: Passed. Looks like an >>>> > OpenSolaris system. >>>> > pkg: Search performance is degraded. >>>> > Run 'pkg rebuild-index' to improve search speed. >>>> > [Mon Nov 20 18:02:39 CET 2017] Cache: Using >>>> > /var/pkg/publisher. >>>> > [Mon Nov 20 18:02:39 CET 2017] Updating non-global zone: Output >>>> follows >>>> > >>>> > >>>> > pkg install: Invalid child image publisher configuration. Child image >>>> > publisher >>>> > configuration must be a superset of the parent image publisher >>>> > configuration. >>>> > Please update the child publisher configuration to match the parent. >>>> If the >>>> > child image is a zone this can be done automatically by detaching and >>>> > attaching the zone. >>>> > >>>> > The parent image has the following enabled publishers: >>>> > PUBLISHER 0: omnios >>>> > PUBLISHER 1: ms.omniti.com >>>> > >>>> > The child image has the following enabled publishers: >>>> > PUBLISHER 0: omnios >>>> > [Mon Nov 20 18:02:42 CET 2017] >>>> > Evaluation: Packages in zone web01 are out of sync >>>> with >>>> > the global zone. To proceed, retry with the -u flag. >>>> > [Mon Nov 20 18:02:44 CET 2017] Result: Attach >>>> Failed. >>>> > >>>> > So I try to run it with -u >>>> > >>>> > zoneadm -z web01 attach -u >>>> > >>>> > Log File: /var/tmp/web01.attach_log.TNaqaR >>>> > Attach Path: /export/zones/web01/root >>>> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >>>> > >>>> > Installing: Using pre-existing data in zonepath >>>> > Cache: Using /var/pkg/publisher. >>>> > Updating non-global zone: Output follows >>>> > ERROR: Could not update attaching zone >>>> > Result: Attach Failed. >>>> > >>>> > With the log file containing: >>>> > [Mon Nov 20 18:20:23 CET 2017] Log File: >>>> /var/tmp/web01.attach_log.TNaqaR >>>> > [Mon Nov 20 18:20:27 CET 2017] Attach Path: >>>> > /export/zones/web01/root >>>> > [Mon Nov 20 18:20:27 CET 2017] Attach ZFS Dataset: >>>> > rpool/export/zones/web01/ROOT/zbe-9 >>>> > >>>> > [Mon Nov 20 18:20:27 CET 2017] existing >>>> > [Mon Nov 20 18:20:27 CET 2017] Installing: Using >>>> > pre-existing data in zonepath >>>> > [Mon Nov 20 18:20:27 CET 2017] Sanity Check: Passed. Looks like an >>>> > OpenSolaris system. >>>> > [Mon Nov 20 18:20:31 CET 2017] Cache: Using >>>> > /var/pkg/publisher. >>>> > [Mon Nov 20 18:20:31 CET 2017] Updating non-global zone: Output >>>> follows >>>> > >>>> > >>>> > pkg install: Invalid child image publisher configuration. Child image >>>> > publisher >>>> > configuration must be a superset of the parent image publisher >>>> > configuration. >>>> > Please update the child publisher configuration to match the parent. >>>> If the >>>> > child image is a zone this can be done automatically by detaching and >>>> > attaching the zone. >>>> > >>>> > The parent image has the following enabled publishers: >>>> > PUBLISHER 0: omnios >>>> > PUBLISHER 1: ms.omniti.com >>>> > >>>> > The child image has the following enabled publishers: >>>> > PUBLISHER 0: omnios >>>> > [Mon Nov 20 18:20:35 CET 2017] ERROR: Could not update attaching zone >>>> > [Mon Nov 20 18:20:36 CET 2017] Result: Attach >>>> Failed. >>>> > >>>> > On global zone: >>>> > >>>> > pkg publisher >>>> > >>>> > PUBLISHER TYPE STATUS P LOCATION >>>> > omnios origin online F >>>> > https://pkg.omniosce.org/r151022/core/ >>>> > >>>> > Any help in resolving this greatly appreciated!! >>>> > >>>> > Thanks in advance!! >>>> > >>>> > Kind regards/met vriendelijke groet, >>>> > >>>> > Serge Fonville >>>> > >>>> > http://www.sergefonville.nl >>>> > >>>> > >>>> > _______________________________________________ >>>> > OmniOS-discuss mailing list >>>> > OmniOS-discuss at lists.omniti.com >>>> > http://lists.omniti.com/mailman/listinfo/omnios-discuss >>>> > >>>> >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From serge.fonville at gmail.com Tue Nov 21 11:57:45 2017 From: serge.fonville at gmail.com (Serge Fonville) Date: Tue, 21 Nov 2017 12:57:45 +0100 Subject: [OmniOS-discuss] ERROR: Could not update attaching zone In-Reply-To: References: <13fd6003-e2de-4cc7-dbba-309e063cc31e@gmx.li> Message-ID: Currently I am no longer able to mount the dataset. When I execute the following command, I get the followign error: > zoneadm -z web01 attach > Output: ERROR: Failed to locate any dataset mounted at /export/zones/web01/root. Attach requires a mounted dataset. Result: Attach Failed. Log: [Tue Nov 21 12:54:41 CET 2017] Log File: /var/tmp/web01.attach_log.8DaGSG [Tue Nov 21 12:54:42 CET 2017] ERROR: Failed to locate any dataset mounted at /export/zones/web01/root. Attach requires a mounted dataset. [Tue Nov 21 12:54:42 CET 2017] Result: Attach Failed. Perhaps I broke something else in the process :-( Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-21 7:54 GMT+01:00 Serge Fonville : > After having updated the canmount property to noauto of the filesystem, > the system now boots again. > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > 2017-11-21 7:08 GMT+01:00 Serge Fonville : > >> After having rebooted the server, I am now no longer able to logon to the >> server, the console shows messages it cannot mount the filesystem. because >> its directory is not empty, since the zone is in configured/detached state, >> how do I tell the system not to try to mount it? >> >> Kind regards/met vriendelijke groet, >> >> Serge Fonville >> >> http://www.sergefonville.nl >> >> 2017-11-21 6:11 GMT+01:00 Serge Fonville : >> >>> Also, since I had to remove it when I upgraded, I was under the >>> impression it was gone everywhere, since pkg publisher does not show it on >>> any other zone (including the GZ). >>> >>> Kind regards/met vriendelijke groet, >>> >>> Serge Fonville >>> >>> http://www.sergefonville.nl >>> >>> 2017-11-21 6:10 GMT+01:00 Serge Fonville : >>> >>>> So how do I see it in the GZ, because pkg publisher does not output it >>>> when I execute it on the GZ? >>>> >>>> Kind regards/met vriendelijke groet, >>>> >>>> Serge Fonville >>>> >>>> http://www.sergefonville.nl >>>> >>>> 2017-11-20 19:02 GMT+01:00 Dominik Hassler : >>>> >>>>> > Child image publisher configuration must be a superset of the parent >>>>> image publisher configuration. >>>>> >>>>> your NGZ is lacking the ms.omniti.com publisher which you have set for >>>>> the GZ. >>>>> >>>>> after doing a: >>>>> # pkg -R /export/zones/web01/root set-publisher -g >>>>> http://pkg.omniti.com/omniti-ms/ ms.omniti.com >>>>> >>>>> attaching the zone should work. >>>>> >>>>> On 11/20/2017 06:26 PM, Serge Fonville wrote: >>>>> > Hi, >>>>> > >>>>> > When I tried to attach a zone I got the following errors: >>>>> > >>>>> > zoneadm -z web01 attach >>>>> > >>>>> > Log File: /var/tmp/web01.attach_log.olaaFy >>>>> > Attach Path: /export/zones/web01/root >>>>> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >>>>> > >>>>> > Installing: Using pre-existing data in zonepath >>>>> > Cache: Using /var/pkg/publisher. >>>>> > Updating non-global zone: Output follows >>>>> > >>>>> > Evaluation: Packages in zone web01 are out of sync >>>>> with >>>>> > the global zone. To proceed, retry with the -u flag. >>>>> > Result: Attach Failed. >>>>> > With the log file containing: >>>>> > [Mon Nov 20 18:02:28 CET 2017] Log File: >>>>> /var/tmp/web01.attach_log.olaaFy >>>>> > [Mon Nov 20 18:02:32 CET 2017] Attach Path: >>>>> > /export/zones/web01/root >>>>> > [Mon Nov 20 18:02:32 CET 2017] Attach ZFS Dataset: >>>>> > rpool/export/zones/web01/ROOT/zbe-9 >>>>> > >>>>> > [Mon Nov 20 18:02:32 CET 2017] existing >>>>> > [Mon Nov 20 18:02:32 CET 2017] Installing: Using >>>>> > pre-existing data in zonepath >>>>> > [Mon Nov 20 18:02:32 CET 2017] Sanity Check: Passed. Looks like an >>>>> > OpenSolaris system. >>>>> > pkg: Search performance is degraded. >>>>> > Run 'pkg rebuild-index' to improve search speed. >>>>> > [Mon Nov 20 18:02:39 CET 2017] Cache: Using >>>>> > /var/pkg/publisher. >>>>> > [Mon Nov 20 18:02:39 CET 2017] Updating non-global zone: Output >>>>> follows >>>>> > >>>>> > >>>>> > pkg install: Invalid child image publisher configuration. Child >>>>> image >>>>> > publisher >>>>> > configuration must be a superset of the parent image publisher >>>>> > configuration. >>>>> > Please update the child publisher configuration to match the >>>>> parent. If the >>>>> > child image is a zone this can be done automatically by detaching and >>>>> > attaching the zone. >>>>> > >>>>> > The parent image has the following enabled publishers: >>>>> > PUBLISHER 0: omnios >>>>> > PUBLISHER 1: ms.omniti.com >>>>> > >>>>> > The child image has the following enabled publishers: >>>>> > PUBLISHER 0: omnios >>>>> > [Mon Nov 20 18:02:42 CET 2017] >>>>> > Evaluation: Packages in zone web01 are out of sync >>>>> with >>>>> > the global zone. To proceed, retry with the -u flag. >>>>> > [Mon Nov 20 18:02:44 CET 2017] Result: Attach >>>>> Failed. >>>>> > >>>>> > So I try to run it with -u >>>>> > >>>>> > zoneadm -z web01 attach -u >>>>> > >>>>> > Log File: /var/tmp/web01.attach_log.TNaqaR >>>>> > Attach Path: /export/zones/web01/root >>>>> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >>>>> > >>>>> > Installing: Using pre-existing data in zonepath >>>>> > Cache: Using /var/pkg/publisher. >>>>> > Updating non-global zone: Output follows >>>>> > ERROR: Could not update attaching zone >>>>> > Result: Attach Failed. >>>>> > >>>>> > With the log file containing: >>>>> > [Mon Nov 20 18:20:23 CET 2017] Log File: >>>>> /var/tmp/web01.attach_log.TNaqaR >>>>> > [Mon Nov 20 18:20:27 CET 2017] Attach Path: >>>>> > /export/zones/web01/root >>>>> > [Mon Nov 20 18:20:27 CET 2017] Attach ZFS Dataset: >>>>> > rpool/export/zones/web01/ROOT/zbe-9 >>>>> > >>>>> > [Mon Nov 20 18:20:27 CET 2017] existing >>>>> > [Mon Nov 20 18:20:27 CET 2017] Installing: Using >>>>> > pre-existing data in zonepath >>>>> > [Mon Nov 20 18:20:27 CET 2017] Sanity Check: Passed. Looks like an >>>>> > OpenSolaris system. >>>>> > [Mon Nov 20 18:20:31 CET 2017] Cache: Using >>>>> > /var/pkg/publisher. >>>>> > [Mon Nov 20 18:20:31 CET 2017] Updating non-global zone: Output >>>>> follows >>>>> > >>>>> > >>>>> > pkg install: Invalid child image publisher configuration. Child >>>>> image >>>>> > publisher >>>>> > configuration must be a superset of the parent image publisher >>>>> > configuration. >>>>> > Please update the child publisher configuration to match the >>>>> parent. If the >>>>> > child image is a zone this can be done automatically by detaching and >>>>> > attaching the zone. >>>>> > >>>>> > The parent image has the following enabled publishers: >>>>> > PUBLISHER 0: omnios >>>>> > PUBLISHER 1: ms.omniti.com >>>>> > >>>>> > The child image has the following enabled publishers: >>>>> > PUBLISHER 0: omnios >>>>> > [Mon Nov 20 18:20:35 CET 2017] ERROR: Could not update attaching zone >>>>> > [Mon Nov 20 18:20:36 CET 2017] Result: Attach >>>>> Failed. >>>>> > >>>>> > On global zone: >>>>> > >>>>> > pkg publisher >>>>> > >>>>> > PUBLISHER TYPE STATUS P LOCATION >>>>> > omnios origin online F >>>>> > https://pkg.omniosce.org/r151022/core/ >>>>> > >>>>> > Any help in resolving this greatly appreciated!! >>>>> > >>>>> > Thanks in advance!! >>>>> > >>>>> > Kind regards/met vriendelijke groet, >>>>> > >>>>> > Serge Fonville >>>>> > >>>>> > http://www.sergefonville.nl >>>>> > >>>>> > >>>>> > _______________________________________________ >>>>> > OmniOS-discuss mailing list >>>>> > OmniOS-discuss at lists.omniti.com >>>>> > http://lists.omniti.com/mailman/listinfo/omnios-discuss >>>>> > >>>>> >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From natxo.asenjo at gmail.com Tue Nov 21 12:13:13 2017 From: natxo.asenjo at gmail.com (Natxo Asenjo) Date: Tue, 21 Nov 2017 13:13:13 +0100 Subject: [OmniOS-discuss] crash after upgrading to 151024 In-Reply-To: References: Message-ID: hi, Not even two days ago I posted my message with a crash after updating to the latest omniosce. I am happy to report that the issue has been fixed by Andy Fiddaman (yesterday I updated to r151024) and everything is working: all the ipkg and lx zones plus de vm's hosted in the nfs serve Thanks for the very fast fix to a humble home user. Amazing response. -- regards, Natxo On Sun, Nov 19, 2017 at 10:22 PM, Andy Fiddaman wrote: > > On Sun, 19 Nov 2017, Natxo Asenjo wrote: > > ; hi, > ; > ; I upgraded our home nas from the old stable ce to the new stable one. The > ; process went ok, but after rebooting it has crashed twice: > ; > ; panicstack = unix:die+df () | unix:trap+e08 () | > ; unix:_cmntrap+e6 () | unix:strncpy+28 () | lx_brand:lx_prctl+48a () | > ; lx_brand:lx_syscall_enter+16f () | unix:brand_sys_syscall+1bd () | > > This looks like a bug in the lx support in r151024 with a commit that came > in fairly recently (so wouldn't have been in r151022). Send me the crash > dump as per the private email I've sent you but I think I can see where > this is (and the problem) just from the above. The crash dump will confirm > and then we'll get it fixed in the next r151024 update. > > Andy > > -- > Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk > Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ > Registered in England and Wales | Company number 4899123 > > -- -- Groeten, natxo -------------- next part -------------- An HTML attachment was scrubbed... URL: From serge.fonville at gmail.com Tue Nov 21 12:36:21 2017 From: serge.fonville at gmail.com (Serge Fonville) Date: Tue, 21 Nov 2017 13:36:21 +0100 Subject: [OmniOS-discuss] ERROR: Could not update attaching zone In-Reply-To: References: <13fd6003-e2de-4cc7-dbba-309e063cc31e@gmx.li> Message-ID: New error: No matching version of consolidation/osnet/osnet-incorporation can be installed: This one seems to be close to the solution.... How do I progress from here? Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-21 12:57 GMT+01:00 Serge Fonville : > Currently I am no longer able to mount the dataset. > When I execute the following command, I get the followign error: > >> zoneadm -z web01 attach >> > Output: > ERROR: Failed to locate any dataset mounted at /export/zones/web01/root. > Attach requires a mounted dataset. > Result: Attach Failed. > Log: > [Tue Nov 21 12:54:41 CET 2017] Log File: /var/tmp/web01.attach_log.8DaGSG > [Tue Nov 21 12:54:42 CET 2017] ERROR: Failed to locate any dataset mounted > at /export/zones/web01/root. Attach requires a mounted dataset. > [Tue Nov 21 12:54:42 CET 2017] Result: Attach Failed. > > Perhaps I broke something else in the process :-( > > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > 2017-11-21 7:54 GMT+01:00 Serge Fonville : > >> After having updated the canmount property to noauto of the filesystem, >> the system now boots again. >> >> Kind regards/met vriendelijke groet, >> >> Serge Fonville >> >> http://www.sergefonville.nl >> >> 2017-11-21 7:08 GMT+01:00 Serge Fonville : >> >>> After having rebooted the server, I am now no longer able to logon to >>> the server, the console shows messages it cannot mount the filesystem. >>> because its directory is not empty, since the zone is in >>> configured/detached state, how do I tell the system not to try to mount it? >>> >>> Kind regards/met vriendelijke groet, >>> >>> Serge Fonville >>> >>> http://www.sergefonville.nl >>> >>> 2017-11-21 6:11 GMT+01:00 Serge Fonville : >>> >>>> Also, since I had to remove it when I upgraded, I was under the >>>> impression it was gone everywhere, since pkg publisher does not show it on >>>> any other zone (including the GZ). >>>> >>>> Kind regards/met vriendelijke groet, >>>> >>>> Serge Fonville >>>> >>>> http://www.sergefonville.nl >>>> >>>> 2017-11-21 6:10 GMT+01:00 Serge Fonville : >>>> >>>>> So how do I see it in the GZ, because pkg publisher does not output it >>>>> when I execute it on the GZ? >>>>> >>>>> Kind regards/met vriendelijke groet, >>>>> >>>>> Serge Fonville >>>>> >>>>> http://www.sergefonville.nl >>>>> >>>>> 2017-11-20 19:02 GMT+01:00 Dominik Hassler : >>>>> >>>>>> > Child image publisher configuration must be a superset of the parent >>>>>> image publisher configuration. >>>>>> >>>>>> your NGZ is lacking the ms.omniti.com publisher which you have set >>>>>> for >>>>>> the GZ. >>>>>> >>>>>> after doing a: >>>>>> # pkg -R /export/zones/web01/root set-publisher -g >>>>>> http://pkg.omniti.com/omniti-ms/ ms.omniti.com >>>>>> >>>>>> attaching the zone should work. >>>>>> >>>>>> On 11/20/2017 06:26 PM, Serge Fonville wrote: >>>>>> > Hi, >>>>>> > >>>>>> > When I tried to attach a zone I got the following errors: >>>>>> > >>>>>> > zoneadm -z web01 attach >>>>>> > >>>>>> > Log File: /var/tmp/web01.attach_log.olaaFy >>>>>> > Attach Path: /export/zones/web01/root >>>>>> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >>>>>> > >>>>>> > Installing: Using pre-existing data in zonepath >>>>>> > Cache: Using /var/pkg/publisher. >>>>>> > Updating non-global zone: Output follows >>>>>> > >>>>>> > Evaluation: Packages in zone web01 are out of sync >>>>>> with >>>>>> > the global zone. To proceed, retry with the -u flag. >>>>>> > Result: Attach Failed. >>>>>> > With the log file containing: >>>>>> > [Mon Nov 20 18:02:28 CET 2017] Log File: >>>>>> /var/tmp/web01.attach_log.olaaFy >>>>>> > [Mon Nov 20 18:02:32 CET 2017] Attach Path: >>>>>> > /export/zones/web01/root >>>>>> > [Mon Nov 20 18:02:32 CET 2017] Attach ZFS Dataset: >>>>>> > rpool/export/zones/web01/ROOT/zbe-9 >>>>>> > >>>>>> > [Mon Nov 20 18:02:32 CET 2017] existing >>>>>> > [Mon Nov 20 18:02:32 CET 2017] Installing: Using >>>>>> > pre-existing data in zonepath >>>>>> > [Mon Nov 20 18:02:32 CET 2017] Sanity Check: Passed. Looks like >>>>>> an >>>>>> > OpenSolaris system. >>>>>> > pkg: Search performance is degraded. >>>>>> > Run 'pkg rebuild-index' to improve search speed. >>>>>> > [Mon Nov 20 18:02:39 CET 2017] Cache: Using >>>>>> > /var/pkg/publisher. >>>>>> > [Mon Nov 20 18:02:39 CET 2017] Updating non-global zone: Output >>>>>> follows >>>>>> > >>>>>> > >>>>>> > pkg install: Invalid child image publisher configuration. Child >>>>>> image >>>>>> > publisher >>>>>> > configuration must be a superset of the parent image publisher >>>>>> > configuration. >>>>>> > Please update the child publisher configuration to match the >>>>>> parent. If the >>>>>> > child image is a zone this can be done automatically by detaching >>>>>> and >>>>>> > attaching the zone. >>>>>> > >>>>>> > The parent image has the following enabled publishers: >>>>>> > PUBLISHER 0: omnios >>>>>> > PUBLISHER 1: ms.omniti.com >>>>>> > >>>>>> > The child image has the following enabled publishers: >>>>>> > PUBLISHER 0: omnios >>>>>> > [Mon Nov 20 18:02:42 CET 2017] >>>>>> > Evaluation: Packages in zone web01 are out of sync >>>>>> with >>>>>> > the global zone. To proceed, retry with the -u flag. >>>>>> > [Mon Nov 20 18:02:44 CET 2017] Result: Attach >>>>>> Failed. >>>>>> > >>>>>> > So I try to run it with -u >>>>>> > >>>>>> > zoneadm -z web01 attach -u >>>>>> > >>>>>> > Log File: /var/tmp/web01.attach_log.TNaqaR >>>>>> > Attach Path: /export/zones/web01/root >>>>>> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >>>>>> > >>>>>> > Installing: Using pre-existing data in zonepath >>>>>> > Cache: Using /var/pkg/publisher. >>>>>> > Updating non-global zone: Output follows >>>>>> > ERROR: Could not update attaching zone >>>>>> > Result: Attach Failed. >>>>>> > >>>>>> > With the log file containing: >>>>>> > [Mon Nov 20 18:20:23 CET 2017] Log File: >>>>>> /var/tmp/web01.attach_log.TNaqaR >>>>>> > [Mon Nov 20 18:20:27 CET 2017] Attach Path: >>>>>> > /export/zones/web01/root >>>>>> > [Mon Nov 20 18:20:27 CET 2017] Attach ZFS Dataset: >>>>>> > rpool/export/zones/web01/ROOT/zbe-9 >>>>>> > >>>>>> > [Mon Nov 20 18:20:27 CET 2017] existing >>>>>> > [Mon Nov 20 18:20:27 CET 2017] Installing: Using >>>>>> > pre-existing data in zonepath >>>>>> > [Mon Nov 20 18:20:27 CET 2017] Sanity Check: Passed. Looks like >>>>>> an >>>>>> > OpenSolaris system. >>>>>> > [Mon Nov 20 18:20:31 CET 2017] Cache: Using >>>>>> > /var/pkg/publisher. >>>>>> > [Mon Nov 20 18:20:31 CET 2017] Updating non-global zone: Output >>>>>> follows >>>>>> > >>>>>> > >>>>>> > pkg install: Invalid child image publisher configuration. Child >>>>>> image >>>>>> > publisher >>>>>> > configuration must be a superset of the parent image publisher >>>>>> > configuration. >>>>>> > Please update the child publisher configuration to match the >>>>>> parent. If the >>>>>> > child image is a zone this can be done automatically by detaching >>>>>> and >>>>>> > attaching the zone. >>>>>> > >>>>>> > The parent image has the following enabled publishers: >>>>>> > PUBLISHER 0: omnios >>>>>> > PUBLISHER 1: ms.omniti.com >>>>>> > >>>>>> > The child image has the following enabled publishers: >>>>>> > PUBLISHER 0: omnios >>>>>> > [Mon Nov 20 18:20:35 CET 2017] ERROR: Could not update attaching >>>>>> zone >>>>>> > [Mon Nov 20 18:20:36 CET 2017] Result: Attach >>>>>> Failed. >>>>>> > >>>>>> > On global zone: >>>>>> > >>>>>> > pkg publisher >>>>>> > >>>>>> > PUBLISHER TYPE STATUS P LOCATION >>>>>> > omnios origin online F >>>>>> > https://pkg.omniosce.org/r151022/core/ >>>>>> > >>>>>> > Any help in resolving this greatly appreciated!! >>>>>> > >>>>>> > Thanks in advance!! >>>>>> > >>>>>> > Kind regards/met vriendelijke groet, >>>>>> > >>>>>> > Serge Fonville >>>>>> > >>>>>> > http://www.sergefonville.nl >>>>>> > >>>>>> > >>>>>> > _______________________________________________ >>>>>> > OmniOS-discuss mailing list >>>>>> > OmniOS-discuss at lists.omniti.com >>>>>> > http://lists.omniti.com/mailman/listinfo/omnios-discuss >>>>>> > >>>>>> >>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From serge.fonville at gmail.com Tue Nov 21 13:23:49 2017 From: serge.fonville at gmail.com (Serge Fonville) Date: Tue, 21 Nov 2017 14:23:49 +0100 Subject: [OmniOS-discuss] ERROR: Could not update attaching zone In-Reply-To: References: <13fd6003-e2de-4cc7-dbba-309e063cc31e@gmx.li> Message-ID: I tried the suggestion of adding the publisher to the zone, and attaching it again, but unfortunately to no avail. I got the following error: [Tue Nov 21 14:20:44 CET 2017] Log File: /var/tmp/web01.attach_log.j6aOsf [Tue Nov 21 14:20:48 CET 2017] Attach Path: /export/zones/web01/root [Tue Nov 21 14:20:48 CET 2017] Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-19 [Tue Nov 21 14:20:48 CET 2017] existing [Tue Nov 21 14:20:48 CET 2017] Installing: Using pre-existing data in zonepath [Tue Nov 21 14:20:48 CET 2017] Sanity Check: Passed. Looks like an OpenSolaris system. [Tue Nov 21 14:20:53 CET 2017] Cache: Using /var/pkg/publisher. [Tue Nov 21 14:20:53 CET 2017] Updating non-global zone: Output follows pkg install: No matching version of consolidation/osnet/osnet-incorporation can be installed: No matching version of incorporation/jeos/omnios-userland can be installed: [Tue Nov 21 14:20:58 CET 2017] ERROR: Could not update attaching zone [Tue Nov 21 14:20:59 CET 2017] Result: Attach Failed. Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-21 13:36 GMT+01:00 Serge Fonville : > New error: > No matching version of consolidation/osnet/osnet-incorporation can be > installed: > This one seems to be close to the solution.... > > How do I progress from here? > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > 2017-11-21 12:57 GMT+01:00 Serge Fonville : > >> Currently I am no longer able to mount the dataset. >> When I execute the following command, I get the followign error: >> >>> zoneadm -z web01 attach >>> >> Output: >> ERROR: Failed to locate any dataset mounted at /export/zones/web01/root. >> Attach requires a mounted dataset. >> Result: Attach Failed. >> Log: >> [Tue Nov 21 12:54:41 CET 2017] Log File: /var/tmp/web01.attach_log.8DaGSG >> [Tue Nov 21 12:54:42 CET 2017] ERROR: Failed to locate any dataset >> mounted at /export/zones/web01/root. Attach requires a mounted dataset. >> [Tue Nov 21 12:54:42 CET 2017] Result: Attach Failed. >> >> Perhaps I broke something else in the process :-( >> >> >> Kind regards/met vriendelijke groet, >> >> Serge Fonville >> >> http://www.sergefonville.nl >> >> 2017-11-21 7:54 GMT+01:00 Serge Fonville : >> >>> After having updated the canmount property to noauto of the filesystem, >>> the system now boots again. >>> >>> Kind regards/met vriendelijke groet, >>> >>> Serge Fonville >>> >>> http://www.sergefonville.nl >>> >>> 2017-11-21 7:08 GMT+01:00 Serge Fonville : >>> >>>> After having rebooted the server, I am now no longer able to logon to >>>> the server, the console shows messages it cannot mount the filesystem. >>>> because its directory is not empty, since the zone is in >>>> configured/detached state, how do I tell the system not to try to mount it? >>>> >>>> Kind regards/met vriendelijke groet, >>>> >>>> Serge Fonville >>>> >>>> http://www.sergefonville.nl >>>> >>>> 2017-11-21 6:11 GMT+01:00 Serge Fonville : >>>> >>>>> Also, since I had to remove it when I upgraded, I was under the >>>>> impression it was gone everywhere, since pkg publisher does not show it on >>>>> any other zone (including the GZ). >>>>> >>>>> Kind regards/met vriendelijke groet, >>>>> >>>>> Serge Fonville >>>>> >>>>> http://www.sergefonville.nl >>>>> >>>>> 2017-11-21 6:10 GMT+01:00 Serge Fonville : >>>>> >>>>>> So how do I see it in the GZ, because pkg publisher does not output >>>>>> it when I execute it on the GZ? >>>>>> >>>>>> Kind regards/met vriendelijke groet, >>>>>> >>>>>> Serge Fonville >>>>>> >>>>>> http://www.sergefonville.nl >>>>>> >>>>>> 2017-11-20 19:02 GMT+01:00 Dominik Hassler : >>>>>> >>>>>>> > Child image publisher configuration must be a superset of the >>>>>>> parent >>>>>>> image publisher configuration. >>>>>>> >>>>>>> your NGZ is lacking the ms.omniti.com publisher which you have set >>>>>>> for >>>>>>> the GZ. >>>>>>> >>>>>>> after doing a: >>>>>>> # pkg -R /export/zones/web01/root set-publisher -g >>>>>>> http://pkg.omniti.com/omniti-ms/ ms.omniti.com >>>>>>> >>>>>>> attaching the zone should work. >>>>>>> >>>>>>> On 11/20/2017 06:26 PM, Serge Fonville wrote: >>>>>>> > Hi, >>>>>>> > >>>>>>> > When I tried to attach a zone I got the following errors: >>>>>>> > >>>>>>> > zoneadm -z web01 attach >>>>>>> > >>>>>>> > Log File: /var/tmp/web01.attach_log.olaaFy >>>>>>> > Attach Path: /export/zones/web01/root >>>>>>> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >>>>>>> > >>>>>>> > Installing: Using pre-existing data in zonepath >>>>>>> > Cache: Using /var/pkg/publisher. >>>>>>> > Updating non-global zone: Output follows >>>>>>> > >>>>>>> > Evaluation: Packages in zone web01 are out of sync >>>>>>> with >>>>>>> > the global zone. To proceed, retry with the -u flag. >>>>>>> > Result: Attach Failed. >>>>>>> > With the log file containing: >>>>>>> > [Mon Nov 20 18:02:28 CET 2017] Log File: >>>>>>> /var/tmp/web01.attach_log.olaaFy >>>>>>> > [Mon Nov 20 18:02:32 CET 2017] Attach Path: >>>>>>> > /export/zones/web01/root >>>>>>> > [Mon Nov 20 18:02:32 CET 2017] Attach ZFS Dataset: >>>>>>> > rpool/export/zones/web01/ROOT/zbe-9 >>>>>>> > >>>>>>> > [Mon Nov 20 18:02:32 CET 2017] existing >>>>>>> > [Mon Nov 20 18:02:32 CET 2017] Installing: Using >>>>>>> > pre-existing data in zonepath >>>>>>> > [Mon Nov 20 18:02:32 CET 2017] Sanity Check: Passed. Looks like >>>>>>> an >>>>>>> > OpenSolaris system. >>>>>>> > pkg: Search performance is degraded. >>>>>>> > Run 'pkg rebuild-index' to improve search speed. >>>>>>> > [Mon Nov 20 18:02:39 CET 2017] Cache: Using >>>>>>> > /var/pkg/publisher. >>>>>>> > [Mon Nov 20 18:02:39 CET 2017] Updating non-global zone: Output >>>>>>> follows >>>>>>> > >>>>>>> > >>>>>>> > pkg install: Invalid child image publisher configuration. Child >>>>>>> image >>>>>>> > publisher >>>>>>> > configuration must be a superset of the parent image publisher >>>>>>> > configuration. >>>>>>> > Please update the child publisher configuration to match the >>>>>>> parent. If the >>>>>>> > child image is a zone this can be done automatically by detaching >>>>>>> and >>>>>>> > attaching the zone. >>>>>>> > >>>>>>> > The parent image has the following enabled publishers: >>>>>>> > PUBLISHER 0: omnios >>>>>>> > PUBLISHER 1: ms.omniti.com >>>>>>> > >>>>>>> > The child image has the following enabled publishers: >>>>>>> > PUBLISHER 0: omnios >>>>>>> > [Mon Nov 20 18:02:42 CET 2017] >>>>>>> > Evaluation: Packages in zone web01 are out of sync >>>>>>> with >>>>>>> > the global zone. To proceed, retry with the -u flag. >>>>>>> > [Mon Nov 20 18:02:44 CET 2017] Result: Attach >>>>>>> Failed. >>>>>>> > >>>>>>> > So I try to run it with -u >>>>>>> > >>>>>>> > zoneadm -z web01 attach -u >>>>>>> > >>>>>>> > Log File: /var/tmp/web01.attach_log.TNaqaR >>>>>>> > Attach Path: /export/zones/web01/root >>>>>>> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >>>>>>> > >>>>>>> > Installing: Using pre-existing data in zonepath >>>>>>> > Cache: Using /var/pkg/publisher. >>>>>>> > Updating non-global zone: Output follows >>>>>>> > ERROR: Could not update attaching zone >>>>>>> > Result: Attach Failed. >>>>>>> > >>>>>>> > With the log file containing: >>>>>>> > [Mon Nov 20 18:20:23 CET 2017] Log File: >>>>>>> /var/tmp/web01.attach_log.TNaqaR >>>>>>> > [Mon Nov 20 18:20:27 CET 2017] Attach Path: >>>>>>> > /export/zones/web01/root >>>>>>> > [Mon Nov 20 18:20:27 CET 2017] Attach ZFS Dataset: >>>>>>> > rpool/export/zones/web01/ROOT/zbe-9 >>>>>>> > >>>>>>> > [Mon Nov 20 18:20:27 CET 2017] existing >>>>>>> > [Mon Nov 20 18:20:27 CET 2017] Installing: Using >>>>>>> > pre-existing data in zonepath >>>>>>> > [Mon Nov 20 18:20:27 CET 2017] Sanity Check: Passed. Looks like >>>>>>> an >>>>>>> > OpenSolaris system. >>>>>>> > [Mon Nov 20 18:20:31 CET 2017] Cache: Using >>>>>>> > /var/pkg/publisher. >>>>>>> > [Mon Nov 20 18:20:31 CET 2017] Updating non-global zone: Output >>>>>>> follows >>>>>>> > >>>>>>> > >>>>>>> > pkg install: Invalid child image publisher configuration. Child >>>>>>> image >>>>>>> > publisher >>>>>>> > configuration must be a superset of the parent image publisher >>>>>>> > configuration. >>>>>>> > Please update the child publisher configuration to match the >>>>>>> parent. If the >>>>>>> > child image is a zone this can be done automatically by detaching >>>>>>> and >>>>>>> > attaching the zone. >>>>>>> > >>>>>>> > The parent image has the following enabled publishers: >>>>>>> > PUBLISHER 0: omnios >>>>>>> > PUBLISHER 1: ms.omniti.com >>>>>>> > >>>>>>> > The child image has the following enabled publishers: >>>>>>> > PUBLISHER 0: omnios >>>>>>> > [Mon Nov 20 18:20:35 CET 2017] ERROR: Could not update attaching >>>>>>> zone >>>>>>> > [Mon Nov 20 18:20:36 CET 2017] Result: Attach >>>>>>> Failed. >>>>>>> > >>>>>>> > On global zone: >>>>>>> > >>>>>>> > pkg publisher >>>>>>> > >>>>>>> > PUBLISHER TYPE STATUS P LOCATION >>>>>>> > omnios origin online F >>>>>>> > https://pkg.omniosce.org/r151022/core/ >>>>>>> > >>>>>>> > Any help in resolving this greatly appreciated!! >>>>>>> > >>>>>>> > Thanks in advance!! >>>>>>> > >>>>>>> > Kind regards/met vriendelijke groet, >>>>>>> > >>>>>>> > Serge Fonville >>>>>>> > >>>>>>> > http://www.sergefonville.nl >>>>>>> > >>>>>>> > >>>>>>> > _______________________________________________ >>>>>>> > OmniOS-discuss mailing list >>>>>>> > OmniOS-discuss at lists.omniti.com >>>>>>> > http://lists.omniti.com/mailman/listinfo/omnios-discuss >>>>>>> > >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From serge.fonville at gmail.com Tue Nov 21 14:20:55 2017 From: serge.fonville at gmail.com (Serge Fonville) Date: Tue, 21 Nov 2017 15:20:55 +0100 Subject: [OmniOS-discuss] ERROR: Could not update attaching zone In-Reply-To: References: <13fd6003-e2de-4cc7-dbba-309e063cc31e@gmx.li> Message-ID: There are 4 packages that are installed from a different publisher: FMRI: pkg://ms.omniti.com/omniti/library/apr at 1.5.2-0.151014: 20170607T153003Z FMRI: pkg://ms.omniti.com/omniti/library/apr-util at 1.5.4-0. 151014:20170607T153107Z FMRI: pkg://ms.omniti.com/omniti/library/uuid at 1.41.14-0.151016: 20160504T142422Z FMRI: pkg://ms.omniti.com/omniti/server/nginx at 1.11.13-0.151014: 20170412T171318Z If I replace these, does that fix anything? Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-21 14:23 GMT+01:00 Serge Fonville : > I tried the suggestion of adding the publisher to the zone, and attaching > it again, but unfortunately to no avail. > I got the following error: > [Tue Nov 21 14:20:44 CET 2017] Log File: /var/tmp/web01.attach_log.j6aOsf > [Tue Nov 21 14:20:48 CET 2017] Attach Path: > /export/zones/web01/root > [Tue Nov 21 14:20:48 CET 2017] Attach ZFS Dataset: > rpool/export/zones/web01/ROOT/zbe-19 > > [Tue Nov 21 14:20:48 CET 2017] existing > [Tue Nov 21 14:20:48 CET 2017] Installing: Using > pre-existing data in zonepath > [Tue Nov 21 14:20:48 CET 2017] Sanity Check: Passed. Looks like an > OpenSolaris system. > [Tue Nov 21 14:20:53 CET 2017] Cache: Using > /var/pkg/publisher. > [Tue Nov 21 14:20:53 CET 2017] Updating non-global zone: Output follows > > pkg install: No matching version of consolidation/osnet/osnet-incorporation > can be installed: > No matching version of incorporation/jeos/omnios-userland can be > installed: > [Tue Nov 21 14:20:58 CET 2017] ERROR: Could not update attaching zone > [Tue Nov 21 14:20:59 CET 2017] Result: Attach Failed. > > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > 2017-11-21 13:36 GMT+01:00 Serge Fonville : > >> New error: >> No matching version of consolidation/osnet/osnet-incorporation can be >> installed: >> This one seems to be close to the solution.... >> >> How do I progress from here? >> >> Kind regards/met vriendelijke groet, >> >> Serge Fonville >> >> http://www.sergefonville.nl >> >> 2017-11-21 12:57 GMT+01:00 Serge Fonville : >> >>> Currently I am no longer able to mount the dataset. >>> When I execute the following command, I get the followign error: >>> >>>> zoneadm -z web01 attach >>>> >>> Output: >>> ERROR: Failed to locate any dataset mounted at >>> /export/zones/web01/root. Attach requires a mounted dataset. >>> Result: Attach Failed. >>> Log: >>> [Tue Nov 21 12:54:41 CET 2017] Log File: /var/tmp/web01.attach_log.8DaG >>> SG >>> [Tue Nov 21 12:54:42 CET 2017] ERROR: Failed to locate any dataset >>> mounted at /export/zones/web01/root. Attach requires a mounted dataset. >>> [Tue Nov 21 12:54:42 CET 2017] Result: Attach Failed. >>> >>> Perhaps I broke something else in the process :-( >>> >>> >>> Kind regards/met vriendelijke groet, >>> >>> Serge Fonville >>> >>> http://www.sergefonville.nl >>> >>> 2017-11-21 7:54 GMT+01:00 Serge Fonville : >>> >>>> After having updated the canmount property to noauto of the filesystem, >>>> the system now boots again. >>>> >>>> Kind regards/met vriendelijke groet, >>>> >>>> Serge Fonville >>>> >>>> http://www.sergefonville.nl >>>> >>>> 2017-11-21 7:08 GMT+01:00 Serge Fonville : >>>> >>>>> After having rebooted the server, I am now no longer able to logon to >>>>> the server, the console shows messages it cannot mount the filesystem. >>>>> because its directory is not empty, since the zone is in >>>>> configured/detached state, how do I tell the system not to try to mount it? >>>>> >>>>> Kind regards/met vriendelijke groet, >>>>> >>>>> Serge Fonville >>>>> >>>>> http://www.sergefonville.nl >>>>> >>>>> 2017-11-21 6:11 GMT+01:00 Serge Fonville : >>>>> >>>>>> Also, since I had to remove it when I upgraded, I was under the >>>>>> impression it was gone everywhere, since pkg publisher does not show it on >>>>>> any other zone (including the GZ). >>>>>> >>>>>> Kind regards/met vriendelijke groet, >>>>>> >>>>>> Serge Fonville >>>>>> >>>>>> http://www.sergefonville.nl >>>>>> >>>>>> 2017-11-21 6:10 GMT+01:00 Serge Fonville : >>>>>> >>>>>>> So how do I see it in the GZ, because pkg publisher does not output >>>>>>> it when I execute it on the GZ? >>>>>>> >>>>>>> Kind regards/met vriendelijke groet, >>>>>>> >>>>>>> Serge Fonville >>>>>>> >>>>>>> http://www.sergefonville.nl >>>>>>> >>>>>>> 2017-11-20 19:02 GMT+01:00 Dominik Hassler : >>>>>>> >>>>>>>> > Child image publisher configuration must be a superset of the >>>>>>>> parent >>>>>>>> image publisher configuration. >>>>>>>> >>>>>>>> your NGZ is lacking the ms.omniti.com publisher which you have set >>>>>>>> for >>>>>>>> the GZ. >>>>>>>> >>>>>>>> after doing a: >>>>>>>> # pkg -R /export/zones/web01/root set-publisher -g >>>>>>>> http://pkg.omniti.com/omniti-ms/ ms.omniti.com >>>>>>>> >>>>>>>> attaching the zone should work. >>>>>>>> >>>>>>>> On 11/20/2017 06:26 PM, Serge Fonville wrote: >>>>>>>> > Hi, >>>>>>>> > >>>>>>>> > When I tried to attach a zone I got the following errors: >>>>>>>> > >>>>>>>> > zoneadm -z web01 attach >>>>>>>> > >>>>>>>> > Log File: /var/tmp/web01.attach_log.olaaFy >>>>>>>> > Attach Path: /export/zones/web01/root >>>>>>>> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >>>>>>>> > >>>>>>>> > Installing: Using pre-existing data in zonepath >>>>>>>> > Cache: Using /var/pkg/publisher. >>>>>>>> > Updating non-global zone: Output follows >>>>>>>> > >>>>>>>> > Evaluation: Packages in zone web01 are out of >>>>>>>> sync with >>>>>>>> > the global zone. To proceed, retry with the -u flag. >>>>>>>> > Result: Attach Failed. >>>>>>>> > With the log file containing: >>>>>>>> > [Mon Nov 20 18:02:28 CET 2017] Log File: >>>>>>>> /var/tmp/web01.attach_log.olaaFy >>>>>>>> > [Mon Nov 20 18:02:32 CET 2017] Attach Path: >>>>>>>> > /export/zones/web01/root >>>>>>>> > [Mon Nov 20 18:02:32 CET 2017] Attach ZFS Dataset: >>>>>>>> > rpool/export/zones/web01/ROOT/zbe-9 >>>>>>>> > >>>>>>>> > [Mon Nov 20 18:02:32 CET 2017] existing >>>>>>>> > [Mon Nov 20 18:02:32 CET 2017] Installing: Using >>>>>>>> > pre-existing data in zonepath >>>>>>>> > [Mon Nov 20 18:02:32 CET 2017] Sanity Check: Passed. Looks >>>>>>>> like an >>>>>>>> > OpenSolaris system. >>>>>>>> > pkg: Search performance is degraded. >>>>>>>> > Run 'pkg rebuild-index' to improve search speed. >>>>>>>> > [Mon Nov 20 18:02:39 CET 2017] Cache: Using >>>>>>>> > /var/pkg/publisher. >>>>>>>> > [Mon Nov 20 18:02:39 CET 2017] Updating non-global zone: Output >>>>>>>> follows >>>>>>>> > >>>>>>>> > >>>>>>>> > pkg install: Invalid child image publisher configuration. Child >>>>>>>> image >>>>>>>> > publisher >>>>>>>> > configuration must be a superset of the parent image publisher >>>>>>>> > configuration. >>>>>>>> > Please update the child publisher configuration to match the >>>>>>>> parent. If the >>>>>>>> > child image is a zone this can be done automatically by detaching >>>>>>>> and >>>>>>>> > attaching the zone. >>>>>>>> > >>>>>>>> > The parent image has the following enabled publishers: >>>>>>>> > PUBLISHER 0: omnios >>>>>>>> > PUBLISHER 1: ms.omniti.com >>>>>>>> > >>>>>>>> > The child image has the following enabled publishers: >>>>>>>> > PUBLISHER 0: omnios >>>>>>>> > [Mon Nov 20 18:02:42 CET 2017] >>>>>>>> > Evaluation: Packages in zone web01 are out of >>>>>>>> sync with >>>>>>>> > the global zone. To proceed, retry with the -u flag. >>>>>>>> > [Mon Nov 20 18:02:44 CET 2017] Result: Attach >>>>>>>> Failed. >>>>>>>> > >>>>>>>> > So I try to run it with -u >>>>>>>> > >>>>>>>> > zoneadm -z web01 attach -u >>>>>>>> > >>>>>>>> > Log File: /var/tmp/web01.attach_log.TNaqaR >>>>>>>> > Attach Path: /export/zones/web01/root >>>>>>>> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >>>>>>>> > >>>>>>>> > Installing: Using pre-existing data in zonepath >>>>>>>> > Cache: Using /var/pkg/publisher. >>>>>>>> > Updating non-global zone: Output follows >>>>>>>> > ERROR: Could not update attaching zone >>>>>>>> > Result: Attach Failed. >>>>>>>> > >>>>>>>> > With the log file containing: >>>>>>>> > [Mon Nov 20 18:20:23 CET 2017] Log File: >>>>>>>> /var/tmp/web01.attach_log.TNaqaR >>>>>>>> > [Mon Nov 20 18:20:27 CET 2017] Attach Path: >>>>>>>> > /export/zones/web01/root >>>>>>>> > [Mon Nov 20 18:20:27 CET 2017] Attach ZFS Dataset: >>>>>>>> > rpool/export/zones/web01/ROOT/zbe-9 >>>>>>>> > >>>>>>>> > [Mon Nov 20 18:20:27 CET 2017] existing >>>>>>>> > [Mon Nov 20 18:20:27 CET 2017] Installing: Using >>>>>>>> > pre-existing data in zonepath >>>>>>>> > [Mon Nov 20 18:20:27 CET 2017] Sanity Check: Passed. Looks >>>>>>>> like an >>>>>>>> > OpenSolaris system. >>>>>>>> > [Mon Nov 20 18:20:31 CET 2017] Cache: Using >>>>>>>> > /var/pkg/publisher. >>>>>>>> > [Mon Nov 20 18:20:31 CET 2017] Updating non-global zone: Output >>>>>>>> follows >>>>>>>> > >>>>>>>> > >>>>>>>> > pkg install: Invalid child image publisher configuration. Child >>>>>>>> image >>>>>>>> > publisher >>>>>>>> > configuration must be a superset of the parent image publisher >>>>>>>> > configuration. >>>>>>>> > Please update the child publisher configuration to match the >>>>>>>> parent. If the >>>>>>>> > child image is a zone this can be done automatically by detaching >>>>>>>> and >>>>>>>> > attaching the zone. >>>>>>>> > >>>>>>>> > The parent image has the following enabled publishers: >>>>>>>> > PUBLISHER 0: omnios >>>>>>>> > PUBLISHER 1: ms.omniti.com >>>>>>>> > >>>>>>>> > The child image has the following enabled publishers: >>>>>>>> > PUBLISHER 0: omnios >>>>>>>> > [Mon Nov 20 18:20:35 CET 2017] ERROR: Could not update attaching >>>>>>>> zone >>>>>>>> > [Mon Nov 20 18:20:36 CET 2017] Result: Attach >>>>>>>> Failed. >>>>>>>> > >>>>>>>> > On global zone: >>>>>>>> > >>>>>>>> > pkg publisher >>>>>>>> > >>>>>>>> > PUBLISHER TYPE STATUS P LOCATION >>>>>>>> > omnios origin online F >>>>>>>> > https://pkg.omniosce.org/r151022/core/ >>>>>>>> > >>>>>>>> > Any help in resolving this greatly appreciated!! >>>>>>>> > >>>>>>>> > Thanks in advance!! >>>>>>>> > >>>>>>>> > Kind regards/met vriendelijke groet, >>>>>>>> > >>>>>>>> > Serge Fonville >>>>>>>> > >>>>>>>> > http://www.sergefonville.nl >>>>>>>> > >>>>>>>> > >>>>>>>> > _______________________________________________ >>>>>>>> > OmniOS-discuss mailing list >>>>>>>> > OmniOS-discuss at lists.omniti.com >>>>>>>> > http://lists.omniti.com/mailman/listinfo/omnios-discuss >>>>>>>> > >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Richard.Jahnel at RealPage.com Wed Nov 22 15:20:04 2017 From: Richard.Jahnel at RealPage.com (Richard Jahnel) Date: Wed, 22 Nov 2017 15:20:04 +0000 Subject: [OmniOS-discuss] Panic under heavy I/O conditions Message-ID: <1df2a1fa63cf4185a63c11ddf9d36f5e@RCEEXC001.Corp.realpage.com> I have briefly touched on this panic condition before, however since upgrading to R151022ce the previous mitigation of restricting the pool to 3 specific flags is no longer working. So here I am for some further discussion and hopefully more clues with which to chase the core issue down and kill it dead. Initial condition is to have a pool under very heavy write I/O. In our case here it is performing an eager zero during the creation of a VMDK file by an esxi fibre client. Then while the eager zero is in progress have a scheduled snapshot destroy and creation script run. At this point there is about a 20ish percent chance you will generate a panic during the execution of that script. All the technical readouts I have been able to generate thus far follow. > ::status debugging crash dump vmcore.2 (64-bit) from DALSTOR1 operating system: 5.11 omnios-r151022-5e982daae6 (i86pc) image uuid: febd682c-2ba5-69ea-b5c4-c8a30c88ffc4 panic message: hati_pte_map: flags & HAT_LOAD_REMAP dump content: kernel pages only > $C ffffd000f5d6f7b0 vpanic() ffffd000f5d6f850 hati_pte_map+0x3ab(ffffd0341195c518, 46, ffffd000af162cd8, 8000001756ea8007, 0, 0) ffffd000f5d6f8e0 hati_load_common+0x139(ffffd0321f9a8908, 8046000, ffffd000af162cd8, 40b, 0, 0, 1756ea8) ffffd000f5d6f960 hat_memload+0x75(ffffd0321f9a8908, 8046000, ffffd000af162cd8, b, 0) ffffd000f5d6fa80 segvn_faultpage+0x730(ffffd0321f9a8908, ffffd03252f19df0, 8046000, fffffffffffff000, 0, ffffd000f5d6fb50, ffffd03400000000, ffffd03100000001, ffffd00000000002, ffffffff00000001) ffffd000f5d6fc50 segvn_fault+0x8e6(ffffd0321f9a8908, ffffd03252f19df0, 8046000, 1000, 1, 2) ffffd000f5d6fd60 as_fault+0x312(ffffd0321f9a8908, ffffd0321fa22e20, 8046efc, 1, 1, 2) ffffd000f5d6fdf0 pagefault+0x96(8046efc, 1, 2, 0) ffffd000f5d6ff00 trap+0x30c(ffffd000f5d6ff10, 8046efc, b) ffffd000f5d6ff10 0xfffffffffb8001d6() > ::stack vpanic() hati_pte_map+0x3ab(ffffd0341195c518, 46, ffffd000af162cd8, 8000001756ea8007, 0, 0) hati_load_common+0x139(ffffd0321f9a8908, 8046000, ffffd000af162cd8, 40b, 0, 0) hat_memload+0x75(ffffd0321f9a8908, 8046000, ffffd000af162cd8, b, 0) segvn_faultpage+0x730(ffffd0321f9a8908, ffffd03252f19df0, 8046000, fffffffffffff000, 0, ffffd000f5d6fb50) segvn_fault+0x8e6(ffffd0321f9a8908, ffffd03252f19df0, 8046000, 1000, 1, 2) as_fault+0x312(ffffd0321f9a8908, ffffd0321fa22e20, 8046efc, 1, 1, 2) pagefault+0x96(8046efc, 1, 2, 0) trap+0x30c(ffffd000f5d6ff10, 8046efc, b) 0xfffffffffb8001d6() > ::cpuinfo ID ADDR FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD PROC 0 fffffffffbc397a0 1f 0 0 39 no no t-0 ffffd031ff4cb060 DALV4_snapcycle. 1 ffffd031ea372b00 1f 2 0 -1 no no t-0 ffffd000f45fdc40 (idle) 2 ffffd031ea36f500 1f 0 0 -1 no no t-0 ffffd000f46f7c40 (idle) 3 ffffd031ea369540 1f 0 0 -1 no no t-0 ffffd000f47a9c40 (idle) 4 ffffd031ea368040 1f 0 0 -1 no no t-0 ffffd000f467bc40 (idle) 5 ffffd031ea4bdb00 1f 0 0 -1 no no t-0 ffffd000f4868c40 (idle) 6 ffffd031ea4b3a80 1f 1 0 -1 no no t-0 ffffd000f49afc40 (idle) 7 ffffd031ea4aa540 1f 2 0 -1 no no t-0 ffffd000f50a7c40 (idle) 8 ffffd031ea4a9040 1f 2 0 -1 no no t-0 ffffd000f51a1c40 (idle) 9 ffffd031ea60cb00 1f 2 0 -1 no no t-0 ffffd000f5253c40 (idle) 10 ffffd031ea602a80 1f 1 0 -1 no no t-0 ffffd000f5305c40 (idle) 11 fffffffffbc440a0 1b 0 0 29 no no t-0 ffffd03220006b60 DALV4_snapcycle. > ffffd031ff4cb060::findstack -v stack pointer for thread ffffd031ff4cb060: ffffd000f78fd720 ffffd000f78fd910 page_trylock+1() ffffd000f78fd9c0 zfs_getpage+0x185(ffffd031ffb33e40, e2000, 1000, ffffd000f78fdbec, ffffd000f78fdb50, 8000, ffffd0347314fbf8, fef02000, 3, ffffd0327ee27c80, 0) ffffd000f78fda80 fop_getpage+0x7e(ffffd031ffb33e40, e2000, 1000, ffffd000f78fdbec, ffffd000f78fdb50, 8000, ffffd0347314fbf8, fef02000, ffffd00000000003, ffffd0327ee27c80, 0) ffffd000f78fdc50 segvn_fault+0xdfa(ffffd0321f9a8598, ffffd0347314fbf8, fef02000, 1000, 0, 3) ffffd000f78fdd60 as_fault+0x312(ffffd0321f9a8598, ffffd0321fa229c0, fef0276b, 1, 0, 3) ffffd000f78fddf0 pagefault+0x96(fef0276b, 0, 3, 0) ffffd000f78fdf00 trap+0x30c(ffffd000f78fdf10, fef0276b, 0) ffffd000f78fdf10 0xfffffffffb8001d6() > ffffd03220006b60::findstack -v stack pointer for thread ffffd03220006b60: ffffd000f5d6f740 ffffd000f5d6f7b0 param_preset() ffffd000f5d6f850 hati_pte_map+0x3ab(ffffd0341195c518, 46, ffffd000af162cd8, 8000001756ea8007, 0 , 0) ffffd000f5d6f8e0 hati_load_common+0x139(ffffd0321f9a8908, 8046000, ffffd000af162cd8, 40b, 0, 0 , 1756ea8) ffffd000f5d6f960 hat_memload+0x75(ffffd0321f9a8908, 8046000, ffffd000af162cd8, b, 0) ffffd000f5d6fa80 segvn_faultpage+0x730(ffffd0321f9a8908, ffffd03252f19df0, 8046000, fffffffffffff000, 0, ffffd000f5d6fb50, ffffd03400000000, ffffd03100000001, ffffd00000000002, ffffffff00000001) ffffd000f5d6fc50 segvn_fault+0x8e6(ffffd0321f9a8908, ffffd03252f19df0, 8046000, 1000, 1, 2) ffffd000f5d6fd60 as_fault+0x312(ffffd0321f9a8908, ffffd0321fa22e20, 8046efc, 1, 1, 2) ffffd000f5d6fdf0 pagefault+0x96(8046efc, 1, 2, 0) ffffd000f5d6ff00 trap+0x30c(ffffd000f5d6ff10, 8046efc, b) ffffd000f5d6ff10 0xfffffffffb8001d6() > hati_pte_map+0x3ab::dis hati_pte_map+0x37e: movq %r12,%rdx hati_pte_map+0x381: movq $0xfffffffffb93ae08,%rdi hati_pte_map+0x388: xorl %eax,%eax hati_pte_map+0x38a: call +0x665e1 hati_pte_map+0x38f: movq $0xfffffffffb93acf8,%rdi hati_pte_map+0x396: xorl %eax,%eax hati_pte_map+0x398: call +0x665d3 hati_pte_map+0x39d: movq $0xfffffffffb93ad18,%rdi hati_pte_map+0x3a4: xorl %eax,%eax hati_pte_map+0x3a6: call +0x665c5 hati_pte_map+0x3ab: movq $0xfffffffffb957c1f,%rdi hati_pte_map+0x3b2: xorl %eax,%eax hati_pte_map+0x3b4: call +0x665b7 hati_pte_map+0x3b9: movq $0xfffffffffb93adb0,%rdi hati_pte_map+0x3c0: xorl %eax,%eax hati_pte_map+0x3c2: call +0x665a9 hati_pte_map+0x3c7: movq $0xfffffffffb93ad70,%rdi hati_pte_map+0x3ce: xorl %eax,%eax hati_pte_map+0x3d0: call +0x6659b hati_pte_map+0x3d5: movq $0xfffffffffb93ad40,%rdi hati_pte_map+0x3dc: xorl %eax,%eax > fop_getpage+0x7e::dis fop_getpage+0x52: movq 0x30(%rbp),%rdi fop_getpage+0x56: movq 0x40(%rbx),%r10 fop_getpage+0x5a: movl %eax,0x10(%rsp) fop_getpage+0x5e: movq 0x18(%rbp),%rax fop_getpage+0x62: movq %rdi,0x20(%rsp) fop_getpage+0x67: movq %rbx,%rdi fop_getpage+0x6a: movq %rax,0x8(%rsp) fop_getpage+0x6f: movq 0x10(%rbp),%rax fop_getpage+0x73: movq %rax,(%rsp) fop_getpage+0x77: call *0xf0(%r10) fop_getpage+0x7e: movq 0x18(%rbx),%r12 fop_getpage+0x82: testq %r12,%r12 fop_getpage+0x85: je +0x51 fop_getpage+0x87: movq 0xa0(%r12),%r13 fop_getpage+0x8f: testq %r13,%r13 fop_getpage+0x92: je +0x44 fop_getpage+0x94: testb $0x20,0x21(%r12) fop_getpage+0x9a: je +0x3c fop_getpage+0x9c: cmpl $0xb,0x28(%rbx) fop_getpage+0xa0: je +0x36 fop_getpage+0xa2: leaq 0x640(%r13),%rdx > zfs_getpage+0x185::dis zfs_getpage+0x169: movq -0x68(%rbp),%r13 zfs_getpage+0x16d: jmp +0x9 zfs_getpage+0x16f: nop zfs_getpage+0x170: subq %rbx,%r13 zfs_getpage+0x173: je +0x1c zfs_getpage+0x175: addq %rbx,%r12 zfs_getpage+0x178: xorl %edx,%edx zfs_getpage+0x17a: movq %r12,%rsi zfs_getpage+0x17d: movq %r15,%rdi zfs_getpage+0x180: call +0x3e0abdb zfs_getpage+0x185: movq %rax,(%r14) zfs_getpage+0x188: addq $0x8,%r14 zfs_getpage+0x18c: testq %rax,%rax zfs_getpage+0x18f: jne -0x21 zfs_getpage+0x191: movq -0x70(%rbp),%rax zfs_getpage+0x195: movl 0xc4(%rax),%ecx zfs_getpage+0x19b: testl %ecx,%ecx zfs_getpage+0x19d: je +0x11 zfs_getpage+0x19f: movq -0x70(%rbp),%rdx zfs_getpage+0x1a3: movq (%rdx),%rax zfs_getpage+0x1a6: testb $0x1,0x20(%rax) > hati_load_common+0x139::dis hati_load_common+0x113: call -0x8d8 hati_load_common+0x118: cmpq %r13,+0x419f31(%rip) hati_load_common+0x11f: je +0x4f hati_load_common+0x121: movq -0x70(%rbp),%rdx hati_load_common+0x125: movl -0x74(%rbp),%esi hati_load_common+0x128: xorl %r9d,%r9d hati_load_common+0x12b: movl %r12d,%r8d hati_load_common+0x12e: movq %rax,%rcx hati_load_common+0x131: movq %rbx,%rdi hati_load_common+0x134: call -0x529 hati_load_common+0x139: movq %rbx,%rdi hati_load_common+0x13c: movl %eax,-0x80(%rbp) hati_load_common+0x13f: call +0x609c hati_load_common+0x144: movq %gs:0x18,%rdx hati_load_common+0x14d: decb 0x302(%rdx) hati_load_common+0x153: movl -0x80(%rbp),%eax hati_load_common+0x156: movq -0x58(%rbp),%rbx hati_load_common+0x15a: movq -0x50(%rbp),%r12 hati_load_common+0x15e: movq -0x48(%rbp),%r13 hati_load_common+0x162: movq -0x40(%rbp),%r14 hati_load_common+0x166: movq -0x38(%rbp),%r15 > hat_memload+0x75::dis hat_memload+0x51: cmpq +0x419e40(%rip),%rbx hat_memload+0x58: jb +0x36 hat_memload+0x5a: movl %r14d,%ecx hat_memload+0x5d: xorl %r9d,%r9d hat_memload+0x60: movq %r12,%rdx hat_memload+0x63: orb $0x4,%ch hat_memload+0x66: movq %rbx,%rsi hat_memload+0x69: movq %r13,%rdi hat_memload+0x6c: movq %rax,(%rsp) hat_memload+0x70: call -0x365 hat_memload+0x75: testl %eax,%eax hat_memload+0x77: jne +0x2a hat_memload+0x79: movq -0x50(%rbp),%rbx hat_memload+0x7d: movq -0x48(%rbp),%r12 hat_memload+0x81: movq -0x40(%rbp),%r13 hat_memload+0x85: movq -0x38(%rbp),%r14 hat_memload+0x89: leave hat_memload+0x8a: ret hat_memload+0x8b: nopl 0x0(%rax,%rax) hat_memload+0x90: movl %r8d,%ecx hat_memload+0x93: movl %r14d,%edx > ****** the DALV4_snapcycle script contains the following. #! /bin/sh # # The Script to do a full snapshot and replica on $svol # #Get and set dayand hour for NOW and PAST NOW=$(date +"%a%d-%H") PAST=$(TZ=GMT+125 date +"%a%d-%H") # set variables svol="DAL1P2/DALV4" #record start time echo "$svol@$NOW Start" >> /vmt/timelog.txt date >> /vmt/timelog.txt # Destroy the prior $PAST snapshot echo "Destroying $svol@$PAST" /sbin/zfs destroy $svol@$PAST # Create the Snapshot echo "Creating $svol@$NOW" /sbin/zfs snapshot $svol@$NOW # Catch errors and send an email if test $? -ne 0 then echo "$svol@$NOW snapshot errored" | mailx -s "DALV4 error report" imemo at ellipseinc.com echo "$svol@$NOW died" >> /vmt/timelog.txt date >> /vmt/timelog.txt exit 1 fi #record finish time echo "$svol@$NOW Finish" >> /vmt/timelog.txt date >> /vmt/timelog.txt exit 0 ________________________________ This message is intended only for the use of the individual(s) or entity to which it is addressed and may contain information that is privileged, confidential, and/or proprietary to RealPage and its affiliated companies. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, forwarding or copying of this communication is prohibited without the express permission of the sender. If you have received this communication in error, please notify the sender immediately and delete the original message. -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephan.budach at jvm.de Thu Nov 23 05:52:11 2017 From: stephan.budach at jvm.de (Stephan Budach) Date: Thu, 23 Nov 2017 06:52:11 +0100 (CET) Subject: [OmniOS-discuss] omniOS/Samba/Kerberos? Message-ID: <1942719831.1527.1511416324017.JavaMail.stephan.budach@budy.stephanbudach.de> Hi, has anybody ever tried to authenticate a SMB client, e.g. a Mac, to a Samba server running on omniOS via Kerberos? My plan is to have our Macs get a ticket from our AD server and then have them logged in into our file servers via a valid Kerberos ticket. Would this work only using a full-fledged Samba4 server or would that also work using the kernel/smb? Cheers, Stephan -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5546 bytes Desc: not available URL: From al.slater at scluk.com Thu Nov 23 06:47:57 2017 From: al.slater at scluk.com (Al Slater) Date: Thu, 23 Nov 2017 06:47:57 +0000 Subject: [OmniOS-discuss] sudo update Message-ID: Hi, I have just updated a number of my omniosce boxes to r151022y, bringing in the sudo updates in r151022u. All my machines have BSM auditing enabled, and now I am seeing the following when using sudo sudo: au_preselect: Bad file number regards -- Al Slater From omnios at citrus-it.net Thu Nov 23 10:40:43 2017 From: omnios at citrus-it.net (Andy Fiddaman) Date: Thu, 23 Nov 2017 10:40:43 +0000 (UTC) Subject: [OmniOS-discuss] sudo update In-Reply-To: References: Message-ID: On Thu, 23 Nov 2017, Al Slater wrote: ; Hi, ; ; I have just updated a number of my omniosce boxes to r151022y, bringing ; in the sudo updates in r151022u. ; ; All my machines have BSM auditing enabled, and now I am seeing the ; following when using sudo ; ; sudo: au_preselect: Bad file number Hi, this is something we specifically tested along with the sudo update since auditing was an area that changed quite a bit. Could you please check that all of your packages are up-to-date (particularly SUNWcs) and that the output of the following commands matches on your system? r151022% auditrecord -e AUE_sudo sudo program sudo See sudo(1m) event ID 6650 AUE_sudo class lo,ua,as (0x00061000) header subject exec_arguments command args [text] error message (failure only) return r151022% grep sudo /etc/security/audit_event /usr/lib/audit/audit_record_attr /etc/security/audit_event:# sudo event /etc/security/audit_event:6650:AUE_sudo:sudo(1m):lo,ua,as /usr/lib/audit/audit_record_attr:label=AUE_sudo If the problem persists, please post the audit configuration that you're using so we can try and replicate (auditconfig -getflags) Thanks, Andy -- Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and Wales | Company number 4899123 From al.slater at scluk.com Thu Nov 23 11:06:26 2017 From: al.slater at scluk.com (Al Slater) Date: Thu, 23 Nov 2017 11:06:26 +0000 Subject: [OmniOS-discuss] sudo update In-Reply-To: References: Message-ID: Hi Andy, On 23/11/17 10:40, Andy Fiddaman wrote: > > On Thu, 23 Nov 2017, Al Slater wrote: > > ; Hi, > ; > ; I have just updated a number of my omniosce boxes to r151022y, bringing > ; in the sudo updates in r151022u. > ; > ; All my machines have BSM auditing enabled, and now I am seeing the > ; following when using sudo > ; > ; sudo: au_preselect: Bad file number > > Hi, this is something we specifically tested along with the sudo update > since auditing was an area that changed quite a bit. Could you please check > that all of your packages are up-to-date (particularly SUNWcs) and that the > output of the following commands matches on your system? > > r151022% auditrecord -e AUE_sudo > > sudo > program sudo See sudo(1m) > event ID 6650 AUE_sudo > class lo,ua,as (0x00061000) > header > subject > exec_arguments command args > [text] error message (failure only) > return > > r151022% grep sudo /etc/security/audit_event /usr/lib/audit/audit_record_attr > /etc/security/audit_event:# sudo event > /etc/security/audit_event:6650:AUE_sudo:sudo(1m):lo,ua,as > /usr/lib/audit/audit_record_attr:label=AUE_sudo > > If the problem persists, please post the audit configuration that you're > using so we can try and replicate (auditconfig -getflags) Ok, I can see the issue. The upgrade installed a audit_event.new into /etc/security, but it was not merged into our modified audit_event. I can see what I need to do to fix this now. Thank you for the pointers. -- Al Slater From geoffn at gnaa.net Fri Nov 24 02:56:01 2017 From: geoffn at gnaa.net (Geoff Nordli) Date: Thu, 23 Nov 2017 18:56:01 -0800 Subject: [OmniOS-discuss] Best way to share files with Mac? Message-ID: Hi. I have to support a few mac machines connecting to a few file shares running Omnios. They are reporting problems with the speed when using the "finder". I see there is a netatalk package I can download and compile off of sourceforge, which looks fairly current. Any suggestions on the best way forward to support Mac machines? thanks, Geoff From stephan.budach at jvm.de Fri Nov 24 06:57:14 2017 From: stephan.budach at jvm.de (Stephan Budach) Date: Fri, 24 Nov 2017 07:57:14 +0100 (CET) Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: References: Message-ID: <1213417486.305.1511506630473.JavaMail.stephan.budach@stephan.budach.jvm.de> Hi Geoff, ----- Urspr?ngliche Mail ----- > Von: "Geoff Nordli" > An: "omnios-discuss" > Gesendet: Freitag, 24. November 2017 03:56:01 > Betreff: [OmniOS-discuss] Best way to share files with Mac? > > Hi. > > I have to support a few mac machines connecting to a few file shares > running Omnios. > > They are reporting problems with the speed when using the "finder". > > I see there is a netatalk package I can download and compile off of > sourceforge, which looks fairly current. > > Any suggestions on the best way forward to support Mac machines? > > thanks, > > Geoff > well, the current Netatalk 3.1.x packages will of course get you Mac connectivity, but you should probably go with SMB instead, as no one actually knows, when Apple will pull AFP from macOS. I know that AFP/Netatalk is very fast - we have been using it on Solaris11 for a long time now, but it is in no way future-proof. I think it would make more sense to fix the speed issues, you're seeing when using SMB. What speed issues are you experiencing? Cheers, Stephan -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5546 bytes Desc: not available URL: From manuel at oetiker.ch Fri Nov 24 07:33:10 2017 From: manuel at oetiker.ch (Manuel Oetiker) Date: Fri, 24 Nov 2017 08:33:10 +0100 (CET) Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: References: Message-ID: <87360070.591846.1511508790003.JavaMail.zimbra@oetiker.ch> Hi We are using samba and it works well with macos. you can download our smb package from pkg.oetiker.ch or just run the compilation by your selfe. we store our build script under https://github.com/oposs/pkg.oetiker.ch-build/tree/master/build/samba4 disabling thumbnails preview helps speed up finder ... http://osxdaily.com/2013/01/10/disable-finder-icon-thumbnails-previews-mac-os-x/ cheers Manuel ----- Original Message ----- > From: "Geoff Nordli" > To: "omnios-discuss" > Sent: Friday, November 24, 2017 3:56:01 AM > Subject: [OmniOS-discuss] Best way to share files with Mac? > Hi. > > I have to support a few mac machines connecting to a few file shares > running Omnios. > > They are reporting problems with the speed when using the "finder". > > I see there is a netatalk package I can download and compile off of > sourceforge, which looks fairly current. > > Any suggestions on the best way forward to support Mac machines? > > thanks, > > Geoff > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss From bauernfeind at ipk-gatersleben.de Fri Nov 24 08:03:22 2017 From: bauernfeind at ipk-gatersleben.de (Jens Bauernfeind) Date: Fri, 24 Nov 2017 08:03:22 +0000 Subject: [OmniOS-discuss] omniOS/Samba/Kerberos? In-Reply-To: <1942719831.1527.1511416324017.JavaMail.stephan.budach@budy.stephanbudach.de> References: <1942719831.1527.1511416324017.JavaMail.stephan.budach@budy.stephanbudach.de> Message-ID: Hi Stephan, for test purposes I setup a kernel smb vm a few months ago. I can acquire a tgt via "kinit" on a mac and browse successfully via "Go -> Connect to server -> smb:///share" The only downside against a samba4: I cannot block (or "veto" in samba syntax) the creation of the useless finder files .apdisk/.DS_Store/.Trashes/.TemporaryItems So in every folder a mac user browses, you get at least .DS_Store, hurray. If you use samba4, you can block these files by adding: veto files = /.apdisk/.DS_Store/.Trashes/.TemporaryItems/ to the share definition Jens > -----Original Message----- > From: OmniOS-discuss [mailto:omnios-discuss-bounces at lists.omniti.com] > On Behalf Of Stephan Budach > Sent: Donnerstag, 23. November 2017 06:52 > To: omnios-discuss > Subject: [OmniOS-discuss] omniOS/Samba/Kerberos? > > Hi, > > has anybody ever tried to authenticate a SMB client, e.g. a Mac, to a Samba > server running on omniOS via Kerberos? My plan is to have our Macs get a > ticket from our AD server and then have them logged in into our file servers > via a valid Kerberos ticket. Would this work only using a full-fledged > Samba4 > server or would that also work using the kernel/smb? > > Cheers, > Stephan > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6023 bytes Desc: not available URL: From geoffn at gnaa.net Fri Nov 24 16:32:13 2017 From: geoffn at gnaa.net (Geoff Nordli) Date: Fri, 24 Nov 2017 08:32:13 -0800 Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: <87360070.591846.1511508790003.JavaMail.zimbra@oetiker.ch> References: <87360070.591846.1511508790003.JavaMail.zimbra@oetiker.ch> Message-ID: <471a68cd-276a-c7b6-fafb-b49504c47359@gnaa.net> Hi Manuel. Are there other reasons why you decided to go with samba? thanks, Geoff On 2017-11-23 11:33 PM, Manuel Oetiker wrote: > Hi > > We are using samba and it works well with macos. > > you can download our smb package from pkg.oetiker.ch or just run the compilation by your selfe. > we store our build script under https://github.com/oposs/pkg.oetiker.ch-build/tree/master/build/samba4 > > disabling thumbnails preview helps speed up finder ... > http://osxdaily.com/2013/01/10/disable-finder-icon-thumbnails-previews-mac-os-x/ > > cheers Manuel > > ----- Original Message ----- >> From: "Geoff Nordli" >> To: "omnios-discuss" >> Sent: Friday, November 24, 2017 3:56:01 AM >> Subject: [OmniOS-discuss] Best way to share files with Mac? >> Hi. >> >> I have to support a few mac machines connecting to a few file shares >> running Omnios. >> >> They are reporting problems with the speed when using the "finder". >> >> I see there is a netatalk package I can download and compile off of >> sourceforge, which looks fairly current. >> >> Any suggestions on the best way forward to support Mac machines? >> >> thanks, >> >> Geoff >> >> _______________________________________________ >> OmniOS-discuss mailing list >> OmniOS-discuss at lists.omniti.com >> http://lists.omniti.com/mailman/listinfo/omnios-discuss From manuel at oetiker.ch Fri Nov 24 16:40:13 2017 From: manuel at oetiker.ch (Manuel Oetiker) Date: Fri, 24 Nov 2017 17:40:13 +0100 (CET) Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: <471a68cd-276a-c7b6-fafb-b49504c47359@gnaa.net> References: <87360070.591846.1511508790003.JavaMail.zimbra@oetiker.ch> <471a68cd-276a-c7b6-fafb-b49504c47359@gnaa.net> Message-ID: <1677409733.599848.1511541613884.JavaMail.zimbra@oetiker.ch> Hi Geoff I have a mixed environment with mac/pc/linux smb can talk to everyone .. cheers Manuel ----- Original Message ----- > From: "Geoff Nordli" > To: "Manuel Oetiker" > Cc: "omnios-discuss" > Sent: Friday, November 24, 2017 5:32:13 PM > Subject: Re: [OmniOS-discuss] Best way to share files with Mac? > Hi Manuel. > > Are there other reasons why you decided to go with samba? > > thanks, > > Geoff > > > On 2017-11-23 11:33 PM, Manuel Oetiker wrote: >> Hi >> >> We are using samba and it works well with macos. >> >> you can download our smb package from pkg.oetiker.ch or just run the compilation >> by your selfe. >> we store our build script under >> https://github.com/oposs/pkg.oetiker.ch-build/tree/master/build/samba4 >> >> disabling thumbnails preview helps speed up finder ... >> http://osxdaily.com/2013/01/10/disable-finder-icon-thumbnails-previews-mac-os-x/ >> >> cheers Manuel >> >> ----- Original Message ----- >>> From: "Geoff Nordli" >>> To: "omnios-discuss" >>> Sent: Friday, November 24, 2017 3:56:01 AM >>> Subject: [OmniOS-discuss] Best way to share files with Mac? >>> Hi. >>> >>> I have to support a few mac machines connecting to a few file shares >>> running Omnios. >>> >>> They are reporting problems with the speed when using the "finder". >>> >>> I see there is a netatalk package I can download and compile off of >>> sourceforge, which looks fairly current. >>> >>> Any suggestions on the best way forward to support Mac machines? >>> >>> thanks, >>> >>> Geoff >>> >>> _______________________________________________ >>> OmniOS-discuss mailing list >>> OmniOS-discuss at lists.omniti.com > >> http://lists.omniti.com/mailman/listinfo/omnios-discuss From geoffn at gnaa.net Fri Nov 24 17:05:17 2017 From: geoffn at gnaa.net (Geoff Nordli) Date: Fri, 24 Nov 2017 09:05:17 -0800 Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: <1677409733.599848.1511541613884.JavaMail.zimbra@oetiker.ch> References: <87360070.591846.1511508790003.JavaMail.zimbra@oetiker.ch> <471a68cd-276a-c7b6-fafb-b49504c47359@gnaa.net> <1677409733.599848.1511541613884.JavaMail.zimbra@oetiker.ch> Message-ID: What made you choose Samba vs the built-in SMB server? Active Directory domain controller? On 2017-11-24 08:40 AM, Manuel Oetiker wrote: > Hi Geoff > > I have a mixed environment with mac/pc/linux smb can talk to everyone .. > > cheers Manuel > > > ----- Original Message ----- >> From: "Geoff Nordli" >> To: "Manuel Oetiker" >> Cc: "omnios-discuss" >> Sent: Friday, November 24, 2017 5:32:13 PM >> Subject: Re: [OmniOS-discuss] Best way to share files with Mac? >> Hi Manuel. >> >> Are there other reasons why you decided to go with samba? >> >> thanks, >> >> Geoff >> >> >> On 2017-11-23 11:33 PM, Manuel Oetiker wrote: >>> Hi >>> >>> We are using samba and it works well with macos. >>> >>> you can download our smb package from pkg.oetiker.ch or just run the compilation >>> by your selfe. >>> we store our build script under >>> https://github.com/oposs/pkg.oetiker.ch-build/tree/master/build/samba4 >>> >>> disabling thumbnails preview helps speed up finder ... >>> http://osxdaily.com/2013/01/10/disable-finder-icon-thumbnails-previews-mac-os-x/ >>> >>> cheers Manuel >>> >>> ----- Original Message ----- >>>> From: "Geoff Nordli" >>>> To: "omnios-discuss" >>>> Sent: Friday, November 24, 2017 3:56:01 AM >>>> Subject: [OmniOS-discuss] Best way to share files with Mac? >>>> Hi. >>>> >>>> I have to support a few mac machines connecting to a few file shares >>>> running Omnios. >>>> >>>> They are reporting problems with the speed when using the "finder". >>>> >>>> I see there is a netatalk package I can download and compile off of >>>> sourceforge, which looks fairly current. >>>> >>>> Any suggestions on the best way forward to support Mac machines? >>>> >>>> thanks, >>>> >>>> Geoff >>>> >>>> _______________________________________________ >>>> OmniOS-discuss mailing list >>>> OmniOS-discuss at lists.omniti.com >>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss From geoffn at gnaa.net Fri Nov 24 17:06:52 2017 From: geoffn at gnaa.net (Geoff Nordli) Date: Fri, 24 Nov 2017 09:06:52 -0800 Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: <1213417486.305.1511506630473.JavaMail.stephan.budach@stephan.budach.jvm.de> References: <1213417486.305.1511506630473.JavaMail.stephan.budach@stephan.budach.jvm.de> Message-ID: <4bdcc0b1-c725-988f-3df7-c97f28a62c4a@gnaa.net> On 2017-11-23 10:57 PM, Stephan Budach wrote: > Hi Geoff, > > ----- Urspr?ngliche Mail ----- >> Von: "Geoff Nordli" >> An: "omnios-discuss" >> Gesendet: Freitag, 24. November 2017 03:56:01 >> Betreff: [OmniOS-discuss] Best way to share files with Mac? >> >> Hi. >> >> I have to support a few mac machines connecting to a few file shares >> running Omnios. >> >> They are reporting problems with the speed when using the "finder". >> >> I see there is a netatalk package I can download and compile off of >> sourceforge, which looks fairly current. >> >> Any suggestions on the best way forward to support Mac machines? >> >> thanks, >> >> Geoff >> > well, the current Netatalk 3.1.x packages will of course get you Mac connectivity, but you should probably go with SMB instead, as no one actually knows, when Apple will pull AFP from macOS. I know that AFP/Netatalk is very fast - we have been using it on Solaris11 for a long time now, but it is in no way future-proof. > > I think it would make more sense to fix the speed issues, you're seeing when using SMB. What speed issues are you experiencing? > > Cheers, > Stephan Hello Stephan. I am not 100% sure exactly what the issues are with the finder.? I wanted to make sure I was focusing on the right protocol first. Manuel suggests going with Samba, which I have been looking at for a couple of years, but nothing really made me want to put the effort into it. thanks!! Geoff From stephan.budach at jvm.de Fri Nov 24 17:39:35 2017 From: stephan.budach at jvm.de (Stephan Budach) Date: Fri, 24 Nov 2017 18:39:35 +0100 (CET) Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: <4bdcc0b1-c725-988f-3df7-c97f28a62c4a@gnaa.net> References: <1213417486.305.1511506630473.JavaMail.stephan.budach@stephan.budach.jvm.de> <4bdcc0b1-c725-988f-3df7-c97f28a62c4a@gnaa.net> Message-ID: <967041233.708.1511545162826.JavaMail.stephan.budach@budy.stephanbudach.de> Hi Geoff, ----- Urspr?ngliche Mail ----- > Von: "Geoff Nordli" > An: "Stephan Budach" > CC: "omnios-discuss" > Gesendet: Freitag, 24. November 2017 18:06:52 > Betreff: Re: [OmniOS-discuss] Best way to share files with Mac? > > > > On 2017-11-23 10:57 PM, Stephan Budach wrote: > > Hi Geoff, > > > > ----- Urspr?ngliche Mail ----- > >> Von: "Geoff Nordli" > >> An: "omnios-discuss" > >> Gesendet: Freitag, 24. November 2017 03:56:01 > >> Betreff: [OmniOS-discuss] Best way to share files with Mac? > >> > >> Hi. > >> > >> I have to support a few mac machines connecting to a few file > >> shares > >> running Omnios. > >> > >> They are reporting problems with the speed when using the > >> "finder". > >> > >> I see there is a netatalk package I can download and compile off > >> of > >> sourceforge, which looks fairly current. > >> > >> Any suggestions on the best way forward to support Mac machines? > >> > >> thanks, > >> > >> Geoff > >> > > well, the current Netatalk 3.1.x packages will of course get you > > Mac connectivity, but you should probably go with SMB instead, as > > no one actually knows, when Apple will pull AFP from macOS. I know > > that AFP/Netatalk is very fast - we have been using it on > > Solaris11 for a long time now, but it is in no way future-proof. > > > > I think it would make more sense to fix the speed issues, you're > > seeing when using SMB. What speed issues are you experiencing? > > > > Cheers, > > Stephan > > Hello Stephan. > > I am not 100% sure exactly what the issues are with the finder.? I > wanted to make sure I was focusing on the right protocol first. > > Manuel suggests going with Samba, which I have been looking at for a > couple of years, but nothing really made me want to put the effort > into it. > > thanks!! > Geoff this is, what I would suggest as well. Actually, we just started an internal project to finally move from AFP to SMB. Although I know, that AFP beats the pants off of SMB, AFP will go away and it's better to switch asap and in your case, not get tainted by AFP's speed in the first place? Better focus on what bothers you when using SMB and getting that sorted out. Cheers, Stephan -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5546 bytes Desc: not available URL: From stephan.budach at jvm.de Fri Nov 24 17:41:16 2017 From: stephan.budach at jvm.de (Stephan Budach) Date: Fri, 24 Nov 2017 18:41:16 +0100 (CET) Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: References: <87360070.591846.1511508790003.JavaMail.zimbra@oetiker.ch> <471a68cd-276a-c7b6-fafb-b49504c47359@gnaa.net> <1677409733.599848.1511541613884.JavaMail.zimbra@oetiker.ch> Message-ID: <1578704036.709.1511545261252.JavaMail.stephan.budach@budy.stephanbudach.de> ----- Urspr?ngliche Mail ----- > Von: "Geoff Nordli" > An: "Manuel Oetiker" > CC: "omnios-discuss" > Gesendet: Freitag, 24. November 2017 18:05:17 > Betreff: Re: [OmniOS-discuss] Best way to share files with Mac? > > What made you choose Samba vs the built-in SMB server? > > Active Directory domain controller? > Yeah, what was it? I already reveived word, that I can use AD/Kerberos to authenticate my Macs to Kernel/SMB. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5546 bytes Desc: not available URL: From david.ledger at ivdcs.co.uk Fri Nov 24 18:26:44 2017 From: david.ledger at ivdcs.co.uk (David Ledger) Date: Fri, 24 Nov 2017 18:26:44 +0000 Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: <1578704036.709.1511545261252.JavaMail.stephan.budach@budy.stephanbudach.de> References: <87360070.591846.1511508790003.JavaMail.zimbra@oetiker.ch> <471a68cd-276a-c7b6-fafb-b49504c47359@gnaa.net> <1677409733.599848.1511541613884.JavaMail.zimbra@oetiker.ch> <1578704036.709.1511545261252.JavaMail.stephan.budach@budy.stephanbudach.de> Message-ID: On 24 Nov 2017, at 17:41, Stephan Budach wrote: > ----- Urspr?ngliche Mail ----- >> Von: "Geoff Nordli" >> An: "Manuel Oetiker" >> CC: "omnios-discuss" >> Gesendet: Freitag, 24. November 2017 18:05:17 >> Betreff: Re: [OmniOS-discuss] Best way to share files with Mac? >> >> What made you choose Samba vs the built-in SMB server? >> >> Active Directory domain controller? >> > > Yeah, what was it? I already reveived word, that I can use AD/Kerberos > to authenticate my Macs to Kernel/SMB. > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss Maybe getting off topic, but what do people use to update Mac user passwords and keychain passwords when they are changed in AD from an app on OmniOS? David From geoffn at gnaa.net Fri Nov 24 18:52:27 2017 From: geoffn at gnaa.net (Geoff Nordli) Date: Fri, 24 Nov 2017 10:52:27 -0800 Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: <87360070.591846.1511508790003.JavaMail.zimbra@oetiker.ch> References: <87360070.591846.1511508790003.JavaMail.zimbra@oetiker.ch> Message-ID: <7da90310-3bdc-bbf8-f037-7edb260a4bd4@gnaa.net> I am trying to build it, but it uses gcc51. That package isn't in the Omniosce core or extra repository. Are you using the https://pkg.omniti.com/omnios/r151022 repo? On 2017-11-23 11:33 PM, Manuel Oetiker wrote: > Hi > > We are using samba and it works well with macos. > > you can download our smb package from pkg.oetiker.ch or just run the compilation by your selfe. > we store our build script under https://github.com/oposs/pkg.oetiker.ch-build/tree/master/build/samba4 > > disabling thumbnails preview helps speed up finder ... > http://osxdaily.com/2013/01/10/disable-finder-icon-thumbnails-previews-mac-os-x/ > > cheers Manuel > > ----- Original Message ----- >> From: "Geoff Nordli" >> To: "omnios-discuss" >> Sent: Friday, November 24, 2017 3:56:01 AM >> Subject: [OmniOS-discuss] Best way to share files with Mac? >> Hi. >> >> I have to support a few mac machines connecting to a few file shares >> running Omnios. >> >> They are reporting problems with the speed when using the "finder". >> >> I see there is a netatalk package I can download and compile off of >> sourceforge, which looks fairly current. >> >> Any suggestions on the best way forward to support Mac machines? >> >> thanks, >> >> Geoff >> >> _______________________________________________ >> OmniOS-discuss mailing list >> OmniOS-discuss at lists.omniti.com >> http://lists.omniti.com/mailman/listinfo/omnios-discuss From stephan.budach at jvm.de Fri Nov 24 19:38:53 2017 From: stephan.budach at jvm.de (Stephan Budach) Date: Fri, 24 Nov 2017 20:38:53 +0100 (CET) Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: References: <87360070.591846.1511508790003.JavaMail.zimbra@oetiker.ch> <471a68cd-276a-c7b6-fafb-b49504c47359@gnaa.net> <1677409733.599848.1511541613884.JavaMail.zimbra@oetiker.ch> <1578704036.709.1511545261252.JavaMail.stephan.budach@budy.stephanbudach.de> Message-ID: <1754006349.732.1511552319867.JavaMail.stephan.budach@budy.stephanbudach.de> ----- Urspr?ngliche Mail ----- > Von: "David Ledger" > An: "omnios-discuss" > Gesendet: Freitag, 24. November 2017 19:26:44 > Betreff: Re: [OmniOS-discuss] Best way to share files with Mac? > > On 24 Nov 2017, at 17:41, Stephan Budach wrote: > > > ----- Urspr?ngliche Mail ----- > >> Von: "Geoff Nordli" > >> An: "Manuel Oetiker" > >> CC: "omnios-discuss" > >> Gesendet: Freitag, 24. November 2017 18:05:17 > >> Betreff: Re: [OmniOS-discuss] Best way to share files with Mac? > >> > >> What made you choose Samba vs the built-in SMB server? > >> > >> Active Directory domain controller? > >> > > > > Yeah, what was it? I already reveived word, that I can use > > AD/Kerberos > > to authenticate my Macs to Kernel/SMB. > > _______________________________________________ > > OmniOS-discuss mailing list > > OmniOS-discuss at lists.omniti.com > > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > Maybe getting off topic, but what do people use to update Mac user > passwords and keychain passwords when they are changed in AD from an > app > on OmniOS? > > David Tried NoMAD? Cheers, Stephan -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5546 bytes Desc: not available URL: From manuel at oetiker.ch Fri Nov 24 19:49:49 2017 From: manuel at oetiker.ch (Manuel Oetiker) Date: Fri, 24 Nov 2017 20:49:49 +0100 (CET) Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: <7da90310-3bdc-bbf8-f037-7edb260a4bd4@gnaa.net> References: <87360070.591846.1511508790003.JavaMail.zimbra@oetiker.ch> <7da90310-3bdc-bbf8-f037-7edb260a4bd4@gnaa.net> Message-ID: <1088095933.602114.1511552989926.JavaMail.zimbra@oetiker.ch> hi Geoff you should switch to https://omniosce.org cheers Manuel ----- Original Message ----- > From: "Geoff Nordli" > Cc: "omnios-discuss" > Sent: Friday, November 24, 2017 7:52:27 PM > Subject: Re: [OmniOS-discuss] Best way to share files with Mac? > I am trying to build it, but it uses gcc51. > > That package isn't in the Omniosce core or extra repository. > > Are you using the https://pkg.omniti.com/omnios/r151022 repo? > > > On 2017-11-23 11:33 PM, Manuel Oetiker wrote: >> Hi >> >> We are using samba and it works well with macos. >> >> you can download our smb package from pkg.oetiker.ch or just run the compilation >> by your selfe. >> we store our build script under >> https://github.com/oposs/pkg.oetiker.ch-build/tree/master/build/samba4 >> >> disabling thumbnails preview helps speed up finder ... >> http://osxdaily.com/2013/01/10/disable-finder-icon-thumbnails-previews-mac-os-x/ >> >> cheers Manuel >> >> ----- Original Message ----- >>> From: "Geoff Nordli" >>> To: "omnios-discuss" >>> Sent: Friday, November 24, 2017 3:56:01 AM >>> Subject: [OmniOS-discuss] Best way to share files with Mac? >>> Hi. >>> >>> I have to support a few mac machines connecting to a few file shares >>> running Omnios. >>> >>> They are reporting problems with the speed when using the "finder". >>> >>> I see there is a netatalk package I can download and compile off of >>> sourceforge, which looks fairly current. >>> >>> Any suggestions on the best way forward to support Mac machines? >>> >>> thanks, >>> >>> Geoff >>> >>> _______________________________________________ >>> OmniOS-discuss mailing list >>> OmniOS-discuss at lists.omniti.com >>> http://lists.omniti.com/mailman/listinfo/omnios-discuss > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss From geoffn at gnaa.net Fri Nov 24 20:28:53 2017 From: geoffn at gnaa.net (Geoff Nordli) Date: Fri, 24 Nov 2017 12:28:53 -0800 Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: <1088095933.602114.1511552989926.JavaMail.zimbra@oetiker.ch> References: <87360070.591846.1511508790003.JavaMail.zimbra@oetiker.ch> <7da90310-3bdc-bbf8-f037-7edb260a4bd4@gnaa.net> <1088095933.602114.1511552989926.JavaMail.zimbra@oetiker.ch> Message-ID: <1b7cb87e-e98b-298c-f135-7385ffd34acb@gnaa.net> That is what I am currently running. #cat /etc/release ? OmniOS v11 r151024c ? Copyright 2017 OmniTI Computer Consulting, Inc. All rights reserved. ? Copyright 2017 OmniOS Community Edition (OmniOSce) Association. ? All rights reserved. Use is subject to license terms. #pkg publisher PUBLISHER?????????????????? TYPE???? STATUS P LOCATION extra.omnios??????????????? origin?? online F https://pkg.omniosce.org/r151024/extra/ omnios????????????????????? origin?? online F https://pkg.omniosce.org/r151024/core/ I think i am missing something though, because it seems that it is installed #sudo pkg install gcc51 No updates necessary for this image. It seems there is a gcc51 available in the catalog. # pkg search gcc51 INDEX????? ACTION VALUE????????????????? PACKAGE pkg.fmri?? set??? omnios/developer/gcc51 pkg:/developer/gcc51 at 5.1.0-0.151024 but when I list the packages, it doesn't show up pkg list | grep gcc5 developer/gcc5 (omnios) 5.5.0-0.151024???????????? i-- developer/gcc5/libgmp-gcc5 (omnios) 6.1.2-0.151024???????????? i-- developer/gcc5/libmpc-gcc5 (omnios) 1.0.3-0.151024???????????? i-- developer/gcc5/libmpfr-gcc5 (omnios) 3.1.5-0.151024???????????? i-- any ideas? thanks!! On 2017-11-24 11:49 AM, Manuel Oetiker wrote: > hi Geoff > > you should switch to https://omniosce.org > > cheers Manuel > > > ----- Original Message ----- >> From: "Geoff Nordli" >> Cc: "omnios-discuss" >> Sent: Friday, November 24, 2017 7:52:27 PM >> Subject: Re: [OmniOS-discuss] Best way to share files with Mac? >> I am trying to build it, but it uses gcc51. >> >> That package isn't in the Omniosce core or extra repository. >> >> Are you using the https://pkg.omniti.com/omnios/r151022 repo? >> >> >> On 2017-11-23 11:33 PM, Manuel Oetiker wrote: >>> Hi >>> >>> We are using samba and it works well with macos. >>> >>> you can download our smb package from pkg.oetiker.ch or just run the compilation >>> by your selfe. >>> we store our build script under >>> https://github.com/oposs/pkg.oetiker.ch-build/tree/master/build/samba4 >>> >>> disabling thumbnails preview helps speed up finder ... >>> http://osxdaily.com/2013/01/10/disable-finder-icon-thumbnails-previews-mac-os-x/ >>> >>> cheers Manuel >>> >>> ----- Original Message ----- >>>> From: "Geoff Nordli" >>>> To: "omnios-discuss" >>>> Sent: Friday, November 24, 2017 3:56:01 AM >>>> Subject: [OmniOS-discuss] Best way to share files with Mac? >>>> Hi. >>>> >>>> I have to support a few mac machines connecting to a few file shares >>>> running Omnios. >>>> >>>> They are reporting problems with the speed when using the "finder". >>>> >>>> I see there is a netatalk package I can download and compile off of >>>> sourceforge, which looks fairly current. >>>> >>>> Any suggestions on the best way forward to support Mac machines? >>>> >>>> thanks, >>>> >>>> Geoff >>>> >>>> _______________________________________________ >>>> OmniOS-discuss mailing list >>>> OmniOS-discuss at lists.omniti.com >>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss >> _______________________________________________ >> OmniOS-discuss mailing list >> OmniOS-discuss at lists.omniti.com >> http://lists.omniti.com/mailman/listinfo/omnios-discuss From omnios at citrus-it.net Fri Nov 24 20:44:18 2017 From: omnios at citrus-it.net (Andy Fiddaman) Date: Fri, 24 Nov 2017 20:44:18 +0000 Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: <1b7cb87e-e98b-298c-f135-7385ffd34acb@gnaa.net> References: <87360070.591846.1511508790003.JavaMail.zimbra@oetiker.ch> <7da90310-3bdc-bbf8-f037-7edb260a4bd4@gnaa.net> <1088095933.602114.1511552989926.JavaMail.zimbra@oetiker.ch> <1b7cb87e-e98b-298c-f135-7385ffd34acb@gnaa.net> Message-ID: <5801BBE7-7EA8-40AD-B74E-B26E4261BD49@citrus-it.net> The package is now called just ?gcc5? gcc51 is there as a renamed package. > On 24 Nov 2017, at 20:28, Geoff Nordli wrote: > > That is what I am currently running. > > #cat /etc/release > OmniOS v11 r151024c > Copyright 2017 OmniTI Computer Consulting, Inc. All rights reserved. > Copyright 2017 OmniOS Community Edition (OmniOSce) Association. > All rights reserved. Use is subject to license terms. > > #pkg publisher > PUBLISHER TYPE STATUS P LOCATION > extra.omnios origin online F https://pkg.omniosce.org/r151024/extra/ > omnios origin online F https://pkg.omniosce.org/r151024/core/ > > > I think i am missing something though, because it seems that it is installed > > #sudo pkg install gcc51 > No updates necessary for this image. > > It seems there is a gcc51 available in the catalog. > > # pkg search gcc51 > INDEX ACTION VALUE PACKAGE > pkg.fmri set omnios/developer/gcc51 pkg:/developer/gcc51 at 5.1.0-0.151024 > > > but when I list the packages, it doesn't show up > > pkg list | grep gcc5 > developer/gcc5 (omnios) 5.5.0-0.151024 i-- > developer/gcc5/libgmp-gcc5 (omnios) 6.1.2-0.151024 i-- > developer/gcc5/libmpc-gcc5 (omnios) 1.0.3-0.151024 i-- > developer/gcc5/libmpfr-gcc5 (omnios) 3.1.5-0.151024 i-- > > > any ideas? > > thanks!! > > > >> On 2017-11-24 11:49 AM, Manuel Oetiker wrote: >> hi Geoff >> >> you should switch to https://omniosce.org >> >> cheers Manuel >> >> >> ----- Original Message ----- >>> From: "Geoff Nordli" >>> Cc: "omnios-discuss" >>> Sent: Friday, November 24, 2017 7:52:27 PM >>> Subject: Re: [OmniOS-discuss] Best way to share files with Mac? >>> I am trying to build it, but it uses gcc51. >>> >>> That package isn't in the Omniosce core or extra repository. >>> >>> Are you using the https://pkg.omniti.com/omnios/r151022 repo? >>> >>> >>>> On 2017-11-23 11:33 PM, Manuel Oetiker wrote: >>>> Hi >>>> >>>> We are using samba and it works well with macos. >>>> >>>> you can download our smb package from pkg.oetiker.ch or just run the compilation >>>> by your selfe. >>>> we store our build script under >>>> https://github.com/oposs/pkg.oetiker.ch-build/tree/master/build/samba4 >>>> >>>> disabling thumbnails preview helps speed up finder ... >>>> http://osxdaily.com/2013/01/10/disable-finder-icon-thumbnails-previews-mac-os-x/ >>>> >>>> cheers Manuel >>>> >>>> ----- Original Message ----- >>>>> From: "Geoff Nordli" >>>>> To: "omnios-discuss" >>>>> Sent: Friday, November 24, 2017 3:56:01 AM >>>>> Subject: [OmniOS-discuss] Best way to share files with Mac? >>>>> Hi. >>>>> >>>>> I have to support a few mac machines connecting to a few file shares >>>>> running Omnios. >>>>> >>>>> They are reporting problems with the speed when using the "finder". >>>>> >>>>> I see there is a netatalk package I can download and compile off of >>>>> sourceforge, which looks fairly current. >>>>> >>>>> Any suggestions on the best way forward to support Mac machines? >>>>> >>>>> thanks, >>>>> >>>>> Geoff >>>>> >>>>> _______________________________________________ >>>>> OmniOS-discuss mailing list >>>>> OmniOS-discuss at lists.omniti.com >>>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss >>> _______________________________________________ >>> OmniOS-discuss mailing list >>> OmniOS-discuss at lists.omniti.com >>> http://lists.omniti.com/mailman/listinfo/omnios-discuss > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -- Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and Wales | Company number 4899123 From geoffn at gnaa.net Fri Nov 24 20:57:51 2017 From: geoffn at gnaa.net (Geoff Nordli) Date: Fri, 24 Nov 2017 12:57:51 -0800 Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: <5801BBE7-7EA8-40AD-B74E-B26E4261BD49@citrus-it.net> References: <87360070.591846.1511508790003.JavaMail.zimbra@oetiker.ch> <7da90310-3bdc-bbf8-f037-7edb260a4bd4@gnaa.net> <1088095933.602114.1511552989926.JavaMail.zimbra@oetiker.ch> <1b7cb87e-e98b-298c-f135-7385ffd34acb@gnaa.net> <5801BBE7-7EA8-40AD-B74E-B26E4261BD49@citrus-it.net> Message-ID: <6500993c-8f2f-d74d-4b26-ebe5c7fda2bb@gnaa.net> looking at the build script for that package, in the functions.sh file, it is explicitly looking for the 5.1. BasicRequirements(){ ??? local needed="" ??? [[ -x /opt/gcc-5.1.0/bin/gcc ]] || needed+=" developer/gcc51" Obviously, easy enough to fix that script, just wondering if Samba should compile well with 5.5. On 2017-11-24 12:44 PM, Andy Fiddaman wrote: > The package is now called just ?gcc5? > gcc51 is there as a renamed package. > >> On 24 Nov 2017, at 20:28, Geoff Nordli wrote: >> >> That is what I am currently running. >> >> #cat /etc/release >> OmniOS v11 r151024c >> Copyright 2017 OmniTI Computer Consulting, Inc. All rights reserved. >> Copyright 2017 OmniOS Community Edition (OmniOSce) Association. >> All rights reserved. Use is subject to license terms. >> >> #pkg publisher >> PUBLISHER TYPE STATUS P LOCATION >> extra.omnios origin online F https://pkg.omniosce.org/r151024/extra/ >> omnios origin online F https://pkg.omniosce.org/r151024/core/ >> >> >> I think i am missing something though, because it seems that it is installed >> >> #sudo pkg install gcc51 >> No updates necessary for this image. >> >> It seems there is a gcc51 available in the catalog. >> >> # pkg search gcc51 >> INDEX ACTION VALUE PACKAGE >> pkg.fmri set omnios/developer/gcc51 pkg:/developer/gcc51 at 5.1.0-0.151024 >> >> >> but when I list the packages, it doesn't show up >> >> pkg list | grep gcc5 >> developer/gcc5 (omnios) 5.5.0-0.151024 i-- >> developer/gcc5/libgmp-gcc5 (omnios) 6.1.2-0.151024 i-- >> developer/gcc5/libmpc-gcc5 (omnios) 1.0.3-0.151024 i-- >> developer/gcc5/libmpfr-gcc5 (omnios) 3.1.5-0.151024 i-- >> >> >> any ideas? >> >> thanks!! >> >> >> >>> On 2017-11-24 11:49 AM, Manuel Oetiker wrote: >>> hi Geoff >>> >>> you should switch to https://omniosce.org >>> >>> cheers Manuel >>> >>> >>> ----- Original Message ----- >>>> From: "Geoff Nordli" >>>> Cc: "omnios-discuss" >>>> Sent: Friday, November 24, 2017 7:52:27 PM >>>> Subject: Re: [OmniOS-discuss] Best way to share files with Mac? >>>> I am trying to build it, but it uses gcc51. >>>> >>>> That package isn't in the Omniosce core or extra repository. >>>> >>>> Are you using the https://pkg.omniti.com/omnios/r151022 repo? >>>> >>>> >>>>> On 2017-11-23 11:33 PM, Manuel Oetiker wrote: >>>>> Hi >>>>> >>>>> We are using samba and it works well with macos. >>>>> >>>>> you can download our smb package from pkg.oetiker.ch or just run the compilation >>>>> by your selfe. >>>>> we store our build script under >>>>> https://github.com/oposs/pkg.oetiker.ch-build/tree/master/build/samba4 >>>>> >>>>> disabling thumbnails preview helps speed up finder ... >>>>> http://osxdaily.com/2013/01/10/disable-finder-icon-thumbnails-previews-mac-os-x/ >>>>> >>>>> cheers Manuel >>>>> >>>>> ----- Original Message ----- >>>>>> From: "Geoff Nordli" >>>>>> To: "omnios-discuss" >>>>>> Sent: Friday, November 24, 2017 3:56:01 AM >>>>>> Subject: [OmniOS-discuss] Best way to share files with Mac? >>>>>> Hi. >>>>>> >>>>>> I have to support a few mac machines connecting to a few file shares >>>>>> running Omnios. >>>>>> >>>>>> They are reporting problems with the speed when using the "finder". >>>>>> >>>>>> I see there is a netatalk package I can download and compile off of >>>>>> sourceforge, which looks fairly current. >>>>>> >>>>>> Any suggestions on the best way forward to support Mac machines? >>>>>> >>>>>> thanks, >>>>>> >>>>>> Geoff >>>>>> >>>>>> _______________________________________________ >>>>>> OmniOS-discuss mailing list >>>>>> OmniOS-discuss at lists.omniti.com >>>>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss >>>> _______________________________________________ >>>> OmniOS-discuss mailing list >>>> OmniOS-discuss at lists.omniti.com >>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss >> _______________________________________________ >> OmniOS-discuss mailing list >> OmniOS-discuss at lists.omniti.com >> http://lists.omniti.com/mailman/listinfo/omnios-discuss From cf at ferebee.net Sat Nov 25 14:45:44 2017 From: cf at ferebee.net (Chris Ferebee) Date: Sat, 25 Nov 2017 15:45:44 +0100 Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: References: Message-ID: Hi Geoff, I love the way you put this: > They are reporting problems with the speed when using the "finder". Oh, yes. I spent months of my life in 2014 fighting the Finder vs. a major installation of netatalk, which I deployed on SmartOS. We have a large server (dual 6-core XEON, 128 GB RAM, 22 x 4 TB SAS, STEC ZeusRAM) running as a fileserver for Macs. The client does motion graphics and has a very large number of files, 100+ million on the largest share. (Not more than a few thousand files per directory, though.) What we saw was that opening the Finder to a directory on the AFP share would show a blank window for 20?180 seconds before displaying the contents, even if there were maybe just 10?20 subdirectories to display. Then, as long as the Finder window was open, it would peg one CPU core on the server at 100%, even though the display did not change. It turned out that the Finder was looping continually through files several subdirectories deep, querying extended attributes. Due to the way netatalk is coded, this requires a call to getcwd() each time, which is very expensive on Solaris. (getcwd() = get the path name of the current working directory.) A SmartOS engineer was kind enough to advise me on this, and basically told me: if you have getcwd() in your hot path, you are screwed. This is probably a reason why the problem, though actually a netatalk issue, is less pronounced on Linux, where getcwd() is not as expensive as on Solaris. I never did get to the bottom of this. It appears that it doesn?t happen when the Finder is talking to Apple?s own AFP server, perhaps because there the Finder is able to use FSEvents to track changes. Unfortunately, it appears that netatalk has never fully addressed this, at least I haven?t seen anything indicating that it has gained FSEvents supports in the past years. Here is what netatalk dev Ralph B?hme had to say: In the end, I switched the client to a (commercial, expensive) AFP server, HELIOS EtherShare, and all problems went away, performance as expected, and I didn?t investigate further. If you are dealing with Adobe applications, be aware that there are a number of reasons why they do not work well on a Mac over SMB. We didn?t get past a hard maximum path length of 254 characters, but there are others. I?m happy to discuss this further, and would be quite interested to find a less-expensive solution for large-scale file service for Macs. We can take it off-list if it goes any further off topic. Good luck, Chris > Am 24.11.2017 um 03:56 schrieb Geoff Nordli : > > Hi. > > I have to support a few mac machines connecting to a few file shares running Omnios. > > They are reporting problems with the speed when using the "finder". > > I see there is a netatalk package I can download and compile off of sourceforge, which looks fairly current. > > Any suggestions on the best way forward to support Mac machines? > > thanks, > > Geoff > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss From danmcd at kebe.com Sat Nov 25 15:03:30 2017 From: danmcd at kebe.com (Dan McDonald) Date: Sat, 25 Nov 2017 10:03:30 -0500 Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: References: Message-ID: <82AF0747-4BF7-4ED2-9836-526BF3B003A9@kebe.com> I use NFS. I either use automounter on MacOS (i.e. /net/server//...) or now that I have Carbon Copy Cloner, I also use NFS URLs (nfs://server/), though I set up distinct ZFS datasets for CCC. I see problems occasionally, but less so as time has gone on. Seeing the ._filename files (where Mac resource fork data is kept) on the OmniOS side of things is always weird, but not THAT weird. Dan From geoffn at gnaa.net Sun Nov 26 06:28:24 2017 From: geoffn at gnaa.net (Geoff Nordli) Date: Sat, 25 Nov 2017 22:28:24 -0800 Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: <87360070.591846.1511508790003.JavaMail.zimbra@oetiker.ch> References: <87360070.591846.1511508790003.JavaMail.zimbra@oetiker.ch> Message-ID: Is it the vfs_fruit module, the major reason why samba works better? On 2017-11-23 11:33 PM, Manuel Oetiker wrote: > Hi > > We are using samba and it works well with macos. > > you can download our smb package from pkg.oetiker.ch or just run the compilation by your selfe. > we store our build script under https://github.com/oposs/pkg.oetiker.ch-build/tree/master/build/samba4 > > disabling thumbnails preview helps speed up finder ... > http://osxdaily.com/2013/01/10/disable-finder-icon-thumbnails-previews-mac-os-x/ > > cheers Manuel > > ----- Original Message ----- >> From: "Geoff Nordli" >> To: "omnios-discuss" >> Sent: Friday, November 24, 2017 3:56:01 AM >> Subject: [OmniOS-discuss] Best way to share files with Mac? >> Hi. >> >> I have to support a few mac machines connecting to a few file shares >> running Omnios. >> >> They are reporting problems with the speed when using the "finder". >> >> I see there is a netatalk package I can download and compile off of >> sourceforge, which looks fairly current. >> >> Any suggestions on the best way forward to support Mac machines? >> >> thanks, >> >> Geoff >> >> _______________________________________________ >> OmniOS-discuss mailing list >> OmniOS-discuss at lists.omniti.com >> http://lists.omniti.com/mailman/listinfo/omnios-discuss From geoffn at gnaa.net Sun Nov 26 06:54:20 2017 From: geoffn at gnaa.net (Geoff Nordli) Date: Sat, 25 Nov 2017 22:54:20 -0800 Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: References: Message-ID: <4334e269-ef64-11a0-3f96-7886bda79aa1@gnaa.net> Hi Chris. I wonder if now this is fixed with the vfs_fruit module in Samba. http://plazko.io/apple-osx-finder-is-listing-files-very-very-slow-when-connected-to-smb-shared-hard-drive-connected-to-a-wifi-router/ thanks, Geoff On 2017-11-25 06:45 AM, Chris Ferebee wrote: > Hi Geoff, > > I love the way you put this: > >> They are reporting problems with the speed when using the "finder". > Oh, yes. I spent months of my life in 2014 fighting the Finder vs. a major installation of netatalk, which I deployed on SmartOS. > > We have a large server (dual 6-core XEON, 128 GB RAM, 22 x 4 TB SAS, STEC ZeusRAM) running as a fileserver for Macs. The client does motion graphics and has a very large number of files, 100+ million on the largest share. (Not more than a few thousand files per directory, though.) > > What we saw was that opening the Finder to a directory on the AFP share would show a blank window for 20?180 seconds before displaying the contents, even if there were maybe just 10?20 subdirectories to display. > > Then, as long as the Finder window was open, it would peg one CPU core on the server at 100%, even though the display did not change. > > It turned out that the Finder was looping continually through files several subdirectories deep, querying extended attributes. Due to the way netatalk is coded, this requires a call to getcwd() each time, which is very expensive on Solaris. (getcwd() = get the path name of the current working directory.) > > A SmartOS engineer was kind enough to advise me on this, and basically told me: if you have getcwd() in your hot path, you are screwed. This is probably a reason why the problem, though actually a netatalk issue, is less pronounced on Linux, where getcwd() is not as expensive as on Solaris. > > I never did get to the bottom of this. It appears that it doesn?t happen when the Finder is talking to Apple?s own AFP server, perhaps because there the Finder is able to use FSEvents to track changes. Unfortunately, it appears that netatalk has never fully addressed this, at least I haven?t seen anything indicating that it has gained FSEvents supports in the past years. Here is what netatalk dev Ralph B?hme had to say: > > > > In the end, I switched the client to a (commercial, expensive) AFP server, HELIOS EtherShare, and all problems went away, performance as expected, and I didn?t investigate further. > > If you are dealing with Adobe applications, be aware that there are a number of reasons why they do not work well on a Mac over SMB. We didn?t get past a hard maximum path length of 254 characters, but there are others. > > I?m happy to discuss this further, and would be quite interested to find a less-expensive solution for large-scale file service for Macs. We can take it off-list if it goes any further off topic. > > Good luck, > Chris > > >> Am 24.11.2017 um 03:56 schrieb Geoff Nordli : >> >> Hi. >> >> I have to support a few mac machines connecting to a few file shares running Omnios. >> >> They are reporting problems with the speed when using the "finder". >> >> I see there is a netatalk package I can download and compile off of sourceforge, which looks fairly current. >> >> Any suggestions on the best way forward to support Mac machines? >> >> thanks, >> >> Geoff >> >> From stephan.budach at jvm.de Sun Nov 26 08:24:27 2017 From: stephan.budach at jvm.de (Stephan Budach) Date: Sun, 26 Nov 2017 09:24:27 +0100 (CET) Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: <4334e269-ef64-11a0-3f96-7886bda79aa1@gnaa.net> References: <4334e269-ef64-11a0-3f96-7886bda79aa1@gnaa.net> Message-ID: <1989762114.1599.1511684668310.JavaMail.stephan.budach@stephanbudach.local> Hi, ----- Urspr?ngliche Mail ----- > Von: "Geoff Nordli" > An: "Chris Ferebee" > CC: "omnios-discuss" > Gesendet: Sonntag, 26. November 2017 07:54:20 > Betreff: Re: [OmniOS-discuss] Best way to share files with Mac? > > Hi Chris. > > I wonder if now this is fixed with the vfs_fruit module in Samba. > > http://plazko.io/apple-osx-finder-is-listing-files-very-very-slow-when-connected-to-smb-shared-hard-drive-connected-to-a-wifi-router/ > > thanks, > > Geoff > the vfs_fruit extension, afair, provides interlocking capabilities between Netatalk/AFP and Samba 3/4. It allows Macs and PCs to share the same data through both protocols. Looking at the man page of it, it may be doing some more stuff, which may come in handy for macOS clients. However, this module will not work with the kernel/smb and you will have to go with a full-fledged Samba 4 installation. I know Ralph B?hme, the author of vfs_fruit, and I have contacted serNet (the company he's working for) and we be having a conversation about what the odds arem that they provide a package for omniOS as well. Cheers, Stephan > > > On 2017-11-25 06:45 AM, Chris Ferebee wrote: > > Hi Geoff, > > > > I love the way you put this: > > > >> They are reporting problems with the speed when using the > >> "finder". > > Oh, yes. I spent months of my life in 2014 fighting the Finder vs. > > a major installation of netatalk, which I deployed on SmartOS. > > > > We have a large server (dual 6-core XEON, 128 GB RAM, 22 x 4 TB > > SAS, STEC ZeusRAM) running as a fileserver for Macs. The client > > does motion graphics and has a very large number of files, 100+ > > million on the largest share. (Not more than a few thousand files > > per directory, though.) > > > > What we saw was that opening the Finder to a directory on the AFP > > share would show a blank window for 20?180 seconds before > > displaying the contents, even if there were maybe just 10?20 > > subdirectories to display. > > > > Then, as long as the Finder window was open, it would peg one CPU > > core on the server at 100%, even though the display did not > > change. > > > > It turned out that the Finder was looping continually through files > > several subdirectories deep, querying extended attributes. Due to > > the way netatalk is coded, this requires a call to getcwd() each > > time, which is very expensive on Solaris. (getcwd() = get the path > > name of the current working directory.) > > > > A SmartOS engineer was kind enough to advise me on this, and > > basically told me: if you have getcwd() in your hot path, you are > > screwed. This is probably a reason why the problem, though > > actually a netatalk issue, is less pronounced on Linux, where > > getcwd() is not as expensive as on Solaris. > > > > I never did get to the bottom of this. It appears that it doesn?t > > happen when the Finder is talking to Apple?s own AFP server, > > perhaps because there the Finder is able to use FSEvents to track > > changes. Unfortunately, it appears that netatalk has never fully > > addressed this, at least I haven?t seen anything indicating that > > it has gained FSEvents supports in the past years. Here is what > > netatalk dev Ralph B?hme had to say: > > > > > > > > In the end, I switched the client to a (commercial, expensive) AFP > > server, HELIOS EtherShare, and all problems went away, performance > > as expected, and I didn?t investigate further. > > > > If you are dealing with Adobe applications, be aware that there are > > a number of reasons why they do not work well on a Mac over SMB. > > We didn?t get past a hard maximum path length of 254 characters, > > but there are others. > > > > I?m happy to discuss this further, and would be quite interested to > > find a less-expensive solution for large-scale file service for > > Macs. We can take it off-list if it goes any further off topic. > > > > Good luck, > > Chris > > > > > >> Am 24.11.2017 um 03:56 schrieb Geoff Nordli : > >> > >> Hi. > >> > >> I have to support a few mac machines connecting to a few file > >> shares running Omnios. > >> > >> They are reporting problems with the speed when using the > >> "finder". > >> > >> I see there is a netatalk package I can download and compile off > >> of sourceforge, which looks fairly current. > >> > >> Any suggestions on the best way forward to support Mac machines? > >> > >> thanks, > >> > >> Geoff > >> > >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5546 bytes Desc: not available URL: From geoffn at gnaa.net Sun Nov 26 18:13:35 2017 From: geoffn at gnaa.net (Geoff Nordli) Date: Sun, 26 Nov 2017 10:13:35 -0800 Subject: [OmniOS-discuss] Best way to share files with Mac? In-Reply-To: <1677409733.599848.1511541613884.JavaMail.zimbra@oetiker.ch> References: <87360070.591846.1511508790003.JavaMail.zimbra@oetiker.ch> <471a68cd-276a-c7b6-fafb-b49504c47359@gnaa.net> <1677409733.599848.1511541613884.JavaMail.zimbra@oetiker.ch> Message-ID: <5f1d54a4-e8e1-7254-a073-dc13399ee050@gnaa.net> Do you have a smb conf you can share?? I am especially curious about the fruit parameters for Mac and any shadow parameters you have set for the Windows previous versions to work. thanks!! Geoff On 2017-11-24 08:40 AM, Manuel Oetiker wrote: > Hi Geoff > > I have a mixed environment with mac/pc/linux smb can talk to everyone .. > > cheers Manuel > > > ----- Original Message ----- >> From: "Geoff Nordli" >> To: "Manuel Oetiker" >> Cc: "omnios-discuss" >> Sent: Friday, November 24, 2017 5:32:13 PM >> Subject: Re: [OmniOS-discuss] Best way to share files with Mac? >> Hi Manuel. >> >> Are there other reasons why you decided to go with samba? >> >> thanks, >> >> Geoff >> >> >> On 2017-11-23 11:33 PM, Manuel Oetiker wrote: >>> Hi >>> >>> We are using samba and it works well with macos. >>> >>> you can download our smb package from pkg.oetiker.ch or just run the compilation >>> by your selfe. >>> we store our build script under >>> https://github.com/oposs/pkg.oetiker.ch-build/tree/master/build/samba4 >>> >>> disabling thumbnails preview helps speed up finder ... >>> http://osxdaily.com/2013/01/10/disable-finder-icon-thumbnails-previews-mac-os-x/ >>> >>> cheers Manuel >>> >>> ----- Original Message ----- >>>> From: "Geoff Nordli" >>>> To: "omnios-discuss" >>>> Sent: Friday, November 24, 2017 3:56:01 AM >>>> Subject: [OmniOS-discuss] Best way to share files with Mac? >>>> Hi. >>>> >>>> I have to support a few mac machines connecting to a few file shares >>>> running Omnios. >>>> >>>> They are reporting problems with the speed when using the "finder". >>>> >>>> I see there is a netatalk package I can download and compile off of >>>> sourceforge, which looks fairly current. >>>> >>>> Any suggestions on the best way forward to support Mac machines? >>>> >>>> thanks, >>>> >>>> Geoff >>>> >>>> _______________________________________________ >>>> OmniOS-discuss mailing list >>>> OmniOS-discuss at lists.omniti.com >>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss From tobi at oetiker.ch Sun Nov 26 22:31:38 2017 From: tobi at oetiker.ch (Tobias Oetiker) Date: Sun, 26 Nov 2017 23:31:38 +0100 (CET) Subject: [OmniOS-discuss] Investing into the Future of OmniOS Community Edition Message-ID: <2082283039.636031.1511735498566.JavaMail.zimbra@oetiker.ch> Hi All tl;tr? head over to https://omniosce.org/patron and support your favorite OS with a regular donation. Since the OmniOS Community Edition Association has taken over maintenance and care of OmniOSce, things have been moving at a brisk pace. * Upstream changes from Illumos and Joyent are integrated weekly into our github repo. * Security fixes are normally available within hours. * We have committed to an elaborate long term release plan. * In early November we have released OmniOS r24 on schedule with many enhancements. * Our new website has a lot of new content on feeding and care of your OmniOS instance. Judging from the 566 systems that have been switched over to our new repos, downloading regular updates, we think there is ample interest in OmniOS. Not even taking into account all those who have not yet upgraded. With the release of OmniOSce r24 we have created the OmniOS Patron Page where you can set up regular contribution or a one time donation to the project. Unfortunately only very few people have yet made the step of actually pledging funds. According to the straw poll conducted in spring, there should be at least 80k USD per year available to those who maintain and release updates for OmniOS. At the moment we are getting about 25 USD per month from 4 individuals. This is pretty bleak and does not even begin to cover the cost of running the show and certainly does not allow us to plan for the future. Head over to https://omniosce.org/patron and let us know how much you value OmniOS and our work. If everybody spent just 20 dollar per system and month things would be looking much brighter already. To put this into perspective: a single O365 Enterprise license costs 35 USD/month. Most individuals pay a similar amount every month for the internet connection or mobile phone contract. Andy Fiddaman Dominik Hassler Tobi Oetiker -- OmniOS Community Edition Association Aarweg 17, 4600 Olten, Switzerland www.omniosce.org info at omniosce.org From groups at tierarzt-mueller.de Sun Nov 26 23:16:53 2017 From: groups at tierarzt-mueller.de (Alexander Lesle) Date: Mon, 27 Nov 2017 00:16:53 +0100 Subject: [OmniOS-discuss] Investing into the Future of OmniOS Community Edition In-Reply-To: <2082283039.636031.1511735498566.JavaMail.zimbra@oetiker.ch> References: <2082283039.636031.1511735498566.JavaMail.zimbra@oetiker.ch> Message-ID: <74599745.20171127001653@tierarzt-mueller.de> Guten Abend Tobias Oetiker, at https://omniosce.org/patron are no information about the payment methods. Can you offer for the Europeans your account informations IBAN and BIC on this page please. -- Best Regards Alexander November, 27 2017 From tobi at oetiker.ch Mon Nov 27 05:30:16 2017 From: tobi at oetiker.ch (Tobias Oetiker) Date: Mon, 27 Nov 2017 06:30:16 +0100 (CET) Subject: [OmniOS-discuss] Investing into the Future of OmniOS Community Edition In-Reply-To: <74599745.20171127001653@tierarzt-mueller.de> References: <2082283039.636031.1511735498566.JavaMail.zimbra@oetiker.ch> <74599745.20171127001653@tierarzt-mueller.de> Message-ID: <1996438331.638107.1511760616132.JavaMail.zimbra@oetiker.ch> Hi Alexander, thanks you for the idea ... I have updated the webpage IBAN CH22 0900 0000 6188 9767 7 BIC POFICHBEXX Verein OmniOS Community Edition If there are other requirements, like us sending invoices or some such, please let us know. We are trying something new here ... cheers tobi ----- On Nov 27, 2017, at 12:16 AM, Alexander Lesle groups at tierarzt-mueller.de wrote: > Guten Abend Tobias Oetiker, > > at https://omniosce.org/patron are no information about the > payment methods. > Can you offer for the Europeans your account informations > IBAN and BIC on this page please. > > -- > Best Regards > Alexander > November, 27 2017 -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland www.oetiker.ch tobi at oetiker.ch +41 62 775 9902 From alka at hfg-gmuend.de Mon Nov 27 09:15:47 2017 From: alka at hfg-gmuend.de (Guenther Alka) Date: Mon, 27 Nov 2017 10:15:47 +0100 Subject: [OmniOS-discuss] Investing into the Future of OmniOS Community Edition In-Reply-To: <2082283039.636031.1511735498566.JavaMail.zimbra@oetiker.ch> References: <2082283039.636031.1511735498566.JavaMail.zimbra@oetiker.ch> Message-ID: hello Tobias A pure donation modell (pay for something that is available for free) is only ok for small amounts from private persons. Can this be extended by - a function to request a quotation with a given amount together with a (pro forma) invoice online what makes institutional/edu payments possible (to accept this quotation, pay the amount until..) - with some sort of an extra offer over the free offerings maybe a Pro subscription to beta/ bloody releases, a knowledgebase or a plus repository Gea Am 26.11.2017 um 23:31 schrieb Tobias Oetiker: > Hi All > > tl;tr? head over to https://omniosce.org/patron and support your favorite OS with a regular donation. > > Since the OmniOS Community Edition Association has taken over maintenance and care of OmniOSce, things have been moving at a brisk pace. > > * Upstream changes from Illumos and Joyent are integrated weekly into our github repo. > > * Security fixes are normally available within hours. > > * We have committed to an elaborate long term release plan. > > * In early November we have released OmniOS r24 on schedule with many enhancements. > > * Our new website has a lot of new content on feeding and care of your OmniOS instance. > > Judging from the 566 systems that have been switched over to our new repos, downloading regular updates, we think there is ample interest in OmniOS. Not even taking into account all those who have not yet upgraded. > > With the release of OmniOSce r24 we have created the OmniOS Patron Page where you can set up regular contribution or a one time donation to the project. > > Unfortunately only very few people have yet made the step of actually pledging funds. According to the straw poll conducted in spring, there should be at least 80k USD per year available to those who maintain and release updates for OmniOS. > > At the moment we are getting about 25 USD per month from 4 individuals. This is pretty bleak and does not even begin to cover the cost of running the show and certainly does not allow us to plan for the future. > > Head over to https://omniosce.org/patron and let us know how much you value OmniOS and our work. If everybody spent just 20 dollar per system and month things would be looking much brighter already. > > To put this into perspective: a single O365 Enterprise license costs 35 USD/month. Most individuals pay a similar amount every month for the internet connection or mobile phone contract. > > Andy Fiddaman > Dominik Hassler > Tobi Oetiker > > -- > OmniOS Community Edition Association > Aarweg 17, 4600 Olten, Switzerland > www.omniosce.org > info at omniosce.org -- H f G Hochschule f?r Gestaltung university of design Schw?bisch Gm?nd Rektor-Klaus Str. 100 73525 Schw?bisch Gm?nd Guenther Alka, Dipl.-Ing. (FH) Leiter des Rechenzentrums head of computer center Tel 07171 602 627 Fax 07171 69259 guenther.alka at hfg-gmuend.de http://rz.hfg-gmuend.de From stephan.budach at jvm.de Mon Nov 27 09:52:10 2017 From: stephan.budach at jvm.de (Stephan Budach) Date: Mon, 27 Nov 2017 10:52:10 +0100 (CET) Subject: [OmniOS-discuss] Investing into the Future of OmniOS Community Edition In-Reply-To: References: <2082283039.636031.1511735498566.JavaMail.zimbra@oetiker.ch> Message-ID: <1538952809.2142.1511776331395.JavaMail.stephan.budach@stephan.budach.jvm.de> +1 Cheers, Stephan ----- Urspr?ngliche Mail ----- > Von: "Guenther Alka" > An: "omnios-discuss" > Gesendet: Montag, 27. November 2017 10:15:47 > Betreff: Re: [OmniOS-discuss] Investing into the Future of OmniOS Community Edition > > hello Tobias > > A pure donation modell (pay for something that is available for free) > is > only ok for small amounts from private persons. > > Can this be extended by > - a function to request a quotation with a given amount together with > a > (pro forma) invoice online what makes institutional/edu payments > possible > (to accept this quotation, pay the amount until..) > > - with some sort of an extra offer over the free offerings > maybe a Pro subscription to beta/ bloody releases, a knowledgebase or > a > plus repository > > Gea > > > Am 26.11.2017 um 23:31 schrieb Tobias Oetiker: > > Hi All > > > > tl;tr? head over to https://omniosce.org/patron and support your > > favorite OS with a regular donation. > > > > Since the OmniOS Community Edition Association has taken over > > maintenance and care of OmniOSce, things have been moving at a > > brisk pace. > > > > * Upstream changes from Illumos and Joyent are integrated weekly > > into our github repo. > > > > * Security fixes are normally available within hours. > > > > * We have committed to an elaborate long term release plan. > > > > * In early November we have released OmniOS r24 on schedule with > > many enhancements. > > > > * Our new website has a lot of new content on feeding and care > > of your OmniOS instance. > > > > Judging from the 566 systems that have been switched over to our > > new repos, downloading regular updates, we think there is ample > > interest in OmniOS. Not even taking into account all those who > > have not yet upgraded. > > > > With the release of OmniOSce r24 we have created the OmniOS Patron > > Page where you can set up regular contribution or a one time > > donation to the project. > > > > Unfortunately only very few people have yet made the step of > > actually pledging funds. According to the straw poll conducted in > > spring, there should be at least 80k USD per year available to > > those who maintain and release updates for OmniOS. > > > > At the moment we are getting about 25 USD per month from 4 > > individuals. This is pretty bleak and does not even begin to cover > > the cost of running the show and certainly does not allow us to > > plan for the future. > > > > Head over to https://omniosce.org/patron and let us know how much > > you value OmniOS and our work. If everybody spent just 20 dollar > > per system and month things would be looking much brighter > > already. > > > > To put this into perspective: a single O365 Enterprise license > > costs 35 USD/month. Most individuals pay a similar amount every > > month for the internet connection or mobile phone contract. > > > > Andy Fiddaman > > Dominik Hassler > > Tobi Oetiker > > > > -- > > OmniOS Community Edition Association > > Aarweg 17, 4600 Olten, Switzerland > > www.omniosce.org > > info at omniosce.org > > -- > H f G > Hochschule f?r Gestaltung > university of design > > Schw?bisch Gm?nd > Rektor-Klaus Str. 100 > 73525 Schw?bisch Gm?nd > > Guenther Alka, Dipl.-Ing. (FH) > Leiter des Rechenzentrums > head of computer center > > Tel 07171 602 627 > Fax 07171 69259 > guenther.alka at hfg-gmuend.de > http://rz.hfg-gmuend.de > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5546 bytes Desc: not available URL: From groups at tierarzt-mueller.de Mon Nov 27 10:46:07 2017 From: groups at tierarzt-mueller.de (Alexander Lesle) Date: Mon, 27 Nov 2017 11:46:07 +0100 Subject: [OmniOS-discuss] Investing into the Future of OmniOS Community Edition In-Reply-To: References: <2082283039.636031.1511735498566.JavaMail.zimbra@oetiker.ch> Message-ID: <1814152440.20171127114607@tierarzt-mueller.de> Hello, for small amounts from private persons it will be better you offer paypal (-donation) too. https://www.paypal.com/de/cgi-bin/webscr?cmd=_flow&SESSION=0DhZCUoQyUfgZxqWh-_3fbqRqn5hNJFMTEAow8szClc8p7wgNC3c8pDbUeC&dispatch=5885d80a13c0db1f8e263663d3faee8dc3f308debf7330dd8d0b0a9f21afd7d3&rapidsState=Merchant__ButtonDesignerFlow___StateButtonDesignerStart&rapidsStateSignature=885abefea41ef918124519b9a82d2f77d8c3e533 Invoice online or as pdf I prefer too. Tobias, few minutes ago I send my donation by bank wire in EURO. Please check what you get CHF or EURO and how much are the bank charges from your Postfinance AG. Maybe its better when you have a bank account in the EURO-Zone (Germany, France are near to you) because few banks collecting bank charges by wiring to Switzerland. Feedback by PN please. On November, 27 2017, 10:15 wrote in [1]: > hello Tobias > A pure donation modell (pay for something that is available for free) is > only ok for small amounts from private persons. > Can this be extended by > - a function to request a quotation with a given amount together with a > (pro forma) invoice online what makes institutional/edu payments possible > (to accept this quotation, pay the amount until..) > - with some sort of an extra offer over the free offerings > maybe a Pro subscription to beta/ bloody releases, a knowledgebase or a > plus repository > Gea -- Best Regards Alexander November, 27 2017 ........ [1] mid:b9446f72-0d97-ed5c-1f8c-195c0f51129a at hfg-gmuend.de ........ From tobi at oetiker.ch Mon Nov 27 12:52:28 2017 From: tobi at oetiker.ch (Tobias Oetiker) Date: Mon, 27 Nov 2017 13:52:28 +0100 (CET) Subject: [OmniOS-discuss] Investing into the Future of OmniOS Community Edition In-Reply-To: <1538952809.2142.1511776331395.JavaMail.stephan.budach@stephan.budach.jvm.de> References: <2082283039.636031.1511735498566.JavaMail.zimbra@oetiker.ch> <1538952809.2142.1511776331395.JavaMail.stephan.budach@stephan.budach.jvm.de> Message-ID: <2002322690.647195.1511787148799.JavaMail.zimbra@oetiker.ch> Hi Stephan, Hi Guenther the proforma invoice, yes we will look into that ... what we also discussed is offering some repo with pre compiled packages for a fee. but we are not there yet. still trusting that users realize that omnios does not create itself out of thin air. applying some business logic and risk analysis should make this abundantly clear to most people with business responsibilities. cheers tobi ----- On Nov 27, 2017, at 10:52 AM, Stephan Budach stephan.budach at jvm.de wrote: > +1 > > Cheers, > Stephan > > ----- Urspr?ngliche Mail ----- >> Von: "Guenther Alka" >> An: "omnios-discuss" >> Gesendet: Montag, 27. November 2017 10:15:47 >> Betreff: Re: [OmniOS-discuss] Investing into the Future of OmniOS Community >> Edition >> >> hello Tobias >> >> A pure donation modell (pay for something that is available for free) >> is >> only ok for small amounts from private persons. >> >> Can this be extended by >> - a function to request a quotation with a given amount together with >> a >> (pro forma) invoice online what makes institutional/edu payments >> possible >> (to accept this quotation, pay the amount until..) >> >> - with some sort of an extra offer over the free offerings >> maybe a Pro subscription to beta/ bloody releases, a knowledgebase or >> a >> plus repository >> >> Gea >> >> >> Am 26.11.2017 um 23:31 schrieb Tobias Oetiker: >> > Hi All >> > >> > tl;tr? head over to https://omniosce.org/patron and support your >> > favorite OS with a regular donation. >> > >> > Since the OmniOS Community Edition Association has taken over >> > maintenance and care of OmniOSce, things have been moving at a >> > brisk pace. >> > >> > * Upstream changes from Illumos and Joyent are integrated weekly >> > into our github repo. >> > >> > * Security fixes are normally available within hours. >> > >> > * We have committed to an elaborate long term release plan. >> > >> > * In early November we have released OmniOS r24 on schedule with >> > many enhancements. >> > >> > * Our new website has a lot of new content on feeding and care >> > of your OmniOS instance. >> > >> > Judging from the 566 systems that have been switched over to our >> > new repos, downloading regular updates, we think there is ample >> > interest in OmniOS. Not even taking into account all those who >> > have not yet upgraded. >> > >> > With the release of OmniOSce r24 we have created the OmniOS Patron >> > Page where you can set up regular contribution or a one time >> > donation to the project. >> > >> > Unfortunately only very few people have yet made the step of >> > actually pledging funds. According to the straw poll conducted in >> > spring, there should be at least 80k USD per year available to >> > those who maintain and release updates for OmniOS. >> > >> > At the moment we are getting about 25 USD per month from 4 >> > individuals. This is pretty bleak and does not even begin to cover >> > the cost of running the show and certainly does not allow us to >> > plan for the future. >> > >> > Head over to https://omniosce.org/patron and let us know how much >> > you value OmniOS and our work. If everybody spent just 20 dollar >> > per system and month things would be looking much brighter >> > already. >> > >> > To put this into perspective: a single O365 Enterprise license >> > costs 35 USD/month. Most individuals pay a similar amount every >> > month for the internet connection or mobile phone contract. >> > >> > Andy Fiddaman >> > Dominik Hassler >> > Tobi Oetiker >> > >> > -- >> > OmniOS Community Edition Association >> > Aarweg 17, 4600 Olten, Switzerland >> > www.omniosce.org >> > info at omniosce.org >> >> -- >> H f G >> Hochschule f?r Gestaltung >> university of design >> >> Schw?bisch Gm?nd >> Rektor-Klaus Str. 100 >> 73525 Schw?bisch Gm?nd >> >> Guenther Alka, Dipl.-Ing. (FH) >> Leiter des Rechenzentrums >> head of computer center >> >> Tel 07171 602 627 >> Fax 07171 69259 >> guenther.alka at hfg-gmuend.de >> http://rz.hfg-gmuend.de >> >> _______________________________________________ >> OmniOS-discuss mailing list >> OmniOS-discuss at lists.omniti.com >> http://lists.omniti.com/mailman/listinfo/omnios-discuss >> > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland www.oetiker.ch tobi at oetiker.ch +41 62 775 9902 From alka at hfg-gmuend.de Tue Nov 28 12:55:49 2017 From: alka at hfg-gmuend.de (Guenther Alka) Date: Tue, 28 Nov 2017 13:55:49 +0100 Subject: [OmniOS-discuss] Investing into the Future of OmniOS Community Edition In-Reply-To: <2002322690.647195.1511787148799.JavaMail.zimbra@oetiker.ch> References: <2082283039.636031.1511735498566.JavaMail.zimbra@oetiker.ch> <1538952809.2142.1511776331395.JavaMail.stephan.budach@stephan.budach.jvm.de> <2002322690.647195.1511787148799.JavaMail.zimbra@oetiker.ch> Message-ID: <3e417e10-24f3-751a-4fd5-2d87ef70471e@hfg-gmuend.de> hello Tobias During a contact with a storage systemhouse that intends to offer OmniOS as an additional storage OS, I asked about sponsoring of OmniOS ce and I was asked if there would be an option of something like a gold/silver/bronce patron to bepublished on the patron page. Gea Am 27.11.2017 um 13:52 schrieb Tobias Oetiker: > Hi Stephan, Hi Guenther > > the proforma invoice, yes we will look into that ... what we also discussed is offering some repo with pre compiled packages for a fee. but we are not there yet. still trusting that users realize that omnios does not create itself out of thin air. applying some business logic and risk analysis should make this abundantly clear to most people with business responsibilities. > > cheers > tobi > > ----- On Nov 27, 2017, at 10:52 AM, Stephan Budach stephan.budach at jvm.de wrote: > >> +1 >> >> Cheers, >> Stephan >> >> ----- Urspr?ngliche Mail ----- >>> Von: "Guenther Alka" >>> An: "omnios-discuss" >>> Gesendet: Montag, 27. November 2017 10:15:47 >>> Betreff: Re: [OmniOS-discuss] Investing into the Future of OmniOS Community >>> Edition >>> >>> hello Tobias >>> >>> A pure donation modell (pay for something that is available for free) >>> is >>> only ok for small amounts from private persons. >>> >>> Can this be extended by >>> - a function to request a quotation with a given amount together with >>> a >>> (pro forma) invoice online what makes institutional/edu payments >>> possible >>> (to accept this quotation, pay the amount until..) >>> >>> - with some sort of an extra offer over the free offerings >>> maybe a Pro subscription to beta/ bloody releases, a knowledgebase or >>> a >>> plus repository >>> >>> Gea >>> >>> >>> Am 26.11.2017 um 23:31 schrieb Tobias Oetiker: >>>> Hi All >>>> >>>> tl;tr? head over to https://omniosce.org/patron and support your >>>> favorite OS with a regular donation. >>>> >>>> Since the OmniOS Community Edition Association has taken over >>>> maintenance and care of OmniOSce, things have been moving at a >>>> brisk pace. >>>> >>>> * Upstream changes from Illumos and Joyent are integrated weekly >>>> into our github repo. >>>> >>>> * Security fixes are normally available within hours. >>>> >>>> * We have committed to an elaborate long term release plan. >>>> >>>> * In early November we have released OmniOS r24 on schedule with >>>> many enhancements. >>>> >>>> * Our new website has a lot of new content on feeding and care >>>> of your OmniOS instance. >>>> >>>> Judging from the 566 systems that have been switched over to our >>>> new repos, downloading regular updates, we think there is ample >>>> interest in OmniOS. Not even taking into account all those who >>>> have not yet upgraded. >>>> >>>> With the release of OmniOSce r24 we have created the OmniOS Patron >>>> Page where you can set up regular contribution or a one time >>>> donation to the project. >>>> >>>> Unfortunately only very few people have yet made the step of >>>> actually pledging funds. According to the straw poll conducted in >>>> spring, there should be at least 80k USD per year available to >>>> those who maintain and release updates for OmniOS. >>>> >>>> At the moment we are getting about 25 USD per month from 4 >>>> individuals. This is pretty bleak and does not even begin to cover >>>> the cost of running the show and certainly does not allow us to >>>> plan for the future. >>>> >>>> Head over to https://omniosce.org/patron and let us know how much >>>> you value OmniOS and our work. If everybody spent just 20 dollar >>>> per system and month things would be looking much brighter >>>> already. >>>> >>>> To put this into perspective: a single O365 Enterprise license >>>> costs 35 USD/month. Most individuals pay a similar amount every >>>> month for the internet connection or mobile phone contract. >>>> >>>> Andy Fiddaman >>>> Dominik Hassler >>>> Tobi Oetiker >>>> >>>> -- >>>> OmniOS Community Edition Association >>>> Aarweg 17, 4600 Olten, Switzerland >>>> www.omniosce.org >>>> info at omniosce.org >>>> >>>> _______________________________________________ >>>> OmniOS-discuss mailing list >>>> OmniOS-discuss at lists.omniti.com >>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss >>>> >> From johan.kragsterman at capvert.se Tue Nov 28 13:20:16 2017 From: johan.kragsterman at capvert.se (Johan Kragsterman) Date: Tue, 28 Nov 2017 14:20:16 +0100 Subject: [OmniOS-discuss] Ang: Re: Investing into the Future of OmniOS Community Edition In-Reply-To: <3e417e10-24f3-751a-4fd5-2d87ef70471e@hfg-gmuend.de> References: <3e417e10-24f3-751a-4fd5-2d87ef70471e@hfg-gmuend.de>, <2082283039.636031.1511735498566.JavaMail.zimbra@oetiker.ch> <1538952809.2142.1511776331395.JavaMail.stephan.budach@stephan.budach.jvm.de> <2002322690.647195.1511787148799.JavaMail.zimbra@oetiker.ch> Message-ID: Hi! I believe that is a good way to go, to offer marketing space and perhaps other marketing possibilities for the sponsors. That is a much preferred option than cutting off the community from certain publishers, or other "cut offs", because that would only cause bad blood. Best regards from/Med v?nliga h?lsningar fr?n Johan Kragsterman Capvert -----"OmniOS-discuss" skrev: ----- Till: omnios-discuss at lists.omniti.com Fr?n: Guenther Alka S?nt av: "OmniOS-discuss" Datum: 2017-11-28 14:00 ?rende: Re: [OmniOS-discuss] Investing into the Future of OmniOS Community Edition hello Tobias During a contact with a storage systemhouse that intends to offer OmniOS as an additional storage OS, I asked about sponsoring of OmniOS ce and I was asked if there would be an option of something like a gold/silver/bronce patron to bepublished on the patron page. Gea Am 27.11.2017 um 13:52 schrieb Tobias Oetiker: > Hi Stephan, Hi Guenther > > the proforma invoice, yes we will look into that ... what we also discussed is offering some repo with pre compiled packages for a fee. but we are not there yet. still trusting that users realize that omnios does not create itself out of thin air. applying some business logic and risk analysis should make this abundantly clear to most people with business responsibilities. > > cheers > tobi > > ----- On Nov 27, 2017, at 10:52 AM, Stephan Budach stephan.budach at jvm.de wrote: > >> +1 >> >> Cheers, >> Stephan >> >> ----- Urspr?ngliche Mail ----- >>> Von: "Guenther Alka" >>> An: "omnios-discuss" >>> Gesendet: Montag, 27. November 2017 10:15:47 >>> Betreff: Re: [OmniOS-discuss] Investing into the Future of OmniOS Community >>> Edition >>> >>> hello Tobias >>> >>> A pure donation modell (pay for something that is available for free) >>> is >>> only ok for small amounts from private persons. >>> >>> Can this be extended by >>> - a function to request a quotation with a given amount together with >>> a >>> (pro forma) invoice online what makes institutional/edu payments >>> possible >>> (to accept this quotation, pay the amount until..) >>> >>> - with some sort of an extra offer over the free offerings >>> maybe a Pro subscription to beta/ bloody releases, a knowledgebase or >>> a >>> plus repository >>> >>> Gea >>> >>> >>> Am 26.11.2017 um 23:31 schrieb Tobias Oetiker: >>>> Hi All >>>> >>>> tl;tr? head over to https://omniosce.org/patron and support your >>>> favorite OS with a regular donation. >>>> >>>> Since the OmniOS Community Edition Association has taken over >>>> maintenance and care of OmniOSce, things have been moving at a >>>> brisk pace. >>>> >>>> * Upstream changes from Illumos and Joyent are integrated weekly >>>> into our github repo. >>>> >>>> * Security fixes are normally available within hours. >>>> >>>> * We have committed to an elaborate long term release plan. >>>> >>>> * In early November we have released OmniOS r24 on schedule with >>>> many enhancements. >>>> >>>> * Our new website has a lot of new content on feeding and care >>>> of your OmniOS instance. >>>> >>>> Judging from the 566 systems that have been switched over to our >>>> new repos, downloading regular updates, we think there is ample >>>> interest in OmniOS. Not even taking into account all those who >>>> have not yet upgraded. >>>> >>>> With the release of OmniOSce r24 we have created the OmniOS Patron >>>> Page where you can set up regular contribution or a one time >>>> donation to the project. >>>> >>>> Unfortunately only very few people have yet made the step of >>>> actually pledging funds. According to the straw poll conducted in >>>> spring, there should be at least 80k USD per year available to >>>> those who maintain and release updates for OmniOS. >>>> >>>> At the moment we are getting about 25 USD per month from 4 >>>> individuals. This is pretty bleak and does not even begin to cover >>>> the cost of running the show and certainly does not allow us to >>>> plan for the future. >>>> >>>> Head over to https://omniosce.org/patron and let us know how much >>>> you value OmniOS and our work. If everybody spent just 20 dollar >>>> per system and month things would be looking much brighter >>>> already. >>>> >>>> To put this into perspective: a single O365 Enterprise license >>>> costs 35 USD/month. Most individuals pay a similar amount every >>>> month for the internet connection or mobile phone contract. >>>> >>>> Andy Fiddaman >>>> Dominik Hassler >>>> Tobi Oetiker >>>> >>>> -- >>>> OmniOS Community Edition Association >>>> Aarweg 17, 4600 Olten, Switzerland >>>> www.omniosce.org >>>> info at omniosce.org >>>> >>>> _______________________________________________ >>>> OmniOS-discuss mailing list >>>> OmniOS-discuss at lists.omniti.com >>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss >>>> >> _______________________________________________ OmniOS-discuss mailing list OmniOS-discuss at lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss From henson at acm.org Tue Nov 28 20:45:49 2017 From: henson at acm.org (Paul B. Henson) Date: Tue, 28 Nov 2017 12:45:49 -0800 Subject: [OmniOS-discuss] Investing into the Future of OmniOS Community Edition In-Reply-To: <2002322690.647195.1511787148799.JavaMail.zimbra@oetiker.ch> References: <2082283039.636031.1511735498566.JavaMail.zimbra@oetiker.ch> <1538952809.2142.1511776331395.JavaMail.stephan.budach@stephan.budach.jvm.de> <2002322690.647195.1511787148799.JavaMail.zimbra@oetiker.ch> Message-ID: <181f01d36889$dfcf7640$9f6e62c0$@acm.org> > From: Tobias Oetiker > Sent: Monday, November 27, 2017 4:52 AM > > out of thin air. applying some business logic and risk analysis should make this > abundantly clear to most people with business responsibilities. Hmm, methinks you don't have a good understanding of the average MBA bean counter 8-/. I was able to convince the management at my university to purchase "commercial support" from OmniTI in order to support OmniOS, but it's quite unlikely I'd be able to get them to "donate money to free software development" 8-/. If something that gave the facade of "commercial support" could be offered, even if it was just "email a list of developers and one will try to reply when they have time" I could try to regain the funding that was going to OmniTI and send it your way. From tobi at oetiker.ch Tue Nov 28 20:59:36 2017 From: tobi at oetiker.ch (Tobias Oetiker) Date: Tue, 28 Nov 2017 21:59:36 +0100 (CET) Subject: [OmniOS-discuss] Ang: Re: Investing into the Future of OmniOS Community Edition In-Reply-To: References: <3e417e10-24f3-751a-4fd5-2d87ef70471e@hfg-gmuend.de> <2082283039.636031.1511735498566.JavaMail.zimbra@oetiker.ch> <1538952809.2142.1511776331395.JavaMail.stephan.budach@stephan.budach.jvm.de> <2002322690.647195.1511787148799.JavaMail.zimbra@oetiker.ch> Message-ID: <490808614.685796.1511902776146.JavaMail.zimbra@oetiker.ch> Hi All Over the last few days we got several suggestions on the income front. These are the things we are looking into at the moment: * Invoice generator: To create a downloadable invoice for a OmniOS CE voluntary License (ideas for a good name welcome) You will be able to specify your address and the invoice amount * Gold/Silver/Bronce Sponsorship contracts where your logo will be shown on our the website. * Genuine Support Contracts where we will help you with your OmniOS issues. details to come. cheers tobi ----- On Nov 28, 2017, at 2:20 PM, Johan Kragsterman johan.kragsterman at capvert.se wrote: > Hi! > > > I believe that is a good way to go, to offer marketing space and perhaps other > marketing possibilities for the sponsors. > > That is a much preferred option than cutting off the community from certain > publishers, or other "cut offs", because that would only cause bad blood. > > > Best regards from/Med v?nliga h?lsningar fr?n > > Johan Kragsterman > > Capvert > > > > -----"OmniOS-discuss" skrev: ----- > Till: omnios-discuss at lists.omniti.com > Fr?n: Guenther Alka > S?nt av: "OmniOS-discuss" > Datum: 2017-11-28 14:00 > ?rende: Re: [OmniOS-discuss] Investing into the Future of OmniOS Community > Edition > > hello Tobias > > During a contact with a storage systemhouse that intends to offer OmniOS > as an additional storage OS, I asked about sponsoring of OmniOS ce and I > was asked if there would be an option of something like a > gold/silver/bronce patron to bepublished on the patron page. > > > Gea > > > Am 27.11.2017 um 13:52 schrieb Tobias Oetiker: >> Hi Stephan, Hi Guenther >> >> the proforma invoice, yes we will look into that ... what we also discussed is >> offering some repo with pre compiled packages for a fee. but we are not there >> yet. still trusting that users realize that omnios does not create itself out >> of thin air. applying some business logic and risk analysis should make this >> abundantly clear to most people with business responsibilities. >> >> cheers >> tobi >> >> ----- On Nov 27, 2017, at 10:52 AM, Stephan Budach stephan.budach at jvm.de wrote: >> >>> +1 >>> >>> Cheers, >>> Stephan >>> >>> ----- Urspr?ngliche Mail ----- >>>> Von: "Guenther Alka" >>>> An: "omnios-discuss" >>>> Gesendet: Montag, 27. November 2017 10:15:47 >>>> Betreff: Re: [OmniOS-discuss] Investing into the Future of OmniOS Community >>>> Edition >>>> >>>> hello Tobias >>>> >>>> A pure donation modell (pay for something that is available for free) >>>> is >>>> only ok for small amounts from private persons. >>>> >>>> Can this be extended by >>>> - a function to request a quotation with a given amount together with >>>> a >>>> (pro forma) invoice online what makes institutional/edu payments >>>> possible >>>> (to accept this quotation, pay the amount until..) >>>> >>>> - with some sort of an extra offer over the free offerings >>>> maybe a Pro subscription to beta/ bloody releases, a knowledgebase or >>>> a >>>> plus repository >>>> >>>> Gea >>>> >>>> >>>> Am 26.11.2017 um 23:31 schrieb Tobias Oetiker: >>>>> Hi All >>>>> >>>>> tl;tr? head over to https://omniosce.org/patron and support your >>>>> favorite OS with a regular donation. >>>>> >>>>> Since the OmniOS Community Edition Association has taken over >>>>> maintenance and care of OmniOSce, things have been moving at a >>>>> brisk pace. >>>>> >>>>> * Upstream changes from Illumos and Joyent are integrated weekly >>>>> into our github repo. >>>>> >>>>> * Security fixes are normally available within hours. >>>>> >>>>> * We have committed to an elaborate long term release plan. >>>>> >>>>> * In early November we have released OmniOS r24 on schedule with >>>>> many enhancements. >>>>> >>>>> * Our new website has a lot of new content on feeding and care >>>>> of your OmniOS instance. >>>>> >>>>> Judging from the 566 systems that have been switched over to our >>>>> new repos, downloading regular updates, we think there is ample >>>>> interest in OmniOS. Not even taking into account all those who >>>>> have not yet upgraded. >>>>> >>>>> With the release of OmniOSce r24 we have created the OmniOS Patron >>>>> Page where you can set up regular contribution or a one time >>>>> donation to the project. >>>>> >>>>> Unfortunately only very few people have yet made the step of >>>>> actually pledging funds. According to the straw poll conducted in >>>>> spring, there should be at least 80k USD per year available to >>>>> those who maintain and release updates for OmniOS. >>>>> >>>>> At the moment we are getting about 25 USD per month from 4 >>>>> individuals. This is pretty bleak and does not even begin to cover >>>>> the cost of running the show and certainly does not allow us to >>>>> plan for the future. >>>>> >>>>> Head over to https://omniosce.org/patron and let us know how much >>>>> you value OmniOS and our work. If everybody spent just 20 dollar >>>>> per system and month things would be looking much brighter >>>>> already. >>>>> >>>>> To put this into perspective: a single O365 Enterprise license >>>>> costs 35 USD/month. Most individuals pay a similar amount every >>>>> month for the internet connection or mobile phone contract. >>>>> >>>>> Andy Fiddaman >>>>> Dominik Hassler >>>>> Tobi Oetiker >>>>> >>>>> -- >>>>> OmniOS Community Edition Association >>>>> Aarweg 17, 4600 Olten, Switzerland >>>>> www.omniosce.org >>>>> info at omniosce.org >>>>> >>>>> _______________________________________________ >>>>> OmniOS-discuss mailing list >>>>> OmniOS-discuss at lists.omniti.com >>>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss >>>>> >>> > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > > > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland www.oetiker.ch tobi at oetiker.ch +41 62 775 9902 From geoffn at gnaa.net Wed Nov 29 20:43:28 2017 From: geoffn at gnaa.net (Geoff Nordli) Date: Wed, 29 Nov 2017 12:43:28 -0800 Subject: [OmniOS-discuss] Samba4 and Omnios Message-ID: Hi. Does anyone have any links to configuring Samba4 as an AD DC on Omnios/Solaris? thanks, Geoff From geoffn at gnaa.net Wed Nov 29 21:02:07 2017 From: geoffn at gnaa.net (Geoff Nordli) Date: Wed, 29 Nov 2017 13:02:07 -0800 Subject: [OmniOS-discuss] Building samba4 on Omnios Message-ID: <23d3dfcb-1f1f-37bc-dcb5-b124e511cdfd@gnaa.net> Hi. In case anyone else wants to go down this path, I was able to get the Samba4 packages built on omnios from this repo: https://github.com/oposs/pkg.oetiker.ch-build The functions.sh file points to gcc-5.1.0, but there is only gcc-5 pkg.oetiker.ch-build/lib$ grep -i gcc functions.sh PATH="/opt/gcc-5.1.0/bin:/opt/oep/bin:/opt/omni/bin:/usr/ccs/bin:/usr/bin:/usr/sbin:/usr/gnu/bin:/usr/sfw/bin" ??? [[ -x /opt/gcc-5.1.0/bin/gcc ]] || needed+=" developer/gcc5" I decided to create a symlink for gcc-5.1.0 #cd /opt #sudo ln -s gcc-5 gcc-5.1.0 #ls -al /opt/gcc-5* lrwxrwxrwx 1 root root 5 Nov 24 13:10 /opt/gcc-5.1.0 -> gcc-5 Setup a publisher: #pkgrepo create /oep-pkg #pkgrepo -s /oep-pkg add-publisher pkg.oetiker.ch In the lib/functions.sh file I needed to add sudo to the pkgsend command. logcmd sudo $PKGSEND -s $PKGSRVR publish -d $DESTDIR -d $TMPDIR/$BUILDDIR \ logcmd sudo $PKGSEND -s $PKGSRVR publish $P5M_FINAL || \ Then go in and build the openldap and samba4 packages. now, on to getting a working samba4 system... Geoff From groenveld at acm.org Wed Nov 29 22:26:37 2017 From: groenveld at acm.org (John D Groenveld) Date: Wed, 29 Nov 2017 17:26:37 -0500 Subject: [OmniOS-discuss] Samba4 and Omnios In-Reply-To: Your message of "Wed, 29 Nov 2017 12:43:28 -0800." References: Message-ID: <201711292226.vATMQbhQ009474@groenveld.us> In message , Geoff Nordli writes : >Does anyone have any links to configuring Samba4 as an AD DC on >Omnios/Solaris? The OI docs for configuring authentication are helpful: John groenveld at acm.org