apt-get upgrade error [solved]

[soydepr]

Do you want to continue? [Y/n] Y
Setting up libpam-chksshpwd:armhf (1.1.8-3.1+deb8u2+rpi2) ...
mkdir: cannot create directory ‘/var/lib/chksshpwd/’: File exists
dpkg: error processing package libpam-chksshpwd:armhf (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
libpam-chksshpwd:armhf
E: Sub-process /usr/bin/dpkg returned an error code (1

[romney_yw]

I get exactly the same error, although I'm using apt rather than apt-get.

In my case, the directory /var/lib/chksshpwd (on two separate installations) was created on Feb 15, presumably by a previous upgrade. I found that this directory was empty, so I removed it and then tried the upgrade again. Success! And the /var/lib/chksshpwd directory was recreated with today's date.

This would appear to be an easy work-around for the problem, which I hope will be fixed soon. I assume the mkdir command should really have a -p option, so that it doesn't complain when the directory has been created previously?

Hope this helps.....

[pngwen]

I can confirm that I had the same problem, and deleting the /var/lib/chksshpwd directory fixed the issue. It looks like there must be some sort of a bug in the dpkg script for libpam-chksshpwd:armhf.

[twop0intfive]

I too can confirm that I had the same issue described above and that following the suggestion to delete that directory corrected it for me. I'm glad I wasn't the only one!

[pumpkinpi]

Same here. Fixed with:

Code: Select all

cd /var/lib
sudo rm -R chksshpwd

PPi

[romney_yw]

Perhaps safer to use

Code: Select all

sudo rmdir /var/lib/chksshpwd

which will only delete the directory if it's empty.

If it's NOT empty, you should maybe find another solution for the problem, until the issue is resolved properly.

They've sold more than 12.5 million Pis. While many don't use Rasbian and I think quite a lot of users do not upgrade the software routinely, there should be more than just a handful of us who have encountered this issue. Mine is just an average sort of Pi - for the time being.

It is also possible that the problem is inherited from Debian or elsewhere in the wider Linux world. As a relative newcomer, I don't know whether the problem should be reported, and if so to whom?

Or should we just wait to see if "they" notice and hope it is fixed at the next update?

[soydepr]

Thanks all. Solution worked like a diamond ring. Issue solved this can be closed

[wayne.dolesman]

The package should still be updated to prevent others from having the same issue. Not sure who the package maintainers are.

[romney_yw]

Agreed. "They" are already aware of the problem....

See discussion here for more information: viewtopic.php?p=1137945#p1137945

(Thanks Simon . )

[rpdom]

It is also possible that the problem is inherited from Debian or elsewhere in the wider Linux world. As a relative newcomer, I don't know whether the problem should be reported, and if so to whom?

It is not a Debian issue. That package is one that is produced by the Raspberry Pi Foundation/Raspberry Pi Trading Ltd. They are aware of the issue and a fixed version will be released very soon now. I think I read somewhere that the directory that causes this error isn't used in the current version of the package and was supposed to be removed.

[jadro]

Thanx,

Same problem, this solution works for me too.

Jadro

[anderhoff]

Been searching on and off for the last two days. Nice to finally see a solution for this problem. An older related posting mentioned needing a larger capacity SD or simply starting fresh with a new SD card. In my case, it was a fresh image download and a brand new SanDisk 32GB SD card. Was it already bad or broken? Nope - those were not the problems.

Now I need to figure out how to use this new external Seagate 4TB HDD with NTFS.. err, nevermind.. maxium supported HDD is 2TB?!? or maybe it needs 64-bit kernel and/or more ram - IDK??

[davidcoton]

Issue solved this can be closed

You do that yourself by editing your first post in the thread and adding "[Solved]" to the title.