On 30 July 2017 at 12:15, Peter Tribble wrote:
> illumos panics when trying to use the xen network.
Do you have a crash dump, or at least a stack trace, for this? We
should probably get a ticket filed.
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.
lltimestamp - last > 100/
{
printf("\n");
}
zfs-dbgmsg
{
printf("%Y %s\n", walltimestamp, stringof(arg0));
last = walltimestamp;
}
'
Cheers.
--
Joshua M. Clul
y is that? There shouldn't be any difference between a native zone
and an LX zone with respect to untrusted workloads. The containment
model is the same in both cases.
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
t up to a high number made my
logs almost silent. Most of the cheap (and thus plentiful) scans are
on port 22 only.
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.o
truss -t "open,ioctl" -f diskinfo
Once it starts hanging, you should be able to see which open(2) and
ioctl(2) calls happened just before the hang.
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
I think you've grabbed the "sudo" process, rather than the child
"diskinfo" process. If you use "ptree" on the pid first, you'll be
able to see the full tree of processes.
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
f0011b57f10 sys_syscall32+0x123()
That might tell us where in the storage subsystem you're getting stuck.
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti
ltiple_ potentially
untrustworthy but independent sources, and using them only to
occasionally _reseed_ a high quality PRNG rather than directly using
the "random" output, we should be safe.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
__
set the BIOS to an "optimised performance" factory
defaults set.
Can you try various default BIOS settings that to see if that allows
the system to boot?
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OmniOS
dd the appropriate console settings, e.g.
-B console=ttyb,ttyb-mode="115200,8,n,1,-"
(NB: that's for "ttyb", aka COM2. If your IPMI serial-over-LAN port
is COM1 you'll want ttya instead.)
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
__
n expander. An expander is just another active
component with its own potentially buggy firmware.
Less firmware is essentially a riff on "less moving parts" from a
reliability standpoint. Also, if you ever need to upgrade the
firmware in the expander, that will likely be extremely diffi
e to
> know ahead of time
We make heavy use of the PostgreSQL packages from pkgsrc[1] at Joyent,
but running on SmartOS (another illumos distribution). I should
expect it works just as well on OmniOS!
[1]: https://pkgsrc.joyent.com/
--
Joshua M. Clulow
UNIX Admin/
tem calls and
other Linux facilities, 64-bit support, etc.
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
CPU is in it? We have
experienced some issues with SmartOS running in VMware Fusion on some
models of Intel CPU. I believe there is an erratum about spurious
page faults when running a hypervisor that makes use of EPT.
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
ad to memory exhaustion deadlocks, amongst other things. I
don't know if it's expected to be tuneable without a reboot.
Cheers.
--
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
15 matches
Mail list logo