- Joined
- Apr 6, 2017
- Messages
- 9
- Reaction score
- 1
Our 3cx system is set to automatically run updates.
Our 3CX update (20.0.10.1785) also triggered a Debian OS update that included grub-pc. Because grub-pc.postinst spawned an interactive debconf frontend prompt asking which disk (/dev/nvme0n1) to install GRUB onto—and there was no interactive terminal attached to the background 3CX updater—dpkg and apt-get have been sitting frozen on that prompt, holding the package lock while 3cxpbx is half-upgraded.
This was quite frustrating, as the dependency on 3cx to manage these auto-updates, effectively failed half way, leaving the entire system inaccessible until we manually found the issue, got the grup-pc matter resolved and finalising the update.
My question is - is this a common issue, and why did the update trigger if it needed an interactive prompt on an administrator side to finalise the update? This caused quite a considerable amount of down time for the end users and was extremely difficult to figure out.
Our 3CX update (20.0.10.1785) also triggered a Debian OS update that included grub-pc. Because grub-pc.postinst spawned an interactive debconf frontend prompt asking which disk (/dev/nvme0n1) to install GRUB onto—and there was no interactive terminal attached to the background 3CX updater—dpkg and apt-get have been sitting frozen on that prompt, holding the package lock while 3cxpbx is half-upgraded.
This was quite frustrating, as the dependency on 3cx to manage these auto-updates, effectively failed half way, leaving the entire system inaccessible until we manually found the issue, got the grup-pc matter resolved and finalising the update.
My question is - is this a common issue, and why did the update trigger if it needed an interactive prompt on an administrator side to finalise the update? This caused quite a considerable amount of down time for the end users and was extremely difficult to figure out.