It just failed for me on hardy while updating samba, resulting in smbd
not being running this morning:
Subject: Cron r...@fen-apps apt-get -qq update apt-get -qq upgrade
apt-get clean
(Reading database ... 79236 files and directories currently installed.)
Preparing to replace smbclient
It just failed for me on hardy while updating samba, resulting in smbd
not being running this morning:
Subject: Cron r...@fen-apps apt-get -qq update apt-get -qq upgrade
apt-get clean
(Reading database ... 79236 files and directories currently installed.)
Preparing to replace smbclient
here ist the output from the email (had two more since from hourly run
cron job, so by far not the same every run):
/etc/cron.hourly/apt-security-updates:
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to
here ist the output from the email (had two more since from hourly run
cron job, so by far not the same every run):
/etc/cron.hourly/apt-security-updates:
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to
This morning cron mailed me again about this debconf error about not
beeing able to set frontend, TERM not set, etc.
Unfortunatelly I've deleted the mail already. The orcward thing is
aptitude runs fine acording to my logs and installes packages from
hardy-security just fine. Last time was Jul 10
This morning cron mailed me again about this debconf error about not
beeing able to set frontend, TERM not set, etc.
Unfortunatelly I've deleted the mail already. The orcward thing is
aptitude runs fine acording to my logs and installes packages from
hardy-security just fine. Last time was Jul 10
This was never a bug in samba, but in update-inetd; and the current
version of the update-inetd package is debconf-aware, so doesn't happen
with the current version. Marking as fixed.
** Changed in: update-inetd (Ubuntu)
Sourcepackagename: samba = update-inetd
Status: Confirmed = Fix
you're right Sam Morris, thing is update-inetd does not check the
variable DEBCONF_FRONTEND, but checks DEBIAN_FRONTEND if it is set
to noninteractive ... so this is no bug of samba directly (i encountered
this one when installing postfix via onetime bootscript), but it is a
problem w.
One for the server team.
** Changed in: samba (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Server Team
Status: New = Confirmed
--
Fails to upgrade non-interactively
https://bugs.launchpad.net/bugs/53049
You received this bug notification because you are a
Check update-inetd line 29. I think that if it fails to open /dev/tty
then it should fall back to /dev/null (which is used in the first place
if DEBCONF_FRONTEND=noninteractive).
--
Fails to upgrade non-interactively
https://launchpad.net/bugs/53049
--
ubuntu-bugs mailing list
** Changed in: samba (Ubuntu)
Status: Needs Info = Unconfirmed
--
Fails to upgrade non-interactively
https://launchpad.net/bugs/53049
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Isn't the error the failure of update-inetd?
Anyway, the command in /etc/crontab is: apt-get -qq --yes dist-upgrade
--
Fails to upgrade non-interactively
https://launchpad.net/bugs/53049
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The issue is the line that says Starting Samba ... that needed to be
output to the terminal. Shall we mark this bug as a wishlist item that
says the that the output should/could be suppressed when run non-
interactively?
What was the command you were running from Cron, in any case?
Thank you.
13 matches
Mail list logo
