OMV 5.0 - finally out! :-)

Perfect

Checking if everything is ok i found my filesystems tab full of 'zram'. Those were not there before. Should i worry?

And, the last two commands, unistalled docker. How can i install it again?

Just from the drop down menu?

EDIT: Yes installed. Also containerd was deleted with those commands. Strange. Hope those commands have not deleted something very important

Zitat von steakhutzeee

And, the last two commands, unistalled docker. How can i install it again?

Just from the drop down menu?

EDIT: Yes installed. Also containerd was deleted with those commands. Strange. Hope those commands have not deleted something very important

For important things you should have backups.

Is the Network Discovery (zeroconf?) option gone for Services in OMV5? In OMV4 there used to be toggle options I think at System -> Network -> Services(?) but that tab no longer exists.

Zitat von ryecoaaron

The commands will tell you exactly what it was going to install and then prompt you if you want to uninstall them. Did you read it?

Yes, were all packets related to Stretch (don't remember the exact name). Anyway I have reinstalled docker and performed an apt-get update and an update-dist and found nothing to install so I suppose I have all the packets I need right?

Any idea on the zram present into the file system tab?

Updating from 4 to 5, error in openmediavault.postinst in line

mv-salt deploy run collectd chrony postfix

Some network property ("mtu") ?

+ omv-salt deploy run collectd chrony postfix
omv-nas.local:
Data failed to compile:
----------
Rendering SLS 'base:omv.deploy.collectd.plugins.interface' failed: Jinja error: Failed to convert property 'mtu': invalid literal for int() with base 10: ''
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/openmediavault/config/datamodel.py", line 290, in property_convert
result = int(value)
ValueError: invalid literal for int() with base 10: ''


During handling of the above exception, another exception occurred:


Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/salt/utils/templates.py", line 394, in render_jinja_tmpl
output = template.render(**decoded_context)
File "/usr/lib/python3/dist-packages/jinja2/asyncsupport.py", line 76, in render
return original_render(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1008, in render
return self.environment.handle_exception(exc_info, True)
File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 780, in handle_exception
reraise(exc_type, exc_value, tb)
File "/usr/lib/python3/dist-packages/jinja2/_compat.py", line 37, in reraise
raise value.with_traceback(tb)
File "<template>", line 21, in top-level template code
File "/var/cache/salt/minion/extmods/modules/omv_conf.py", line 82, in get_by_filter
objs = db.get_by_filter(id_, openmediavault.config.DatabaseFilter(filter_), **kwargs)
File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 125, in get_by_filter
query.execute()
File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 683, in execute
self._response = self._elements_to_object(elements)
File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 467, in _elements_to_object
obj.set_dict(self._element_to_dict(element), False)
File "/usr/lib/python3/dist-packages/openmediavault/config/object.py", line 207, in set_dict
self.set(key, value, validate)
File "/usr/lib/python3/dist-packages/openmediavault/config/object.py", line 185, in set
value = self.model.property_convert(name, value)
File "/usr/lib/python3/dist-packages/openmediavault/config/datamodel.py", line 300, in property_convert
name, str(e)))
ValueError: Failed to convert property 'mtu': invalid literal for int() with base 10: ''


; line 21


---
[...]
#
# You should have received a copy of the GNU General Public License
# along with OpenMediaVault. If not, see <http://www.gnu.org/licenses/>.


{% set interfaces = [] %}
{% for interface in salt['omv_conf.get_by_filter'](    <======================
'conf.system.network.interface',
{'operator': 'or', 'arg0': {'operator': 'stringEquals', 'arg0': 'type', 'arg1': 'ethernet'}, 'arg1': {'operator': 'stringEquals', 'arg0': 'type', 'arg1': 'wireless'}}) %}
{% set used_by = salt['omv_conf.get_by_filter'](
'conf.system.network.interface',
{'operator': 'stringContains', 'arg0': 'slaves', 'arg1': interface.devicename}) %}
[...]
---
dpkg: error processing package openmediavault (--configure):
installed openmediavault package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
openmediavault

Removing collectd from that line let me continue and finish upgrading. I can't tell any ill effects, and collectd is just perf monitoring?

Well

I was curious so I did the uprade from the post 38 everything was more or less ok until reboot my root password was not working any longer, so I was not able to perform

apt-get purge openmediavault-omvextrasorg resolvconf
wget -O - https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install | bash
apt-get update
apt-get dist-upgrade

omv-salt deploy run nginx

omv-salt deploy run phpfpm

So I went to the GUI I was able to login I got the yellow prompt asking me to save the new config I did it, since that I am not able to access the GUI page: got "502 bad request"

