Here is the ami I used, which I believe is 12.04: http://thecloudmarket.com/image/ami-7747d01e--ubuntu-images-ubuntu-precise-12-04-amd64-server-20130204
Thanks. Harry On Oct 28, 2013, at 1:54 PM, Branden Visser <[email protected]> wrote: > This is the error: > > """ > Error: Execution of '/usr/bin/apt-get -q -y -o > DPkg::Options::=--force-confold install fonts-international' returned > 100: Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > fonts-international : Depends: fonts-mikachan but it is not installable > """ > > Which says that the package fonts-mikachan is not installable. Perhaps > Ubuntu cannot find it. What version of ubuntu are you running on? > > Thanks, > Branden > > On Mon, Oct 28, 2013 at 1:37 PM, Harry Wang <[email protected]> wrote: >> Hi Branden, >> >> Thanks a lot for your reply - I will try that. I attached the full log in my >> previous email and attach it with this email again. >> >> Yes. There were a bunch of errors, which I cannot understand based on my >> limited knowledge of Vagrant/Puppet :) >> >> Thanks again. >> >> Harry >> >> >> >> On Oct 28, 2013, at 1:29 PM, Branden Visser <[email protected]> wrote: >> >>> Hi Harry, I have put some responses inline below: >>> >>> On Mon, Oct 28, 2013 at 12:42 PM, Harry Wang <[email protected]> wrote: >>>> Hi, >>>> >>>> I find another issue: >>>> c3: etherpad does not work with the following error >>>> >>>> [2013-10-28T16:36:13.296Z] ERROR: etherpad/2733 on ip-10-151-75-70: Could >>>> not create an etherpad group. (contentId=c:tenant1:ek98wKX-4) >>>> err: { >>>> "code": 4, >>>> "message": "no or wrong API Key" >>>> } >>>> >>> >>> You'll need to make sure you have an APIKEY.txt file in /opt/etherpad >>> that contains just a complex string key, and also ensure that the >>> config.js value "config.etherpad.apikey" matches that value. Odd that >>> puppet didn't set these for you, as it should [1][2]. I would >>> recommend ensuring that puppet completed successfully -- is there any >>> red text output when you run puppet? >>> >>>> After that I have to manually do the following: >>>> >>>> b1. create /opt/files folder manually on the AWS machine >>> >>> Puppet should have done this for you [3]. It's possible it didn't >>> complete successfully. >>> >>>> b2. start Hilary manually at /opt/oae by running sudo node app.js | >>>> node_modules/.bin/bunyan >>>> >>> >>> If puppet completes successfully, it places the init script in >>> /etc/init.d/hilary [4]. If you want to get it the rest of the way >>> manually, you can copy the template from [5] into >>> /etc/init/hilary.conf and replace the placeholder areas (<% ... %>) >>> with your information. >>> >>>> The problems I have are: >>>> >>>> c1. once I close the terminal that running sudo node app.js | >>>> node_modules/.bin/bunyan, the server goes down and shows 502 error: I tried >>>> to use setsid or nohup but they did not work >>> >>> Placing the service script into /etc/init will allow it to start as a >>> daemon. I'm not sure why nohup isn't working here, did you background >>> the process? "nohup node app.js &" >>> >>>> c2. the preview does not seem to work. It shows "Processing this file. Grab >>>> some tea and sit back." forever. >>>> >>> >>> Is there an error in the logs? Given the number of things that appear >>> to have failed I would not be surprised if something else did not >>> install properly that the preview processor needed. >>> >>> As mentioned, would be good to get into the puppet logs to ensure it >>> ran successfully. Did it give some output? >>> >>> Also, keep in mind that any changes you make to application >>> configuration files directly will get overridden the next time puppet >>> runs. >>> >>> Hope that helps, >>> Branden >>> >>> [1] >>> https://github.com/oaeproject/puppet-hilary/blob/master/modules/hilary/templates/config.js.erb#L381 >>> [2] >>> https://github.com/oaeproject/puppet-hilary/blob/master/modules/etherpad/manifests/init.pp#L66 >>> [3] >>> https://github.com/oaeproject/puppet-hilary/blob/master/modules/hilary/manifests/init.pp#L100 >>> [4] >>> https://github.com/oaeproject/puppet-hilary/blob/master/modules/hilary/manifests/init.pp#L147 >>> [5] >>> https://github.com/oaeproject/puppet-hilary/blob/master/modules/hilary/templates/upstart_hilary.conf.erb >>> [6] >>> https://github.com/oaeproject/puppet-hilary/blob/master/provisioning/vagrant/init.sh#L63 >> >> _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
