Manual install of patch 118844-28

I'm trying to do a patchadd on 118844-28, but it complains that patch 117435-02 must be installed first or that the computer needs to be rebooted after the patch 117435-02 has been applied.
When using the Update Manager it seems that 117435-02 has been installed and I've rebooted numerous times after that, but still when I try patchadd on the kernel patch above it gives me that error message.
Am I doing something wrong or what's going on?
It was quite awhile since I used Solaris and I've now installed Solaris 10 x86 1/06 and used the Update Manager to install patches, but the kernel patch apparently must be installed manually so I've done a "shutdown -i S" to get into single user mode (I'm not sure if that's how one is supposed to do it) then
cd /var/sadm/spool/
patchadd 118844-28
Any ideas?

There may be a bug in the patch, in the prepatch script to be precise.
In the prepatch script there the line
bootdev=`prtconf -v /devices | sed -n '/boot-device/{n;p;}' | grep pci | cut -f 2 -d \'`
change boot-device to bootpath and then the patch seems to install alright.
See this thread for more information http://forum.sun.com/thread.jspa?threadID=28707&tstart=0

Similar Messages

Patch 118844-28 fails to install on Ultra 20?

We're trying to run the standard updatemanager on our Ultra 20 running Solaris 10 x86. We've installed patches a number of times but we're hitting a wall with the recent kernel patch, 118844-28.
This patch shows up as needing to be applied in both the updatemanager gui as well as when we run smpatch analyze. The problem is that it doesn't seem like it will install even though the tools say that the installation procedure was successful. Specifically: we instruct the gui to install the patch, it goes off and looks like it's installing, it comes back and says that the installation is complete and successful and that we need to reboot the machine, we tell it to reboot the machine and it does. But when the machine comes back up the updatemanager (and smpatch) still says that this patch needs to be applied. And showrev says that we're still back at version 27. So it seems like it's properly applying the patch but then the patch isn't actually applied.
We tried to install the patch by hand with smpatch add in single user mode and we had a similar experience. The only exception being that the patch process complained that we had to have patch 117435-02 installed (which we do).
Has anybody seen this before? Has anybody gotten this patch to install on this hardware?

Yes, I agree with that fix- I just did it a little opposite:
# eeprom boot-device=/pci@0,0/pci-ide@11,1/ide@0/cmdk@0,0:a
which added an extra alias (permanently) to my 'BIOS' settings-
# eeprom | grep boot
bootpath=/pci@0,0/pci-ide@7/ide@0/cmdk@0,0:a
boot-device=/pci@0,0/pci-ide@7/ide@0/cmdk@0,0:a
I re-ran the 10 Rec. Cluster and it not only installed the kernel patch, but, a handful of other patches in the bundle too.
--David

Manually Install Patch Agent??

We recently purchased Zenworks Patch Management. However, right before
purchasing ZCM Patch Mgmt, we upgraded to ZCM 11. The ZCM 11 Agent
components for patch management automatically installed to ZCM 11 clients,
but not to version 10 clients. My guess is that it might have something to
do with the fact that the MSIs for 10.3.1 are now renamed as "superceded"
MSIs.
I had a friend build me an "unconfigured" ZCM agent package from his 10.3.1
system (he has ZCM Patch Management), and that successfully installs on a
freshly imaged machine and Zenworks Patch Management seems to be working.
However, that doesn't help me with the rest of my 10.3.1 machines that I
don't wish to reimage right now.
If you're asking: Why don't I upgrade my clients to the ZCM 11 Agent? I'll
tell you my answer: IT'S WAY TOO SLOW!! Until they iron out a few issues,
we're going to hang with the 10.3.1 agent.
So, my question is: Is there anyway to take the MSIs that are renamed as
"superceded" and manually install them to a workstation to get ZCM Patch
Management working on my existing 10.3.1 clients? I tried to simply install
the MSIs, but it doesn't seem to show up as an installed option on the ZCM
Agent properties page.
Thanks in advance!

Ryan,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

How to install a patch from local JAR file...

Newbie question -
I'm getting an error when deploying an MDB on WL 10.0 - someone else had also come across that same error and he sent me a patch (CR326377_10GA.jar) that should fix it.
How do I install that patch on my local WinXP installation of WL - do I just add an entry to the CLASSPATH of the startweblogic.bat file? I'm a little concenred about the order of JARs there... is there a better way?!
I tried looking up this patch using the Smart Update utility - but I could not find it there - how do I do it manually?
thanks,
james
Edited by jdepaul at 03/20/2008 4:13 PM

