Re: [IBMiOSS] node.js - 'module did not self-register' error

[Aaron Bartell <aaronbartell@xxxxxxxxx>]

> I can see from Google that this is a fairly common issue and is normally
down to a mismatch with the version of node, which shouldn't be the case
here.


I'd be curious if a different version of Node.js was present at ~compile~
(gcc/node-gyp) time of the kerberos npm vs. run time.  Can you confirm the
same Node.js version was used at kerberos compile and run time?

Aaron Bartell
IBM i hosting, starting at $157/month.  litmis.com/spaces


On Wed, Sep 6, 2017 at 7:17 AM, Mark Ford <Mark.Ford@xxxxxxxxxxx> wrote:

> One of our requirements for an node.js Express based application being
> tested on our IBM i is for it to support Kerberos based authentication.
> Simple enough we thought - just find and install a suitable package (we are
> trying 'kerberos') with npm and use that. It wasn't quite that simple.
>
> This package has a native module that requires compiling (node-gyp) which
> took this to a whole new level of needing to get the chroot and gcc
> compiler support installed. After much trial and error, trying 5733OPS
> option 3 then the more up-to-date scripts from ibmichroot, reading lots of
> posts here, updating gmake (to 4.2 as 4.1 had the virtual memory exhausted
> error), etc we have just about managed to get working.
>
> The npm install of the kerberos package now completes but we receive the
> following error when trying to run a test script using it...
>
> module.js:597
>   return process.dlopen(module, path._makeLong(filename));
>                  ^
>
> Error: Module did not self-register.
>     at Error (native)
>     at Object.Module._extensions..node (module.js:597:18)
>     at Module.load (module.js:487:32)
>     at tryModuleLoad (module.js:446:12)
>     at Function.Module._load (module.js:438:3)
>     at Module.require (module.js:497:17)
>     at require (internal/module.js:20:19)
>     at Object.<anonymous> (/home/xx/node/krb/node_
> modules/kerberos/lib/kerberos.js:1:78
>     at Module._compile (module.js:570:32)
>     at Object.Module._extensions..js (module.js:579:10)
>
>
> I can see from Google that this is a fairly common issue and is normally
> down to a mismatch with the version of node, which shouldn't be the case
> here. Has anybody else here encountered this or know of a possible solution?
>
> Thanks,
>
> Mark.
> --