Is any update process for production deployments?

Support
1

Hi,

I have a production instance of licode installed from commit 34e6653, now I see lots of commits in master branch.

How can I update my instance? Do you have process to update?

My worry is about losing data or if I need to make some manual actions to ensure the service.

Thanks

2

I’m trying to perform the update in a snapshot of my production environment, but I’m having issues.

I’ve executed installUbuntuDeps.sh because I’ve seen in commits you have changed the node installation to use nvm, but when I try tu start all node precess the nuve process gives me the next error:

/usr/share/licode/nuve/nuveAPI/mdb/erizoControllerRegistry.js:11
    db.erizoControllers.find({}).toArray(function (err, erizoControllers) {
                        ^
TypeError: Cannot call method 'find' of undefined
    at Object.exports.getErizoControllers (/usr/share/licode/nuve/nuveAPI/mdb/erizoControllerRegistry.js:11:25)
    at checkKA (/usr/share/licode/nuve/nuveAPI/cloudHandler.js:90:29)
    at wrapper [as _onTimeout] (timers.js:261:14)
    at Timer.listOnTimeout [as ontimeout] (timers.js:112:15)

Then I’ve executed installNuve.sh, but the problem persists and after this script execution the SuperService ID and SuperService Key have changed.

Do you have any doc describing the update process? Is a way to update without changing SuperService credentials?

3

Thanks! It should be fixed in https://github.com/ging/licode/pull/710

4

Yes thanks,

Now it runs correctly.

But the update process is still make me headache, after I run the installErizo and installNuve I can see that the licode_conf.js has been replaced by the fresh one and I lose all my config.

Do you have the process or steps to update licode and don’t lose information or config?

5

I’m back with new problem after solving the erizoController.
Now I have problems with erizoAgent, I can see this in the erizoAgent log:

2017-01-25 14:38:07.418  - INFO: ErizoAgent - message: launched new ErizoJS, erizoId: e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3] module.js:356
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]   Module._extensions[extension](this, filename);
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3] ^
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3]
[erizo-e26e7be3-fd2c-d1c5-04a4-7ed0b9d285a3] Error: /usr/share/licode/erizoAPI/build/Release/addon.node: undefined symbol: node_module_register
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/usr/share/licode/erizo_controller/erizoJS/erizoJS.js:4:13)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)

Searching in google I’ve found this post http://stackoverflow.com/questions/22868307/undefined-symbol-in-node-js-c-addon-under-linux-why and I’ve tried to debug

/usr/share/licode/erizoAPI/build/Release(master*) # nm -C addon.node|grep node_module_register                                                                                          root@dagobah-licode
                 U node_module_register
------------------------------------------------------------

The node_module_register appears as undefined, is this related to bad script execution? how can I re-launch the scritps to solve it?

Thanks

6

Have you built erizo after the update?

7

Yes and the problem persists, some idea?

8

In environment that is already deployed if I launch installErizo.sh I have the next ERROR

Pasted image1436×124 18.1 KB