Sun Fire[TM] 12K/15K/E20K/E25K: SMS fomd daemon generates warnings like "Propagation/retrieval of <filename> failed - check earlier messages for the following code: 50000"

Asset ID:	1-72-1620190.1
Update Date:	2017-09-29
Keywords:

Solution Type Problem Resolution Sure

Solution 1620190.1 : Sun Fire[TM] 12K/15K/E20K/E25K: SMS fomd daemon generates warnings like "Propagation/retrieval of failed - check earlier messages for the following code: 50000"

Applies to:

Sun Fire E25K Server - Version All Versions to All Versions [Release All Releases]
Sun Fire 12K Server - Version All Versions to All Versions [Release All Releases]
Sun Fire E20K Server - Version All Versions to All Versions [Release All Releases]
Sun Fire 15K Server - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

SMS fomd daemon on Main System Controller (where SMS services are active) may continuously report "Propagation/retrieval" warnings, like:

fomd[797]: [8542 46167871404955379 WARNING PropMgr.cc 510] Propagation/retrieval of "/var/opt/SUNWSMS/adm/E/wfailoutput/wfailoutput.140127.2032.37" failed - check earlier messages for the following code: 50000
fomd[797]: [8542 46167871412657110 WARNING PropMgr.cc 510] Propagation/retrieval of "/var/opt/SUNWSMS/adm/E/wfailoutput/wfailoutput.131224.1357.54" failed - check earlier messages for the following code: 50000
fomd[797]: [8542 46167871420865106 WARNING PropMgr.cc 510] Propagation/retrieval of "/var/opt/SUNWSMS/adm/E/wfailoutput/wfailoutput.140116.2130.56" failed - check earlier messages for the following code: 50000

This may cause other SMS commands to run extremely slow and domain recovery to take a very long time.

Cause

Analysis shows that this scenario can be caused by fomd daemon on Main SC having SMS failover enabled, and / (root) filesystem on spare SC being full.

This causes fomd to continously attempt to propagate to the Spare SC, but the Spare is unable to deal with these files.

Solution

Check if the above applies; if so, turn off failover on Main SC using the "setfailover off" command. Then, log into Spare SC and delete unnecessary files from the / filesystem.

Finally, enable SMS failover once again using "setfailover on" and file propagation should now complete successfully.

Internal Section

References for more info and troubleshooting:

Sun Fire[TM] 12K/15K/E20K/E25K: Enabling Debug Messages in SMS (Doc ID 1004617.1)
Sun Fire[TM] 12K/15K/E20K/E25K: System Management Software (SMS) Daemons Overview (Doc ID 1010533.1)

Another example of fomd generating similar Propagation errors is: Sun Fire[TM] 12K/15K: fomd error 8542 (Doc ID 1018742.1)

Attachments

This solution has no attachment