qewd-up on Cache'

[Michael Reach]

We recently tried upgrading node-js to version 19 from version 12.16.1 to 19.3.0. We couldn't get qewd-up started afterwards; get this message that it can't find mg-dbx.

1) Is there a restriction on which node-js we can use?

2) Is there a simple way to get a fresh working install of qewd-up afterwards? We'll keep all our own qewd-up files that were working fine till the upgrade.

Thanks,

Michael Reach

[rtweed]

Hi Michael

You'll need to provide some more information for anyone to help, eg:

-  what platform / OS are you using for QEWD?

- Is it a native or dockerised system that you're using and how are you starting it?  

-- please provide your QEWD configuration data too.

- Finally please give details of the exact error message you see that is telling you it can't find mg-dbx.

Many thanks

Rob

[Rob Tweed]

Also, any reason for going to Node.js v19?  v18 is the more sensible one to use for production as it has long term support.  v19 is primarily a development strand

--
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/4d2ae9eb-cc99-4459-ae1a-0add31bd8170n%40googlegroups.com.

--

Rob Tweed
Director, M/Gateway Developments Ltd
http://www.mgateway.com

[Michael Reach]

Hi, Rob! Thanks.

Windows Server 2016 Datacenter, version 1607, 64 bit, x64

OS Build 14393.5582

Native, not dockerized qewd.

config.json:

{
  "qewd": {
    "managementPassword": "qewdtest",
    "serverName": "CACHET1 QEWD Server",
    "poolSize": 1,
    "port": 8080,
    "database": {
      "type": "dbx",
      "params": {
        "database": "Cache",
        "path": "D:\\Cache\\SMILE\\Mgr",
        "username": "QEWD",
        "password": XXXX,
        "namespace": "SMILE"
      }
    }
  }
}

[Michael Reach]

