Difference between revisions of "VALT 6.6.17"
IVSWikiBlue (talk | contribs) (Created page with "July 14th, 2026 '''Technical''' * Features ** Added automatic SSH key setup between Media servers and their Application server during install/reconfiguration * Fixes ** Fixe...") |
IVSWikiBlue (talk | contribs) |
||
| Line 2: | Line 2: | ||
'''Technical''' | '''Technical''' | ||
| − | + | * Added automatic SSH key setup between Media servers and their Application server during install/reconfiguration | |
| − | + | * Fixed issue where the Media-to-Application Wowza configuration sync could fail with a permission error or be silently skipped due to connecting with the wrong SSH user | |
| − | + | * Fixed issue where newly installed SSH private keys were left with permissions SSH rejects, causing repeated password prompts | |
| − | + | * Fixed issue where SSH key setup would continue after a failed key installation and report success | |
| − | + | * Disabled innodb_snapshot_isolation on MariaDB to prevent "record has changed since last read" errors introduced by the MySQL to MariaDB migration | |
| − | |||
| − | |||
| − | |||
Revision as of 10:31, 14 July 2026
July 14th, 2026
Technical
- Added automatic SSH key setup between Media servers and their Application server during install/reconfiguration
- Fixed issue where the Media-to-Application Wowza configuration sync could fail with a permission error or be silently skipped due to connecting with the wrong SSH user
- Fixed issue where newly installed SSH private keys were left with permissions SSH rejects, causing repeated password prompts
- Fixed issue where SSH key setup would continue after a failed key installation and report success
- Disabled innodb_snapshot_isolation on MariaDB to prevent "record has changed since last read" errors introduced by the MySQL to MariaDB migration
