Apr 1 14:03:22 router-002 kernel: carp: 2@vmx1: MASTER -> BACKUP (more frequent advertisement received) Apr 1 14:03:22 router-002 kernel: in_scrubprefix: err=65, prefix delete failed Apr 1 14:03:22 router-002 carp-ovh[98074]: Not MASTER -> exit
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 3 2026
Apr 2 2026
Apr 1 2026
Mar 31 2026
Mar 30 2026
Apr 1 14:01:39 router-002 kernel: carp: 2@vmx1: BACKUP -> MASTER (master timed out) Apr 1 14:01:39 router-002 carp-ovh[98049]: Detected MAC on vmx1: 00:50:56:09:3c:f2 Apr 1 14:01:39 router-002 carp-ovh[98053]: Checking current state... Apr 1 14:01:39 router-002 carp-ovh[98057]: Checking IPs for MAC 00:50:56:09:3c:f2 Apr 1 14:01:39 router-002 carp-ovh[98061]: OVH returned: ['178.32.70.110', '51.68.252.230'] Apr 1 14:01:39 router-002 carp-ovh[98065]: VIP is already on correct MAC -> nothing to do
When router-003 (The MASTER) become unavailable :
Mar 29 2026
Mar 25 2026
Two actions to fix:
The nginx configuration doesn't seem the same for the Docker container and the development site:
Mar 24 2026
The script to test if we can access to the OVH credentials (application_key, application_secret, consumer_key):
The script to test the connection to Vault, using a YAML configuration file that tells the secretsmith client how to connect to Vault :
Mar 23 2026
We can consider the mail server as deployed and create tasks for extra actions in the Mail projects.
Deployed and working fine.
Dovecot deployed and working well.
With Salt, sudo files content are now managed from rOPS.
See also T1784 to improve UX and URLs.
Software has been renamed to Redpanda Connect:
Checked today, it works fine:
Mar 22 2026
Next: configure DNS records
This method works well, Salt automation is welcome.