USER PID ACCESS COMMAND
/var/cache/debconf/config.dat: root 13393 F.... (root)frontend
I killed process and update/ upgrade finished without error.
Thanks, we can call this a fix.
The only way to make sure people you agree with can speak is to support the rights of people you don't agree with.
-Eleanor Holmes Norton, US Congressional Delegate
On 11-05-18 10:04 AM, Clint Byrum wrote:
> Excerpts from Ron's message of Tue May 17 00:18:20 UTC 2011:
>> Did as suggested with the following result:
>>
>>
>> The following packages will be upgraded:
>> postfix
>> 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>> 29 not fully installed or removed.
>> Need to get 0 B/1,165 kB of archives.
>> After this operation, 0 B of additional disk space will be used.
>> Do you want to continue [Y/n]? Y
>> debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
>> another process: Resource temporarily unavailable
>> (Reading database ... 181555 files and directories currently installed.)
>> Preparing to replace postfix 2.8.2-1ubuntu1 (using
>> .../postfix_2.8.2-1ubuntu2.1_i386.deb) ...
>> debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
>> another process: Resource temporarily unavailable
>> dpkg: error processing
>> /var/cache/apt/archives/postfix_2.8.2-1ubuntu2.1_i386.deb (--unpack):
>> subprocess new pre-installation script returned error exit status 1
>> Errors were encountered while processing:
>> /var/cache/apt/archives/postfix_2.8.2-1ubuntu2.1_i386.deb
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>
>>
>> Can't seem to get past this error. It's been a couple of weeks.. Almost
>> makes one think of what MS windows 7 is like. ( almost but never)
> Ron, I understand the frustration. Its entirely possible there is
> another process holding this file open that shouldn't be, which would
> be a bug. Can you open a Terminal and add the output of this command to
> the bug report:
>
> sudo fuser -vu /var/cache/debconf/config.dat
>
> It should show the process which has config.dat locked. If you determine
> that its ok to kill that process, you can run:
>
> sudo kill #####
>
> Where ##### is the process ID shown in the output of fuser.
>
I ran command as suggested, with a process as :
/var/cache/
I killed process and update/ upgrade finished without error.
Thanks, we can call this a fix.
The only way to make sure people you agree with can speak is to support the rights of people you don't agree with.
-Eleanor Holmes Norton, US Congressional Delegate
On 11-05-18 10:04 AM, Clint Byrum wrote: debconf/ config. dat is locked by 2.8.2-1ubuntu2. 1_i386. deb) ... debconf/ config. dat is locked by apt/archives/ postfix_ 2.8.2-1ubuntu2. 1_i386. deb (--unpack): apt/archives/ postfix_ 2.8.2-1ubuntu2. 1_i386. deb debconf/ config. dat
> Excerpts from Ron's message of Tue May 17 00:18:20 UTC 2011:
>> Did as suggested with the following result:
>>
>>
>> The following packages will be upgraded:
>> postfix
>> 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>> 29 not fully installed or removed.
>> Need to get 0 B/1,165 kB of archives.
>> After this operation, 0 B of additional disk space will be used.
>> Do you want to continue [Y/n]? Y
>> debconf: DbDriver "config": /var/cache/
>> another process: Resource temporarily unavailable
>> (Reading database ... 181555 files and directories currently installed.)
>> Preparing to replace postfix 2.8.2-1ubuntu1 (using
>> .../postfix_
>> debconf: DbDriver "config": /var/cache/
>> another process: Resource temporarily unavailable
>> dpkg: error processing
>> /var/cache/
>> subprocess new pre-installation script returned error exit status 1
>> Errors were encountered while processing:
>> /var/cache/
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>
>>
>> Can't seem to get past this error. It's been a couple of weeks.. Almost
>> makes one think of what MS windows 7 is like. ( almost but never)
> Ron, I understand the frustration. Its entirely possible there is
> another process holding this file open that shouldn't be, which would
> be a bug. Can you open a Terminal and add the output of this command to
> the bug report:
>
> sudo fuser -vu /var/cache/
>
> It should show the process which has config.dat locked. If you determine
> that its ok to kill that process, you can run:
>
> sudo kill #####
>
> Where ##### is the process ID shown in the output of fuser.
>