CLI tool for updatemanager
I would like to patch a new solaris 10 installation on a sunfire v100, which has no monitor port, and as it will only be acting as a web server, it doesn't run a windowing system.
Running smpatch returns the following error:
Failure: Cannot connect to retrieve detectors: Server returned HTTP response code: 403 for URL: https://getupdates.sun.com/solaris/
Which I assume means that the machine has not been registered yet.
How can I register this machine with the sun update web site to allow it to download patches?
[556 byte] By [
1..c5] at [2007-11-26 6:03:40]
# 1
Did setting DISPLAY to point to a machine which runs X not work with updatemanager? I think it is a basic X application.
On your desktop machine running X:
xhost +sunfire
On your sunfire:
DISPLAY=myDesktop:0
export DISPLAY
/usr/bin/updatemanager
updatemanager window should now be visible on myDesktop's X session.
# 2
Short term you'll have to xhost to another machine that you can run the gui to register the machine. After it has been registered, you can use smpatch directly.
Running X across remote machines can be painful depending on the network topology and bandwidth limitations. Another recommendation is to run a local vncserver on the box, if you can, and then connect via vncviewer to run the gui to register the machine.
A cli registration tool is currently in the works and will be out shortly.
# 3
If you setup one of your boxes as a local patch proxy server (LPS), then you can point the internal boxes to it and they don't need to be registered.
Of course you won't be using updatemanager, but rather smpatch. My guess is you are used to working without all the fluff anyhow so this shouldn't bother you.
once you have the LPS working, just point the interal clients to it, run smpatch download, then smpatch update. (the downloads can fail several times, that's why I say do the download first)
The latest 1.0 version of LPS supports Solaris 8/9/10 which is nice :-)
# 4
Thank you to all for responding.
The solution I used was to connect to the sun box using my Mac OS X desktop machine:
mac% xhosts +
mac% ssh -X sunfire
sunfire$ export DISPLAY=mac:0.0
sunfire$ /usr/bin/updatemanager
Now that the machine has been registered I can run smpatch locally.
For multiple installations, using a local patching proxy should simplify the task even more.
1c5 at 2007-7-6 13:28:39 >
# 5
> once you have the LPS working, just point the interal
> clients to it, run smpatch download, then smpatch
> update. (the downloads can fail several times,
> that's why I say do the download first)
I would love to do that but how do I convince smpatch to use the LPS without using updatemanager.
when I try:
smpatch download -H proxy:3816
I get:
Option(s) "-H proxy:3816" require CIM support,
but CIM client support is not installed.
It is not clear to me whether the -H parameter wants a regular http proxy or a "Sun Update Connection Proxy"
Nico at 2007-7-6 13:28:39 >
# 6
The message you got does not correspond to the error message you get when your system has not registered. Are your proxy settings correct?
If you want to register your system from the command line, you must first download and install the registration CLI patch on your system. Select either the patch ID 120776 (SPARC version) or 120777 (x86 version) as appropriate for your system. See Sun Update Connection 1.0, System Edition Registration Guide for the Command-Line Interface. http://sunsolve.sun.com/searchproxy/document.do?assetkey=1-9-82688-1
# 7
Actually I don't want to register that system. According to the documentation of the Update Connection Proxy clients that only connect to the proxy and don't need to be managed on-line via Sun Update connection don't need to be registered.
I have patch 120776 installed but that doesn't seem to make any difference. I get the same error whether I try to use the Update Connection Proxy or our regular http proxy. I know the Update Connection Proxy is working because I tried to use it via Update Manager from another system. However I do not want to install 20 Solaris 10 servers and then have to run the Update Manager GUI on all of them just to get the proxy settings right.
Nico at 2007-7-6 13:28:39 >
# 8
On the client that you want to connect to the SUC proxy try setting the patchpro source by using the following command -
# smpatch set patchpro.patch.source
It will then prompt you for the source and you'll want to enter your SUC proxy address in the following format -
http://<server-name>:3816/solaris/
# 9
Great! Thanks!
Nico at 2007-7-6 13:28:39 >
