Error after using prebuilt installer for Ubuntu with YottaDB

[OldMster]

Ran the install on the web site, started it up with node qewd, then went to 'myipaddress':8080/qewd-monitor/index.html

The web page sticks at 'Please Wait', and the following error shows up on the console:

marksires@clientproduct:~/qewd$ node qewd

Double ended queue max length set to 20000

webServerRootPath = /home/marksires/qewd/www/

Worker Bootstrap Module file written to node_modules/ewd-qoper8-worker.js

========================================================

ewd-qoper8 is up and running.  Max worker pool size: 1

========================================================

========================================================

QEWD.js is listening on port 8080

========================================================

no available workers

sent qoper8-start message to 25981

process.argv[2] = qewd.worker

workerModule: qewd; worker

*** uncaughtException in worker 25981 at Fri, 09 Oct 2020 17:43:01 GMT

/home/marksires/qewd/node_modules/fs-extra/lib/mkdirs/make-dir.js:85

      } catch {

              ^

SyntaxError: Unexpected token {

    at createScript (vm.js:80:10)

    at Object.runInThisContext (vm.js:139:10)

    at Module._compile (module.js:617:28)

    at Object.Module._extensions..js (module.js:664:10)

    at Module.load (module.js:566:32)

    at tryModuleLoad (module.js:506:12)

    at Function.Module._load (module.js:498:3)

    at Module.require (module.js:597:17)

    at require (internal/module.js:11:18)

    at Object.<anonymous> (/home/marksires/qewd/node_modules/fs-extra/lib/mkdirs/index.js:3:44)

*** worker 25981 is shutting down now ...

I tried to track it down, but all I can tell is that it is likely 'pth' in make-dir.js that is not right.

Mark

[wdbacker]

I suspect a permissions error in your directory structure.

Can you debug using VSCode on this machine? This makes life much easier finding the error.

You'll find instructions how to set up debugging in the qewd-howtos.

Put a breakpoint in VSCode at make-dir.js e.g. on line 58 and inspect the variables & call stack:

HTH,

Ward

[wdbacker]

In my reply above, the inline screenshot is missing - Google groups doesn't allow this apparently.

[OldMster]

I suspect you are right.  My first thought was to just spin up a new virtual machine and start from scratch.  But this presents a good opportunity to learn how to use debugging with QEWD in VS-Code, so I'll try that first.

Thanks!

Mark

[Rob Tweed]

Mark

I suspect you’re doing things the old QEWD way. Give me a day or two and I’ll have a set of documentation specifically on how to start working with QEWD on Linux and YottaDB (non Dockerised). It’s now a very simple process.

Rob

Sent from my iPhone

On 10 Oct 2020, at 20:25, OldMster <sires...@gmail.com> wrote:



--
You received this message because you are subscribed to the Google Groups "Enterprise Web Developer Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enterprise-web-develope...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/enterprise-web-developer-community/bf32863b-de3b-4ec3-b4e6-e1b4ac43b5e1o%40googlegroups.com.

[Rob Tweed]

I've packaged all the instructions up for QEWD running on Ubuntu Linux with YottaDB - using the QEWD-Up approach/syntax.  See:

https://github.com/robtweed/qewd-starter-kit-yottadb

Let me know how you get on

Rob

[OldMster]

One issue right off the bat.  The directions to clone https://github.com/robtweed/qewd-yottadb should be https://github.com/robtweed/qewd-starter-kit-yottadb.  Proceeding onward with that correction

marksires@genxlasvegasserver:~$ git clone https://github.com/robtweed/qewd-yottadb qewd

Cloning into 'qewd'...

remote: Repository not found.

fatal: repository 'https://github.com/robtweed/qewd-yottadb/' not found

marksires@genxlasvegasserver:~$

[OldMster]

Other than the repository name wrong, the directions worked fine, I now have it up and running. Thanks Rob!

Mark

On Sunday, October 11, 2020 at 7:23:26 AM UTC-4, rtweed wrote:

[rtweed]

Thanks Mark - I've now fixed that documentation error in the repo's README.  Glad to hear the rest of the instructions worked OK for you.

Rob