I had been toying around with a lot of different settings, it's possible I just
messed something up in the process. Let me try again with a fresh zone.
Sent from my iPhone
> On Dec 11, 2014, at 2:18 AM, Tim Rice wrote:
>
> On Thu, 11 Dec 2014, Alex McWhirter wrote:
>
> | Yea, some services pi
On Thu, 11 Dec 2014, Alex McWhirter wrote:
| Yea, some services picked it up but others did not. It seems the
identity/node service does not have the config variable set for nodename. I
attempted to set it but received and error saying that the variable didn't
exist.
|
| I don't think this was
Editing nodename and rebooting the zone will give it a different name. I do
this on my own HDC.
Dan
Sent from my iPhone (typos, autocorrect, and all)
> On Dec 11, 2014, at 1:30 AM, Tim Rice wrote:
>
>> On Wed, 10 Dec 2014, Alex McWhirter wrote:
>>
>> I have a small cluster of servers hostin
Yea, some services picked it up but others did not. It seems the identity/node
service does not have the config variable set for nodename. I attempted to set
it but received and error saying that the variable didn't exist.
I don't think this was ever an intended function for a zone.
Sent from m
On Wed, 10 Dec 2014, Alex McWhirter wrote:
> I have a small cluster of servers hosting zones over multiple VLAN’s. I would
> like to name the zones so that they don’t run into naming collisions. For
> example, instead of “web0” i would like to name them “2049_web0” and
> “2050_web0”. The proble
I have a small cluster of servers hosting zones over multiple VLAN’s. I would
like to name the zones so that they don’t run into naming collisions. For
example, instead of “web0” i would like to name them “2049_web0” and
“2050_web0”. The problem is that this set’s the hostname to “_web0”. Is
Thanks Dan.
Alas, I get stuck here:
root@massive02-b:~# pkg -R /mnt update
Creating Plan -
pkg update: The certificate which issued this
certificate:/C=US/ST=Maryland/O=OmniTI/OU=OmniOS/CN=OmniOS r151012
Release Signing Certificate/emailAddress=omnios-supp...@omniti.com
could not be found. The is
Thank you to Eric Sproul (now of Circonus)! Here's his good news:
. . .
Good news everyone!
As many of you are aware, the current practice for core OmniOS
packaging is to separate packages for a given release into their own
repository. This was prompted by all the headaches caused when
r151
Hi Dan,
Am 10.12.14 um 21:17 schrieb Dan McDonald:
On Dec 10, 2014, at 3:14 PM, Stephan Budach wrote:
Now, this one… I don't get it. ;)
root@nfsvmpool01:~# ipadm create-if ixgbe3
root@nfsvmpool01:~# ipadm show-if
IFNAME STATECURRENT PERSISTENT
lo0ok -m-v--46 ---
> On Dec 10, 2014, at 3:14 PM, Stephan Budach wrote:
>
>>
> Now, this one… I don't get it. ;)
>
> root@nfsvmpool01:~# ipadm create-if ixgbe3
> root@nfsvmpool01:~# ipadm show-if
> IFNAME STATECURRENT PERSISTENT
> lo0ok -m-v--46 ---
> igb0 ok bm
Am 10.12.14 um 20:56 schrieb Stephan Budach:
I don't know… it seems to have serious issues with the MTU specifically…
root@nfsvmpool01:~# dladm show-phys
LINK MEDIASTATE SPEED DUPLEX DEVICE
igb0 Ethernet up 1000 full igb0
igb1
Am 10.12.14 um 20:28 schrieb Dan McDonald:
On Dec 10, 2014, at 2:23 PM, Stephan Budach wrote:
This worked, but I wanted to change the MTU, so I deciced to remove this config
again:
ipadm delete-addr ixgb3/v4static
ipadm delete-if ixgbe3
Interesting. Your "dladm show-linkprop" output didn't
> On Dec 10, 2014, at 2:23 PM, Stephan Budach wrote:
>
> This worked, but I wanted to change the MTU, so I deciced to remove this
> config again:
>
> ipadm delete-addr ixgb3/v4static
> ipadm delete-if ixgbe3
Interesting. Your "dladm show-linkprop" output didn't have anything for
ixgbe3. I
Am 10.12.14 um 20:12 schrieb Dan McDonald:
You said it was ipadm earlier, not dladm.
Well, yes it was. I am sure that ipadm will now hang as well.
On Dec 10, 2014, at 2:07 PM, Stephan Budach wrote:
Ahh… here we go again…
root@nfsvmpool01:~# dladm show-linkprop -p mtu
LINK PROPERTY
You said it was ipadm earlier, not dladm.
> On Dec 10, 2014, at 2:07 PM, Stephan Budach wrote:
> Ahh… here we go again…
>
> root@nfsvmpool01:~# dladm show-linkprop -p mtu
> LINK PROPERTYPERM VALUE DEFAULT POSSIBLE
> igb0 mtu rw 1500 1500
Am 10.12.14 um 17:38 schrieb Stephan Budach:
Am 10.12.14 um 17:20 schrieb Dan McDonald:
On Dec 10, 2014, at 11:12 AM, Stephan Budach
wrote:
Hi Dan,
I actually don't know the term "incantation" yet, but I assume, that
you wanted to know the release of OmniOS I am running?
I meant what exact
> On Dec 10, 2014, at 1:42 PM, Ian Kaufman wrote:
>
> It looks like this system is in some weird state where there are
> packages from 151006 and 151008.
Oh my.
Yes, you've been bitten by the pkg upgrade problems between 006 and 008. This
was before my time here, so I'm not sure how best to
It looks like this system is in some weird state where there are
packages from 151006 and 151008.
For example, /etc/release shows:
root@massive02-b:~# cat /etc/release
OmniOS v11 r151008
Copyright 2013 OmniTI Computer Consulting, Inc. All rights reserved.
Use is subject to license terms.
b
> On Dec 10, 2014, at 12:01 PM, Ian Kaufman wrote:
>
> Hi all,
>
> I have a situation where a bunch of libs are complaining about missing
> the following:
>
> libc.so.1 (ILLUMOS_0.7)
>
> or
>
> libc.so.1 (ILLUMOS_0.6)
>
> This is happening on one system, but I have others that are fine. A
>
Hi all,
I have a situation where a bunch of libs are complaining about missing
the following:
libc.so.1 (ILLUMOS_0.7)
or
libc.so.1 (ILLUMOS_0.6)
This is happening on one system, but I have others that are fine. A
standard libc.so.1 exists, but various libs are looking for the tagged
one.
Any
Am 10.12.14 um 17:20 schrieb Dan McDonald:
On Dec 10, 2014, at 11:12 AM, Stephan Budach wrote:
Hi Dan,
I actually don't know the term "incantation" yet, but I assume, that you wanted
to know the release of OmniOS I am running?
I meant what exact command-line arguments you typed for ipadm(1M)
> On Dec 10, 2014, at 11:12 AM, Stephan Budach wrote:
>
> Hi Dan,
>
> I actually don't know the term "incantation" yet, but I assume, that you
> wanted to know the release of OmniOS I am running?
I meant what exact command-line arguments you typed for ipadm(1M). But that's
okay, because it'
Hi Dan,
I actually don't know the term "incantation" yet, but I assume, that you
wanted to know the release of OmniOS I am running? If not, please
correct me on that.
What is really funny, is that running pstack against the ipadm process,
somehow brought things back in line:
root@nfsvmpool01
> On Dec 10, 2014, at 4:16 AM, Stephan Budach wrote:
>
> Hi all,
>
> I have run into a situation, where ipadm hangs upon trying to create a new
> interface on my ixgbe adaptors. ipadm create-if ixgbe[0|1|2] didn't return
> and either got killed eventually by the system or by kill -9, which I
On Tue, Dec 9, 2014 at 9:51 AM, Dominik Hassler wrote:
> Chip,
>
> when I had to reflash an onboard LSI2308 I used the UEFI shell. No
> fiddling around with boot disks etc.
>
> Not sure, if it is applicable to your problem.
>
That was the trick. Under DOS I kept getting "ERROR: Failed to initia
Hi Michael,
Today Michael Mounteney wrote:
> On Wed, 10 Dec 2014 06:14:56 +0100 (CET)
> Tobias Oetiker wrote:
>
> > This leads me to suspect, that either only very few people are
> > using omnios as a kvm server OR it is also a hardware dependent
> > problem.
>
> I think it must be. I'm running
On Wed, 10 Dec 2014 06:14:56 +0100 (CET)
Tobias Oetiker wrote:
> This leads me to suspect, that either only very few people are
> using omnios as a kvm server OR it is also a hardware dependent
> problem.
I think it must be. I'm running KVM (Gentoo Linux guests) and have
just gone from 151010 t
Hi all,
I have run into a situation, where ipadm hangs upon trying to create a
new interface on my ixgbe adaptors. ipadm create-if ixgbe[0|1|2] didn't
return and either got killed eventually by the system or by kill -9,
which I issued against that process. I just tried to create another if
on
28 matches
Mail list logo
