WebODM Installation issues - Installer used

Hey everyone,

I’ve been trying to install WebODM using the installer purchased from the website. I’m trying to run WebODM within a VM environment (but not the one created in docker) and wondered if this was why I was having problems. It’s a windows 10 64 bit system and I’ve downloaded the git and docker programmes, but can’t get docker to run in this environment either - though if I’ve understood the WebODM guide correctly by using the installer I should be able to bypass the docker?

Forgive my ignorance here but I’m very new to all this and just trying to understand why it does not seem to work from the install. The error message I get is that the node is offline and I don’t appear to be able to create an account to modify the settings for the node at all.

If anyone is able to help with this it would be very much appreciated.

All the best
J

2 Likes

Welcome!

Nested virtualization can certainly be tricky.

What is your Host Operating System? What Virtual Machine are you trying to run WebODM within?

If you downloaded the newest WebODM for Windows (native) installer, then yes, this no longer requires docker or any virtualization technology.

If you can, email [email protected] with your order confirmation email/number (MYS-xxxxxxxxxx) and we can make sure you have the latest installer version if you don’t already.

Thanks for the warm welcome! Sorry to post problems straight off!

Host Operating system is Windows 10 Enterprise.

The WebODM downloaded was the version 1.9.2 build 25.

1 Like

Not a problem! That sounds like it should have been the WebODM for Windows (native), so you would not need git nor docker to run alongside it.

I have not attempted to run it in a VM, however (though I can’t see why it wouldn’t run in one).

What Host Virtual Machine are you using? Windows Hyper-V?

Oh sorry yes hyper V.

Does it help you narrow things down by mentioning that it specifically gives the message node-odm-1 being offline and I can’t seem to add data for a user at all …

1 Like

I’m trying it locally with Windows Sandbox/WDAG (Hyper-V based) and am getting similar issues:

Allowing firewall entries;

Installing VC++ Redist:

Launching:

If I had to guess, it has something to do with how Hyper-V handles bridging the network adapters from the Host to the VM.

I think that if we can modify the listening address, we could get it to work, but I’m not sure how to do that at present.

Try editing C:\WebODM\resources\app\nodeodm.js and change the host from 127.0.0.1 to localhost or 0.0.0.0.

You will also need to change C:\WebODM\resources\app\main.js:135

      await launchPythonEnv('python', ['manage.py', 'addnode', '127.0.0.1', '29301', '--label', 'node-odm-1', '--token', creds.nodeodm], webodmDir);

So that the Node gets properly added.

1 Like

Hi Iam running in vmware and installed on ubuntu. Install ubunto 20.04 in the normal way with the iso. Then look at my post on install on odm but you need loads of ram. The memory management is poor ( shame ) you need more then 64gig available to run any large amount of images.

Sorry just seen your running on hyper V not vmware.

When changing the C:\WebODM\resources\app\main.js:135

I assume I’m simply changing the host from 127.0.0.1 to either 0.0.0.0 or localhost?

e.g.
await launchPythonEnv(‘python’, [‘manage.py’, ‘addnode’, ‘0.0.0.0’, ‘29301’, ‘–label’, ‘node-odm-1’, ‘–token’, creds.nodeodm], webodmDir);

1 Like

Ooo actually might have some success - I changed everything to the localhost and everything is now showing the node as online. I’m trying to create a simple 3d model now using this node. It seems to be taking a long time - resolution only 1024 36 images - and currently 2hrs45mins just running. I’m not sure if this is to be expected though so I’ll carry on leaving it in the background for now! Thanks for all the help so far!

2 Likes

Hard to say, haha! Depends upon many things.

1 Like

Hmm well some progress, but it does appear that I’m still struggling to simply upload the images to the processing node.

What changed from when you had success processing a few days ago?

Well even the other day when uploading I got a an error message during processing or incredibly long processing times that didn’t appear to ever end (I left the machine running overnight and the status bar didn’t move after 16 hours). After this I tried simply restarting the processing and the uploading of images doesn’t appear to even update with a time or update with an error message so - not entirely sure what’s changed.

Okay so now when I’m restarting the job entirely I get an error message and a very long description in the log. I don’t know if you want the whole thing, but it ends with the following errors:

“redis-server: [8624] 17 Aug 09:18:06.043 * 10 changes in 300 seconds. Saving … /n”
“redis-server: [8624] 17 Aug 09:18:06.043 * background saving started by pid 6368\n”
“redis-server: [6368] 17 Aug 09:18:06.043 * Write error saving db on disk: No space left on device \n”
“redis-server: [6368] 17 Aug 09:18:06.043 * rdbSave failed in qfork: No space left on device \n”
“redis-server: [8624] 17 Aug 09:18:06.043 * fork operation completed\n [8624] Aug 19:08:06.152 # Background saving error \n”

So I’m going to take a wild guess and say that’s a disk space issue haha

1 Like

Seems it! How much room do you have in your virtual drive?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.