Sun Connection Application Issues

This section describes issues that you might encounter when using Sun Connection applications.

• Solaris Channels Cannot Handle Patches Uploaded In A *.tar.gz Format (CR 6571151)

• Time Out Message When Running a Large Job In Single-User Mode

• Console Sometimes Hangs (CR 6456138)

• Console Can Hang When Preferences Changed (CR 6464925)

• Job Can Hang When "Remote Hosts" is Used to Upload RPM (CR 6466850)

• Copying Non-Certified Objects Between Channels (CR 6456000)

Solaris Channels Cannot Handle Patches Uploaded In A *.tar.gz Format (CR 6571151)

Description:

The browser-based upload utility, upload.html, allows you to upload patches in various packed formats (*.zip, *.tar, *.tar.gz). However, the agent can only handle patches in a *.zip or **.jar format. The agent cannot handle a patch in the *.tar.gz format.

Results:

An error message similar to the following is displayed:

Execution of PATCH Job FAILED. Details: PATCH_INSTALL_JOB_124630-06-0
Patch intaller failed. Check if should continue.
Task will continue.
Commit Phase - Finished With error: 117515008 ( Cannot run job. ).
} Task Finished with a failure ! ( JobID = 52 )

Workaround

If the patch cluster is in a *.tar.gz format, unpack the archive and then use a *.zip or *.jar format to repack the patches.

Time Out Message When Running a Large Job In Single-User Mode

Description:

If you are single-user mode and running a large job on a Solaris 10 system, you might see the following message on the serial console:

svc.startd[7]: svc:/milestone/single-user:default: Method or service exit timed out. Killing contract 27. [ milestone/single-user:default timed out, fault threshold reached (see 'svcs -x' for details) ] Requesting System Maintenance Mode (See /lib/svc/share/README for more information.) Console login service(s) cannot run Root password for system maintenance (control-d to bypass):

Workaround:

This is normal. The patch job is still running, and no action is required.

To prevent the message from displaying, increase the default single-user milestone time out limit. The timeout seconds parameter is located in the /var/svc/manifest/milestone/single-user.xml file.

Console Sometimes Hangs (CR 6456138)

Description:

Sometimes the console hangs if open for a long time.

Workaround:

Close the console when not is use or close the console occasionally when you use it for a long time.

The system on which you run the console should have at least 1 Gbyte of memory.

Console Can Hang When Preferences Changed (CR 6464925)

Description:

If the console preferences are changed, and then an attempt is made to change them for a second time, the console can hang.

Workaround:

Kill the console and restart it.

Job Can Hang When "Remote Hosts" is Used to Upload RPM (CR 6466850)

Description:

If the "Remote Hosts" option is used to upload a file, and the remote host goes offline during the upload, the job remains stuck in the console, even after the remote host restarts.

Workaround:

Kill the console and restart it.

Copying Non-Certified Objects Between Channels (CR 6456000)

If you want to copy Non-Certified Objects (NCOs) between channels, use the scriptable API.