Upgrade to Stone Burner gives error

markus-fried@gmx.de · 11. März 2016

Hi,

I tried the Stone Burner upgrade using omv-release-upgrade and got the following error.

All seems to work well, but I'm a bit nervous about this result - what should I do?

Regards

Mark.

Code

Installing new version of config file /etc/udev/rules.d/99-openmediavault-scheduler.rules ...
Updating configuration ...
Reloading nginx configuration: nginx.
chown: invalid user: `nadja'
run-parts: /usr/share/openmediavault/mkconf/ssh.d/20authorized_keys exited with return code 1
dpkg: error processing openmediavault (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of openmediavault-nut:
 openmediavault-nut depends on openmediavault (>= 2.0.11); however:
  Package openmediavault is not configured yet.


dpkg: error processing openmediavault-nut (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 openmediavault
 openmediavault-nut
Creating index of upgradeable packages ...
Creating index of openmediavault plugins ...
E: Sub-process /usr/bin/dpkg returned an error code (1)

Alles anzeigen

subzero79 · 12. März 2016

You have a user nadja that you probably deleted in cli buy you did not delete it using the omv interface.
The user won't display (not sure) at omv panel, but is inside the config.xml.
Check with omv-showkey users

markus-fried@gmx.de · 12. März 2016

ok, this user is not shown using the GUI, but it is listed when using omv -showkey users

How can I get rid of it and how to procede afterwards?

Thanx for your help

Mark.

subzero79 · 12. März 2016

You have to edit this file manually

/etc/openmediavault/config.xml

And delete the nadja user entry. Make a backup first of the file, wrong tag and the whole webinteface goes down

markus-fried@gmx.de · 12. März 2016

ok, but how do I trigger the rest of the upgrade process, that got interrupted??

subzero79 · 12. März 2016

Try apt-get -f install

Also be careful with omv-release-upgrade if you execute this command being in 2.x version you'll end up in 3.0

So check first that the package hasn't upgraded yet.

dpkg -l | grep openmediavault

Check that is 1.19 still, then run omv-release-upgrade

markus-fried@gmx.de · 12. März 2016

OMV was already 2.2.1

apt-get -f install ran through without errors, so I guess all is well now

Thanks a lot for your help!!

Jetzt mitmachen!