z.archive.spectrometer-dev@lists.opendaylight.org | spectrometer.opendaylight.org is down

Home Messages Hashtags Subgroups

This group is locked. No changes can be made to the group while it is locked.

Date Date 1 - 10 of 10

spectrometer.opendaylight.org is down

Jamo Luhrsen <jluhrsen@...> #417 Hi all, I already merged Thanh's patch under the pretense that a blank front end or 502 can't get any more broken. I think it's ok now, btw. JamO toggle quoted message Show quoted text On 01/31/2017 12:13 PM, Thomas Nadeau wrote: Let me pull Thanh's patch and test it out now, but I agree I agree. —Tom On Jan 31, 2017:3:08 PM, at 3:08 PM, Vasu Srinivasan <vasya10@... <mailto:vasya10@...>> wrote: Edit above: If Node6 version works, then we should go for it. I will review the patch. Regards, Vasu Srinivasan ----------------------------------- vagartham.wordpress.com <http://vagartham.wordpress.com/> vasya10.wordpress.com <http://vasya10.wordpress.com/> On Tue, Jan 31, 2017 at 2:07 PM, Vasu Srinivasan <vasya10@... <mailto:vasya10@...>> wrote: I am still using NodeJS 4 locally, but moving to Node6 must not be a problem. if Node 6 versions, Id recommend going to it. Regards, Vasu Srinivasan ----------------------------------- vagartham.wordpress.com <http://vagartham.wordpress.com/> vasya10.wordpress.com <http://vasya10.wordpress.com/> On Tue, Jan 31, 2017 at 12:08 PM, Thanh Ha <thanh.ha@... <mailto:thanh.ha@...>> wrote: Submitted patch here: https://git.opendaylight.org/gerrit/51269 <https://git.opendaylight.org/gerrit/51269> Regards, Thanh On Tue, Jan 31, 2017 at 1:03 PM, Thanh Ha <thanh.ha@... <mailto:thanh.ha@...>> wrote: I updated to the latest LTS version 6.9.4 and it seems to be working now. I'm working on a JJB patch to make sure the job pulls in the new version. Regards, Thanh On Tue, Jan 31, 2017 at 12:15 PM, Thanh Ha <thanh.ha@... <mailto:thanh.ha@...>> wrote: Hi Vasu, What version of Node JS are we recommending now. I think things aren't working after the new patch with node 4.4.6 anymore. Regards, Thanh On Tue, Jan 31, 2017 at 11:31 AM, Thanh Ha <thanh.ha@... <mailto:thanh.ha@...>> wrote: On Tue, Jan 31, 2017 at 10:17 AM, Thanh Ha <thanh.ha@... <mailto:thanh.ha@...>> wrote: On Tue, Jan 31, 2017 at 7:34 AM, Thomas Nadeau <tnadeau@... <mailto:tnadeau@...>> wrote: Thanh, Please take a look. —Tom Hi Tom, 502 Bad Gateway usually just means spectrometer isn't running. Anyone can force spectrometer to restart by finding any Gerrit spectrometer patch and just leaving a comment "remerge". I forced the web deploy job to queue in Jenkins by doing just this. Let's see if it brings it back up. So poking around a bit and noticed /api still works which tells me the backend is fine and only the front-end broke. Most likely because of this patch [0]. I deleted the nodeenv directory on the spectrometer server to force it to reinstall node and the node_modules. Let's see if that forces the packages to update correctly and successfully start the web frontend. Regards, Thanh [0] https://git.opendaylight.org/gerrit/50725 <https://git.opendaylight.org/gerrit/50725> _______________________________________________ spectrometer-dev mailing list spectrometer-dev@... https://lists.opendaylight.org/mailman/listinfo/spectrometer-dev
Thomas Nadeau #416 Let me pull Thanh's patch and test it out now, but I agree I agree. —Tom toggle quoted message Show quoted text On Jan 31, 2017:3:08 PM, at 3:08 PM, Vasu Srinivasan <vasya10@...> wrote: Edit above: If Node6 version works, then we should go for it. I will review the patch. Regards, Vasu Srinivasan ----------------------------------- vagartham.wordpress.com vasya10.wordpress.com On Tue, Jan 31, 2017 at 2:07 PM, Vasu Srinivasan <vasya10@...> wrote: I am still using NodeJS 4 locally, but moving to Node6 must not be a problem. if Node 6 versions, Id recommend going to it. Regards, Vasu Srinivasan ----------------------------------- vagartham.wordpress.com vasya10.wordpress.com On Tue, Jan 31, 2017 at 12:08 PM, Thanh Ha <thanh.ha@...> wrote: Submitted patch here: https://git.opendaylight.org/gerrit/51269 Regards, Thanh On Tue, Jan 31, 2017 at 1:03 PM, Thanh Ha <thanh.ha@...> wrote: I updated to the latest LTS version 6.9.4 and it seems to be working now. I'm working on a JJB patch to make sure the job pulls in the new version. Regards, Thanh On Tue, Jan 31, 2017 at 12:15 PM, Thanh Ha <thanh.ha@...> wrote: Hi Vasu, What version of Node JS are we recommending now. I think things aren't working after the new patch with node 4.4.6 anymore. Regards, Thanh On Tue, Jan 31, 2017 at 11:31 AM, Thanh Ha <thanh.ha@...> wrote: On Tue, Jan 31, 2017 at 10:17 AM, Thanh Ha <thanh.ha@...> wrote: On Tue, Jan 31, 2017 at 7:34 AM, Thomas Nadeau <tnadeau@...> wrote: Thanh, Please take a look. —Tom Hi Tom, 502 Bad Gateway usually just means spectrometer isn't running. Anyone can force spectrometer to restart by finding any Gerrit spectrometer patch and just leaving a comment "remerge". I forced the web deploy job to queue in Jenkins by doing just this. Let's see if it brings it back up. So poking around a bit and noticed /api still works which tells me the backend is fine and only the front-end broke. Most likely because of this patch [0]. I deleted the nodeenv directory on the spectrometer server to force it to reinstall node and the node_modules. Let's see if that forces the packages to update correctly and successfully start the web frontend. Regards, Thanh [0] https://git.opendaylight.org/gerrit/50725
Vasu Srinivasan <vasya10@...> #415 Edit above: If Node6 version works, then we should go for it. I will review the patch. Regards, Vasu Srinivasan ----------------------------------- vagartham.wordpress.com vasya10.wordpress.com toggle quoted message Show quoted text On Tue, Jan 31, 2017 at 2:07 PM, Vasu Srinivasan <vasya10@...> wrote: I am still using NodeJS 4 locally, but moving to Node6 must not be a problem. if Node 6 versions, Id recommend going to it. Regards, Vasu Srinivasan ----------------------------------- vagartham.wordpress.com vasya10.wordpress.com On Tue, Jan 31, 2017 at 12:08 PM, Thanh Ha <thanh.ha@...> wrote: Submitted patch here: https://git.opendaylight.org/gerrit/51269 Regards, Thanh On Tue, Jan 31, 2017 at 1:03 PM, Thanh Ha <thanh.ha@...> wrote: I updated to the latest LTS version 6.9.4 and it seems to be working now. I'm working on a JJB patch to make sure the job pulls in the new version. Regards, Thanh On Tue, Jan 31, 2017 at 12:15 PM, Thanh Ha <thanh.ha@...> wrote: Hi Vasu, What version of Node JS are we recommending now. I think things aren't working after the new patch with node 4.4.6 anymore. Regards, Thanh On Tue, Jan 31, 2017 at 11:31 AM, Thanh Ha <thanh.ha@...> wrote: On Tue, Jan 31, 2017 at 10:17 AM, Thanh Ha <thanh.ha@...> wrote: On Tue, Jan 31, 2017 at 7:34 AM, Thomas Nadeau <tnadeau@...> wrote: Thanh, Please take a look. —Tom Hi Tom, 502 Bad Gateway usually just means spectrometer isn't running. Anyone can force spectrometer to restart by finding any Gerrit spectrometer patch and just leaving a comment "remerge". I forced the web deploy job to queue in Jenkins by doing just this. Let's see if it brings it back up. So poking around a bit and noticed /api still works which tells me the backend is fine and only the front-end broke. Most likely because of this patch [0]. I deleted the nodeenv directory on the spectrometer server to force it to reinstall node and the node_modules. Let's see if that forces the packages to update correctly and successfully start the web frontend. Regards, Thanh [0] https://git.opendaylight.org/gerrit/50725
Vasu Srinivasan <vasya10@...> #414 I am still using NodeJS 4 locally, but moving to Node6 must not be a problem. if Node 6 versions, Id recommend going to it. Regards, Vasu Srinivasan ----------------------------------- vagartham.wordpress.com vasya10.wordpress.com toggle quoted message Show quoted text On Tue, Jan 31, 2017 at 12:08 PM, Thanh Ha <thanh.ha@...> wrote: Submitted patch here: https://git.opendaylight.org/gerrit/51269 Regards, Thanh On Tue, Jan 31, 2017 at 1:03 PM, Thanh Ha <thanh.ha@...> wrote: I updated to the latest LTS version 6.9.4 and it seems to be working now. I'm working on a JJB patch to make sure the job pulls in the new version. Regards, Thanh On Tue, Jan 31, 2017 at 12:15 PM, Thanh Ha <thanh.ha@...> wrote: Hi Vasu, What version of Node JS are we recommending now. I think things aren't working after the new patch with node 4.4.6 anymore. Regards, Thanh On Tue, Jan 31, 2017 at 11:31 AM, Thanh Ha <thanh.ha@...> wrote: On Tue, Jan 31, 2017 at 10:17 AM, Thanh Ha <thanh.ha@...> wrote: On Tue, Jan 31, 2017 at 7:34 AM, Thomas Nadeau <tnadeau@...> wrote: Thanh, Please take a look. —Tom Hi Tom, 502 Bad Gateway usually just means spectrometer isn't running. Anyone can force spectrometer to restart by finding any Gerrit spectrometer patch and just leaving a comment "remerge". I forced the web deploy job to queue in Jenkins by doing just this. Let's see if it brings it back up. So poking around a bit and noticed /api still works which tells me the backend is fine and only the front-end broke. Most likely because of this patch [0]. I deleted the nodeenv directory on the spectrometer server to force it to reinstall node and the node_modules. Let's see if that forces the packages to update correctly and successfully start the web frontend. Regards, Thanh [0] https://git.opendaylight.org/gerrit/50725
Thanh Ha <thanh.ha@...> #413 Submitted patch here: https://git.opendaylight.org/gerrit/51269 Regards, Thanh toggle quoted message Show quoted text On Tue, Jan 31, 2017 at 1:03 PM, Thanh Ha <thanh.ha@...> wrote: I updated to the latest LTS version 6.9.4 and it seems to be working now. I'm working on a JJB patch to make sure the job pulls in the new version. Regards, Thanh On Tue, Jan 31, 2017 at 12:15 PM, Thanh Ha <thanh.ha@...> wrote: Hi Vasu, What version of Node JS are we recommending now. I think things aren't working after the new patch with node 4.4.6 anymore. Regards, Thanh On Tue, Jan 31, 2017 at 11:31 AM, Thanh Ha <thanh.ha@...> wrote: On Tue, Jan 31, 2017 at 10:17 AM, Thanh Ha <thanh.ha@...> wrote: On Tue, Jan 31, 2017 at 7:34 AM, Thomas Nadeau <tnadeau@...> wrote: Thanh, Please take a look. —Tom Hi Tom, 502 Bad Gateway usually just means spectrometer isn't running. Anyone can force spectrometer to restart by finding any Gerrit spectrometer patch and just leaving a comment "remerge". I forced the web deploy job to queue in Jenkins by doing just this. Let's see if it brings it back up. So poking around a bit and noticed /api still works which tells me the backend is fine and only the front-end broke. Most likely because of this patch [0]. I deleted the nodeenv directory on the spectrometer server to force it to reinstall node and the node_modules. Let's see if that forces the packages to update correctly and successfully start the web frontend. Regards, Thanh [0] https://git.opendaylight.org/gerrit/50725
Thanh Ha <thanh.ha@...> #412 I updated to the latest LTS version 6.9.4 and it seems to be working now. I'm working on a JJB patch to make sure the job pulls in the new version. Regards, Thanh toggle quoted message Show quoted text On Tue, Jan 31, 2017 at 12:15 PM, Thanh Ha <thanh.ha@...> wrote: Hi Vasu, What version of Node JS are we recommending now. I think things aren't working after the new patch with node 4.4.6 anymore. Regards, Thanh On Tue, Jan 31, 2017 at 11:31 AM, Thanh Ha <thanh.ha@...> wrote: On Tue, Jan 31, 2017 at 10:17 AM, Thanh Ha <thanh.ha@...> wrote: On Tue, Jan 31, 2017 at 7:34 AM, Thomas Nadeau <tnadeau@...> wrote: Thanh, Please take a look. —Tom Hi Tom, 502 Bad Gateway usually just means spectrometer isn't running. Anyone can force spectrometer to restart by finding any Gerrit spectrometer patch and just leaving a comment "remerge". I forced the web deploy job to queue in Jenkins by doing just this. Let's see if it brings it back up. So poking around a bit and noticed /api still works which tells me the backend is fine and only the front-end broke. Most likely because of this patch [0]. I deleted the nodeenv directory on the spectrometer server to force it to reinstall node and the node_modules. Let's see if that forces the packages to update correctly and successfully start the web frontend. Regards, Thanh [0] https://git.opendaylight.org/gerrit/50725
Thanh Ha <thanh.ha@...> #411 Hi Vasu, What version of Node JS are we recommending now. I think things aren't working after the new patch with node 4.4.6 anymore. Regards, Thanh toggle quoted message Show quoted text On Tue, Jan 31, 2017 at 11:31 AM, Thanh Ha <thanh.ha@...> wrote: On Tue, Jan 31, 2017 at 10:17 AM, Thanh Ha <thanh.ha@...> wrote: On Tue, Jan 31, 2017 at 7:34 AM, Thomas Nadeau <tnadeau@...> wrote: Thanh, Please take a look. —Tom Hi Tom, 502 Bad Gateway usually just means spectrometer isn't running. Anyone can force spectrometer to restart by finding any Gerrit spectrometer patch and just leaving a comment "remerge". I forced the web deploy job to queue in Jenkins by doing just this. Let's see if it brings it back up. So poking around a bit and noticed /api still works which tells me the backend is fine and only the front-end broke. Most likely because of this patch [0]. I deleted the nodeenv directory on the spectrometer server to force it to reinstall node and the node_modules. Let's see if that forces the packages to update correctly and successfully start the web frontend. Regards, Thanh [0] https://git.opendaylight.org/gerrit/50725
Thanh Ha <thanh.ha@...> #410 On Tue, Jan 31, 2017 at 10:17 AM, Thanh Ha <thanh.ha@...> wrote: On Tue, Jan 31, 2017 at 7:34 AM, Thomas Nadeau <tnadeau@...> wrote: Thanh, Please take a look. —Tom Hi Tom, 502 Bad Gateway usually just means spectrometer isn't running. Anyone can force spectrometer to restart by finding any Gerrit spectrometer patch and just leaving a comment "remerge". I forced the web deploy job to queue in Jenkins by doing just this. Let's see if it brings it back up. So poking around a bit and noticed /api still works which tells me the backend is fine and only the front-end broke. Most likely because of this patch [0]. I deleted the nodeenv directory on the spectrometer server to force it to reinstall node and the node_modules. Let's see if that forces the packages to update correctly and successfully start the web frontend. Regards, Thanh [0] https://git.opendaylight.org/gerrit/50725
Thanh Ha <thanh.ha@...> #409 On Tue, Jan 31, 2017 at 7:34 AM, Thomas Nadeau <tnadeau@...> wrote: Thanh, Please take a look. —Tom Hi Tom, 502 Bad Gateway usually just means spectrometer isn't running. Anyone can force spectrometer to restart by finding any Gerrit spectrometer patch and just leaving a comment "remerge". I forced the web deploy job to queue in Jenkins by doing just this. Let's see if it brings it back up. Regards, Thanh
Thomas Nadeau #408 Thanh, Please take a look. —Tom

1 - 10 of 10

1

Previous Topic Next Topic

Home Hashtags Subgroups Terms