The following troubleshooting issues relate to the browser interface.
You provide the correct Change Manager URL, but you are unable to reach the login page. Following is the correct form of the URL:
https://server_name.domain:6789/changemgr |
Try restarting the web server.
# /usr/sadm/bin/smcwebserver restart |
You type a valid Change Manager user name and password on the Change Manager login page, but the login attempt fails.
Try restarting the Sun Management Center server.
# /opt/SUNWsymon/sbin/es-start -A |
You provide a valid Solaris user name and password, but are unable to start the Change Manager application.
Ensure that you are an authorized Sun Management Center user by inspecting the file /var/opt/SUNWsymon/cfg/esusers.
To access all areas of Change Manager, you need to be an authorized Sun Management Center domain administrator. Ensure that you are a member of both the esadm and esdomadm groups.
You provide the correct Change Manager URL, but the following error message appears in a dialog box:
document contained no data. |
Verify that the URL is correct.
The following example shows the correct form of the Change Manager URL:
https://server_name.domain:6789/changemgr |
Ensure that the URL begins with https, not http.
If the URL is correct, try restarting the web server.
# /usr/sadm/bin/smcwebserver restart |
Netscape Communicator Version 4 produces this message:
The server's certificate has an invalid signature. You will not be able to connect to this site securely. |
Restart the Netscape Communicator, then access the page again.
The browser interface cannot display the contents of directories that are not publicly readable. This problem prevents the file browser from accessing private directories even though the user has appropriate permissions.
Directly specify files in such a directory by supplying a full path name to the file.
The Sun Management Center Web Console server continues to use the cached Change Manager 1.0 JSP classes instead of recompiling them from the new Change Manager 1.0.1 JSP sources.
This happens because the JSP classes have a later timestamp than the JSP source files.
Stop the Sun Management Center Web Console server, remove the cached Change Manager 1.0 JSP classes, then restart the web console server.
The procedure differs, depending on the version of Solaris you are running on the Change Manager server.
If you are running Solaris 9 12/02, or an earlier release of Solaris, run these commands:
# /usr/sadm/sbin/smcwebserver stop # rm -rf /var/sadm/webconsole/work/localhost/changemgr # /usr/sadm/bin/smcwebserver start |
If you are running at least Solaris 9 4/03, run these commands:
# /usr/sadm/bin/smcwebserver stop # rm -rf /var/sadm/webconsole/work/Standalone/localhost/changemgr # /usr/sadm/bin/smcwebserver start |