Error: Module version mismatch, refusing to load.

[nkhine]

hello,
i get this error when trying to deploy on AppFog:

====> /logs/stderr.log <====

module.js:485
process.dlopen(filename, module.exports);
^
Error: Module version mismatch, refusing to load.
at Object.Module._extensions..node (module.js:485:11)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:362:17)
at require (module.js:378:17)
at Object. (/mnt/var/vcap.local/dea/apps/blade-0-28d75b77b7dbb3c424efe4b18b1fce80/app/node_modules/express-minify/node_modules/node-sass/sass.js:11:13)
at Module._compile (module.js:449:26)
at Object.Module._extensions..js (module.js:467:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)

express-minify requires, 0.4.2 of node-sass, https://github.com/breeswish/express-minify/blob/master/package.json#L24

any advice much appreciated.

[bwilkins]

Hi @nkhine,

Diagnosis

This is likely to be a node version issue. I'm not sure when it originally started, but at some point we started compiling against node v0.10.x, which is likely to not be backwards compatible with older versions of node. @andrew may be more readily able to tell us when that happened.

Alternatively, the inverse could also be true, and 0.4.2 could be compiled against an older version of node, the ABI of which may not be supported well in later versions (I believe @andrew has encountered this in previous bugs).

Advice

• Find out what version of node is running on AppFog
• Find out what architecture is running your code on AppFog (linux x86/x64?)
• Patch the version number in express-minify and make a pull request

[bwilkins]

Hi @nkhine,

Did you find a solution to this at all?

[nkhine]

hi @bwilkins
on appfog, the runtime that the app is running is 0.8.14 and this is deployed on amazon ec2. will try to get the rest of the info.

[bwilkins]

Are you able to get the 0.10.x runtime at all? This is what we've been building against as of late.

[nkhine]

no, appfog's node runtimes are:

☺ af runtimes * master d875f3f""

+---------+-------------+---------+
| Name | Description | Version |
+---------+-------------+---------+
| java | | 1.7.0 |
| php | | 5.3.10 |
| ruby18 | | 1.8.7 |
| ruby192 | | 1.9.2 |
| ruby193 | | 1.9.3 |
| python2 | | 2.7.3 |
| node04 | | 0.4.12 |
| node06 | | 0.6.17 |
| node08 | | 0.8.14 |
+---------+-------------+---------+

will try and push on Heroku as they are the only provider to run 0.10.x and advise

[andrew]

@nkhine any luck getting it working?

[deanmao]

It doesn't make sense to support older versions of node because they changed the libuv data type signatures. If we supported older node versions, we'd need to create a fork and maintain both forks with patches. Just don't use AppFog or tell them to get with the program and update their node version.

[spro]

Strangely, I'm getting this same error with node v0.10.12

[dean-m]

I'm using v0.10.12 here on linux 64bit & mac, but not getting errors... can you provide more info?

[nkhine]

i am using v0.10.1 on mac and am not getting errors.

[pho3nixf1re]

We are having this problem on an Ubuntu VM. This seems to not be related to node versions. Both the ubuntu vm and my Mac (osx 10.8) are running node 0.10.12 . EDIT: the local Mac is working fine.

[spro]

Interesting, my problem was also on Linux (Arch). Fine on OS X.

[pho3nixf1re]

Turns out that (the reboot) didn't actually fix it, there was just a different problem. Now we are fighting with the Ubuntu VM again. Could it be that this is a problem on Linux systems and not osx?

[jamesearl]

I just ran into this issue. Was on node 0.6.4. Updated to latest, 0.10.13, and issue is solved. Windows 64bit, fwiw.