Package: nbd-client Version: 1:2.9.21-1 Severity: normal Hi,
during upgrade of nbd-client I got the following output: mrvn@frosties:~% sudo apt-get install nbd-client Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: nbd-client 1 upgraded, 0 newly installed, 0 to remove and 941 not upgraded. Need to get 54.8kB of archives. After this operation, 4096B of additional disk space will be used. Get:1 http://chocos/debian/ sid/main nbd-client amd64 1:2.9.21-1 [54.8kB] Fetched 54.8kB in 0s (1496kB/s) debconf: delaying package configuration, since apt-utils is not installed (Reading database ... 164302 files and directories currently installed.) Preparing to replace nbd-client 1:2.9.16-4 (using .../nbd-client_1%3a2.9.21-1_amd64.deb) ... Unpacking replacement nbd-client ... Processing triggers for man-db ... Setting up nbd-client (1:2.9.21-1) ... Installing new version of config file /etc/init.d/nbd-client ... /var/lib/dpkg/info/nbd-client.config: line 75: [: argument expected Stopping NBD client process: Disconnecting /dev/nbd0 ERROR: Module nbd does not exist in /proc/modules nbd-client. Starting NBD client process: Connecting...Error: Socket failed: Connection refused Exiting. connected /dev/nbd0 Activating... /dev/nbd0: raw selected. doing nothing. nbd-client. update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... /boot/initrd.img-2.6.18-4-amd64 does not exist. Cannot update. 1) I have NBD builtin so there is no nbd module to load and none needed. Maybe this could be detected and avoid the error message. 2) The nbd-server isn't currently running so the failure to connect is expected. But then why does it later say "connected /dev/nbd0" and tries to activate the device? MfG Goswin -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (666, 'unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-rc7-xen-1 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages nbd-client depends on: ii debconf [debconf-2.0] 1.5.35 Debian configuration management sy ii libc6 2.13-4 Embedded GNU C Library: Shared lib nbd-client recommends no packages. nbd-client suggests no packages. -- debconf information: * nbd-client/device: /dev/nbd0 * nbd-client/host: localhost nbd-client/no-auto-config: nbd-client/extra: * nbd-client/killall: false * nbd-client/port: 2000 * nbd-client/type: raw * nbd-client/number: 1
# If you don't want to reconfigure this package after installing, uncomment # the following line: #AUTO_GEN="n" # If you don't want the init script to kill nbd-client devices that aren't # specified in this configuration file, set the following to "false": KILLALL="false" # Note that any statical settings in this file will be preserved # regardless of the setting of AUTO_GEN, so its use is only recommended # if you set things in a dynamical way (e.g., through a database) # # Name of the first used nbd /dev-entry: NBD_DEVICE[0]="/dev/nbd0" # # Type; s=swap, f=filesystem (with entry in /etc/fstab), r=raw (no other setup # than to run the client) NBD_TYPE[0]="r" # # The host on which the nbd-server process is running NBD_HOST[0]="localhost" # # The port on which this client needs to connect NBD_PORT[0]="2000" # # The second networked block device could look like: # NBD_DEVICE[1]=/dev/nbd1 # NBD_TYPE[1]="f" # NBD_HOST[1]="localhost" # NBD_PORT[1]="1235" # # You can add as many as you want, but don't skip any number in the variable # names, or the initscript will fail. NBD_EXTRA[0]=""
