[00:06:54] *** myers has joined ##nexenta
[00:08:20] *** drac_h has quit IRC
[00:19:14] *** bklang_ has quit IRC
[00:36:54] *** andy_js_ has joined ##nexenta
[00:39:53] *** andy_js has quit IRC
[00:39:53] *** andy_js_ is now known as andy_js
[00:41:47] *** andy_js has quit IRC
[00:59:08] *** RichiH has left ##nexenta
[01:25:39] <victori> well hasn't crashed so far, *knocks on wood*
[01:29:08] *** myers has quit IRC
[02:13:37] <victori> nexenta lacks projmod projadd?
[02:18:10] *** myers has joined ##nexenta
[02:24:38] <Teknix> victori: I posted #232 and there is no way around it without backporting the fix that went into Illumos and building a new package
[02:24:51] <Teknix> er, #242
[02:25:03] <victori> but it is addressed in 3.1 ncp right?
[02:25:12] <Teknix> apparently
[02:25:29] <Teknix> the question is, will that be NCP 3.1 or only NexentaStor 3.1
[02:26:03] <Teknix> there has already been a newer release of NexentaStor with backported fixes, but not an equivalent NCP release
[02:26:19] <Teknix> in theory Nexenta will be updating the community in the next week or so
[02:26:20] <victori> ouch ;-(
[02:26:26] <victori> oh nice
[02:27:08] <victori> well hopefully the box wonder fall apart under the web traffic
[02:27:13] <victori> won't*
[02:27:39] <Teknix> I haven't experienced it in awhile, but I make it a point to try and not restart any tomcat instances
[02:27:57] <Teknix> it really sucks on a box that has other non-web zones on it, because it takes the whole box down
[02:28:05] *** jon____ has joined ##nexenta
[02:28:26] <victori> Teknix not using tomcat but jetty, but I am sure the symptoms  are the same
[02:28:53] <Teknix> probably
[02:29:25] <Teknix> I have over 25 zones running on NCP 2 still because of this
[02:29:33] <victori> ah
[03:05:19] *** master_of_master has quit IRC
[03:09:44] *** master_of_master has joined ##nexenta
[03:53:19] *** Sergef has joined ##nexenta
[03:53:52] *** Sergef has quit IRC
[03:54:48] *** Sergef has joined ##nexenta
[04:39:33] *** Thrae has quit IRC
[04:49:30] *** Thrae has joined ##nexenta
[05:29:10] *** myers has joined ##nexenta
[06:05:10] *** myers has quit IRC
[06:16:46] <victori> yep, box is crashing
[06:18:27] *** jon____ has quit IRC
[06:53:21] <victori> Teknix does this only happen in zones?
[06:54:56] *** tsukasa has quit IRC
[06:58:11] *** ry has quit IRC
[07:07:06] *** tsukasa has joined ##nexenta
[07:13:14] *** jon__ has joined ##nexenta
[07:25:58] *** jon__ has quit IRC
[07:28:45] <victori>  http://webcache.googleusercontent.com/search?q=cache:aD1tJBtm5SAJ:bugs.opensolaris.org/bugdatabase/printableBug.do%3Fbug_id%3D6926316+kernal+panic+crgrprele&cd=1&hl=en&ct=clnk&gl=us&source=www.google.com  -- this thread really helped me figure out what is specifically triggering the bug
[07:28:58] <victori> postfix ;-(
[07:38:28] *** HyperJohnGraham has quit IRC
[07:40:34] <victori> is it possible to upgrade from NCP to NexentaStor community edition -- if that is were the work is being done?
[07:41:11] <Andys^> doubt it
[07:42:15] <victori> and I don't suppose there is some -bleeding apt repo for 3.1?
[07:42:32] <Andys^> nope
[07:42:42] <victori> yep I am screwed.
[07:42:56] <Andys^> want my advice?
[07:42:59] <victori> sure
[07:43:20] <Andys^> run a linux distro in a VM of some kind, use nexenta as its storage back end
[07:44:01] <victori> well, won't that still trigger the tcp bug if the vm is running ontop of nexenta?
[07:44:11] <Andys^> shouldn't do
[07:44:15] <Andys^> it'll use the guest's TCP stack
[07:45:42] <victori> I guess I can install solaris 11 in virtualbox and run it from there -- we have a pretty complex mail setup + hosting stack, lots of automation that depends on smf etc. Why I have not hopped ship from *solaris to say freebsd.
[07:46:02] <victori> Andys^ that is some good advice actually, worth a shot
[07:46:13] <Andys^> ah ok - SMF ties you pretty closely to solaris then
[07:51:06] <Triskelios> possibly good news, http://apt.nexentastor.org/3.1/ seems to be public
[07:51:20] <victori> time to try it on  a vm
[07:51:45] <Andys^> its probably just a copy of 3.0 ;)
[07:52:03] <Triskelios> no, it's current
[07:52:25] <victori> Andys^: so I can possibly use it to update the kernel past this bug?
[07:52:28] <victori> err
[07:52:30] <victori> Triskelios: I mean
[07:53:26] <Triskelios> victori: yes, although I can't guarantee anything when using a NS repo on NCP (although I don't know of anything that would cause breakage)
[07:53:31] <Triskelios> (since the core packages are the same anyway)
[07:54:32] <victori> and how would you point to 3.1 specifically?
[07:54:34] <victori> in apt sources?
[07:55:08] <Triskelios> right, that becomes the base URL
[07:56:03] *** jon____ has joined ##nexenta
[07:56:09] <victori> deb http://apt.nexenta.org hardy-unstable main contrib non-free   --- not sure how it is picking up on it?
[07:56:23] <victori> http://apt.nexenta.org/  -- does not have hard-unstable in that path
[07:56:38] <victori> oh under dists I suppose
[07:57:30] <victori> yep here goes nothing
[07:57:50] <victori> if this works, I will be jumping for joy ;-)
[08:05:10] <victori> well looks like it updated and booted but kernel 134f in 3.1?
[08:05:47] <victori> motd now says 3.1
[08:06:47] <Andys^> same kernel? :/
[08:06:56] <victori> looks like kernel got updated
[08:07:00] <victori> says the zpool is old
[08:07:04] <victori> which is good, new kernel.
[08:07:13] <Andys^> what were you running before though?
[08:07:22] <Andys^> i'm using NCP 3.0.1 and i'm pretty sure its 134f
[08:07:26] <victori> zpool 26
[08:07:39] <victori> now the pool in the version is 28
[08:13:01] <Andys^> hrmm
[08:13:12] <Andys^> weird, i'm on NexentaOS_134f but zpool 26
[08:13:18] <victori> so the kernel is newer, just not sure how explicitly check which version
[08:13:25] <victori> right Andys^ that is my point
[08:13:35] <victori> since updating to 3.1 repo I have access to upgrade to zpool 28
[08:16:14] <victori> oh well, I do have apt-clone snapshots, worth a shot to update to newer version and see if it works
[08:19:46] *** ry has joined ##nexenta
[08:20:01] <victori> going to update server now -- worked well in vm ;-/
[08:21:57] <MACscr> victori: v28 has some significant improvements doesnt it?
[08:22:23] <victori> does it? improved snapshot creation and multiple vdev replacements
[08:22:26] <victori> or so upgrade says
[08:23:37] <Andys^> multiple replace? *boggle*
[08:23:41] <Andys^> i guess thats useful for RAID10
[08:25:00] <MACscr> wasnt the volatility of zil drastically improved as well?
[08:25:04] <victori> what was the last opensolaris kernel btw?
[08:26:25] <Andys^> ~148 i think
[08:26:42] <Andys^> MACscr: perhaps you are referring to zpool import -F. Allows to rewind corrupted pool to earlier
[08:26:56] <victori> all I have to say, awesome that I can update to 3.1 and rollback if needed. zfs++
[08:28:35] <Andys^> yeah :)
[08:28:36] <victori> box is backup and in business; Triskelios thanks for the apt repo heads up
[08:29:04] <Andys^> and did it fix the bug?
[08:29:20] <victori> Andys^: well I have a dtrace script that can induce it
[08:29:33] <victori> dtrace -w -n '::crfree:entry,::crhold:entry /args[0]->cr_ref == 0 || args[0]->cr_ref == 0xdeadbeef/ { panic();}'
[08:30:06] <Andys^> hah
[08:30:31] <victori> I don't want to run it though, I will just see if the box kernel panics overnight
[08:30:44] <victori> the morning web traffic rush should induce the bug
[08:33:27] <victori> also must say, dpkg > ips by far, opensolaris cloned updates had a 50 50 chance of updating to a newer revision without segfaulting the python interpreter
[08:48:29] *** jon____ has quit IRC
[08:54:06] <Andys^> :D
[09:15:48] <victori> I guess this explains why nexentastor 3.1 apt repo is still 134f -- http://lists.illumos.org/pipermail/developer/2011-February/001463.html
[09:27:21] *** nacx has joined ##nexenta
[09:35:37] *** ibarrera has joined ##nexenta
[09:36:55] *** Tweener has joined ##nexenta
[10:25:58] *** eXeC001er has joined ##nexenta
[10:32:02] *** Darkman_ has joined ##nexenta
[10:54:44] *** andy_js has joined ##nexenta
[11:25:28] *** anatoly_l has quit IRC
[14:05:15] *** jamiec has quit IRC
[14:05:21] *** jamiec has joined ##nexenta
[14:21:28] *** bklang_ has joined ##nexenta
[14:34:11] *** 14WAA8BRS has joined ##nexenta
[14:39:15] *** myers has joined ##nexenta
[14:50:36] *** Teknix has quit IRC
[14:54:04] *** Teknix has joined ##nexenta
[14:55:49] *** Thrae has quit IRC
[14:58:28] <Edgeman> woah
[14:58:42] <Edgeman> run apt-get update and apt-get upgrade as per usual
[14:58:47] <Edgeman> expect nothing to do
[14:59:02] <Edgeman> get 317 updates
[14:59:02] <Edgeman> UNEXPECTED
[15:00:38] <Edgeman> I guess it's time for apt-clone upgrade
[15:03:22] *** anatoly_l has joined ##nexenta
[15:03:24] *** bklang_ has quit IRC
[15:09:08] *** bklang has joined ##nexenta
[15:09:12] *** myers has quit IRC
[15:21:32] *** bklang has quit IRC
[15:32:04] *** myers has joined ##nexenta
[15:38:13] *** bklang has joined ##nexenta
[15:41:27] *** zeboop has joined ##nexenta
[15:42:03] *** myers has quit IRC
[15:45:42] *** myers has joined ##nexenta
[15:48:44] *** bklang has quit IRC
[15:50:27] *** bklang_ has joined ##nexenta
[15:56:45] <Tekni> yeah, kernel still says 134f
[15:56:57] <Tekni> wonder if this is the 3.1 kernel or not
[15:59:23] <andy_js> Still no announcement :\
[16:00:48] <Tekni> I'm hopeful :)
[16:02:08] *** swy has joined ##nexenta
[16:02:22] <Tekni> well I ran zpool upgrade and it still says it's 26, so that must not be the 3.1 kernel
[16:08:47] *** McBofh has quit IRC
[16:12:38] <zeboop> I did an in-place upgrade from 3.01 to 3.04 and started seeing various problems:  system crashes when running auto-tier jobs to second Nexentastor server, auto-tier jobs fail to run for local rsync between volumes, very slow response from gui.  My second server is running 3.03 with no problems.  My question is this:  should I do apt-get update/upgrade to make sure all packages are up-to-date or just do a clean install?
[16:20:20] <zeboop> http://www.youtube.com/watch?v=vXGhvoekY44&feature=related
[16:38:01] *** pavlenko has joined ##nexenta
[16:45:46] <Edgeman> Tekni: same here
[16:46:02] <Edgeman> nothing exciting in uname -a or zpool upgrade
[16:46:46] <Edgeman> zeboop: you may want #nexentastor
[16:48:23] <zeboop> thx
[16:49:08] *** zeboop has left ##nexenta
[16:50:24] <Triskelios> the NCP repo is synced to 3.0.5 now, I think. we also didn't bump the uname version for minor releases
[16:54:22] <Tekni> Triskelios: ah, cool
[16:54:42] <Tekni> so the tcp/ip bug is definitely fixed in 3.1?
[16:56:48] <Triskelios> the reporter (was it you?) confirmed it to match an issue filed in Bugster, which we addressed
[16:57:25] <Tekni> yeah, it was me
[16:58:27] <victori> Triskelios btw thank you so much -- looks like tcp bug is squashed using http://apt.nexentastor.org/3.1/
[16:59:05] <Triskelios> great. I'll add a note to 242
[17:00:10] <Tekni> I might try it also.. is it likely that the 3.1 kernel packages will just be moved over to NCP?  Mixing packages from the two could lead to some problems
[17:00:34] <Triskelios> yeah, I expect NCP to resync after 3.1 is released
[17:01:07] <Darkman_> is there an expected release time?
[17:01:15] *** swy has quit IRC
[17:01:21] <Tekni> according to blogs.nexenta.org, any day now
[17:01:27] <victori> will switch back to older boot environment and update NCP to 3.1 when that gets released, so for now I will use the current nexentastor boot environment
[17:01:38] *** swy has joined ##nexenta
[17:01:49] <Tekni> victori: I'll be interested to know if you run into any problems
[17:02:22] <Darkman_> ok, cool, because i can wait a few days to put the new nexenta box live ;)
[17:05:06] <Edgeman> ah, so my ncp is now 3.0.5 ?
[17:05:08] <Edgeman> spiffy :)
[17:08:40] *** Thrae has joined ##nexenta
[17:09:15] <victori> Tekni so far so good, box has been up since last night.
[17:23:42] *** andygraybeal has joined ##nexenta
[17:27:00] *** kart_ has joined ##nexenta
[17:38:09] *** Darkman_ has quit IRC
[17:57:10] *** kreign has joined ##nexenta
[17:57:23] *** asqui has joined ##nexenta
[18:02:00] *** swy has quit IRC
[18:02:24] *** swy has joined ##nexenta
[18:09:44] *** Tweener has quit IRC
[18:17:14] *** nacx has quit IRC
[18:18:35] *** 14WAA8BRS has quit IRC
[18:33:20] *** McBofh has joined ##nexenta
[18:39:20] *** HyperJohnGraham has joined ##nexenta
[18:44:57] *** Dark_Mobile has joined ##nexenta
[18:52:17] *** trbs has joined ##nexenta
[19:03:02] *** swy has quit IRC
[19:03:12] *** swy has joined ##nexenta
[19:16:58] *** JagWaugh has joined ##nexenta
[19:18:16] *** devolish has quit IRC
[19:18:38] *** devolish has joined ##nexenta
[19:27:34] *** Dark_Mobile has quit IRC
[19:44:36] *** kwazar has joined ##nexenta
[19:54:54] *** MACscr has quit IRC
[19:59:03] *** MACscr has joined ##nexenta
[20:03:44] *** swy has quit IRC
[20:05:26] *** swy has joined ##nexenta
[20:19:21] *** kart_ has quit IRC
[20:20:06] *** jdparker has quit IRC
[20:27:36] *** jdparker has joined ##nexenta
[20:34:00] *** swy_ has joined ##nexenta
[20:35:18] *** swy has quit IRC
[20:35:18] *** swy_ is now known as swy
[20:38:36] *** bklang_ has quit IRC
[20:38:46] *** swy has quit IRC
[20:52:06] *** victori_ has joined ##nexenta
[20:55:50] <victori_> anyone know how you would get the current nexenta version that is running? uname -a isn't very helpful
[20:56:47] <Tekni> it would be a combo of uname -a (the NexentaOS_xxx) and something in /etc/release
[20:56:58] <Tekni> in general it can be hard to tell
[21:11:21] *** myers has quit IRC
[21:13:03] *** myers has joined ##nexenta
[22:04:37] *** bklang_ has joined ##nexenta
[22:11:39] *** myers has quit IRC
[22:13:45] *** myers has joined ##nexenta
[22:14:48] *** eXeC001er has quit IRC
[23:10:16] *** sabor has quit IRC
[23:14:24] *** myers has quit IRC
[23:14:51] *** bauruine has quit IRC
[23:26:55] *** JagWaugh has quit IRC
[23:40:40] *** myers has joined ##nexenta
[23:43:05] *** Oriona has quit IRC
[23:47:13] *** tsukasa has quit IRC
[23:47:16] *** Oriona has joined ##nexenta
[23:49:39] *** Oriona has quit IRC

   May 9, 2011  
< | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | >