Hi, There is very little actionable in the bug report. We can’t see the ucf invocation, nor do we see any error messages that might point us to the root cause.
The last lines in the logs: --8<---------------cut here---------------start------------->8--- service bacula-director restart Job for bacula-director.service failed because the control process exited with error code. See "systemctl status bacula-director.service" and "journalctl -xe" for details. --8<---------------cut here---------------end--------------->8--- Point to bacula-director failing to start, which has probably little to do with ucf. The package install part of the logs seems to go wiothout an error. --8<---------------cut here---------------start------------->8--- apt-get -y install bacula bacula-director-pgsql Reading package lists... Building dependency tree... Reading state information... bacula is already the newest version (9.6.3-1). bacula-director-pgsql is already the newest version (9.6.3-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. --8<---------------cut here---------------end--------------->8--- Indeed, this does not seem ucf at all. Can you show me what I am missing? Manoj -- Numeric stability is probably not all that important when you're guessing. Manoj Srivastava <sriva...@acm.org> <http://www.golden-gryphon.com/> 4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20 05B6 CF48 9438 C577 9A1C
smime.p7s
Description: S/MIME cryptographic signature