Settings file watchdog.properties¶
Watch dog server availability checking subsystem settings
| Parameter | Default value | Description |
|---|---|---|
| watchdog_autorun | `false` | If `true`, Watchdog will start automatically with the server. |
| watchdog_events | `CoreProcessDown,EventScannerDown` | `CoreProcessDown` - watch for the server process availability `EventScannerDown` - watch for SIP-stack operability `RegDoesNotWork` - periodically test SIP registration on the SIP account |
| on_watchdog_event | `watchdog_event_hook.sh` |
The setting that points to the shell script located in the `/usr/local/FlashphonerWebCallServer/bin` directory and is used to create error reports. The script receives three parameters:
`$1` - PID, process identifier
`$2` - Event, event name
`$3` - home directory `/usr/local/FlashphonerWebCallServer`
PID can be empty, if the `CoreProcessDown` event has occurred.
To create complete reports, make sure the script works correctly - run it manually:
In this example `9033` is a PID of the WCS Core Java process.
As a result, a complete report will be created in the `logs/watchdog` directory.
|
| client.jmx_port | `50999` | JMX port of the server the Watchdogs will connect to |
| client.jmx_login | `admin` | Watchdog login |
| client.jmx_password | `admin` | Watchdog password |
| client.failure_check_interval | `20000` | Interval in milliseconds Watchdog should performs its checks |
| client.notification.email | E-mail to send a report to if Watchdog detects WCS server availability problems | |
| notify_only | `false` | If the value is set to `true`, Watchdog will merely create reports and notify about failures by e-mail. It won't try to fix the issue by restarting the server or the SIP-stack. |
| server.registration.credentials | This setting holds the data of the test SIP account in the following format: Here: `WCS1` - SIP login `WCS1` - SIP Authentication Name (same as SIP login) `12345` - SIP password `sip.org` - SIP domain `sip.org` - SIP proxy (same as domain) `5060` - SIP port | |
| server.registration.credentials.delimiter1 | `,` | Treat comma as a delimiter when parsing data in the `server.registration.credentials` setting |
| server.registration.credentials.delimiter2 | `:` | Treat colon as a second delimiter when parsing data in the `server.registration.credentials` setting |
| mail.smtp.auth | `true` | Enable authorization when sending mail via SMTP |
| mail.smtp.starttls.enable | `true` | Enable the secure TLS protocol |
| mail.smtp.host | SMTP host. For example, `smtp.gmail.com` | |
| mail.smtp.port | SMTP port. For example, `587` | |
| mail.username | SMTP user name. Example: `test@flashphoner.com` | |
| mail.password | SMTP Password |