But beside this on a big positive point: my emby is working even with the data on an outside drive and apparently I can even get it from outside thru my letsencrypt config

So how to fix the login from CMD and from the GUI?

I know I have to do

[tt]omv-salt deploy run nginx

[tt]omv-salt deploy run phpfpm

But I need to get back my root PW !

EDIT

I was lucky I had a user with ssh access previously configured so I am doing this Default SSH password "openmediavault" not work (OMV_3_0_88_RaspberryPi_2_3_4.9.41.img)

So know I am kind of happy since the upgrade was very easy,

but I am getting also frustrated since with my config portainer does not deploy, I am getting exactly the same problem I got with a previous new install "Something went wrong trying to pull and start portainer ..." and this is because my dockers are on an external drive

the field Docker storage got: /var/lib/docker witch is a symlink aiming to my Docker folder on an external drive

I tried to change the field with /srv/dev-disk-by-label-WD_10TB_1/docker/docker but same issue apparently cannot get portainer working if Docker storage is not blank

So what is the solution because noway I do not want to rebuild my dockers specially since there are working?

not sure if it has something to do with the kernel I use?

And finally some progress I installed it manually

docker pull portainer/portainer
docker volume create portainer_data
docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer

Update

This did not survive a reboot.

I had to enter again

docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer

but now I got 3 portainers images one is stopped!

Zitat von Nefertiti

Update

This did not survive a reboot.

I had to enter again

Code

docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer

but now I got 3 portainers images one is stopped!

If you read the documentation on the Portainer site is stated that the configuration for portainer is stored inside the container. If you want to store it outside and let the configuration to survive a reboot, you have to use a real directory instead of "portainer_data".

For example "path/to/config/on/your/drive:/data

Hello hello I have to questions or maybe rather remarks:

1) wouldn't it be better to have that are dedicated Tutorial for the upgrade instead of hiding it inside a long thread?

2) it may be needed to run

omv-confdbadm migrate conf 5.0.0omv-confdbadm migrate conf 5.0.0

after the installation for me and and another user without this the Webinterface did not work.

Greetings Hendrik

Zitat von steakhutzeee

If you read the documentation on the Portainer site is stated that the configuration for portainer is stored inside the container. If you want to store it outside and let the configuration to survive a reboot, you have to use a real directory instead of "portainer_data".

For example "path/to/config/on/your/drive:/data

Got an issue

The container name "/portainer" is already in use by container "3e31f81d232cadadd94d90dd5e00a656dd7f1fffabafae48126f3ca0fa1697a4". You have to remove (or rename) that container to be able to reuse that name.

when I am using

docker run -d -p 9000:9000 -p 8000:8000 --name portainer --restart always -v /var/run/docker.sock:/var/run/docker.sock -v /path/on/host/data:/data portainer/portainer

I am changing the/ path/on/host/data: with my own.

Well as the error says clearly, if you have multiple portainer containers created with the wrong path to /data, just remove them and then create the container with the correct path to /data.

Anyway I suggest to use docker-compose instead.

I just upgraded from 4 to 5 with no major issues. This what I used.

apt-get purge openmediavault-cups openmediavault-dnsmasq openmediavault-docker-gui \
    openmediavault-domoticz openmediavault-duplicati openmediavault-eyefi openmediavault-ldap \
    openmediavault-letsencrypt openmediavault-mysql openmediavault-nginx openmediavault-openvpn \
    openmediavault-pxe openmediavault-remotedesktop openmediavault-route openmediavault-shellinabox \
    openmediavault-syncthing openmediavault-transmissionbt openmediavault-urbackup-server \
    openmediavault-vdo openmediavault-virtualbox openmediavault-webdav
sed -i "s/stretch/buster/g" /etc/apt/sources.list
sed -i "s/stretch/buster/g" /etc/apt/sources.list.d/*
sed -i "s/arrakis/usul/g" /etc/apt/sources.list.d/*
sed -i "/[Dd]ocker/d" /etc/apt/sources.list.d/omv-extras-org.list
apt-get update
apt-get dist-upgrade
reboot
apt-get purge openmediavault-omvextrasorg resolvconf
wget -O - https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install | bash
apt-get update
apt-get dist-upgrade

I would add also the following since it caused an issue

apt-get purge openmediavault-nut

It stopped the dist-upgrade but when I removed it and run again dist-upgrade everything was fine.

In the end I lost the UI but

omv-salt deploy run nginx
omv-salt deploy run phpfpm

fixed that!

Thanks all