OMV6 sure looks like a huge upgrade

Zitat von ryecoaaron

The code is using php's function gethostname since I can't use javascript to get the hostname anymore. I may have to execute the command hostname -f and use its output. Does hostname -f return the correct hostname on your system?

Unfortunately, it isn't cut&paste.

The symlinks plugin shouldn't be a problem to port since it is pretty simple.

ryecoaaron You can use \OMV\System\Net\DNS to get the hostname, but the better approach is to load the conf.system.network.dns database object and build the hostname yourself. Think about the situation where the hostname is modified but not applied, then your plugin is modified and the PHP code uses gethostname to get the hostname, this will finally end in incorrect data.

I don't know the plugin, but why not getting the hostname while deploying the configuration. You can use Salt grains to get the hostname or easily access the conf.system.network.dns database object. You can make 'hostname' a dependency of your RPC module, thus 'hostname' is deployed before your plugin, and you can be sure the Salt grain contains the correct hostname.

Zitat von votdev

You can use \OMV\System\Net\DNS to get the hostname, but the better approach is to load the conf.system.network.dns database object and build the hostname yourself. Think about the situation where the hostname is modified but not applied, then your plugin is modified and the PHP code uses gethostname to get the hostname, this will finally end in incorrect data.

I don't know the plugin, but why not getting the hostname while deploying the configuration. You can use Salt grains to get the hostname or easily access the conf.system.network.dns database object. You can make 'hostname' a dependency of your RPC module, thus 'hostname' is deployed before your plugin, and you can be sure the Salt grain contains the correct hostname.

The plugin is just trying to find the hostname to open a browser window. I used to use the javascript function location.hostname to build the url but I can't do that anymore. I don't care if the hostname has been modified but not applied because the plugin needs the current name that is resolving. Salt can't be used here either because this is all client side stuff.

Zitat von ryecoaaron

The plugin is just trying to find the hostname to open a browser window. I used to use the javascript function location.hostname to build the url but I can't do that anymore. I don't care if the hostname has been modified but not applied because the plugin needs the current name that is resolving. Salt can't be used here either because this is all client side stuff.

OK, that is an easy task. Simply use {{ location.hostname }} in a string, and the UI will automatically fill it with the current hostname. See https://github.com/openmediava…/functions.helper.ts#L307

Zitat von KM0201

That's definitely not right. Are you sure doctor is installed

Sorry, I forgot that I had uninstalled it.

wayne@omv6:/$ docker info | grep Root

 Docker Root Dir: /var/lib/docker

Zitat von votdev

OK, that is an easy task. Simply use {{ location.hostname }} in a string, and the UI will automatically fill it with the current hostname. See https://github.com/openmediava…/functions.helper.ts#L307

Looks like it should actually be: {{ location() | get("hostname") }} but it is working.

Zitat von insp1re

the only issue i maintain with this un-release is the nut plugin is missing from collectd, so unable to configure the ups service.

Could you please post the error message.

Zitat von frauhansen

is there/will be there a update option from a existing 5.x to 6.x?

It is planned to add support to migrate from 5 to 6.

Zitat von Noter2017

No idea why this is marked alpha. I did a fresh install 3 days ago and didn't face a single problem.

SMB shares work, GUI works, OMV extras and Docker (qBittorrent, Adguard Home, Cloud Commander, Scrutiny) work as well.

Just because it "works for you", has nothing to do with why it is marked Alpha.

1. It hasn't been extensively tested.

2. Debian 11, which it is based on, isn't even stable yet

Zitat von Noter2017

It seems to be working pretty pretty good for many people. Only major complaints I saw on the forum were about FTP but that was fixed.

I had a spare NUC lying around, installed OMV 6 and I couldn't be happier with it.

OK, again.. that is irrelevant and has nothing to do with whether software is Alpha, Beta, etc. I've tested it quite a bit and like it a lot... but that doesn't mean it's stable... especially when the underlying OS isn't even stable yet

Zitat von no_Legend

I'm just going to set up my my system completely from scratch.

So I'm now not sure if it should give OMV 6.0 a try.

But how it will be if there will updates from OMV6.0 alpha to beta and further to final release.
Is there update possible or could it also the way that I need to install the hole system from scratch again?

Edit: quick installed it in vm an found a few problems:

1. No login possible after typing in the password and hit Enter. Enter just make the password readable. You need to use the mouse to push the login button. Tested with firefox

2. Update are not possible to install by webgui. so the packed openmediavault 6.0-16 need to be installed by hand.

3. there are updates shown wich are on not visible on the console. Releoad and search for update on the webgui is not cleaning the update list.

Is there any official way to report all this found errors.

Cheers Robert

Alles anzeigen

The login screen password issue should be fixed. You just need to run updates.

I've not had the other issues.

Zitat von KM0201

Well, for now... I've just edited the daemon.json and put the correct path in. Restarted docker a few times from both command line and the webUI, also restarted the entire virtual machine, and it seems to be holding the change (although the webUI still shows /var/lib/docker)

I suspect if an update gets pushed I'll lose this. I guess the true test will be when I start installing containers and I see where they go.

Code

joe@omv6-test:~$ docker info | grep Root
 Docker Root Dir: /srv/dev-disk-by-uuid-b83f2343-f13e-4066-9f3a-55dfe8ce8f2b/Containers
joe@omv6-test:~$ 

Alles anzeigen

Did your docker path persist?