Configuration
This page covers both Odoo server-level configuration (timeouts, workers) and Tower application settings.
Odoo Server Settings
SSH commands can take significant time to complete. To avoid Odoo timeout, we recommend increasing the timeout limits in the Odoo configuration file or in the command line parameters.
We also recommend using the Cetmix Tower Server Queue module to run commands and flight plans asynchronously with at least several workers per channel:
[options]
(...)
limit_time_cpu=300 ; 5 minutes, more is better
limit_time_real=360 ; 6 minutes, more is better
workers = 4
server_wide_modules = web,queue_job
(...)
[queue_job]
channels = root:2
ODOO_QUEUE_JOB_CHANNELS=root:2 odoo-bin --config=/etc/odoo/odoo.conf \
--load=web,queue_job \
--workers=4 \
--limit-time-cpu=300 \
--limit-time-real=360 \
...
This will allow you to run more commands and flight plans in parallel without the risk of Odoo timeout.
General Settings
The Cetmix Tower General Settings allow you to configure system-wide behavior and notifications. Access them via Cetmix Tower > Settings > General Settings.
Access level
General Settings are available only to users with Root access level.
System Settings
| Setting | Description |
|---|---|
| Command timeout | Timeout in seconds after which a running command will be terminated. Set to 0 to disable. |
| Cron Job (Command timeout) | Opens the cron job that checks for zombie (stuck) commands. |
| Pull files from server | Configures the cron job that automatically pulls Files from servers to Tower. |
| Run scheduled tasks | Configures the cron job that runs Scheduled Tasks. |
Notifications
Configure how Tower displays in-app notifications:
| Setting | Description |
|---|---|
| Error Notifications | Show notifications for error events. Select "Sticky" to keep the notification visible until dismissed. Leave empty to disable. |
| Success Notifications | Show notifications for success events. Select "Sticky" to keep the notification visible until dismissed. Leave empty to disable. |
