Join GitHub today
Licode stops automatically after several days #688
I have deployed licode on Ubuntu Server 14.04 with node v6.9.3. After some days licode automatically stops. I am posting last logs.
I've noticed that occasionally Nuve stop seeing ErizoController, is this a rabittmq related issue? 2017-01-18 21:39 GMT-03:00 Prakhar Singh <firstname.lastname@example.org>:…
@lodoyun <https://github.com/lodoyun> Do you see any abnormality in the logs? This happens for me after every two weeks. I am on an OVH server running ubuntu 14.04 server. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#688 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACgajV70qa48dySjYSWpBISS3bqCY3Cks5rTrDBgaJpZM4Lg71K> .
We are also facing the same issue. Please find the logs below:
NOTE: In our case, issue is not after weeks time of licode start. It happened after few days (~2 days).
In this scenario, we can notice erizoController.js & rabbitmq is still running, because of which there is no service restart (But CloudHandler logs no erizoController), which results in createToken error.
To overcome this, we added process.exit(0), So that entire service will be restarted.
Is this fine?
And how we can fix this issue?
Thanks & Regards,