I believe you can contact support and get a patch id and passcode for this
patch and then install using smart update.
StartWeblogic.cmd will also look for a weblogic_patch.jar in the patch
directory. I.e. something like
d:\BEA10\patch_wls100\profiles\default\sys_manifest_classpath\weblogic_patch.jar
Cut/paste the directory from the output of startweblogic.cmd and then create
the directory and copy the patch to the right filename.
Or you can put the patch before any other jars in the classpath.
Peter
<James DePaul> wrote in message news:[email protected]..
Newbie question -
I'm getting an error when deploying an MDB on WL 10.0 - someone else had
also come across that same error and he sent me a patch (CR326377_10GA.jar)
that should fix it.
How do I install that patch on my local WinXP installation of WL - do I just
add an entry to the CLASSPATH of the startweblogic.bat file? I'm a little
concenred about the order of JARs there... is there a better way?!
I tried looking up this patch using the Smart Update utility - but I could
not find it there - how do I do it manually?
thanks,
james
Edited by jdepaul at 03/20/2008 4:13 PM

Error while installing a patch for Mainwin 5.0.2 on Solaris 2.8

Hi,
I am relatively new in this field, so i apologise for any slip-ups.
We use a Solaris 2.8-SPARC server. I was given an external drive which contained the porting software Visual Mainwin 5.0.2 and was told to install it from the drive. On checking it, i found that the entire folder structure of the software was damaged, i.e. every file of the software was changed to uppercase. UNIX being highly case-sensitive, i manually changed each and every file present in the software directory to lowercase and then ran it.
The software ran fine, it got installed and the license server was also up. the licenses were also nicely distributed. everything was fine until i was asked to install the patch 'vmw502_sunos5_HF1.sh'. While installing i got the following output :
# sh vmw502_sunos5_HF*
Extracting installation package to "/tmp/mwspselfextr27624".
Please stand by ... Done.
=====================================================================
Visual MainWin Patch Installation
HF1 for VMW 5.0.2 <sunos5> 24-Jul-2003.14:01 Cycle115
=====================================================================
***Error: cannot find file
/export/home/tools/solaris/env/mainsoft/../mwver/mwversion.ini
Something wrong with your Visual MainWin installation - aborting
when i checked the installation directory, i found that the file 'mwversion.ini' was present inside the directory 'mwver'. I cant see any reason why the patch is not recognizing the file.
Can anybody help?? Any kind of help will really be appreciated.
-SD

Hope you already tried: ls -l /export/home/tools/solaris/env/mainsoft/../mwver/mwversion.ini If ls returns the file name, try running the script under truss to find some clues.
% truss -f -vall -rall -wall -o /tmp/mwpatch.log sh vmw502_sunos5_HF*

Solaris 10 X86 kernel patch 118844-30 ... probably bad

I installed the patch on some Dells. Seemed to run fine.
Actually, I installed 121127-01, 113000-07, and 118344-06
first since they were required by 118844-30.
Some problems have now turned up.
1. When you power cycle one of the patched machines they
refuse to boot with
Warning - The following files in / differ from the boot archive:
/boot/solaris/bootenv.rc
to continue booting .. #svc clear system/boot-archive
and then demand the root password.
2. Randomly, when you do a reboot, a patched machine will claim
that the hardware has changed and demand that you run
kdmconfig. Simply going in and out of kdmconfig, without
changes, does the job. Weird.
3. I went to patch the next machine and after the patch
install and reboot, it was a total brick, with the error
File not executable
Panic : No entry point in kernel/unix
Press any key to reboot
And, naturally, this patch cannot be backed out. For yucks
I tried the equivalent patches on a sparc. No problems. So
I think Sun effed up the GRUB stuff in the kernel patch

Ok ... I noticed that deep down in the README for the patch
they say to do a "reboot -r". Cute. We'll try that.
That seemed to go ok, but when I tried a power cycle, it
wouldn't boot, claiming
SMF database integrity check of /etc/svc/repository.db
failed making me run
/lib/svc/bin/restore_repository
which turned out to be a struggle.
My advice - stay FAR AWAY from this patch. At minumum,
it makes the power up boot process VERY delicate. Wait
for the -32 rev, which I predict will not be long in coming.
Thank you sun.

Unable to boot the sytem after applying kernel patch 118844-27

We have an hp ProLiant DL380 Storage server connected to HP StorageWorks Moduler Smart Array 30 via SCSI. Solaris 03/05 was installed previously on this system with kernel 118844-20. When I queried and installed all required patches with 'smpatch add -i .. ' command, all patches applied and the system is rebooted. After reboot, the system kept restarting. I followed the instructions on Sun Alert document 102087, and installed grub using 01/06 1st CDROM. It installed successfully, but problem persisted. The systems started booting, but before printing 'Configuring devices' the system rebooted again. Providing -v option to the kernel, it lastly printed a PCI device id (/pci@....) and after 2-3 seconds rebooted again.
Finally I had to reinstall the solaris (this time 01/06). The disk was accessible after booting with CD ROM, and I was able to get cylinder numbers of disk, and I installed the new system to the root partition of the other live upgrade environment. The boot disk was partitioned under linux, it was three partitions, Solaris2 (50GB),Solaris(4GB),Linux(18GB). Installation medium told that the fdisk partition was invalid, and i repartitioned the whole disk again.
System up and running Solaris 10 01/06 now, but the strange thing is that, previously hard disk (both boot disk and disks on array) locations were identified as '/dev/rdsk/c0tx' but now, the system sees that hard disks at '/dev/c1tx' and CDROM at '/dev/c0t0'.
Now I want to ask tow questions:
* Could this disk number change made the system unbootable previously?
* May I safely apply patch 118844-28 to the system
-Thanks