Error message (this is no longer current as we've started failbacks and stuff) from a few days ago when this started:

I’m getting the following error in the Log (D:\qewd\qewd-up\Log\Output.txt), whenever I try to restart via the script

(PS D:\qewd\qewd-up> cqewd-up restart):

 

*** master received exit event from worker process 1584

socket 31mLxw8TiaHRoQE-AAAB disconnected

no available workers

sent qoper8-start message to 5204

process.argv[2] = qewd.worker

workerModule: qewd; worker

Thu, 22 Dec 2022 19:23:16 GMT; master process received response from worker 5204: {"type":"error","finished":true,"message":"The specified procedure could not be found.\r\n\\\\?\\d:\\qewd\\qewd-up\\node_modules\\mg-dbx.node"}

*** master received exit event from worker process 5204

[Michael Reach]

I don't think we have a particular attachment to node-js v19!

[Rob Tweed]

OK as it's a Windows system, I think it's due to the qewd/up/run_native.js module being out of date.

At the top of it you'll see these lines:

const dbx_github_url = {

  v12: "https://raw.githubusercontent.com/chrisemunt/mg-dbx/master/bin/winx64/node12/mg-dbx.node",

  v14: "https://raw.githubusercontent.com/chrisemunt/mg-dbx/master/bin/winx64/node14/mg-dbx.node"

};

Can you edit your copy and add a line for v19:

  v19: "https://raw.githubusercontent.com/chrisemunt/mg-dbx/master/bin/winx64/node19/mg-dbx.node"

Alternatively, manually copy the node19 version of mg-dbx.node to your setup's node_modules file

Let me know if that get's you working?

Rob

On Fri, 30 Dec 2022 at 15:26, Michael Reach <michoe...@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/2187b453-3c20-4a63-aa5e-c4adad440d98n%40googlegroups.com.

[Michael Reach]

I'll let you know.

[wdbacker]

Hi Michael,

I'd recommend to stay always on even-numbered Node.js versions. Odd numbered versions are for developing new features, but not for production use.

ATM, I'd still recommend v16 which is still under maintenance. The LTS version v18 has some issues with popular frameworks like Nuxt (see this issue), that's the reason why I personally still run on v16. This will definitely change in the coming weeks/months, but I have the impression that some packages still show some issues.

HTH,

Ward

[Michael Reach]

So qewd-up came back, but when we tried starting it on my application, it keeps saying that node_module pieces are missing. I recall you once suggested removing node_modules and doing something to reload it?

Michael

[Rob Tweed]

Yes, you should probably delete (preferably rename) your node_modules directory and run npm install which will recreate it, pulling in all the dependencies specified in your QEWD system’s package.json file. Remember to copy in a new instance of mg_dbx.node afterwards. 

Rob

Sent from my iPhone

On 4 Jan 2023, at 20:42, Michael Reach <michoe...@gmail.com> wrote:

So qewd-up came back, but when we tried starting it on my application, it keeps saying that node_module pieces are missing. I recall you once suggested removing node_modules and doing something to reload it?

To view this discussion on the web, visit https://groups.google.com/d/msgid/enterprise-web-developer-community/73a60cb4-f812-4a94-982b-87caa733e5fdn%40googlegroups.com.

[aditya varun]

Can we read/write json data in YottoDB using python?

[aditya varun]

Hi,

I am just tryont to explore YottaDB.

Just want to confirm , Can we read/write json data to YottaDB using Python?

Thanks for the replies!!

Thanks and Regards,

Aditya

On Thursday, 5 January 2023 at 21:08:51 UTC+5:30 rtweed wrote:

[Michael Reach]

So this fix worked well in the Development system. But now we are trying to repeat the node-js upgrade (to v.18, as suggested) in our Live system. After all this, the service that runs qewd-up gets Paused right after it starts.

The output.txt in the Log folder looks okay, but we're getting an Error.txt in the Log folder that looks like this:

d:\qewd\qewd-up\node_modules\qewd\node_modules\engine.io\build\server.js:379
        this.ws = new this.opts.wsEngine({
                  ^

TypeError: this.opts.wsEngine is not a constructor
    at Server.init (d:\qewd\qewd-up\node_modules\qewd\node_modules\engine.io\build\server.js:379:19)
    at new BaseServer (d:\qewd\qewd-up\node_modules\qewd\node_modules\engine.io\build\server.js:58:14)
    at new Server (d:\qewd\qewd-up\node_modules\qewd\node_modules\engine.io\build\server.js:368:1)
    at attach (d:\qewd\qewd-up\node_modules\qewd\node_modules\engine.io\build\engine.io.js:52:20)
    at Server.initEngine (d:\qewd\qewd-up\node_modules\qewd\node_modules\socket.io\dist\index.js:289:43)
    at Server.attach (d:\qewd\qewd-up\node_modules\qewd\node_modules\socket.io\dist\index.js:228:14)
    at new Server (d:\qewd\qewd-up\node_modules\qewd\node_modules\socket.io\dist\index.js:118:18)
    at module.exports (d:\qewd\qewd-up\node_modules\qewd\node_modules\socket.io\dist\index.js:798:33)
    at startServer (d:\qewd\qewd-up\node_modules\qewd\lib\master.js:245:38)
    at qoper8.<anonymous> (d:\qewd\qewd-up\node_modules\qewd\lib\master.js:301:7)

Node.js v18.16.0

What does it mean?

Thanks,

Michael Reach

[wdbacker]

Hi,

You should check your socket.io module version in your package.json file: you can't use the recent versions (> v2.x) because the options syntax changed in version 4.x: https://socket.io/docs/v4/migrating-from-3-x-to-4-0/#wsengine-option

In case you're adding the socket.io module in your own package.json file, this can interfere with the version that the qewd module needs.

As Rob already suggested, make sure you completely delete your main node_modules folder (in case you have your own *.js files in the main node_modules directory: don't forget to backup them first!!!) and also delete the package-lock.json file in your qewd root directory, then run "npm install" again.

HTH,

Ward

[Michael Reach]

Thank you, that makes sense.

It is hard to track down internal pieces like socket-io. I only found out about it by reading through the log files. Is there a clear sequence that should be followed when upgrading node-js in this way? In other words, starting from our current node-js v 14 installation, and whatever other qewd-up pieces (plus we also use multer and dot-env). Is there a set of steps that we would expect would yield a new working system? 

Thanks,

Michael