Can't install OMV after apt full-upgrade

ExpectedProton · 11. September 2021

I did a apt full-upgrade, which yes I know is not recommended. After doing that command I noticed it said it was removing the openmediavault package, and sure enough, after it was done, openmediavault was gone. When I tried to reinstall it, I get this message:

Code

Reading package lists... Done
Building dependency tree       
Reading state information... Done
openmediavault-keyring is already the newest version (1.0).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 openmediavault : Depends: watchdog but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Alles anzeigen

I looked into downgrading again, and it seems like it can end up being even more unstable than the original full-upgrade.

I also noticed there's an alpha version for OMV version 6, would that work on my version of Debian?

KM0201 · 12. September 2021

Zitat von ExpectedProton
I did a apt full-upgrade, which yes I know is not recommended. After doing that command I noticed it said it was removing the openmediavault package, and sure enough, after it was done, openmediavault was gone. When I tried to reinstall it, I get this message:
Code
Reading package lists... Done
Building dependency tree       
Reading state information... Done
openmediavault-keyring is already the newest version (1.0).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 openmediavault : Depends: watchdog but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Alles anzeigen
I looked into downgrading again, and it seems like it can end up being even more unstable than the original full-upgrade.

I also noticed there's an alpha version for OMV version 6, would that work on my version of Debian?

LOL. Did you know it wasn't recommended before you did this? It's hard to have much sympathy when it told you right there what it was doing.

What is the output of

Code

cat /etc/debian_version

Assuming you are on Debian 11... you can reinstall with the install script.

ExpectedProton · 13. September 2021

Zitat von KM0201
LOL. Did you know it wasn't recommended before you did this? It's hard to have much sympathy when it told you right there what it was doing.

What is the output of
Code
cat /etc/debian_version
Assuming you are on Debian 11... you can reinstall with the install script.

Yes, I did know. I was actually trying to install Proxmox, which I installed, then decided to uninstall after realising I would need a seperate disk. I probably should've read up about that. I was also fully aware that it could easily break my install, I took the risk for some reason and I regret everything.

Running cat /etc/debian_version gives me 10.10.

I'm very confused now, did I downgrade somehow? I swear I was on Debian 11 before...

ExpectedProton · 13. September 2021

Ok so I managed to upgrade to Debian 11 following this article, and now cat /etc/debian_version gives me 11.0. Now I have many dependancy issues:

https://pastebin.com/wbmFFgN0

I tried out sudo apt --fix-broken install, but it didn't help

https://pastebin.com/sd0Ce34s

I also got this message halfway through sudo apt --fix-broken install.

Code

 ┌──────────────────────────────────────────┤ Configuring libpam-modules ├───────────────────────────────────────────┐
 │                                                                                                                   │
 │ you are using pam_tally or pam_tally2 in your configuration                                                       │
 │                                                                                                                   │
 │ The pam_tally and pam_tally2 modules have been removed from PAM. You are using one of these modules in your PAM   │
 │ configuration in /etc/pam.d. You must remove the uses of these modules before PAM can be upgraded; including      │
 │ these modules in your PAM configuration after the upgrade will stop users from being able to log into the         │
 │ system.                                                                                                           │
 │                                                                                                                   │
 │ Consider the pam_faillock module as a replacement for pam_tally.                                                  │
 │                                                                                                                   │
 │                                                      <Ok>                                                         │
 │                                                                                                                   │
 └───────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

Alles anzeigen

KM0201 · 13. September 2021

You can reinstall using the OMV install script, same as you would over any Debian install (since you're on Debian 11, it's going to install OMV 6)... but it sounds like you've got bigger issues there.

ViniS · 31. Dezember 2021

Hello,

I had the same issue today. In the message, they are telling you to replace pam_tally and pam_tally2 by pam_faillock. We “just” have to look through the configuration files in /etc/pam.d and show if we are using pam_tally*:

Bash

root@omv:~# cd /etc/pam.d
root@omv:/etc/pam.d# ls
chfn                           cron.dpkg-new               proftpd
chpasswd                       login                       runuser
chsh                           monit                       runuser-l
common-account                 newusers                    samba
common-auth                    openmediavault              sshd
common-password                openmediavault-common-auth  su
common-session                 openmediavault-webgui       su-l
common-session-noninteractive  other                       sudo
cron                           passwd                      systemd-user
root@omv:/etc/pam.d# cat * | grep pam_tally*
account     required        pam_tally2.so
auth        required        pam_tally2.so onerr=fail audit deny=3 unlock_time=180
account     required        pam_tally2.so

Alles anzeigen

The last command above will only show the line containing pam_tally or pam_tally2 (most probably pam_tally2). We now know how many lines to replace. Here, I've been lazy, because I suspected that those lines were in the openmediavault related files (I checked using cat openmediavault* | grep pam_faillock) and it was the case. Then you just have to use nano or other on the openmediavault files and to replace each instance of pam_tally2.so by pam_faillock.so.

After that, you can rerun sudo apt --fix-broken install (it should not fail). Then you rerun sudo apt full-upgrade.

I hope it can help…

Happy new year.

proto_typ · 11. Mai 2022

Zitat von ViniS

The last command above will only show the line containing pam_tally or pam_tally2 (most probably pam_tally2). We now know how many lines to replace. Here, I've been lazy, because I suspected that those lines were in the openmediavault related files (I checked using cat openmediavault* | grep pam_faillock) and it was the case. Then you just have to use nano or other on the openmediavault files and to replace each instance of pam_tally2.so by pam_faillock.so.

After that, you can rerun sudo apt --fix-broken install (it should not fail). Then you rerun sudo apt full-upgrade.

I hope it can help…

Happy new year.

Alles anzeigen

This was one last key information after upgrading from OMV 5.x to 6.x. Something went wrong in the process of upgrading and I couldn't log into the webGUI due to the "Pam"-issue. Thanks!

rickyx · 7. Juni 2022

Zitat von ViniS

Then you just have to use nano or other on the openmediavault files and to replace each instance of pam_tally2.so by pam_faillock.so.

I had the same problem and it worked!

In detail, to find out the guilty files I did:

find . -type f -print | xargs grep "tally"

...I had to edit 3 files:

./openmediavault:account required pam_tally2.so

./openmediavault-webgui:account required pam_tally2.so

./openmediavault-common-auth:auth required pam_tally2.so onerr=fail audit deny=3 unlock_time=180

Thank you

Riccardo

ps. I just when you want to upgrade ex. from omv 5 to 6 you better repeat omv-release-upgrade instead of apt full-upgrade

DarthVegan1969 · 30. November 2022

For the record, after cd'ing to /etc/pam.d, you can do a global search and replace for it in all files in the current working directory..

Code

sed -i 's|pam_tally2.so|pam_faillock.so|g' *

Can't install OMV after apt full-upgrade

Jetzt mitmachen!

Tags