Picture of Mark D'Aquin
Upgrade
by Mark D'Aquin - Saturday, 18 June 2016, 12:26 AM
 

Hi,

I have the following:

  • node v4.2.6
  • npm 2.14.12

Everything was working fine and I noticed I needed to do an upgrade. So, I ran the following...

  • sudo rm –r node_modules
  • sudo npm install –-production (seemed to work)
  • sudo node upgrade (with this I get the following error)

******************

info: [18 Jun 2016 00:23:23 +00:00] configuration loaded from /devfs/adapt_authoring/conf/config.json
fs.js:808
return binding.readdir(pathModule._makeLong(path));
^

Error: ENOENT: no such file or directory, scandir '/home/i839211/devfs/adapt_authoring/plugins'
at Error (native)
at Object.fs.readdirSync (fs.js:808:18)
at PluginManager.getPluginTypes (/devfs/adapt_authoring/lib/pluginmanager.js:55:27)
at PluginManager.getPlugin (/devfs/adapt_authoring/lib/pluginmanager.js:154:26)
at ContentManager.loadContentPlugins (/devfs/adapt_authoring/lib/contentmanager.js:492:17)
at moduleLoaded (/devfs/adapt_authoring/lib/contentmanager.js:1727:22)
at emitOne (events.js:82:20)
at Origin.emit (events.js:169:7)
at Origin.<anonymous> (/devfs/adapt_authoring/lib/application.js:172:16)
at Array.some (native)
at Origin.modulePreloadEventHandler (/devfs/adapt_authoring/lib/application.js:161:24)
at emitTwo (events.js:87:13)
at emit (events.js:172:7)
at moduleLoaded (/devfs/adapt_authoring/lib/pluginmanager.js:541:21)
at emitOne (events.js:82:20)
at Origin.emit (events.js:169:7)

***************************

Now I can not run node server. Can anyone tell me what I need to do at this point? Thank you!

Picture of Mark D'Aquin
Re: Upgrade
by Mark D'Aquin - Wednesday, 22 June 2016, 7:43 PM
 

Can someone provide assistance here?

Thank you!

Mark

Sushil Vispute
Re: Upgrade
by Sushil Vispute - Thursday, 23 June 2016, 5:33 AM
 

Hi Mark,

For node upgrade try

node upgrade.js

Picture of Mark D'Aquin
Re: Upgrade
by Mark D'Aquin - Monday, 27 June 2016, 3:44 PM
 

Hi Sushil,

Thank you for your reply. Basically that is what I did with Sudo node upgrade.js and per my previous email that was the result. Now I am not sure what to do to fix it.

Thanks.

Mark