bƙmd` ˙˙˙˙˙˙˙˙˙& ˙˙˙;J˙˙˙˙˙˙Nzf˙˙˙yc˙˙˙˙˙˙Šj Ÿp˙˙˙ ´¨˙˙˙˙˙˙ÇÔߝ˙˙˙ ň.˙˙˙˙˙˙6 <˙˙˙-S˙˙˙˙˙˙@‰Xɝ˙˙˙kJ˙˙˙˙˙˙|R‘X˙˙˙Śo˙˙˙˙˙˙šĽ #Ńç˙˙˙äh˙˙˙˙˙˙őp v˙˙˙˙˙˙˙˙˙2Ě J ˙˙˙]Š˙˙˙˙˙˙n’!ƒ˜˙˙˙"˜Ż˙˙˙˙˙˙Ťĺ)Ă" ˙˙˙%ÖŁ ˙˙˙˙˙˙çŤ $'üą ˙˙˙(Č ˙˙˙˙˙˙$ &,<; ˙˙˙+Oź ˙˙˙˙˙˙`Ä *.uĘ ˙˙˙˙˙˙Šá -/ ˙˙˙˙˙˙ľ[ IČÜ ˙˙˙2Ů㠝˙˙˙˙˙˙îé 14 ˙˙˙5‹ ˙˙˙˙˙˙. 39A¨˙˙˙8RŻ˙˙˙˙˙˙gľ7:|̝˙˙˙;Đ˙˙˙˙˙˙§*6BşÎ˙˙˙>Ë՝˙˙˙˙˙˙ŕŰ=@őň˙˙˙Ac˙˙˙˙˙˙ ä?E3„˙˙˙DD‹˙˙˙˙˙˙Y‘CGn¨˙˙˙˙˙˙FH™U˙˙˙˙˙˙Ź:<U˝A˙˙˙KŇG˙˙˙˙˙˙ç^JMú0˙˙˙N€˙˙˙˙˙˙%'LR6.˙˙˙QK4˙˙˙˙˙˙`KPSsS˙˙˙T‹˙˙˙˙˙˙˙žO[Ż¤˙˙˙WÄŞ˙˙˙˙˙˙ŮÁVYěϝ˙˙˙Z˙˙˙˙˙˙š!X^(Ą!˙˙˙]=§!˙˙˙˙˙˙Rž!\`e"˙˙˙˙˙˙}Ř"_aĽ%˙˙˙˙˙˙ĄŹ%0”ś˛%˙˙˙dËÉ%˙˙˙˙˙˙Ţ%'cföÁ'˙˙˙g D+˙˙˙˙˙˙K+ek/Q+˙˙˙jDh+˙˙˙˙˙˙Wł,ilo-˙˙˙m‚.˙˙˙˙˙˙“.ht¨ .˙˙˙p˝7.˙˙˙˙˙˙ĐZ/orčş/˙˙˙sű“0˙˙˙˙˙˙ š0qw!  0˙˙˙v6 ˇ0˙˙˙˙˙˙I Ć1uya /2˙˙˙˙˙˙t ö3xz… ý3˙˙˙˙˙˙š 4n‡Ż 4˙˙˙} ’4˙˙˙˙˙˙Ú ě4|í Č5˙˙˙€ţ Ď5˙˙˙˙˙˙ Ő5~„( ě5˙˙˙ƒ; f7˙˙˙˙˙˙S Î7‚…f -9˙˙˙†w 49˙˙˙˙˙˙Œ :9Ą Q9˙˙˙‰´ Ŕ9˙˙˙˙˙˙Ě :ˆ‹ß l=˙˙˙Œđ s=˙˙˙˙˙˙ y=Š =˙˙˙- Ś>˙˙˙˙˙˙E ?Ž’X ,B˙˙˙˙˙˙i 3B‘“~ 9B˙˙˙˙˙˙“ PB{­Ś iC˙˙˙–ž ŇC˙˙˙˙˙˙Ń pF•˜â wF˙˙˙™÷ }F˙˙˙˙˙˙ ”F— ™G˙˙˙œ7 EH˙˙˙˙˙˙J šJ›ž[ ŔJ˙˙˙Ÿp ĆJ˙˙˙˙˙˙… ÝJšŚ˜ öK˙˙˙˘° TL˙˙˙˙˙˙Ă žMĄ¤Ô ĹM˙˙˙Ľé ËM˙˙˙˙˙˙ţ âMŁŠ řN˙˙˙¨) @O˙˙˙˙˙˙< yP§ŤM €P˙˙˙˙˙˙b †PŞŹw P˙˙˙˙˙˙Š ­Q š˘ üQ˙˙˙Żľ lT˙˙˙˙˙˙Ć sTŽąŰ yT˙˙˙˛đ T˙˙˙˙˙˙şU°ś' to see a list of services waiting for the service to start.)The Solaris Service manager tried to import a manifest or apply a profile defining the service, but detected one or more entities with conflicting definitions.Edit the problematic manifest or profile to resolve the conflict and reimport or reapply it, or use svccfg to administratively override the conflicting definitions. Then clear the maintenance state. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.defectmajorThe service has been placed into the maintenance state.% is unavailable.A service failed - %.Run 'svcs -xv %' to determine the generic reason why the service failed, the location of any logfiles, and a list of other services impacted. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.ireportmajorNo automated response.Functionality provided by the service is unavailable.The indicated service has transitioned to the maintenance statePlease refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.ireportminorNo automated response.Functionality provided by the service is unavailable.The indicated service has transitioned to the uninitialized statePlease refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.ireportminorNo automated response.Some functionality provided by the service may be unavailable.The indicated service has transitioned to the degraded statePlease refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.ireportminorNo automated response.Functionality provided by the service is unavailable.The indicated service has transitioned to the disabled statePlease refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.ireportminorNo automated response.Functionality provided by the service is now available.The indicated service has transitioned to the online statePlease refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.ireportminorNo automated response.Functionality provided by the offline service is unavailable.The indicated service has transitioned to the offline statePlease refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.Functionality provided by the maintenanced service is unavailable. The service will not be started until the maintenance state is cleared.The service requesting maintenance has detected some configuration issue and decide to place this service in maintenance.Run svcs -xv service_fmri to see the responsible service that placed this service in maintanence. Check the responsible service's log file for errors and/or explanations. Correct the errors and run svcadm clear service_fmri to clear maintenance state and restart the service. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.N/AGeneral instructions on handling and recovering from potential errors during system boot.See Details for potential actions. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.A previous invocation of the service may still be running, despite a request to disable, refresh, or restart it.The service still transitioning to a new state. Once the transition has completed, the service will be placed in its new state. Wait until the service reaches the declared next state, or definitively fails to do so. (If the service's executing method executes for longer than its associated timeout, then the restarter will declare the method to have failed.) The next state may be viewed by invoking "svcs -v". Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service instance's behavior is not well defined; it may or may not have been started or stopped correctly.The service instance's state is not recognized by the system. Wait for a moment in case the responsible restarter is still processing commands. If the condition persists, try refreshing or disabling and enabling the service with svcadm(1M). If the service remains in the invalid state, this error suggests a defect in the responsible restarter, the configuration repository daemon, or the temporary repository contents. Contact Sun Service with the output of svcs -x, svcs -l restarter_service_fmri, a core file of the restarter, a core file of svc.configd(1M), and a copy of /etc/svc/volatile/svc_nonpersist.db. A core file can be generated by the gcore(1) utility. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMajorNo automated response.The Solaris Service Manager will start an sulogin(1M) shell on the console to allow the administrator to recover the system. The system will not be able to boot until a non-corrupted replacement is installed.The Solaris Repository Daemon discovered that the smf(5) repository is corrupt.Log in to the sulogin(1M) shell. Run the command /lib/svc/bin/restore_repository, and follow its instructions to restore one of the automatic backup copies of the repository. Upon successful completion, the system or local zone will be rebooted, and the restored repository will take effect. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service will remain stopped until its maintenance state is cleared. Other services with require-type dependencies on the service will not be started until this service is repaired. (Use svcs -xv service_fmri to list such impacted services.)The service terminated and was restarted more frequently than normal. The Solaris Service Manager placed the service into maintenance mode instead of restarting it again. Determine why the service was terminating. If the service's restarter is svc.startd, consult the service's log file; its name is based on the FMRI of the service and it is located in /var/svc/log (/etc/svc/volatile if early in boot). Also consult service-specific log files and documentation (use svcs -x service_fmri to list documentation references for the service). Once the problem is fixed, run svcadm clear service_fmri to request the Solaris Service Manager to restart the service. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service is not running. It will not be started until the maintenance state is cleared. Services with require-type dependencies on the service will not be started. (Use svcs -xv service_fmri to see a list of services waiting for the service to start.)The Solaris Service manager tried to start the service, but could not. Determine why the service's start method failed. Consult the service's log file, typically in /var/svc/log and named based on the service's FMRI. (Very early in boot, service logs are placed in /etc/svc/volatile.) Once the problem has been fixed, run svcadm clear service_fmri to request that the Solaris Service Manager clear the service's maintenance state and treat the service normally. If it is still enabled and its dependencies are met, it will be started. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service is not running. It will remain in the maintenance state until the invalid dependency is corrected or removed, its configuration is refreshed, and the maintenance state is cleared.The service was placed into maintenance because its dependency configuration is invalid. The dependencies of a service may be retrieved using svcs -l service_fmri. Invalid dependencies will be marked. Depending on administrator understanding of the impacted service, it may be preferable to attempt repair or removal of the dependency using svccfg or to consult with Sun Service. Once the dependency is corrected, svcadm refresh service_fmri will update the service's running configuration snapshot, and svcadm clear service_fmri will instruct the Service Manager to restore the service to normal operation. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service is not running. It will remain in maintenance until the chain of dependencies which leads back to it is broken and the Service Manager has reread the service's configuration. Services which depend on the service will not be started. (Use svcs -xv service_fmri to see a list of services waiting for the service to start.)The Solaris Service Manager has determined that the service depends on itself, directly or indirectly, and has placed the service in the maintenance state. Determine the dependency chain which leads to the service. The Solaris Service Manager logged the FMRIs of the services to /var/adm/messages under standard syslogd(1M) settings. Direct dependencies of the service may be listed with svcs -l service_fmri. Depending on administrator understanding of the impacted service, it may be preferable to attempt repair or removal of the dependency using svccfg(1M) or to consult with Sun Service. Once the dependency chain has been broken, svcadm refresh service_fmri will instruct the Service Manager to reread the service's dependencies, and svcadm clear service_fmri will instruct the Service Manager to clear the service's maintenance state. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service is not running. It will remain offline until its dependencies are met, when the Solaris Service Manager will attempt to start it. Services with require-type dependencies on the service will not be started. (Use svcs -xv service_fmri to see a list of services which are waiting for the service to start.)The service is offline because it depends on a service which is not running.Use svcs -x dependency_fmri to determine why the dependency service is not running. Once it is running, the service will be started. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service is not running. It will remain offline while the excluding service is running (online or degraded). Services with require-type dependencies on the service will not be started. (Use svcs -xv service_fmri to see a list of services waiting for the service to start.)The service is offline because it has an exclude-type dependency on a service which is running.If the service should be running, execute svcadm disable on the excluding service. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service is not running. It will remain offline until the required services are running. Services with require-type dependencies on the service will not be started. (Use svcs -xv service_fmri to see a list of services waiting for the service to start.)The service is offline because it specifies a require-type dependency on a service which does not exist.Install and enable appropriate required services. A list of the required services may be retrieved using svcs -lservice_fmri. If the dependencies are erroneous, remove them with svccfg(1M) and use svcadm refresh service_fmri to instruct the Service Manager to read the corrected set of dependencies. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service is running. It will remain in the degraded state until changed by an administrator, or until system reset.The service is running, but an administrator has requested that it be marked as degraded.Run svcadm clear service_fmrito remove the administratively marked state. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service is in the process of starting. Services with require-type dependencies on this service will not be started until the start action has completed successfully. Services with optional dependencies on this service will be started when the start action has completed. (Use svcs -xv service_fmri to see a list of services waiting for the service to start.)The service is offline, but it is being started. It will be marked online if the action is successful.Wait until the service reaches the online state, or definitively fails to do so. (If the service's start method executes for longer than its associated timeout, then the restarter will declare the method to have failed.) Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.Uncertain. Use svcs -xv service_fmri to see a list of services waiting for this service to start.An explanation for the current state of the service could not be determined. Determine the restarter for the service with svcs -l service_fmri. For services managed by svc:/system/svc/restarter:default, collect data for Sun Service. In particular, obtain a core file for svc.startd(1M) by using gcore(1), as well as svcs -x output. Once data has been obtained, it may be possible to restore service operation by requesting restart or clearing a degraded or maintenance state, using svcadm(1M). For services managed by other restarters, no diagnosis may be available by design. See the documentation for the relevant restarter for guidance. If the service is in the maintenance state, svcadm clear service_fmri will instruct the restarter to clear it. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service may or may not be running. It will not be started until the maintenance state is cleared. Services with require-type dependencies on the service will not be started. (Use svcs -xv service_fmri for a list of services waiting for the service to start.)The restarter for the service placed the service into the maintenance state without explanation. Use svcs -l service_fmri to determine the restarter for the service. For services managed by svc:/system/svc/restarter:default, collect data for Sun Service. In particular, obtain a core file for svc.startd using gcore(1), as well as svcs -x output. Once data has been obtained, it may be possible to restore service operation clearing the maintenance state with svcadm(1M). For services managed by other restarters, no diagnosis may be available by design. See the documentation for the relevant restarter for guidance. Running svcadm clear service_fmri will request that the restarter clear the maintenance state. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service may or may not be running. It will not be started until the maintenance state is cleared. Services with require-type dependencies on the service will not be started. (Use svcs -xv service_fmri to see a list of services waiting for the service to start.)The service's restarter tried to execute a method for the service, but it did not complete successfully.Determine what method failed and why. Consult the service's log file, typically in /var/svc/log and named based on the service's FMRI. (Very early in boot, service logs are placed in /etc/svc/volatile.) If the stop method failed, processes which belonged to the service may still be running.Once the problem has been fixed, run svcadm clear service_fmri to request that the Solaris Service Manager clear the maintenance state and treat the service normally. If it is enabled and its dependencies are met, it will be started. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service will remain in the maintenance state until the condition that led to method failure is remedied, and the service's maintenance state is cleared by the administrator. Services that express a dependency on the impacted services may also be affected.The Solaris Service Manager has determined that the service has been moved into maintenance because one of its methods (other than the start method) has failed repeatedly.The per-instance log file may contain information to determine the cause of method failure. Log files associated with the service are typically in /var/svc/log and are named based on the service instance's FMRI. (Services that start very early in boot may log instead to /etc/svc/volatile.) A review of the service's configuration files may also be appropriate. Once remedied, run svcadm clear impacted_service_fmri to bring the service instance out of the maintenance state. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service may or may not be running. It will not be started until the maintenance state is cleared. Services with require-type dependencies on the service will not be started. (Use svcs -xv service_fmri to see a list of services waiting for the service to start.)An administrator requested that the Solaris Service Manager stop the service for maintenance.Run svcadm clear service_fmri to request that the Solaris Service Manager clear the service's maintenance state and treat the service normally. If the service is enabled and its dependencies are met, it will be started. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service is not running. It will remain in the uninitialized state until its restarter runs and initializes it. Services with dependencies on the service may be affected. (Use svcs -xv instance_fmri to see a list of services waiting for the service to start.)The service cannot be manipulated because its restarter is not running.Use svcs -l service_fmri to determine the FMRI of the service's restarter. Use svcs -x restarter_service_fmri to see an explanation for the restarter's state. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service is not running. It will remain in the uninitialized state until the restarter executes correctly. Services with dependencies on the service may be affected. (Use svcs -xv service_fmri to see a list of services waiting for the service to start.)The service's restarter is online, but did not initialize the service's state. Wait for a moment in case the responsible restarter is still processing commands. If the condition persists, try refreshing or disabling and enabling the service with svcadm(1M). If the service remains in uninitialized, this error suggests a defect in the responsible restarter. Contact Sun Service with the output of svcs -x, svcs -l restarter_service_fmri, and a core file of the restarter. A core file can be generated by the gcore(1) utility. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service will remain in the current state until the specified restarter is installed or the service's restarter declaration is fixed. Services with dependencies on the service may be affected. (Use svcs -xv service_fmri to see a list of services waiting for the service to start.)The Solaris Service Manager can not manipulate the service because the restarter it specified does not exist on the local system. Due to a bug in svc.startd, changes to a service's restarter do not take effect immediately. There are two ways to work around the bug. If you don't have a service manifest for the service, create one by running svccfg export service_fmri > service.xml . Correct or delete the element of the manifest. Delete the service from the configuration repository with svccfg delete service_fmri . Recreate the service with svccfg import service.xml . Change the restarter for the service by running svcadm delegate restarter_fmri service_fmri . Then restart svc.startd by running pkill svc.startd . Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service will remain in the current state until its restarter declaration is fixed. Services with dependencies on the service may be affected. (Use svcs -xv service_fmri to see a list of services waiting for the service to start.)The Solaris Service Manager can not manipulate the service because its restarter specification is invalid. Due to a bug in svc.startd, changes to a service's restarter do not take effect immediately. There are two ways to work around the bug. If you don't have a service manifest for the service, create one by running svccfg export service_fmri > service.xml . Correct or delete the element of the manifest. Delete the service from the configuration repository with svccfg delete service_fmri . Recreate the service with svccfg import service.xml . Change the restarter for the service by running svcadm delegate restarter_fmri service_fmri . Then restart svc.startd by running pkill svc.startd . Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service is not running. It will remain in the disabled state until it is enabled (for example, with svcadm enable -t). Services with require-type dependencies on it will not be started. (Use svcs -xv service_fmri to see a list of services waiting for the service to start.)The service is disabled. It is not running and will not be started until next boot.To request the Solaris Service Manager to start the service, run svcadm enable service_fmri. To see its state, run svcs service_fmri. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.DefectMinorNo automated response.The service is not running. It will remain in the disabled state until it is enabled (for example, with svcadm enable -t). Services with require-type dependencies on it will not be started. (Use svcs -xv service_fmri to see a list of services waiting for the service to start.)The service is disabled. It is not running and will not be started.To request the Solaris Service Manager to start the service, run svcadm enable service_fmri. To see its state, run svcs service_fmri. Please refer to the associated reference document at %s for the latest service procedures and policies regarding this diagnosis.