Insufficient start timeout value in Solaris install

Description

When there are a reasonable number of nodes on a Solaris server started via svcadm, if it is unable to start up in 300 seconds it is automatically killed. A larger value is required for the start_timeout in /opt/opennms/contrib/smf-manifest.xml e.g.
<exec_method
type='method'
name='start'
exec='/opt/opennms/contrib/svc-opennms start'
timeout_seconds='600'>
<method_context>
<method_credential user='opennms' group='opennms' privileges='basic,net_icmpaccess,net_privaddr' />
</method_context>
</exec_method>

If the installed value is insufficient then the workround is:

svccfg -s opennms
setprop start/timeout_seconds = nnn
listprop
exit
svcadm refresh opennms

Environment

Solaris

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Seth Leger June 1, 2015 at 12:46 PM

Solaris is no longer supported as of OpenNMS 14.

Won't Fix

Details

Assignee

Reporter

Components

Affects versions

Priority

PagerDuty

Created December 10, 2010 at 5:41 AM
Updated June 1, 2015 at 12:46 PM
Resolved June 1, 2015 at 12:46 PM