Here's a similar topic https://bbs.archlinux.org/viewtopic.php?pid=536210 also if that doesn't work you should install vesa as it also says it's not found in your log.

Driver e1000g problem - patch 118844-30

Hi,
the situation is like this. I have fujitsu-siemens pc and Solaris 10 03/05 x86 installed. I wanted to patch it with latest recommended patch cluster. After that I was not able to get to default router and switch did not see my mac anymore. I looked in the patch cluster and removed patch by patch till the kernel patch 118844-30. I finished my todays troubleshooting with one big ZERO :-), but it works now a can sleep well. There was no error reported in log files, no smf failed, nothing. If anyone knows, where is the real problem or how to apply some work-around, it would be great.
Le

Yes, I also experienced the same thing with 118844-30 and 118822-30. It seems other people are also having issues with 118855-xx. I simply bypassed these patches, after a painful rebuild, and now everything is OK, including all other recommended patches.

Bad patch 118844-30

Just wondering if no one else is having issues with the Sun kernel patches?
A month ago we tried to install 118844-28, which failed to install see http://forum.sun.com/thread.jspa?threadID=28707&tstart=0
Now they release a new kernel patch, which seem to have the exact same problem.
The patch refuses to install saying that patch 117435-02 must be installed first and machine must be rebooted. The 117435-02 patch came with the installation of the OS.
From the prepatch script     #
     # biosdev failed. We can still apply the patch if the rootdisk
     # is the same as the bootdisk
     bootdev=`prtconf -v /devices | sed -n '/boot-device/{n;p;}' | grep pci | cut -f 2 -d \'`
     rootdev=`df -k ${BASEDIR:-/} | nawk 'NR > 1 { print $1 }'`
     if [ -n "$bootdev" ] ; then
          ls -l $rootdev | grep $bootdev > /dev/null
          if [ $? = 0 ]; then
               return 0
          fi
     fiRunning prtconf -v /devices will result in the following (among other things)name='bootpath' type=string items=1
            value='/pci@0,0/pci-ide@7/ide@0/cmdk@0,0:a'
name='bios-boot-device' type=string items=1
            value='80'Since they are still using sed -n '/boot-device/{n;p;}' which will return value='80' this patch will fail to install.

I've been trying to upgrade past 118844-26 for a while. This machine started out as a Solaris 10 x86 1/06 DVD install. I experience errors like you guys have listed here. My favorite so far was this, though:
118844-27
Executing prePatch script...
Once this KU patch is installed and you have rebooted your system,
you will not be able to patchrm this patch safely. Once the NEWBOOT
support is installed, removing it may cause your system to not
be bootable.
Do you wish to continue this installation {yes or no} [yes]?
(by default, installation will continue in 60 seconds)
Checking installed patches...
Executing prepatch script...
Usage: grep -hblcnsviw pattern file . . .
ERROR: One of the following may need to be corrected prior to installing this patch.
ERROR:
ERROR: The boot device may be different from the root device on biteme4.
ERROR: If you have booted from a floppy disk, eject the disk and reboot biteme4 prior
ERROR: to installing this patch.
ERROR: You may have forgotten to reboot biteme4 AFTER installing 117435-02.
ERROR: This configuration requires that 117435-02 be installed first and the
ERROR: system must then be rebooted prior to installing this patch.
The prepatch script exited with return code 1.
Patchadd is terminating.note the usage error on 'grep' ... apparently this patch had its grep arguments not quite sorted :)
I'll try the techniques posted here to see if I can move forward. Thanks for the input on this subject, folks!

Prob installing snmpdx patch on 2.6

Anyone know why I'd be getting this message when I try to install patch 106787-17 (snmp vulnerability)?
Checking installed patches...
One or more patch packages included in
106787-17 are not installed on this system.
I did a pkginfo -il on all the packages in the directory and they are (4 of them) installed.

