Thanks, Jason. Yes, both of these issues are known, and we're working on fixing them.
Nexenta-on is deprecated.. the source package is now nexenta-on-source. So as an end user you only have to apt-get install nexenta-on-source cd /usr/src/nexenta-on-source; apt-satisfydepends <- this will pull in things like Sun Studio 12, etc dpkg-buildpackage (Note.. it is 'apt-get install' and not 'apt-get source') This package is in flux and the package had a small patching issue, which is being fixed. You can try the above on an upgraded box, there's a complete build of ON is done, and a local apt repository of the new ON packages created (from which you should be able to apt-clone dist-upgrade) Once the kinks in the above process are ironed out, it will be documented, and should provide a simple entry point for community contributions. The nexenta-gate and nexenta-gate-experimental (the stable and the under development gates of ON) are hosted at http://www.nexentastor.org/ and the mercurial frontend to repositories is at http://hg.nexentastor.org/ . There are separate repositories for ON patches and the debian/ folder -- Regards Anil On Thu, Oct 8, 2009 at 11:16 AM, Jason Upton <wavejumpe...@gmail.com> wrote: > Hi Anil, > > Many Thanks to you and everyone else involved for the work to get a > newer kernel version available and a build environment that NCP users > can use to try and compile our own kernel versions! I'm excited to > hear that the nexenta-on-source package should allow us to start > compiling on an existing NCP box (or at least get us much closer than > before). I had been trying to get the old nexenta-on from 104 in a > state to try and build but never succeeded (plus trying to understand > the 250+ patches, etc was beyond what I wanted to do). I'll be trying > to understand the new methods once I can get a devzone working with > the new kernel, etc. Which leads me into the rest of the reply. But > before I complain, thanks again! :) > > Now for the bad news you asked to hear about in your announcement- > I have seen two issues after upgrading so far: > > 1. ssh to/from the machine is not working. Here is what a "ssh -v" > output has when trying to ssh from a NCP2 box with kernel 104 to the > NCP2 box with kernel 124 looks like: > > Sun_SSH_1.2, SSH protocols 1.5/2.0, OpenSSL 0x0090801f > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: Rhosts Authentication disabled, originating port will not be trusted. > debug1: ssh_connect: needpriv 0 > debug1: Connecting to 192.168.111.24 [192.168.111.24] port 22. > debug1: Connection established. > debug1: identity file /export/home/nexenta/.ssh/identity type -1 > debug1: identity file /export/home/nexenta/.ssh/id_rsa type -1 > debug1: identity file /export/home/nexenta/.ssh/id_dsa type -1 > debug1: Remote protocol version 2.0, remote software version Sun_SSH_1.4 > debug1: no match: Sun_SSH_1.4 > debug1: Enabling compatibility mode for protocol 2.0 > debug1: Local version string SSH-2.0-Sun_SSH_1.2 > debug1: use_engine is 'yes' > debug1: pkcs11 engine initialized, now setting it as default for RSA, > DSA, and symmetric ciphers > debug1: pkcs11 engine initialization complete > debug1: Failed to acquire GSS-API credentials for any mechanisms (No > credentials were supplied, or the credentials were unavailable or > inaccessible > Unknown code 0 > ) > debug1: SSH2_MSG_KEXINIT sent > > and it just hangs at that point. Trying to ssh from the NCP2 box with > kernel 124 hangs similarly but at the "use_engine" line. Examples > below. > > Here is the attempt to ssh to a NCP2 kernel 104 box from a NCP2 kernel 124 > box: > > Sun_SSH_1.4, SSH protocols 1.5/2.0, OpenSSL 0x009080bf > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: Rhosts Authentication disabled, originating port will not be trusted. > debug1: ssh_connect: needpriv 0 > debug1: Connecting to 192.168.111.25 [192.168.111.25] port 22. > debug1: Connection established. > debug1: identity file /export/home/nexenta/.ssh/identity type -1 > debug1: identity file /export/home/nexenta/.ssh/id_rsa type 1 > debug1: identity file /export/home/nexenta/.ssh/id_dsa type -1 > debug1: Remote protocol version 2.0, remote software version Sun_SSH_1.2 > debug1: match: Sun_SSH_1.2 pat Sun_SSH_1.2* > debug1: Enabling compatibility mode for protocol 2.0 > debug1: Local version string SSH-2.0-Sun_SSH_1.4 > debug1: use_engine is 'yes' > > Here is an attempt to ssh to a Debian Linux box from NCP2 kernel 124 box: > > Sun_SSH_1.4, SSH protocols 1.5/2.0, OpenSSL 0x009080bf > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: Rhosts Authentication disabled, originating port will not be trusted. > debug1: ssh_connect: needpriv 0 > debug1: Connecting to 192.168.111.23 [192.168.111.23] port 22. > debug1: Connection established. > debug1: identity file /export/home/nexenta/.ssh/identity type -1 > debug1: identity file /export/home/nexenta/.ssh/id_rsa type 1 > debug1: identity file /export/home/nexenta/.ssh/id_dsa type -1 > debug1: Remote protocol version 2.0, remote software version > OpenSSH_5.1p1 Debian-5 > debug1: match: OpenSSH_5.1p1 Debian-5 pat OpenSSH* > debug1: Enabling compatibility mode for protocol 2.0 > debug1: Local version string SSH-2.0-Sun_SSH_1.4 > debug1: use_engine is 'yes' > > > 2. Something is wrong with service svc:/system/rbac:default - it is > in maintenance mode after booting the new kernel from apt-clone > dist-upgrade. > > Here is the output of "svcs -xv" command: > svc:/system/rbac:default (Assemble the RBAC *attr files.) > State: maintenance since Wed Oct 07 20:12:41 2009 > Reason: Start method exited with $SMF_EXIT_ERR_FATAL. > See: http://sun.com/msg/SMF-8000-KS > See: /var/svc/log/system-rbac:default.log > Impact: This service is not running. > > Here is an example of what shows up in the > /var/svc/log/system-rbac:default.log file: > > [ Oct 7 20:12:34 Enabled. ] > [ Oct 7 20:12:40 Executing start method ("/lib/svc/method/svc-rbac start"). ] > /usr/sadm/install/scripts/i.rbac: not found. > [ Oct 7 20:12:41 Method "start" exited with status 95. ] > > The /lib/svc/method/svc-rbac file exists and is what produces the "not > found" message above from this code snippet: > > irbac=/usr/sadm/install/scripts/i.rbac > > if [ ! -x $irbac ] > then > echo "${irbac}: not found." > exit $SMF_EXIT_ERR_FATAL > fi > > > So looks like it may be simply that there is a missing > /usr/sadm/install/scripts/i.rbac file. The nexenta-on-source package > seems to contain this file in the location > usr/src/pkgdefs/common_files/i.rbac but I have not tried putting it in > place to see if it fixes the problem. I will try to do that and > report back my findings in a separate reply. > > Let me know if you are aware of these and are already working on them. > If you want them in Launchpad just let me know and I'll file the > bugs. Hopefully I'm not the first to see these but wanted to point > them out since no one else had so far via email or lauchpad yet. I > have not visited IRC in a long time so not sure if it has been brought > up there or not... sorry to have "disappeared" for so long. I've been > pretty busy with work/etc and haven't had much time to volunteer over > the last few months. > > Thanks a bunch for any info/fixes on these! > Jason > > On Mon, Sep 28, 2009 at 9:25 PM, Anil Gulecha <anil.ve...@gmail.com> wrote: >> Hi All, >> >> A quick heads-up to all users.. we will be uploading b124 of >> opensolaris to hardy-unstable shortly. >> >> If you plan on upgrading, you *may* face some issues. Please report >> them in reply to this, or post on >> https://bugs.launchpad.net/nexenta/+filebug . We will be working on >> fixing them ASAP. If any upgrade does go b0rk.. you can simply revert >> back thanks to apt-clone (since this is a kernel upgrade, apt-clone >> _will_ create a checkpoint). >> >> We will also be setting up hardy-stable shortly (something we missed >> with NCP2), and populating it with the latest kernel and stable bits. >> This will form the basis of NCP3 release in the coming month. >> >> -- >> Regards >> Anil >> _______________________________________________ >> gnusol-devel mailing list >> gnusol-devel@lists.sonic.net >> http://lists.sonic.net/mailman/listinfo/gnusol-devel >> > _______________________________________________ gnusol-devel mailing list gnusol-devel@lists.sonic.net http://lists.sonic.net/mailman/listinfo/gnusol-devel
