Problem running Sun Patch Manager 2.0 after a successful installation
SunOS rpu1 5.8 Generic_117350-25 sun4u sparc SUNW,Sun-Fire-480R
I installed Sun PM 2.0 successfully on this server, but when I ran smaptch analyze I got this message:
# smpatch analyze
Unknown host (updateserver.sun.com) connecting to https://updateserver.sun.com/solaris/
Meanwhile during the installation it asked if i would like to upgrade to java version 1.4, I said yes, but when I try to check the java version I got:
# java -version
java version "1.2.2"
Solaris VM (build Solaris_JDK_1.2.2_17b, native threads, sunwjit)
How do I resolve this.
Thank you.
[621 byte] By [
aye_babaa] at [2007-11-26 19:05:51]
# 1
Do you normally use an HTTP proxy to get out onto the Internet?
If so, please set the proxy value with:
smpatch set patchpro.proxy.host=<proxyHostnameOrIP>
smpatch set patchpro.proxy.passwd=<passwd>
smpatch set patchpro.proxy.port=<port>
Could you also post the output from:
# echo $JAVA_HOME
# which java
# ls -l /usr/java
# 2
The output is shown below:
# echo $JAVA_HOME
/opt/j2sdk1.4.2_13
# which java
/usr/bin/java
# ls -l /usr/java
lrwxrwxrwx1 rootother 9 Jul 13 2004 /usr/java -> ./java1.2
I have not tried to browse before, and I don't really know much about the internet or HTTP setting, could you direct me on this too?
Thank you.
# 3
This would certainly appear to be a network related issue,
If you do not know you current setup we would recommend that you run the following commands:
# ping updateserver.sun.com
# ping -s updateserver.sun.com
# traceroute -p 443 updateserver.sun.com
# telnet updateserver.sun.com 443
And return the output generated.
# 4
Here is the output for the ping, traceroute and telnet:
# ping updateserver.sun.com
ping: unknown host updateserver.sun.com
# ping -s updateserver.sun.com
ping: unknown host updateserver.sun.com
# traceroute -p 443 updateserver.sun.com
traceroute: unknown host updateserver.sun.com
# telnet updateserver.sun.com 443
updateserver.sun.com: Unknown host
#
# 5
im getting this same problem as well..
a brand new install of opensolaris 5.11 snv_57 i86pc
omeo[/export/00/home/gwilson] nslookup updateserver.sun.com
Server: 203.8.183.1
Address:203.8.183.1#53
Non-authoritative answer:
Name:updateserver.sun.com
Address: 198.232.168.135
omeo[/export/00/home/gwilson] ping 198.232.168.135
^C
omeo[/export/00/home/gwilson]
# 6
Could you both check your /etc/nsswitch file, and ensure that 'dns' is listed for hosts if you are directly connected to the Internet, or that the correct HTTP proxy, port and user details are listed by:
# smpatch get patchpro.proxy.host
# smpatch get patchpro.proxy.port
# smpatch get patchpro.proxy.user
# 7
Here is the output I got from my nsswitch.files
# more /etc/nsswitch.files
#
# /etc/nsswitch.files:
#
# An example file that could be copied over to /etc/nsswitch.conf; it
# does not use any naming service.
#
# "hosts:" and "services:" in this file are used only if the
# /etc/netconfig file has a "-" for nametoaddr_libs of "inet" transports.
passwd:files
group:files
hosts:files
ipnodes:files
networks:files
protocols: files
rpc:files
ethers:files
netmasks:files
bootparams: files
publickey: files
# At present there isn't a 'files' backend for netgroup; the system will
#figure it out pretty quickly, and won't use netgroups at all.
netgroup:files
automount: files
aliases:files
services:files
sendmailvars:files
printers:user files
auth_attr: files
prof_attr: files
project:files
#
# 8
We can see here that you do not have the "host" parameter set to dns:
hosts: files
Which may prohibit direct acces, and would account for why you were seeing the errors, running the connectivity commands which we requested you to run.
Whilst we can assist you configuring the Patch Manager 2.0 tool, we cannot provide information on how you should access the internet.
Do you have a network or firewall team that can assist you with your setup.
# 9
I will try get in touch with network guys and get back to you.Thanks for your help so far.