Anyone know why I'd be getting this message when I try
to install patch 106787-17 (snmp vulnerability)?
Checking installed patches...
One or more patch packages included in
106787-17 are not installed on this system.
I did a pkginfo -il on all the packages in the
directory and they are (4 of them) installed.I had the same problems when I tried to install the patch on our E250's running 2.6 and 2.7,
Solaris 8 was no problem. I cehcked (like you did) that I had indeed all the packages installed.
I was however in the lucky situation that I could just disable SNMP as it was not doing anything useful...
I think if you look in the patch that you could perhaps just replace the files manually and then restart the service. (I guess it's a good idea to try on only one host first;)
Good luck,
Thomas

Patch 118844-21 killed my laptop!

Solaris 3/05 loaded just fine, recently patch 118844-21 installed GRUB as a bootloader, replacing the one that Sol 10 3/05 installed. Now the machine does not complete a boot. It loads the copyright notice and then hangs. Before this patch my laptop was quite happy. What gives?

Hi,
I'm new on Solaris, I installed the Solaris 10 3/05 on my lap and yesterday I installed the patches recommended and today I found that I can't boot with Solaris. I think I have the same problem but I don't know how to uninstall the patches that you mentioned.
Can you help me?
Thanks.

Kernel patch 118844-30 problem

I have an AMD-64 computer and when I try to install patch 118844-30 (and dependent patch for send mail), and restart, I get a million error messages at bootup, including "is syslogd running?". I had to reinstall the whole OS to get back to normal. Other updates worked fine.

Yes, I also experienced the same thing with 118844-30 and 118822-30. It seems other people are also having issues with 118855-xx. I simply bypassed these patches, after a painful rebuild, and now everything is OK, including all other recommended patches.

Can't install latest patch, "Patch Module for 32-Bit Version of Lenove Patch Utility" v 1.0.3

Hi,
I'm hoping someone can offer some help: I am unable to install the above patch on a T61 w/XP Pro/SP3. Error is simply, "1 Package did not install." Manual install gets same result. In the past when a patch did not instaqll I have had success by downloading and manually installing it, but I can't find the executable for this particular patch. Can anyone make a suggestion? Or point me to the executable?
GaryK
Solved!
Go to Solution.

This is how I was able to successfully install the Lenovo Patch Utility:
1) Enable if necessary and log into the built-in Administrator account.
2) Run System Update. Download and install the Lenovo Patch Utility (unsure if this is a necessary step,)
3) At this point, the Lenovo Patch Utility is not installed. The previous version of the Lenovo Patch Utility will display in Programs and Features.
4) Run System Update under an administrator account. Download and install the Lenovo Patch Utility (I ran this under a user-created Administrator account; unsure if works under built-in Administrator account..) Lenovo Patch Utility will no longer appear in Programs and Features. This indicates it has been succesfully installed.
5) Disable built-in Administrator account if desired for security reasons.

How to manually install QTP Agent Chrome plug-in

Hello All,
How can I manually install QTP Agent Chrome plug-in? Unable to locate plug-in in my machine.
I have installed QTP patch: QTPWEB_00088.EXE
By mistake, I have removed it from chrome extensions.
Thanks.
Ankit Nigam

Solution:
Install Chrome Agent.crx located at C:\Program Files\HP\QuickTest Professional\bin\Chrome
Can refer steps to install crx file:
http://askubuntu.com/questions/254643/ho-to-install-an-already-downloaded-crx-file-extension-in-chro...

Passcode for installing cluster patch

Hi,
I installed solaris 10 for x86 and now I would install cluster patch.
I downloaded zip cluster and unzipped in a dir.
When I start installation with "install_cluster" script, it ask me a passcode saying that in needed to allow install_cluster to continue running.
I never have seen a passcode for a cluster patch.
Anyone can help me please?

This thread prompted me to try to reproduce what was seen by the original post.
I have an old Pentium-III 440BX system with Solaris 10 GA (3/05) installed and never patched.
So ...
1. Ignore my earlier comments about signed versus unsigned patches.
It doesn't apply to the full cluster, only individual patches that you might download, sometime.
2. Yes, it pays to read the documentation.
The README file is clear about the passcode of "newboot".
3. That README file also cautions about the potential for multiple reboots,
depending on how far down-rev the system might be.
The document suggests three reboots could happen.
My old box needed four.
The cluster update script initiated the reboots.
The old 440BX chipset board interpreted the reboot signal
as a kernel page fault panic, sync'd the filesystems, and bounced the box.
No manual intervention was needed to cause the reboots.
I just had to start the update process all over again after each restart,
then sit back and watch the return codes tell me that such-and-so patch was
already installed, then finally get far enough along to apply the next patches per the script.
I'm now fully patched. Running showrev on a bunch of the patch numbers confirms it.
Curious, though. GRUB was installed but it's not being used.
The old x86 box is still using the original bootloader. No big deal.
I had been thinking of wiping that 7.5GB drive and installing the current release, anyway.

Manual install of patch 118844-28

Similar Messages

Maybe you are looking for