This release is a pre-release and may not be stable for production use.
Dead man’s switch (server)
This module receives status messages by dead_mans_switch_client and notifies you if a client instance didn’t check back in time.
As a side effect, you’ll also get some statistical data from your client instances.
Usage
Install dead_mans_switch_client on a customer instance and configure it as described in that module’s documentation. The clients will register themselves with the server automatically. They will show up with their database uuid, you’ll have to assign a human readable description yourself.
At this point, you can assign a customer to this client instance for reporting purposes, and, more important, add followers to the instance. They will be notified in case the instance doesn’t check back in time. Notification are only turned on for instances in state ‘active’, instances in states ‘new’ or ‘suspended’ will be ignored.
You’ll find the instances’ current state at Reporting/Customer instances.
For further information, please visit:
Security considerations
As the controller receiving status updates is unauthenticated, any internet user can have your server create monitoring instance records. While this is annoying, it’s quite harmless and basically the same as misuse of the fetchmail module.
For a more substantial annoyance, the attacker would have to guess one of your client’s database uuids, so they functionally are your passwords.
To be sure, consider blocking this controller from unknown origins in your SSL proxy. In nginx, it would look like this:
location /dead_mans_switch/alive {
allow 192.168.1.0/24;
# add other client's IPs
deny all;
}
Known issues / Roadmap
matching is done via the database’s uuid, so take care to change this if you clone a database
logging some postgres stats and disk usage would be nice too
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback here.
Credits
Contributors
Holger Brunn <hbrunn@therp.nl>
Maintainer
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
To contribute to this module, please visit http://odoo-community.org.
1 maintainer
Metadata
1 maintainer
Release files for odoo8-addon-dead-mans-switch-server 8.0.1.0.0.99.dev54
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| odoo8_addon_dead_mans_switch_server-8.0.1.0.0.99.dev54-py2-none-any.whl | Python 2 | none | any | Details |
Release files / odoo8_addon_dead_mans_switch_server-8.0.1.0.0.99.dev54-py2-none-any.whl
| Download URL | odoo8_addon_dead_mans_switch_server-8.0.1.0.0.99.dev54-py2-none-any.whl |
|---|---|
| Size | 164.8 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
e6a85a9ba29e023094ff1ca3d25384a92276e3411101b60de90f49bc436718e0
|
|
BLAKE2b-256 checksum How to use checksums |
dba41e82341e0801e07583ce67854e83f81f939e8f8d7a539e86e9aaaf6f9c72
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.5
|
Security for odoo8-addon-dead-mans-switch-server 8.0.1.0.0.99.dev54
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
