Solaris 10 Update 6 with ISA Bind 9.9.3-P2
Due to CVE-2014-8500, We need to upgrade ISC Bind version to 9.10.2.
If we apply Solaris patch
20-Jan-2015
Bind
CVE-2014-8500
SPARC: 119783-30 X86: 119784-30
Will it resolve the issue?
Yes, and this is documented in MOS doc ID 1448883.1
Similar Messages
-
Problem with luactivate procedure in Solaris 10 Update 5
We are having some issues with Live Upgrade procedures with Solaris 10 Update 5 on SUN Enterprise T5240 servers.
We have successfully performed those procedures earlier on SUN Fire v240 using Solaris 10 Update 3.
Here is the problem statement:
1. Created a Flar image successfully
2. Installed on a 5240 machine from InstallServer and using jumpstart profile using a sysidcfg and flash_prof
3. The first installation is successful and system picks up configuration information from sysidcfg file on the install server.
4. Now we use lucreate to create another BE (Boot Environment) BE_2.
5. BE_2 is upgraded with luupgrade using the same flar as used in step 2.
6. Issuing command:
luactivate -s BE_2
7. After a init 6, system tries to boot from BE_2. This time instead of copying system files from BE_1 due to -s options specified, it instead runs the sysconfig command that asks for all the configuration options again.
8. When we were using these steps in Solaris 10 update 3 on Sun Fire v240, everything was working fine. The system config was available in BE_2 without any issue.
***************************************************************************************************************************************************iMovie10 only works in and exports 16:9 aspect ratio.
The resolution is set by that of the first video clip put in a project timeline. To change your project to 1080p do the following:
Create a new project
Put any known 1080p video clip in the project (it can be removed later)
Select the old project and then Edit - Select All then Edit - Copy
Select the new project and then Edit - Copy
The new project should now be 1080p. You can remove the first clip if you want.
Geoff. -
How does one regenerate the /dev/rmt/0 when cfgadm -c configure <device> will not rebuild it? Have attempted reboot -- -r, with modifing /kernel/drv/st.conf as well as /kernel/drv/sgen.conf. Running on a SPARC T4-1 Solaris 10 updat3 11, (1/13).
This has been resolved. Getting the /etc/driver_aliases set correctly: # update_drv -d -i st; update_drv -d -i sgen; add_drv -m '* 0600 root sys' -i '"scsiclass,01" "scsiclass,08" wa' worked. Making sure the st and sgen entries are in /etc/name_to_major were needed. For the Simpana/CommVault WA drivers, in opt/simpana/WA/wa.conf with the name="wa" parent="fp" target=16 lun=0 fc-port-wwn="device's World Wide Number> added for each lun 0 to 7. Then the touch /reconfigure; reboot worked. First the c1::rmt/0 tape and c1::scsi/changer/<wwn> med-changer were mapped. After modifying the minor_perm ('* 0600 root sys') and name_to_major entries, the WA CommValt entries , WA drivers showed up in cfgadm -al as c1::wa0 tape and c1::wa1 med-changer, only recognizable from CommVault. Also had to update the SAS-2 HBA StoregTek Autoloader driver with patch 145648-05. Solaris 10 update 11 (1/13) comes with 145648-03. In our particular case, we found cfgadm -al mapped SAS-2 HBA to c1 using the single mini-sas 6gb connector cable, where it mapped to c7 with the four tail connector.
-
Created zone with defaults won't boot completely (Solaris 10, Update 1)
If I create a zone with defaults, i.e. allowing the zone to inherit the typical package dirs, the resulting zone does not boot completely. When I attach to the zone via zlogin, the zone looks to be in an administrative state. It never boots to a point where one would typically enter in the initial configuration info, e.g. timezone and root password.
However if I create the zone after first removing the inherited dirs, the zone boots to a state where it subsequently can be confiured and fully booted.
Looks as if the SMF facilities are not fully initialized when the zone is configured to inherit its packages. This could be a red herring as I'm a newbie who's moved over from Linux and starting to understand SMF specifically and Solaris in general.
I did not have this problem with Solaris 10. I've just installed Solaris 10 Update 1; the problem seems specific to that installation. I reinstalled and the problem persists.I snipped the output because there were some errors, which on retrospect seems to have been a silly decision. I repeated the process and captured the missing output:
# zoneadm -z foo install
Preparing to install zone <foo>.
Creating list of files to copy from the global zone.
Copying <5913> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <942> packages on the zone.
Initialized <942> packages on zone.
Zone <foo> is initialized.
Installation of <1> packages was skipped.
Installation of these packages generated warnings: <SUNWxwfnt
SUNWxwplt SUNWxwcft SUNWjxmft SUNWxwpls SUNWpmowu
SUNWxilrl SUNWolrte SUNWi13rf SUNWi15rf SUNWi2rf SUNWi5rf
SUNWi7rf SUNWi9rf SUNWtxfnt SUNWdoc SUNWi1of SUNWi4rf
SUNWi8rf SUNW1251f SUNWarrf SUNWxwoft SUNWxwxst
SUNWkoi8f SUNWasu SUNWxrpcrt SUNWasac SUNWasdb
SUNWasut>
The file </zone/foo/root/var/sadm/system/logs/install_log> contains a log of the zone installation.The packages are related to App development and X11. I don't see any that might be related to SMF.
The logfile is too large to post at over 37K lines. However there seemed to be a pattern to the package failures. Hopefully these greps highlight the important messages:
# grep "partially failed" /zone/foo/root/var/sadm/system/logs/install_log
Installation of <SUNWxwfnt> on zone <foo> partially failed.
Installation of <SUNWxwplt> on zone <foo> partially failed.
Installation of <SUNWxwcft> on zone <foo> partially failed.
Installation of <SUNWjxmft> on zone <foo> partially failed.
Installation of <SUNWxwpls> on zone <foo> partially failed.
Installation of <SUNWpmowu> on zone <foo> partially failed.
Installation of <SUNWxilrl> on zone <foo> partially failed.
Installation of <SUNWolrte> on zone <foo> partially failed.
Installation of <SUNWi13rf> on zone <foo> partially failed.
Installation of <SUNWi15rf> on zone <foo> partially failed.
Installation of <SUNWi2rf> on zone <foo> partially failed.
Installation of <SUNWi5rf> on zone <foo> partially failed.
Installation of <SUNWi7rf> on zone <foo> partially failed.
Installation of <SUNWi9rf> on zone <foo> partially failed.
Installation of <SUNWtxfnt> on zone <foo> partially failed.
Installation of <SUNWdoc> on zone <foo> partially failed.
Installation of <SUNWi1of> on zone <foo> partially failed.
Installation of <SUNWi4rf> on zone <foo> partially failed.
Installation of <SUNWi8rf> on zone <foo> partially failed.
Installation of <SUNW1251f> on zone <foo> partially failed.
Installation of <SUNWarrf> on zone <foo> partially failed.
Installation of <SUNWxwoft> on zone <foo> partially failed.
Installation of <SUNWxwxst> on zone <foo> partially failed.
Installation of <SUNWkoi8f> on zone <foo> partially failed.
Installation of <SUNWasu> on zone <foo> partially failed.
Installation of <SUNWxrpcrt> on zone <foo> partially failed.
Installation of <SUNWasac> on zone <foo> partially failed.
Installation of <SUNWasdb> on zone <foo> partially failed.
Installation of <SUNWasut> on zone <foo> partially failed.and# grep "not installed" /zone/foo/root/var/sadm/system/logs/install_log
*** package <SPROmrdwf> was not installed:
*** package <SPROdwrfb> was not installed:
*** package <SPROlang> was not installed:
*** package <SPROlangx> was not installed:
*** package <SPROdwrfx> was not installed:
*** package <SPROsbld> was not installed:
*** package <SPROsbldx> was not installed:
*** package <SPROrdbkb> was not installed:
*** package <SPROrdbkx> was not installed:
*** package <SPROcc> was not installed:
*** package <SPROutool> was not installed:
*** package <SPROmrcc> was not installed:
*** package <SPROmrcom> was not installed:
*** package <SPROmr3m> was not installed:
*** package <SPROmrtcv> was not installed:
*** package <SPROm9xs> was not installed:
*** package <SPROsunms> was not installed:
*** package <SPROsmsx> was not installed:
*** package <SPROsmpx> was not installed:
*** package <SPROmrsbe> was not installed:
*** package <SPROsbe> was not installed:
*** package <SPROpnsn> was not installed:
*** package <SPROfd> was not installed:
*** package <SPROupdck> was not installed:
*** package <SPROcpl> was not installed:
*** package <SPROcplx> was not installed:
*** package <SPROcmpl> was not installed:
*** package <SPROtlbn7> was not installed:
*** package <SPROtll7> was not installed:
*** package <SPROtl7x> was not installed:
*** package <SPROtll7x> was not installed:
*** package <SPROscl> was not installed:
*** package <SPROsclx> was not installed:
*** package <SPROmrstd> was not installed:
*** package <SPROmrcpl> was not installed:
*** package <SPROstl4h> was not installed:
*** package <SPROstl4a> was not installed:
*** package <SPROstl4o> was not installed:
*** package <SPROstl4x> was not installed:
*** package <SPROstl4y> was not installed:
*** package <SPROftool> was not installed:
*** package <SPROl90> was not installed:
*** package <SPROl90x> was not installed:
*** package <SPROl90s> was not installed:
*** package <SPROl90sx> was not installed:
*** package <SPROf90> was not installed:
*** package <SPROmrftn> was not installed:
*** package <SPROgc> was not installed:
*** package <SPROlgc> was not installed:
*** package <SPROgcx> was not installed:
*** package <SPROlgcx> was not installed:
*** package <SPROdbx> was not installed:
*** package <SPROdbxx> was not installed:
*** package <SPROjdbx> was not installed:
*** package <SPROjdbxx> was not installed:
*** package <SPROmrdbx> was not installed:
*** package <SPROdemo> was not installed:
*** package <SPROdmake> was not installed:
*** package <SPROmrdmk> was not installed:
*** package <SPROtdemo> was not installed:
*** package <SPROmride> was not installed:
*** package <SPROdbxui> was not installed:
*** package <SPROsvc> was not installed:
*** package <SPROxdplg> was not installed:
*** package <SPROidext> was not installed:
*** package <SPROjnsnb> was not installed:
*** package <SPROjnsrt> was not installed:
*** package <SPROjnsup> was not installed:
*** package <SPROctags> was not installed:
*** package <SUNWnbide> was not installed:
*** package <SUNWnbcpp> was not installed:
*** package <SUJAnbcpp> was not installed:
*** package <SUZHnbcpp> was not installed:
*** package <SUNWexted> was not installed:
*** package <SUJAexted> was not installed:
*** package <SUZHexted> was not installed:
*** package <SPROnbreg> was not installed:
*** package <SPROfdxd> was not installed:
*** package <SPROmrxd> was not installed:
*** package <SPROgvim> was not installed:
*** package <SPROxmbin> was not installed:
*** package <SPROxmshr> was not installed:
*** package <SPROxmsrc> was not installed:
*** package <SPROmrxm> was not installed:
*** package <SPROprfan> was not installed:
*** package <SPROmrpan> was not installed:
*** package <SPROprfax> was not installed:
*** package <SPROprflb> was not installed:
*** package <SPROprflx> was not installed:
*** package <SPROprfgn> was not installed:
*** package <SPROmrpgn> was not installed:
*** package <SPROhtbas> was not installed:
*** package <SPROhttl7> was not installed:
*** package <SPROhtstd> was not installed:
*** package <SPROhtxd> was not installed:
*** package <SPROdwrfs> was not installed:
*** package <SPROrdbks> was not installed:
*** package <SPROctsrc> was not installed:
*** package <SPROplg> was not installed:
*** package <SPROpl> was not installed:
*** package <SPROplx> was not installed:
*** package <SPROpls> was not installed:
*** package <SPROplsx> was not installed:
*** package <SPROmrpl> was not installed:These messages seem to be inline with the general output captured from the zone install itself.
> What does "svcadm list -vc" give you when you started the zone ?
I took that as a typo, instead using "zoneadm?"
# zoneadm list -vc
ID NAME STATUS PATH
0 global running /
7 foo running /zone/fooThe zone is not on its own slice, however "/zone" is mounted as a loopback from /export/zone. I don't think that's a problem since the zone install seems to work if I don't inherit packages. Unless perhaps its a nesting level of lofs's.
FWIW,
# mount |grep zone
/zone on /export/zone read/write/setuid/devices/dev=1540000 on Fri Feb 24 16:10:55 2006
/zone/foo/root/dev on /zone/foo/dev read/write/setuid/devices/zonedevfs/dev=4640007 on Tue Feb 28 13:13:03 2006
/zone/foo/root/lib on /lib read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/platform on /platform read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/sbin on /sbin read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/usr on /usr read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/proc on proc read/write/setuid/nodevices/zone=foo/dev=4400007 on Tue Feb 28 13:13:06 2006
/zone/foo/root/system/contract on ctfs read/write/setuid/nodevices/zone=foo/dev=43c0008 on Tue Feb 28 13:13:06 2006
/zone/foo/root/etc/svc/volatile on swap read/write/setuid/nodevices/xattr/zone=foo/dev=448000e on Tue Feb 28 13:13:06 2006
/zone/foo/root/etc/mnttab on mnttab read/write/setuid/nodevices/zone=foo/dev=4440008 on Tue Feb 28 13:13:06 2006 -
Solaris 10 update 9 - live upgrade issues with ZFS
Hi
After doing a live upgrade from Solaris 10 update 8 to Solaris 10 update 9 the alternate boot environment I created is no longer bootable.
I have completed all the pre-upgrade steps like:
- Installing the latest version of live upgrade from the update 9 ISO.
- Create and test the new boot environment.
- Create a sysidcfg file used by the live upgrade that has auto_reg=disable in it.
There is also no errors while creating the boot environment or even when activating it.
Here is the error I get:
SunOS Release 5.10 Version Generic_14489-06 64-bit
Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved.
NOTICE: zfs_parse_bootfs: error 22
Cannot mount root on altroot/37 fstype zfs
*panic[cpu0]/thread=fffffffffbc28040: vfs mountroot: cannot mount root*
ffffffffffbc4a8d0 genunix:main+107 ()
Skipping system dump - no dump device configured
Does anyone know how I can fix this?
Edited by: user12099270 on 02-Feb-2011 04:49Found the culprit... *142910-17*... breaks it
System has findroot enabled GRUB
Updating GRUB menu default setting
GRUB menu default setting is unaffected
Saving existing file </boot/grub/menu.lst> in top level dataset for BE <s10x_u8wos_08a> as <mount-point>//boot/grub/menu.lst.prev.
File </etc/lu/GRUB_backup_menu> propagation successful
Successfully deleted entry from GRUB menu
Validating the contents of the media </admin/x86/Patches/10_x86_Recommended/patches>.
The media contains 204 software patches that can be added.
Mounting the BE <s10x_u8wos_08a_Jan2011>.
Adding patches to the BE <s10x_u8wos_08a_Jan2011>.
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
The following requested patches have packages not installed on the system
Package SUNWio-tools from directory SUNWio-tools in patch 142910-17 is not installed on the system. Changes for package SUNWio-tools will not be applied to the system.
Package SUNWzoneu from directory SUNWzoneu in patch 142910-17 is not installed on the system. Changes for package SUNWzoneu will not be applied to the system.
Package SUNWpsm-ipp from directory SUNWpsm-ipp in patch 142910-17 is not installed on the system. Changes for package SUNWpsm-ipp will not be applied to the system.
Package SUNWsshdu from directory SUNWsshdu in patch 142910-17 is not installed on the system. Changes for package SUNWsshdu will not be applied to the system.
Package SUNWsacom from directory SUNWsacom in patch 142910-17 is not installed on the system. Changes for package SUNWsacom will not be applied to the system.
Package SUNWmdbr from directory SUNWmdbr in patch 142910-17 is not installed on the system. Changes for package SUNWmdbr will not be applied to the system.
Package SUNWopenssl-commands from directory SUNWopenssl-commands in patch 142910-17 is not installed on the system. Changes for package SUNWopenssl-commands will not be applied to the system.
Package SUNWsshdr from directory SUNWsshdr in patch 142910-17 is not installed on the system. Changes for package SUNWsshdr will not be applied to the system.
Package SUNWsshcu from directory SUNWsshcu in patch 142910-17 is not installed on the system. Changes for package SUNWsshcu will not be applied to the system.
Package SUNWsshu from directory SUNWsshu in patch 142910-17 is not installed on the system. Changes for package SUNWsshu will not be applied to the system.
Package SUNWgrubS from directory SUNWgrubS in patch 142910-17 is not installed on the system. Changes for package SUNWgrubS will not be applied to the system.
Package SUNWzoner from directory SUNWzoner in patch 142910-17 is not installed on the system. Changes for package SUNWzoner will not be applied to the system.
Package SUNWmdb from directory SUNWmdb in patch 142910-17 is not installed on the system. Changes for package SUNWmdb will not be applied to the system.
Package SUNWpool from directory SUNWpool in patch 142910-17 is not installed on the system. Changes for package SUNWpool will not be applied to the system.
Package SUNWudfr from directory SUNWudfr in patch 142910-17 is not installed on the system. Changes for package SUNWudfr will not be applied to the system.
Package SUNWxcu4 from directory SUNWxcu4 in patch 142910-17 is not installed on the system. Changes for package SUNWxcu4 will not be applied to the system.
Package SUNWarc from directory SUNWarc in patch 142910-17 is not installed on the system. Changes for package SUNWarc will not be applied to the system.
Package SUNWtftp from directory SUNWtftp in patch 142910-17 is not installed on the system. Changes for package SUNWtftp will not be applied to the system.
Package SUNWaccu from directory SUNWaccu in patch 142910-17 is not installed on the system. Changes for package SUNWaccu will not be applied to the system.
Package SUNWppm from directory SUNWppm in patch 142910-17 is not installed on the system. Changes for package SUNWppm will not be applied to the system.
Package SUNWtoo from directory SUNWtoo in patch 142910-17 is not installed on the system. Changes for package SUNWtoo will not be applied to the system.
Package SUNWcpc from directory SUNWcpc.i in patch 142910-17 is not installed on the system. Changes for package SUNWcpc will not be applied to the system.
Package SUNWftdur from directory SUNWftdur in patch 142910-17 is not installed on the system. Changes for package SUNWftdur will not be applied to the system.
Package SUNWypr from directory SUNWypr in patch 142910-17 is not installed on the system. Changes for package SUNWypr will not be applied to the system.
Package SUNWlxr from directory SUNWlxr in patch 142910-17 is not installed on the system. Changes for package SUNWlxr will not be applied to the system.
Package SUNWdcar from directory SUNWdcar in patch 142910-17 is not installed on the system. Changes for package SUNWdcar will not be applied to the system.
Package SUNWnfssu from directory SUNWnfssu in patch 142910-17 is not installed on the system. Changes for package SUNWnfssu will not be applied to the system.
Package SUNWpcmem from directory SUNWpcmem in patch 142910-17 is not installed on the system. Changes for package SUNWpcmem will not be applied to the system.
Package SUNWlxu from directory SUNWlxu in patch 142910-17 is not installed on the system. Changes for package SUNWlxu will not be applied to the system.
Package SUNWxcu6 from directory SUNWxcu6 in patch 142910-17 is not installed on the system. Changes for package SUNWxcu6 will not be applied to the system.
Package SUNWpcmci from directory SUNWpcmci in patch 142910-17 is not installed on the system. Changes for package SUNWpcmci will not be applied to the system.
Package SUNWarcr from directory SUNWarcr in patch 142910-17 is not installed on the system. Changes for package SUNWarcr will not be applied to the system.
Package SUNWscpu from directory SUNWscpu in patch 142910-17 is not installed on the system. Changes for package SUNWscpu will not be applied to the system.
Package SUNWcpcu from directory SUNWcpcu in patch 142910-17 is not installed on the system. Changes for package SUNWcpcu will not be applied to the system.
Package SUNWopenssl-include from directory SUNWopenssl-include in patch 142910-17 is not installed on the system. Changes for package SUNWopenssl-include will not be applied to the system.
Package SUNWdtrp from directory SUNWdtrp in patch 142910-17 is not installed on the system. Changes for package SUNWdtrp will not be applied to the system.
Package SUNWhermon from directory SUNWhermon in patch 142910-17 is not installed on the system. Changes for package SUNWhermon will not be applied to the system.
Package SUNWpsm-lpd from directory SUNWpsm-lpd in patch 142910-17 is not installed on the system. Changes for package SUNWpsm-lpd will not be applied to the system.
Package SUNWdtrc from directory SUNWdtrc in patch 142910-17 is not installed on the system. Changes for package SUNWdtrc will not be applied to the system.
Package SUNWhea from directory SUNWhea in patch 142910-17 is not installed on the system. Changes for package SUNWhea will not be applied to the system.
Package SUNW1394 from directory SUNW1394 in patch 142910-17 is not installed on the system. Changes for package SUNW1394 will not be applied to the system.
Package SUNWrds from directory SUNWrds in patch 142910-17 is not installed on the system. Changes for package SUNWrds will not be applied to the system.
Package SUNWnfsskr from directory SUNWnfsskr in patch 142910-17 is not installed on the system. Changes for package SUNWnfsskr will not be applied to the system.
Package SUNWudf from directory SUNWudf in patch 142910-17 is not installed on the system. Changes for package SUNWudf will not be applied to the system.
Package SUNWixgb from directory SUNWixgb in patch 142910-17 is not installed on the system. Changes for package SUNWixgb will not be applied to the system.
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
142910-17
Checking installed patches...
Executing prepatch script...
Installing patch packages...
Patch 142910-17 has been successfully installed.
See /a/var/sadm/patch/142910-17/log for details
Executing postpatch script...
Creating GRUB menu in /a
Installing grub on /dev/rdsk/c2t0d0s0
stage1 written to partition 0 sector 0 (abs 16065)
stage2 written to partition 0, 273 sectors starting at 50 (abs 16115)
Patch packages installed:
BRCMbnx
SUNWaac
SUNWahci
SUNWamd8111s
SUNWcakr
SUNWckr
SUNWcry
SUNWcryr
SUNWcsd
SUNWcsl
SUNWcslr
SUNWcsr
SUNWcsu
SUNWesu
SUNWfmd
SUNWfmdr
SUNWgrub
SUNWhxge
SUNWib
SUNWigb
SUNWintgige
SUNWipoib
SUNWixgbe
SUNWmdr
SUNWmegasas
SUNWmptsas
SUNWmrsas
SUNWmv88sx
SUNWnfsckr
SUNWnfscr
SUNWnfscu
SUNWnge
SUNWnisu
SUNWntxn
SUNWnv-sata
SUNWnxge
SUNWopenssl-libraries
SUNWos86r
SUNWpapi
SUNWpcu
SUNWpiclu
SUNWpsdcr
SUNWpsdir
SUNWpsu
SUNWrge
SUNWrpcib
SUNWrsgk
SUNWses
SUNWsmapi
SUNWsndmr
SUNWsndmu
SUNWtavor
SUNWudapltu
SUNWusb
SUNWxge
SUNWxvmpv
SUNWzfskr
SUNWzfsr
SUNWzfsu
PBE GRUB has no capability information.
PBE GRUB has no versioning information.
ABE GRUB is newer than PBE GRUB. Updating GRUB.
GRUB update was successfull.
Unmounting the BE <s10x_u8wos_08a_Jan2011>.
The patch add to the BE <s10x_u8wos_08a_Jan2011> completed.
Still need to know how to resolve it though... -
New to solaris---is update manager working correctly?
well as my subject says I am new to solaris having put it on an pc bout a week ago. as I am using the "free" verson (not open solaris) I knew I would not be entitled to certain goodies but seem to have run into an issue getting the updates I (presumably) am entitled to. simply put I open up the solaris application "update manager" which is on my desktop saying "updates available". now upon initially launching the app I specified that I was using the free version (well it let me register without a code so I assume sun knows my status), and then selected the option to put a check mark next to all available updates. well after waiting like a full day with it showing that is was still in the process up updating I eventually aborted the process. I then tried installing a couple of the updates and though it took a while it worked. so I selected 3 of 4 more and again the update manager showed that I was updating but nothing was happening (to my knowledge). after several hours I aborted the app again. so what am I doing wrong. first off I am assuming that what sun presents to me is what is actually available to me using the free unregistered version of solaris. why then would updates fail? btw I know some linux (not an expert) and I figured that behind the scenes update manager was checking for dependencies and installing what I needed from sun repos. but of course I could be way off bass here. so what gives? thanks much in advance.
first off I am assuming that what sun presents to me is what is actually available to me using the free unregistered version of solaris.No. Update Manager will show you everything but will only allow you to install basically security and a small subset of other patches.
When you ran through the Solaris registration GUI you had a chance to enter a support contract #. If you chose not to enter one or if you want to use it without registering then you only get access to a few of the patches.
alan -
How do I refresh a table with a bind variable using a return listener?
JDev 11.1.2.1.0.
I am trying to refresh a table with a bind variable after a record is added.
The main page has a button which, on click, calls a task flow as an inline document. This popup task flow allows the user to insert a record. It has its own transaction and does not share data controls.
Upon task flow return, the calling button's return dialog listener is invoked which should allow the user to see the newly created item in the table. The returnListener code:
// retrieve the bind variable and clear it of any values used to filter the table results
BindingContainer bindings = ADFUtils.getBindings();
AttributeBinding attr = (AttributeBinding)bindings.getControlBinding("pBpKey");
attr.setInputValue("");
// execute the table so it returns all rows
OperationBinding operationBinding = bindings.getOperationBinding("ExecuteWithParams");
operationBinding.execute();
// set the table's iterator to the newly created row
DCIteratorBinding iter = (DCIteratorBinding) bindings.get("AllCustomersIterator");
Object customerId = AdfFacesContext.getCurrentInstance().getPageFlowScope().get("newCustomerId");
iter.setCurrentRowWithKeyValue((String)customerId);
// refresh the page
AdfFacesContext.getCurrentInstance().addPartialTarget(this.getFilterText());
AdfFacesContext.getCurrentInstance().addPartialTarget(this.getCustomerTable());But the table does not refresh ... The bind variable's inputText component is empty. The table flickers as if it updates. But no new values are displayed, just the ones that were previously filtered or shown.
I can do the EXACT SAME code in a button's actionListener that I click manually and the table will refresh fine. I'm really confused and have spent almost all day on this problem.
WillBoth options invoke the create new record task flow. The first method runs the "reset" code shown above through the calling button's returnListener once the task flow is complete. The second method is simply a button which, after the new record is added and the task flow returns, runs the "reset" code by my clicking it manually.
I'm thinking that the returnListener code runs before some kind of automatic ppr happens on the table. I think this because the table contents flicker to show all customers (like I intend) but then goes back to displaying the restricted contents a split second later.
Yes, the table is in the page that invokes the taskflow.
Here are some pictures:
http://williverstravels.com/JDev/Forums/Threads/2337410/Step1.jpg
http://williverstravels.com/JDev/Forums/Threads/2337410/Step2.jpg
http://williverstravels.com/JDev/Forums/Threads/2337410/Step3.jpg
Step1 - invoke new record task flow
Step2 - enter data and click Finish
Step3 - bind parameter / table filter cleared. Table flickers with all values. Table reverts to previously filterd values. -
Why ulimit fails for stack size in Sol 10 update 11 with project settings?
Hi,
The following command fails on Solaris 10 update 11 platform. It works fine with update 10. Something has changed in update 11. Any ideas?
ulimit -Ss 1 (or any number for that matter)
/bin/ksh: ulimit: exceeds allowable limit
We have the following setting in project as well.
process.max-stack-size=(basic,137988707188736,deny)
process.max-stack-size=(priv,137988707188736,deny)
Thanks for your help in advance.
SamyHere are the values from the project command if you anyone is wondering
update 10
======
cat /etc/release
Oracle Solaris 10 8/11 s10x_u10wos_17b X86
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
Assembled 23 August 2011
prctl -n process.max-stack-size $$
process: 10189: /bin/ksh -i
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
process.max-stack-size
privileged 125TB max deny -
system 125TB max deny -
update 11
======
cat /etc/release
Oracle Solaris 10 1/13 s10x_u11wos_24a X86
Copyright (c) 1983, 2013, Oracle and/or its affiliates. All rights reserved.
Assembled 17 January 2013
prctl -n process.max-stack-size $$
process: 24776: /bin/ksh -i
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
process.max-stack-size
basic 125TB - deny 24776
privileged 125TB - deny -
system 125TB max deny - -
Upgrade Solaris 8 to Solaris 10 (Jan 2006) with METASTAT
Hi..
On a v240 server running Solaris 8, I attempted many times to upgrade to Solaris 10 using the Jan 2006 Cd's. However. because a 3310 disk array that was striped, then mirrored using METASTAT and no spare blank disk...all upgrade attempts failed. I had a case open with Sun Support for quite a while and the work around was to unplug the array (containing Oracle 9i databases and 11i Oracle Apps) then do a fresh install of Sol 10, then reconfigure the metastat exactly the same as previously under Solaris 8 so that the databases and applications would become visible again.
So upgrading to Sol 10 from 8 was not simply and easy as one might think (and the marketing hype indicated). Also, I thought the new zfx file system as included with the Jan 2006 release, but sadly, it was not. So there is probably another upgrade from ufs to zfx that will not work because the Solaris 10 upgrade has difficulty with Sun's METASTAT software.
So I wonder out there...is there anyone else that had a similar issue, or solved it easily? And Sol 10 with zfx was to be release in June 2006 sometime...and June is disappearing fast...so any recent update to it?
Roger Sager
Sydney, AusWithout the case and an explorer we can't comment much on this, but I have seen it before that this behavior is normal when people only patch the software and forget about the hardware connected or firmware. But again that is guessing. Also SVM was changed with the Solaris 9 release.
And for ZFS, its was not part of the release of sol10 1/06 as described in the release notes. Solaris 10 Update 2 is still on the testbed as far as I know and it will be release as soon as its ready (and not sooner then that I hope). As for ZFS, its cool and funny, but I would wait for the Solaris 11 release next year (?) when you want to put it to use in production. But if you really want ZFS hot and spicy then you could go for SXCR ;-) -
Solaris 10 update 6 keeps generating core file (/core)
I wonder if somebody has encountered the following issue.
I did a fresh install of Solaris 10 update 6 on two servers (T5140 and T524) from DVD.
I noticed that a core file was in the root filesystem (/core).
So, I deleted it.
As soon as I delete the core file, another one is generated.
This is happening on both servers where I installed Solaris 10 update 6 from the DVD.
This is not a live update install. Solaris was installed from scratch. When prompted to preserve previous data, I replied with 'do not preserve data'
Does anybody know where the core file is coming from and how to stop it being generated?
Found out that is coming from vold
SunOS b1osdtsun02 5.10 Generic_137137-09 sun4v sparc SUNW,T5240
# more /etc/release
Solaris 10 10/08 s10s_u6wos_07b SPARC
Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 27 October 2008
# mdb /core
Loading modules: [ libsysevent.so.1 libnvpair.so.1 libc.so.1 ld.so.1 ]
::statusdebugging core file of vold (32-bit) from b1osdtsun02
file: /usr/sbin/vold
initial argv: /usr/sbin/vold -f /etc/vold.conf
threading model: multi-threaded
status: process terminated by SIGSEGV (Segmentation Fault)
::stacklibc.so.1`strlen+0x18(408450a5, 0, 0, 88b70, 600, 180)
read_slices+0x114(874a0, b, 889a0, feeafd34, 1, 5)
read_hsfs_partition+0x88(b, 46c00, 6d0000, 2c, 34400, 1010101)
read_partition+0x30(874a0, 341a4, 3, 34000, 34400, 9)
create_top_partition+0x140(7cbe0, 7cc24, 7cbe0, 874a0, ffffffff, b)
0x265e0(800012, feeaff9c, c, 598e0, 7cbe0, ffffffff)
create_medium+0x74(800012, feeaff9c, 20, 12, 47800, c)
0x2232c(5d278, 0, 0, 800012, 20, 33000)
libc.so.1`_lwp_start(0, 0, 0, 0, 0, 0)
>
#It seems that vold is failing to mount the DVD on both servers after Solaris was installed.
Is this a Solaris 10 update 6 bug?
Edited by: shen on Jan 29, 2009 8:45 PMNever mind.
It is a known bug documented on manual " [Solaris 10 10/08 Release Notes, Chapter 2 Solaris Runtime Issues|http://docs.sun.com/app/docs/doc/820-5245/chapter2-1000?a=view] " as shown below.
The solution is to apply vold patch [138130-01|http://sunsolve.sun.com/search/document.do?assetkey=1-21-138130-01-1].
Solaris 10 10/08 DVD Media Might Not be Automatically Mounted by vold (6712352)
The Solaris 10 10/08 DVD does not mount by default during runtime. No error message is displayed.
Workaround: Perform the following steps:
1. Become superuser.
2. Disable vold:
* On Solaris 10 Systems:
# svcadm disable -t volfs
* On Solaris 8 and Solaris 9 systems:
/etc/init.d/volmgt stop
3. Mount the media manually by using the # mount -F hsfs path to block device path to mount point command. For example:
# mount -F hsfs /dev/rdsk/c0t2d0s2 /mnt -
Help only displays the frame in Solaris 10, update 6
I have a help application that has been running fine since Solaris 8. It works in Solaris 10, update 1, but not in update 6. Only an empty help frame is displayed. My JRE is 1.6.0_05-b13, and I am using help 1.1.13. I suspect that replacing the default HelpUI with my own subclass has stopped working. My application has this line of code which is used to replace the default HelpUI:
UIManager.getDefaults().put("HelpUI", "HelpUIWithClose");
The users wanted a close button, so HelpUIWithClose is subclassed from BasicHelpUI, and a big close button is added on the toolbar. This has been working for years. Before and after this line of code are two print statements that get the toString value of the UIDefaults HelpUI object. The results are:
(before)
javax.help.plaf.basic.BasicHelpUI
(after)
HelpUIWithClose
I am only guessing at the problem because of all of the "Unknown Source" values in the trace below. If I comment out the UIManager line above that replaces HelpUI with HelpUIWithClose, the help functions normally, but of course it is missing the close button added by HelpUIWithClose.
An alternate question might be how to add a close button to the toolbar of help?
I get a very long trace when this fails. I will post it at the end of this email. Any ideas on what is wrong?
Thanks,
Herb Miller
UIDefaults.getUI() failed: no ComponentUI class for: javax.help.JHelp[,0,0,0x0,invalid,alignmentX=0.0,alignmentY=0.0,border=,flags=0,maximumSize=,minimumSize=,preferredSize=]
java.lang.Error
at javax.swing.UIDefaults.getUIError(Unknown Source)
at javax.swing.MultiUIDefaults.getUIError(Unknown Source)
at javax.swing.UIDefaults.getUI(Unknown Source)
at javax.swing.UIManager.getUI(Unknown Source)
at javax.help.JHelp.updateUI(JHelp.java:299)
at javax.help.JHelp.<init>(JHelp.java:121)
at javax.help.WindowPresentation.createJHelp(WindowPresentation.java:843)
at javax.help.WindowPresentation.createHelpWindow(WindowPresentation.java:879)
at javax.help.WindowPresentation.setDisplayed(WindowPresentation.java:346)
at javax.help.DefaultHelpBroker.setDisplayed(DefaultHelpBroker.java:178)
at javax.help.CSH.displayHelp(CSH.java:749)
at javax.help.CSH.access$200(CSH.java:80)
at javax.help.CSH$DisplayHelpFromSource.actionPerformed(CSH.java:1668)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.AbstractButton.doClick(Unknown Source)
at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source)
at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)Never mind.
It is a known bug documented on manual " [Solaris 10 10/08 Release Notes, Chapter 2 Solaris Runtime Issues|http://docs.sun.com/app/docs/doc/820-5245/chapter2-1000?a=view] " as shown below.
The solution is to apply vold patch [138130-01|http://sunsolve.sun.com/search/document.do?assetkey=1-21-138130-01-1].
Solaris 10 10/08 DVD Media Might Not be Automatically Mounted by vold (6712352)
The Solaris 10 10/08 DVD does not mount by default during runtime. No error message is displayed.
Workaround: Perform the following steps:
1. Become superuser.
2. Disable vold:
* On Solaris 10 Systems:
# svcadm disable -t volfs
* On Solaris 8 and Solaris 9 systems:
/etc/init.d/volmgt stop
3. Mount the media manually by using the # mount -F hsfs path to block device path to mount point command. For example:
# mount -F hsfs /dev/rdsk/c0t2d0s2 /mnt -
Upgrading from Solaris 10 Update 2 to Update 7 (05/09) on V125
I am trying to upgrade a V125 from Solaris 10 Update 2 to Solaris 10 Update 7. When the installer runs, it does not give me a choice for upgrading. I have tried also using text mode (boot cdrom - text) with no luck. Anyone else run into this?
Best!
FrankYou should update all the way to 10.5.8 using the combo updater, which you can download from here:
http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate
Do I have to buy iLife 09 outright?
Yes.
Can I buy just iMovie 09?
Nope!
Lastly, you have plenty of RAM. The only way to increase this would be to sell your two ram sticks on eBay and buy two new 2GB sticks. -
Postgresql service 8.2 on Solaris 10 Update 4
Hi
I have solaris 10 update 4 installed. PostgreSQL with SMF is shipped with Solaris 10 update 4.
I could see two services installed on the OS.
svcs postgresql
disabled 14:58:36 svc:/application/database/postgresql:version_81
maintenance 15:40:42 svc:/application/database/postgresql:version_82
I followed the steps to start postgres service given on Sun website...
PostgreSQL 8.2:
1. As root, su to postgres:
# su - postgres
2. Create PostgreSQL DB cluster:
$ /usr/postgres/8.2/bin/initdb -D /var/postgres/8.2/data
3. As root, use the SMF's svcadm command to start PostgreSQL:
# /usr/sbin/svcadm enable postgresql:version_82
now I could see one serive enabled.
svcs postgresql
disabled 14:58:36 svc:/application/database/postgresql:version_81
online 15:40:42 svc:/application/database/postgresql:version_82
But, when I disabled the service & restarted it using...
svcadm disable svc:/application/database/postgresql:version_82
svcadm enable svc:/application/database/postgresql:version_82
I see the serivce in the maintenance mode.
disabled 14:58:36 svc:/application/database/postgresql:version_81
maintenance 15:40:42 svc:/application/database/postgresql:version_82
Server.log shows following error:-
FATAL: syntax error in file "/var/postgres/8.2/data/postgresql.conf" line 104, near token "MB"
Can anyone help me know the reason?
Thanx in advance
NirajHi
I have solaris 10 update 4 installed. PostgreSQL with SMF is shipped with Solaris 10 update 4.
I could see two services installed on the OS.
svcs postgresql
disabled 14:58:36 svc:/application/database/postgresql:version_81
maintenance 15:40:42 svc:/application/database/postgresql:version_82
I followed the steps to start postgres service given on Sun website...
PostgreSQL 8.2:
1. As root, su to postgres:
# su - postgres
2. Create PostgreSQL DB cluster:
$ /usr/postgres/8.2/bin/initdb -D /var/postgres/8.2/data
3. As root, use the SMF's svcadm command to start PostgreSQL:
# /usr/sbin/svcadm enable postgresql:version_82
now I could see one serive enabled.
svcs postgresql
disabled 14:58:36 svc:/application/database/postgresql:version_81
online 15:40:42 svc:/application/database/postgresql:version_82
But, when I disabled the service & restarted it using...
svcadm disable svc:/application/database/postgresql:version_82
svcadm enable svc:/application/database/postgresql:version_82
I see the serivce in the maintenance mode.
disabled 14:58:36 svc:/application/database/postgresql:version_81
maintenance 15:40:42 svc:/application/database/postgresql:version_82
Server.log shows following error:-
FATAL: syntax error in file "/var/postgres/8.2/data/postgresql.conf" line 104, near token "MB"
Can anyone help me know the reason?
Thanx in advance
Niraj -
Panic after boot in page_retire_thread Solaris 10 update 8
Hi,
I am using Solaris 10 update 8 on a T5120. There was a HW problem that required a new motherboard. Afterward, the system reboots but within a minute of the login prompt the system panics with:
panic[cpu10]/thread=2a100527ca0: BAD TRAP: type=31 rp=2a100527870 addr=8 mmu_fsr
=0 occurred in module "unix" due to a NULL pointer dereference
sched: trap type = 0x31
addr=0x8
pid=0, pc=0x1071140, sp=0x2a100527111, tstate=0x44e2001607, context=0x0
g1-g7: 1866c00, 0, 0, 18602e0, 0, 0, 2a100527ca0
000002a100527590 unix:die+78 (31, 2a100527870, 8, 0, 2a100527650, 10ae000)
%l0-3: 0000000000001fff 0000000000000031 0000000001000000 0000000000002000
%l4-7: 00000000018323a8 0000000001832000 0000000000000017 00000000c658a008
000002a100527670 unix:trap+9e4 (2a100527870, 0, 5, 1c00, 0, 1)
%l0-3: 0000000000000000 000000000185ede0 0000000000000031 0000000000000000
%l4-7: ffffffffffffe000 0000000000000000 0000000000000005 0000000000000001
000002a1005277c0 unix:ktl0+64 (1866cd8, 0, 18602e0, 18602e0, 1860000, 18602e0)
%l0-3: 00000300063c6000 0000000000000050 00000044e2001607 000000000101fa84
%l4-7: 0000000000000000 0000070000066b80 0000000000000000 000002a100527870
000002a100527910 unix:page_retire_hunt+19c (1070eb4, 18614f0, 18636c8, 700000000
00, 18614b0, 18602e0)
%l0-3: 00000000018603d8 0000070000074000 0000000000000000 0000000000000020
%l4-7: 0000000000000023 0000000000000006 ffffffffffffffff 0000000000000008
000002a1005279c0 unix:page_retire_thread+138 (0, 0, 182b000, 1070c00, 2, 1070eb4
%l0-3: 0000000000000002 0000000000000002 000000000185a000 000000000185a000
%l4-7: 00000000000021a4 000000000001d524 000000000185a000 00000000018f3800
syncing file systems... 3 done
dumping to /dev/dsk/c1t0d0s1, offset 860749824, content: kernel
100% done: 193300 pages dumped, compression ratio 7.43, dump succeeded
panic[cpu10]/thread=2a100527ca0: BAD TRAP: type=31 rp=187b9b0 addr=8 mmu_fsr=0 o
ccurred in module "unix" due to a NULL pointer dereference
dump aborted: please record the above information!
panic[cpu10]/thread=2a100527ca0: BAD TRAP: type=31 rp=187b1b0 addr=8 mmu_fsr=0 o
ccurred in module "unix" due to a NULL pointer dereference
dump aborted: please record the above information!
panic[cpu10]/thread=2a100527ca0: BAD TRAP: type=31 rp=187a9b0 addr=8 mmu_fsr=0 o
ccurred in module "unix" due to a NULL pointer dereference
dump aborted: please record the above information!
panic[cpu10]/thread=2a100527ca0: BAD TRAP: type=31 rp=187a1b0 addr=8 mmu_fsr=0 o
ccurred in module "unix" due to a NULL pointer dereference
dump aborted: please record the above information!
I have tried to sign in and run a few commands, but it doesn't seem to matter what I do..always the panic. I am unable to switch boot environments as the panic occurs before the luactivate completes. Switching to run level 1 doesn't help as it panics anyway.
Does anyone know, is this a know problem? Is there a fix? I haven't yet tried to reinstall.
Thanks for any help that can be provided.Can you boot from DVD and do an "upgrade?"
-
Virtual MAC-Address on Solaris 10 update 9
Hi,
i'm installing Solaris 10 update 9 on UCS B-Series (B230 M2 or B440 M2) with M72KR-Q Adapter. We create the Service Profile with vNIC associated to vNIC Template. The vNIC Template use the MAC Pool Address configurated.
When we run ifconfig -a on Solaris we can view only the original MAC-Address instead of Virtual MAC-Addres. Is this correct?
Thanks in advanceWhen you say the "original" MAC are you referring to the Hardware Default?
Ensure your MAC pool has available addresses also. You can also test unbinding the vNIC template from the Solaris service profile, and manually assigning a MAC address (watch for overlap) to the vNIC and see if that pushes to the solaris host.
If that works, then you have a pool/template issue. If not, we'll need to investigate further.
Regards,
Robert
Maybe you are looking for
-
Download and install the updates manually
I have just purchased Photoshop CS6 and ran the updater from within Photoshop. I know some of the updates worked but not all. So I ran it again 3 or 4 attempts now have failed with this message:- It has failed to install - Extension Manager 6.0.6 Upd
-
InDesign cs6 crashes when exporting objects with drop shadows to interactive PDF
I am using the trial version of InDesign CS6 on a mac OSX 10.7.4 I need to export my document as an interactive PDF. I have found that the export works fine so long as none of the objects within my document have a drop shadow. However, if I add a dr
-
I do not have enough memory to update phone. My camera roll is taking up over 8gb of memory so if I delete the photos will they also be deleted on my iPad
-
No audio output device found in Pavillion Dv6700 Win 7 64 bit
Can anyone help with this issue please I am going crazy trying to figure this out, got the sound back for a couple of days,now its gone again... Thanks Pigdaddy001
-
Get Sale order created date & time
Hello. Can anybody help me in finding the function module which takes sale order no. as input & gives me the order created date & time as output. Regards Devika.S