Cannot install at_3.1.10ubuntu4_amd64.deb

[Joe User]

Binary package hint: at

In Feisty, and now in Gutsy, on an amd64 system, I could not install at_3.1.10ubuntu4_amd64.deb.

It shows errors in adept, like:

(Reading database ... 283835 files and directories currently installed.)
Unpacking at (from .../at/at_3.1.10ubuntu4_amd64.deb) ...
Setting up at (3.1.10ubuntu4) ...
 * Starting deferred execution scheduler atd invoke-rc.d: initscript atd, action "start" failed.
dpkg: error processing at (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 at

[ais523 (ais523)]

Here's the error:

case "$1" in
    start)
        log_daemon_msg "Starting deferred execution scheduler" "atd"
        start_daemon $DAEMON
        log_end_msg $?
    ;;

There is no command start_daemon.

I'm not sure how to fix this, but it looks likely to be a trivial fix.

[Joe User (axyz-yahoo)]

Thank you.

When I get home this evening, I will try editing a forced installation of at, file /etc/init.d/at or whatever that file is.

--- On Wed, 11/12/08, ais523 <email address hidden> wrote:

> From: ais523 <email address hidden>
> Subject: [Bug 158178] Re: Cannot install at_3.1.10ubuntu4_amd64.deb
> To: <email address hidden>
> Date: Wednesday, November 12, 2008, 10:10 AM
> Here's the error:
>
> case "$1" in
> start)
> log_daemon_msg "Starting deferred execution
> scheduler" "atd"
> start_daemon $DAEMON
> log_end_msg $?
> ;;
>
> There is no command start_daemon.
>
> I'm not sure how to fix this, but it looks likely to be
> a trivial fix.
>
> --
> Cannot install at_3.1.10ubuntu4_amd64.deb
> https://bugs.launchpad.net/bugs/158178
> You received this bug notification because you are a direct
> subscriber
> of the bug.

[Ben Bucksch (benbucksch)]

I had the same problem when upgrading from 8.04 to 8.10
(via changing sources.list and apt-get update && apt-get dist-upgrade).

The problem is diagnosed nicely on http://ubuntuforums.org/showthread.php?t=366806 .

Basically:
"/etc/init.d/atd start" works, but "invoke-rc.d atd" start does not

(as root:)
# /etc/init.d/atd stop
 * Stopping deferred execution scheduler atd [ OK ]
# /etc/init.d/atd start
 * Starting deferred execution scheduler atd
# /etc/init.d/atd stop
 * Stopping deferred execution scheduler atd [ OK ]
# invoke-rc.d atd start
 * Starting deferred execution scheduler atd invoke-rc.d: initscript atd, action "start" failed.

I consider this critical, as it prevents a proper update of the distro.

[Ben Bucksch (benbucksch)]

Workaround:
1. Delete last line from /var/lib/dpkg/info/at.postinst
2. apt-get -f install

[Ben Bucksch (benbucksch)]

Please note that the start comment does not give an "[OK]". (This is not a paste error.) cron start does give an [OK]. Maybe that's why invoke-rc.d fails?

[xteejx (xteejx-deactivatedaccount)]

As far as supported versions go, 3.1.10ubuntu4 is in hardy, and that is the earliest supported version of Ubuntu, therefore this problem would not arise as it would be a default install. If this problem continues please change the status back to 'New' and we can look into helping you to upgrade. Thank you.

[ais523 (ais523)]

This error continues even with later versions of at, on every upgrade (not just installation); I've just verified it with 3.1.10.2ubuntu2, and an x86 version (on jaunty-proposed):

Setting up at (3.1.10.2ubuntu2) ...
 * Starting deferred execution scheduler atd invoke-rc.d: initscript atd, action "start" failed.
dpkg: error processing at (--configure):
 subprocess post-installation script returned error exit status 1

However, the bug I've seen here might be bug #281672 rather than this one; it's even possible that the two are the same bug. I'm re-opening this per instructions; but it may be worth marking this bug as a duplicate of #281672 if they are indeed the same bug (it's similar symptoms and similar triggers, although of course that doesn't mean they're the same).

[xteejx (xteejx-deactivatedaccount)]

I believe you are right that this has already been reported and is a duplicate of bug 286172, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.