nut 2.2.1-2.1ubuntu1 fails to install on Hardy Heron

Actually everything finally went fine after a reboot... Leaving this bug opened in case somebody else would encounter the same problem.

Marking as incomplete since the bug disappeared after a reboot.

Happened to me too. Haven't rebooted yet.

$ sudo apt-get upgrade nut
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up nut (2.2.1-2.1ubuntu1) ...
cp: cannot create special file `/dev/console': File exists
cp: cannot create special file `/dev/kmem': File exists
cp: cannot create special file `/dev/loop0': File exists
cp: cannot create special file `/dev/net/tun': File exists
cp: cannot create special file `/dev/null': File exists
cp: cannot create special file `/dev/ppp': File exists
invoke-rc.d: initscript udev, action "restart" failed.
dpkg: error processing nut (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 nut
E: Sub-process /usr/bin/dpkg returned an error code (1)

On Fri, Mar 21, 2008 at 01:58:08PM -0000, Dustin Kirkland wrote:
> Happened to me too. Haven't rebooted yet.
>
> invoke-rc.d: initscript udev, action "restart" failed.

Why is there a call to udev restart in the postinst ?

--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com

There isnt one, this was mismerge that got sponsored, not by me.

chuck

This bug was fixed in the package nut - 2.2.1-2.1ubuntu2

---------------
nut (2.2.1-2.1ubuntu2) hardy; urgency=low

  * Fix udev rules. (LP: #204612).
  * Cleaned up debian/control.

 -- Chuck Short <email address hidden> Fri, 21 Mar 2008 20:30:44 -0400

This is still occurring in 2.2.1-2.1ubuntu3:

root@tadow:/home/mfisch# apt-get install nut
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  nut-cgi nut-dev nut-snmp
The following NEW packages will be installed:
  nut
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/1203kB of archives.
After this operation, 2925kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously deselected package nut.
(Reading database ... 107695 files and directories currently installed.)
Unpacking nut (from .../nut_2.2.1-2.1ubuntu3_i386.deb) ...
Setting up nut (2.2.1-2.1ubuntu3) ...
cp: cannot create special file `/dev/kmem': File exists
cp: cannot create special file `/dev/loop0': File exists
cp: cannot create special file `/dev/net/tun': File exists
cp: cannot create special file `/dev/null': File exists
cp: cannot create special file `/dev/ppp': File exists
invoke-rc.d: initscript udev, action "restart" failed.
dpkg: error processing nut (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 nut
E: Sub-process /usr/bin/dpkg returned an error code (1)

This is still occurring in 2.2.1-2.1ubuntu3 or it broke again since the fix.

Another note, rebooting still resolves the issue, as long as you perform an apt-get purge before trying to install again (apt-get remove might work too, I didn't try it).

When I rebooted and tried to install again BEFORE I did the purge, I got this:

mfisch@tadow:~$ sudo apt-get install nut
Reading package lists... Done
Building dependency tree
Reading state information... Done
nut is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Setting up nut (2.2.1-2.1ubuntu3) ...
chown: cannot access `/var/run/nut': No such file or directory
dpkg: error processing nut (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 nut
E: Sub-process /usr/bin/dpkg returned an error code (1)

I am not able to reproduce this at all.

chuck

I cleared my apt cache purged out the old install of nut and reinstalled. I cannot reproduce this either. If this happens to you, a reboot and/or running apt-get clean seems to fix it.

closing

Re-opening as I still hit this. I performed:
apt-get remove --purge nut
apt-get clean
apt-get install nut

and get:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  mcpp libgtkhtml2.0-cil
Use 'apt-get autoremove' to remove them.
Suggested packages:
  nut-cgi nut-dev nut-snmp
The following NEW packages will be installed:
  nut
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 1405kB of archives.
After this operation, 3564kB of additional disk space will be used.
Get:1 http://127.0.0.1 hardy/main nut 2.2.1-2.1ubuntu3 [1405kB]
Fetched 1405kB in 0s (15.4MB/s)
Preconfiguring packages ...
Selecting previously deselected package nut.
(Reading database ... 179459 files and directories currently installed.)
Unpacking nut (from .../nut_2.2.1-2.1ubuntu3_amd64.deb) ...
Setting up nut (2.2.1-2.1ubuntu3) ...
cp: cannot create special file `/dev/kmem': File exists
cp: cannot create special file `/dev/loop0': File exists
cp: cannot create special file `/dev/net/tun': File exists
cp: cannot create special file `/dev/null': File exists
cp: cannot create special file `/dev/ppp': File exists
invoke-rc.d: initscript udev, action "restart" failed.
dpkg: error processing nut (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 nut
E: Sub-process /usr/bin/dpkg returned an error code (1)

I should also mention this is amd64

Mine is on x86 or i386, whatever it's called. If you plan on helping to diagnose this, don't reboot, it seems to clear up the issue.

2008/3/21, Chuck Short <email address hidden>:
> There isnt one, this was mismerge that got sponsored, not by me.

there is one !
(2 in fact ; nut.postinst and nut-hal-drivers.postinst), and this is
not due to a mismerge.
these calls are there to refresh udev rules after the nut one installation.
the aim is to avoid a reboot, and have the system ready for USB UPS
plugging as of the soft install. So simply reloading rules isn't
sufficient enough, since that would require {un,re}plugging the device

I've quickly checked and a call to "udevtrigger
--subsystem-match=usb_device" seems to be sufficient, and should solve
the various issue calling "udev restart"

I don't have much time to try this, since I'm preparing the 2.2.2
release, and some other important stuffs... So test the above and feel
free to call me directly (ie To:) for details and questions since the
mail will be more visible in my (always overloaded) mail stack ;-)

-- Arnaud

We'll ask for a FFE once this gets into debian and appers on merge-o-matic.

chuck

This bug was fixed in the package nut - 2.2.1-2.1ubuntu4~ppa1

---------------
nut (2.2.1-2.1ubuntu4~ppa1) hardy; urgency=low

  * Use udevtrigger to restart udev. (LP: #204612)

 -- Chuck Short <email address hidden> Wed, 26 Mar 2008 13:30:24 -0400

Need testing done.

This bug was fixed in the package nut - 2.2.1-2.1ubuntu4

---------------
nut (2.2.1-2.1ubuntu4) hardy; urgency=low

  * Use udevtrigger to restart udev. (LP: #204612)

 -- Chuck Short <email address hidden> Wed, 26 Mar 2008 13:30:24 -0400

This one worked for me.

:-Dustin

Upgrade from 2.2.1-2.1ubuntu3 to 2.2.1-2.1ubuntu4 worked fine here.