Re: [OpenIndiana-discuss] "bad mutex" crash?
Okay thanks. -Original Message- From: Richard Lowe [mailto:richl...@richlowe.net] Sent: Monday, October 29, 2012 10:13 PM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] "bad mutex" crash? Ruled out what I was wondering. I'd file an illumos bug describing the configuration, etc, and make the crashdump available somehow. -- Rich ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] "bad mutex" crash?
Ruled out what I was wondering. I'd file an illumos bug describing the configuration, etc, and make the crashdump available somehow. -- Rich ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI and console switching
I had a (fruitless) hunch - on most of those SXCE systems I've had remote consoles (serial or IPMI) and used vtdaemon to also have a text login on physical screen/keyboard. I've tried to boot the laptop with console=(text|graphics|ttya) and with no console setting, but these did not help. In ttya mode (laptop has no serial ports) I got text output from SMF scripts echoed to /dev/console. In graphics mode I got a blank text-mode screen for a couple of minutes until I got the GDM login. Text mode and no console setting were identical for me (perhaps due to bootenv.rc, which I'll now untweak). I begin to wonder if virtual terminals somehow depend on some graphics capabilities of the video card, and the AMD E2 CPU/GPU built-in Radeon is not good enough (it is only a VESA VGA for X). This sounds crazy even to me, but might explain the symptoms ;) Puzzled... //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] "bad mutex" crash?
Oh, anyway, no VM snapshots for this VM anyway, since it has a passed-in HBA therefore VM snapshots are disabled... -Original Message- From: Jim Klimov [mailto:jimkli...@cos.ru] Sent: Monday, October 29, 2012 5:33 PM To: openindiana-discuss@openindiana.org Subject: Re: [OpenIndiana-discuss] "bad mutex" crash? 2012-10-28 23:55, Dan Swartzendruber wrote: > fill). I guess I can create a 32GB virtual disk and move the rpool to > it, but it seems like kind of a waste just for the off chance I get a > kernel panic. Are there any ways to dodge this, or do I need to just > bite the bullet? I think you can configure dumpadm to use another pool for dumps. You can certainly use another pool for swap area, and free up space on rpool - if rpool/dump must indeed be on rpool. Quite likely, you can also expand (live or offline) your VM's harddisk and then autoexpand your rpool, though that would likely require merging and destruction of older VM (hypervizor's) snapshots. HTH, //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] "bad mutex" crash?
I'm thinking of migrating to a bigger root pool vmdk. In normal circumstances, the dump zvol will be empty, so using veeam backup should be able to squeeze the dump down to a smaller file. Thanks! -Original Message- From: Jim Klimov [mailto:jimkli...@cos.ru] Sent: Monday, October 29, 2012 5:33 PM To: openindiana-discuss@openindiana.org Subject: Re: [OpenIndiana-discuss] "bad mutex" crash? 2012-10-28 23:55, Dan Swartzendruber wrote: > fill). I guess I can create a 32GB virtual disk and move the rpool to > it, but it seems like kind of a waste just for the off chance I get a > kernel panic. Are there any ways to dodge this, or do I need to just > bite the bullet? I think you can configure dumpadm to use another pool for dumps. You can certainly use another pool for swap area, and free up space on rpool - if rpool/dump must indeed be on rpool. Quite likely, you can also expand (live or offline) your VM's harddisk and then autoexpand your rpool, though that would likely require merging and destruction of older VM (hypervizor's) snapshots. HTH, //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] "bad mutex" crash?
2012-10-28 23:55, Dan Swartzendruber wrote: fill). I guess I can create a 32GB virtual disk and move the rpool to it, but it seems like kind of a waste just for the off chance I get a kernel panic. Are there any ways to dodge this, or do I need to just bite the bullet? I think you can configure dumpadm to use another pool for dumps. You can certainly use another pool for swap area, and free up space on rpool - if rpool/dump must indeed be on rpool. Quite likely, you can also expand (live or offline) your VM's harddisk and then autoexpand your rpool, though that would likely require merging and destruction of older VM (hypervizor's) snapshots. HTH, //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI and console switching
2012-10-28 23:56, Udo Grabowski (IMK) пишет: This is irritating, you have 2 times /dev/console, one with the -p nbofh prompt, one with -p buil. Looks like there is another console process without a tty which started 1:40 minutes after startup. That must be a local zone's console... Also, did you activate the hotkeys ? svccfg -s vtdaemon setprop options/hotkeys=true svcadm refresh vtdaemon svcadm restart vtdaemon log off, restart X server That's embarassing - I did not. Where I came from (SXCE) this did not need to be set, and I still got a "vt" login prompt. Alas, enabling this option did not heal my problem - the switchover in text mode to any other console does not happen :( //JIm ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ACPI errors
Hello, just a quick follow-up on this issue: These ACPI errors are still present both with oi 151a7 and Solaris 11.1. Since I observed a similar message with CentOS 6 (and, by inference, RHEL 6) but not with earlier linux versions, I issued a bug report with them, and got this useful hint: "HP's firmware doesn't like _OSC being called multiple times. This is a violation of 6.2.10 of the ACPI specification, but was worked around in upstream commit 415e12b2379239973feab91850b0dce985c6058a" This "commit" can be found here: http://git.opencores.org/?a=commit&p=linux&h=415e12b2379239973feab91850b0dce985c6058a I hope this helps to get a fix (or workaround) into OpenIndiana ACPI. Best regards, Oliver From: Milan Jurik [milan.ju...@xylab.cz] Sent: Sunday, July 15, 2012 12:36 PM To: Weiergräber, Oliver H. Subject: RE: [OpenIndiana-discuss] ACPI errors Hi Olivier, OK, so you are on the latest OI ACPI, 20110527, the issue found by Dana was fixed already. It looks like some different bug. I have to look at it but it is some time I was working on Solaris ACPI so I need to refresh my knowledge. I will inform you about progress if there will be some. In parallel somebody else is trying to update Illumos ACPI to the newer versions, maybe it will help. Best regards, Milan "Weiergräber, Oliver H." píše v pá 13. 07. 2012 v 20:07 +: > Hi Milan, > > please find attached the log file for a complete boot process. > > "pkg info system/kernel" gives me: > Name: system/kernel >Summary: Core Solaris Kernel >Description: core kernel software for a specific instruction-set > architecture > Category: System/Core > State: Installed > Publisher: openindiana.org >Version: 0.5.11 > Build Release: 5.11 > Branch: 0.151.1.5 > Packaging Date: June 30, 2012 07:54:37 PM > Size: 45.44 MB > FMRI: > pkg://openindiana.org/system/kernel@0.5.11,5.11-0.151.1.5:20120630T195437Z > > "pkg verify system/kernel" does not output anything. > > Best regards and many thanks > Oliver > > > > From: Milan Jurik [milan.ju...@xylab.cz] > Sent: Tuesday, July 10, 2012 7:54 PM > To: Weiergräber, Oliver H. > Subject: RE: [OpenIndiana-discuss] ACPI errors > > Hi Olivier, > > I do not think it is problem of some device you can remove. > > Anyway, can you send me the whole messages file (/var/adm/messages) with > acpica errors. > > Could you run: > > pkg info system/kernel > > pkg verify system/kernel > > on your system? > > Best regards, > > Milan > > "Weiergräber, Oliver H." píše v po 09. 07. 2012 v 08:25 +: > > Dear Milan, > > > > sure, please find attached the output of acpidump. > > > > Did some more research in the meantime. It seems this issue has bothered a > > number of people recently. There are (and have been) a few bug reports for > > RHEL and other linux distributions, often concerning HP workstations (as in > > my case). Looking into https://www.acpica.org/download/changes.txt it > > appears that this issue is mentioned in the release notes from 12 January > > 2011: > > > > "Fixed several issues and a possible fault with the automatic "serialized" > > method support. History: This support changes a method to "serialized" on > > the > > fly if the method generates an AE_ALREADY_EXISTS error, indicating the > > possibility that it cannot handle reentrancy. This fix repairs a couple of > > issues seen in the field, especially on machines with many cores: > > > > 1) Delete method children only upon the exit of the last thread, > >so as to not delete objects out from under other running threads > > (and possibly causing a fault.) > > 2) Set the "serialized" bit for the method only upon the exit of the > >Last thread, so as to not cause deadlock when running threads > >attempt to exit. > > 3) Cleanup the use of the AML "MethodFlags" and internal method flags > >so that there is no longer any confusion between the two. > > > > Lin Ming, Bob Moore. Reported by dana.my...@oracle.com." > > > > But this does not explain why the "AE_ALREADY_EXISTS" error is generated in > > the first place. Would be nice to know which hardware component or function > > is problematic, but not being a developer, I was unable to extract any > > useful information from acpidump. > > > > Hope this helps, > > Oliver > > > > > > > > > > > > > Forschungszentrum Juelich GmbH > 52425 Juelich > Sitz der Gesellschaft: Juelich > Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 > Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher > Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender), > Karsten Beneke (stellv. Vorsitzende
Re: [OpenIndiana-discuss] How to disable local/remote login, still allowing access to smb share?
On 10/29/12 11:42 AM, Dmitry Kozhinov wrote: I have already tried setting a shell to "/bin/false". This may prevent remote logins or local text logins (I have not tested though), but local graphic login went without problems. Disable graphical login on the server. svcadm disable gdm ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to disable local/remote login, still allowing access to smb share?
So the solution should be somewhere around PAM... I would be happy if I could maintain a separate username/password database for smb/cifs shares, not related to OI users, but afraid this is not possible. On 29.10.2012 21:46, Dan Swartzendruber wrote: Wrt /bin/false, I ran into such an exception: I installed freeradius on my ubuntu main server so my astaro gateway could authenticate people. They already had accounts on that host for email - all of them using /bin/false. I naively tried to use the freeradius plugin "unix password" (not the right name, but the gist is accurate.) freeradius would reject auth attempts due to 'invalid shell'. I ended up using the pam plugin and all was well... -Original Message- From: Jan Owoc [mailto:jso...@gmail.com] Sent: Monday, October 29, 2012 11:24 AM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] How to disable local/remote login, still allowing access to smb share? Hi Dmitry, On Mon, Oct 29, 2012 at 9:17 AM, Dmitry Kozhinov wrote: I am still newbie to UNIX administration. Please advise. After setting up a storage server (a number of smb shares, as described at http://wiki.openindiana.org/oi/Using+OpenIndiana+as+a+storage+server), I ended up having a number of users at my system, each one needed only to access an smb share from a Windows client machine. How do I prevent using these usernames/passwords to login locally or remotely to the server, and only use them to access smb shares? I'm not a professional UNIX administrator, but the way I've seen it done is to set the logon shell for those users to "/bin/false". An alternative is "/usr/bin/passwd", so they can't get a logon shell, but they can "log on" to change their password. There are some things for which /bin/false doesn't work, but it might be enough for your needs [1]. [1] http://www.semicomplete.com/articles/ssh-security/ Jan ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to disable local/remote login, still allowing access to smb share?
Wrt /bin/false, I ran into such an exception: I installed freeradius on my ubuntu main server so my astaro gateway could authenticate people. They already had accounts on that host for email - all of them using /bin/false. I naively tried to use the freeradius plugin "unix password" (not the right name, but the gist is accurate.) freeradius would reject auth attempts due to 'invalid shell'. I ended up using the pam plugin and all was well... -Original Message- From: Jan Owoc [mailto:jso...@gmail.com] Sent: Monday, October 29, 2012 11:24 AM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] How to disable local/remote login, still allowing access to smb share? Hi Dmitry, On Mon, Oct 29, 2012 at 9:17 AM, Dmitry Kozhinov wrote: > I am still newbie to UNIX administration. Please advise. After setting > up a storage server (a number of smb shares, as described at > http://wiki.openindiana.org/oi/Using+OpenIndiana+as+a+storage+server), > I ended up having a number of users at my system, each one needed only > to access an smb share from a Windows client machine. How do I prevent > using these usernames/passwords to login locally or remotely to the > server, and only use them to access smb shares? I'm not a professional UNIX administrator, but the way I've seen it done is to set the logon shell for those users to "/bin/false". An alternative is "/usr/bin/passwd", so they can't get a logon shell, but they can "log on" to change their password. There are some things for which /bin/false doesn't work, but it might be enough for your needs [1]. [1] http://www.semicomplete.com/articles/ssh-security/ Jan ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to disable local/remote login, still allowing access to smb share?
I have already tried setting a shell to "/bin/false". This may prevent remote logins or local text logins (I have not tested though), but local graphic login went without problems. On 29.10.2012 21:24, Jan Owoc wrote: Hi Dmitry, On Mon, Oct 29, 2012 at 9:17 AM, Dmitry Kozhinov wrote: I am still newbie to UNIX administration. Please advise. After setting up a storage server (a number of smb shares, as described at http://wiki.openindiana.org/oi/Using+OpenIndiana+as+a+storage+server), I ended up having a number of users at my system, each one needed only to access an smb share from a Windows client machine. How do I prevent using these usernames/passwords to login locally or remotely to the server, and only use them to access smb shares? I'm not a professional UNIX administrator, but the way I've seen it done is to set the logon shell for those users to "/bin/false". An alternative is "/usr/bin/passwd", so they can't get a logon shell, but they can "log on" to change their password. There are some things for which /bin/false doesn't work, but it might be enough for your needs [1]. [1] http://www.semicomplete.com/articles/ssh-security/ Jan ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to disable local/remote login, still allowing access to smb share?
Hi Dmitry, On Mon, Oct 29, 2012 at 9:17 AM, Dmitry Kozhinov wrote: > I am still newbie to UNIX administration. Please advise. After setting up a > storage server (a number of smb shares, as described at > http://wiki.openindiana.org/oi/Using+OpenIndiana+as+a+storage+server), I > ended up having a number of users at my system, each one needed only to > access an smb share from a Windows client machine. How do I prevent using > these usernames/passwords to login locally or remotely to the server, and > only use them to access smb shares? I'm not a professional UNIX administrator, but the way I've seen it done is to set the logon shell for those users to "/bin/false". An alternative is "/usr/bin/passwd", so they can't get a logon shell, but they can "log on" to change their password. There are some things for which /bin/false doesn't work, but it might be enough for your needs [1]. [1] http://www.semicomplete.com/articles/ssh-security/ Jan ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] How to disable local/remote login, still allowing access to smb share?
Hi all, I am still newbie to UNIX administration. Please advise. After setting up a storage server (a number of smb shares, as described at http://wiki.openindiana.org/oi/Using+OpenIndiana+as+a+storage+server), I ended up having a number of users at my system, each one needed only to access an smb share from a Windows client machine. How do I prevent using these usernames/passwords to login locally or remotely to the server, and only use them to access smb shares? Dmitry. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
