Back onto this, I reinstalled the hilary upstart script and everything does actually start via 'service hilary start' - at least I can see the process running. However visiting the URL does not work.
There was no log created in /var/log/upstart/ though. That said the process didn't die on logout so at least that was a winner. Any ideas what might be the problem? thanks, Steve On 31/07/2013, at 10:41 PM, Branden Visser <mrvis...@gmail.com> wrote: > Hi Steve, > > If you've left your config.log configuration to point to stdout, then > it should be redirecting to a file in /var/log/upstart . Note that the > "bootstrap.log" will still get written to in your > <app_root>/bootstrap.log before the system logger is initialized / > configured. > > To log to a file instead, you can simply change the "'stream': > process.stdout" config to: "'path': '/path/to/log/file.log'" instead. > > If you want to reconfigure your logging in a more advanced way (e.g., > logstash, syslog), we use a module called bunyan [1] and we give full > access to its configuration abilities in our config.js file. We have a > good deployment example in our puppet scripts as well of logging to > syslog [2]. > > Hope that helps, > Branden > > [1] https://github.com/trentm/node-bunyan > [2] > https://github.com/oaeproject/puppet-hilary/blob/master/modules/hilary/templates/config.js.erb#L110 > > On Wed, Jul 31, 2013 at 8:10 AM, Steve Swinsburg > <steve.swinsb...@gmail.com> wrote: >> Hi Branden, >> >> Thanks for that. I installed it as per the instructions and adjusted the >> paths, then run service hilary start and get: >> hilary start/running, process 7429 >> >> but the app doesnt come up. Where do the logs get sent to? >> >> I've also tried using forever: >> https://github.com/nodejitsu/forever >> >> Also no luck. >> >> cheers, >> Steve >> >> >> On Wed, Jul 31, 2013 at 12:03 AM, Branden Visser <mrvis...@gmail.com> wrote: >>> >>> Hi Steve, here's ours: >>> >>> https://github.com/oaeproject/puppet-hilary/blob/master/modules/hilary/templates/upstart_hilary.conf.erb >>> >>> You'll just want to replace the <%= app_root_dir %> with the directory >>> that contains the app.js. We drop that file into /etc/init/hilary.conf >>> [1] and it should give you immediate "service hilary start" support -- >>> atleast on Ubuntu 12.04. >>> >>> Hope that helps, >>> Branden >>> >>> [1] >>> https://github.com/oaeproject/puppet-hilary/blob/master/modules/hilary/manifests/init.pp#L182 >>> >>> On Tue, Jul 30, 2013 at 9:50 AM, Steve Swinsburg >>> <steve.swinsb...@gmail.com> wrote: >>>> Turns out the server was still shutting down on session end, even via >>>> nohup. >>>> So now I'm looking at these other methods. >>>> >>>> How do I implement that upstart script? >>>> >>>> thanks, >>>> Steve >>>> >>>> >>>> On Sun, Jul 28, 2013 at 12:18 PM, Branden Visser <mrvis...@gmail.com> >>>> wrote: >>>>> >>>>> Hi Steve: >>>>> >>>>> On Sat, Jul 27, 2013 at 6:57 PM, Steve Swinsburg >>>>> <steve.swinsb...@gmail.com> wrote: >>>>>> Sorry for the multiple emails, but this is what I am using: >>>>>> >>>>>> nohup node app | bunyan & >>>>>> >>>>>> Back on the issue of the blank screen in Safari/Chrome, its only on >>>>>> the >>>>>> Admin UI, the main tenant login screen is working ok in those >>>>>> browsers. >>>>>> >>>>> >>>>> Can you confirm if it is this issue: >>>>> https://github.com/oaeproject/3akai-ux/issues/3100 . That error should >>>>> pop up in your network console if it is. If it is happening quite >>>>> consistently for someone we'll likely bump up its priority. I don't >>>>> seem to run into it very often, and if I do clearing my cache seems to >>>>> fix it. >>>>> >>>>>> >>>>>> On Sun, Jul 28, 2013 at 8:55 AM, Steve Swinsburg >>>>>> <steve.swinsb...@gmail.com> >>>>>> wrote: >>>>>>> >>>>>>> I found this thread, regarding the shutdown of node when the >>>>>>> terminal >>>>>>> session is lost: >>>>>>> >>>>>>> >>>>>>> http://stackoverflow.com/questions/4018154/node-js-as-a-background-service >>>>>>> >>>>>>> Seems like there are a dozen different ways! What do you use? We >>>>>>> should >>>>>>> perhaps settle on one approach, WDYT? >>>>> >>>>> Settling on a common way would be good. Currently we're using an >>>>> upstart [2] script to spawn and manage our app as a daemon process. >>>>> The benefit of tying into upstart / init is that you get first-class >>>>> support from lots of deployment tools like MCollective and Puppet. I >>>>> know that both Ubuntu and RHEL have made the switch to upstart and >>>>> others seem to be on the way at least, I think it's a good candidate >>>>> to standardize on. >>>>> >>>>> "forever" [1] is also a viable option for daemonizing, which can be >>>>> wrapped itself in an upstart e.g., [3], though I'm not a big fan of >>>>> the idea of layering it up like that. Daemon-ception? >>>>> >>>>> [1] https://github.com/nodejitsu/forever >>>>> [2] >>>>> >>>>> https://github.com/oaeproject/puppet-hilary/blob/master/modules/hilary/templates/upstart_hilary.conf.erb >>>>> [3] >>>>> >>>>> https://www.exratione.com/2013/02/nodejs-and-forever-as-a-service-simple-upstart-and-init-scripts-for-ubuntu/ >>>>> >>>>>>> >>>>>>> cheers, >>>>>>> Steve >>>>>>> >>>>>>> >>>>>>> On Sun, Jul 28, 2013 at 8:42 AM, Steve Swinsburg >>>>>>> <steve.swinsb...@gmail.com> wrote: >>>>>>>> >>>>>>>> Ni Nico/Samuel, >>>>>>>> >>>>>>>> I get this response: >>>>>>>> {"anon":true,"tenant":{"alias":"admin","displayName":"Global admin >>>>>>>> server"}} >>>>>>>> >>>>>>>> It seems its broken in Safari and Chrome, on Firefox I get the >>>>>>>> login >>>>>>>> screen. So I might be ok, now that the install is up. Do you want a >>>>>>>> jira or >>>>>>>> github issue for this? >>>>>>>> >>>>>>>> Another question, whats the preferred way to start Hilary so that >>>>>>>> the >>>>>>>> process isn't killed on logout? For Tomcat I use nohup, is that the >>>>>>>> recommended approach here as well? >>>>>>>> >>>>>>>> The command I am using is: node app | bunyan >>>>>>>> >>>>>>>> cheers, >>>>>>>> Steve >>>>>>>> >>>>>>>> >>>>>>>> On Sat, Jul 27, 2013 at 6:11 PM, Nicolaas Matthijs >>>>>>>> <nicolaas.matth...@caret.cam.ac.uk> wrote: >>>>>>>>> >>>>>>>>> Hi Steve, >>>>>>>>> >>>>>>>>> What do you get when you go to <youradminhost>/api/me? >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Nicolaas >>>>>>>>> >>>>>>>>> >>>>>>>>> On 27 Jul 2013, at 08:19, Steve Swinsburg wrote: >>>>>>>>> >>>>>>>>>> Hi all, >>>>>>>>>> >>>>>>>>>> I've run through the install docs (a third time) and am pretty >>>>>>>>>> sure >>>>>>>>>> I >>>>>>>>>> have everything configured properly and all servers started. I >>>>>>>>>> have >>>>>>>>>> started >>>>>>>>>> OAE but when I go to the admin host I configured I get a blank >>>>>>>>>> screen, >>>>>>>>>> however I do see HTML when I view source. >>>>>>>>>> >>>>>>>>>> Everything looks ok in the logs, all INFO messages. >>>>>>>>>> >>>>>>>>>> Any ideas? >>>>>>>>>> >>>>>>>>>> Note this is a remote server. I have DNS records setup to >>>>>>>>>> replace >>>>>>>>>> the >>>>>>>>>> /etc/hosts steps. >>>>>>>>>> >>>>>>>>>> cheers, >>>>>>>>>> Steve >>>>>>>>>> _______________________________________________ >>>>>>>>>> oae-dev mailing list >>>>>>>>>> oae-dev@collab.sakaiproject.org >>>>>>>>>> http://collab.sakaiproject.org/mailman/listinfo/oae-dev >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> oae-dev mailing list >>>>>> oae-dev@collab.sakaiproject.org >>>>>> http://collab.sakaiproject.org/mailman/listinfo/oae-dev >>>>>> >>>> >>>> >> >> _______________________________________________ oae-dev mailing list oae-dev@collab.sakaiproject.org http://collab.sakaiproject.org/mailman/listinfo/oae-dev
