Re: Why does Heroku always find unresolved dependencies?
This is from my deployment message. I dunno...is it normal? Writing objects: 100% (13/13), 1.88 KiB, done. Total 13 (delta 10), reused 0 (delta 0) - Heroku receiving push - Rails app detected - Detected Rails is not set to serve static_assets Installing rails3_serve_static_assets... done - Gemfile detected, running Bundler version 1.0.7 Unresolved dependencies detected; Installing... Using --without test:development:staging Fetching source index for http://rubygems.org/ On Jan 29, 6:50 am, Volkan Unsal spockspla...@gmail.com wrote: I haven't installed any gems since the last time I deployed, but Heroku keeps thinking there is something new I suppose, and that significantly slows down my deployment time. How can I make sure that I don't get this message? Unresolved dependencies detected; Installing... -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Help getting app to start running?
I've put the output from $ heroku logs on pastie for reference: http://pastie.org/1511022 I have an app that runs beautifully on ruby 1.9.2 and rails 3.0.3 in my local rvm environment, but after pushing to heroku and doing heroku stack:migrate to bamboo-mri-1.9.2 my app will not start. I don't really fully understand the output I'm getting from the logs, especially given that it appears to be trying to load something from ruby 1.9.1. Has anyone seen this before? Any idea why the app is crashing on heroku but running on local? I can't even tell what file it's trying to load and not finding...and WHY is it trying to load 1.9.1 if I'm running 1.9.2?? Any help would be much appreciated... -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Downgrading newrelic
I'm using NewRelic Gold right now, and want to downgrade to Silver. If I do heroku addons:add newrelic:silver does that downgrade the same account (preserving data), or do I have to remove the gold addon and then add the silver? Thanks, Helder -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Help getting app to start running?
When I tried something similar, I didn't have much luck with migrating a stack. Try creating a new project with 1.9.2 initially and then your push. That may work better. Scott On Sun, Jan 30, 2011 at 12:40 AM, Jason Preston jasonp...@gmail.com wrote: I've put the output from $ heroku logs on pastie for reference: http://pastie.org/1511022 I have an app that runs beautifully on ruby 1.9.2 and rails 3.0.3 in my local rvm environment, but after pushing to heroku and doing heroku stack:migrate to bamboo-mri-1.9.2 my app will not start. I don't really fully understand the output I'm getting from the logs, especially given that it appears to be trying to load something from ruby 1.9.1. Has anyone seen this before? Any idea why the app is crashing on heroku but running on local? I can't even tell what file it's trying to load and not finding...and WHY is it trying to load 1.9.1 if I'm running 1.9.2?? Any help would be much appreciated... -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- Scott http://steamcode.blogspot.com/ -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Help getting app to start running?
Unfortunately it gives me the same error. I even went ahead and commented the group :development blockin my Gemfile just in case there was something I'm requiring for dev that is being left out of production and breaking it...no dice. Just for fun I tried migrating to 1.8.7 to see if it ran -- it does not. The logs produce the same output every time. Anything else I can provide that would help determine what it's even looking for? It boggles my mind that it runs locally - I don't even have ruby 1.9.1 installed... On Jan 30, 8:43 am, Scott LaBounty slabou...@gmail.com wrote: When I tried something similar, I didn't have much luck with migrating a stack. Try creating a new project with 1.9.2 initially and then your push. That may work better. Scott On Sun, Jan 30, 2011 at 12:40 AM, Jason Preston jasonp...@gmail.com wrote: I've put the output from $ heroku logs on pastie for reference: http://pastie.org/1511022 I have an app that runs beautifully on ruby 1.9.2 and rails 3.0.3 in my local rvm environment, but after pushing to heroku and doing heroku stack:migrate to bamboo-mri-1.9.2 my app will not start. I don't really fully understand the output I'm getting from the logs, especially given that it appears to be trying to load something from ruby 1.9.1. Has anyone seen this before? Any idea why the app is crashing on heroku but running on local? I can't even tell what file it's trying to load and not finding...and WHY is it trying to load 1.9.1 if I'm running 1.9.2?? Any help would be much appreciated... -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- Scotthttp://steamcode.blogspot.com/ -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Help getting app to start running?
You seem to be missing whatever provides Digest. Does it run locally if you create a blank gem set in RVM (rvm create 1.9.2@blank - make sure you don't have default gems by running gem list in that gemset). Oren On Sun, Jan 30, 2011 at 9:56 AM, Jason Preston jasonp...@gmail.com wrote: Unfortunately it gives me the same error. I even went ahead and commented the group :development blockin my Gemfile just in case there was something I'm requiring for dev that is being left out of production and breaking it...no dice. Just for fun I tried migrating to 1.8.7 to see if it ran -- it does not. The logs produce the same output every time. Anything else I can provide that would help determine what it's even looking for? It boggles my mind that it runs locally - I don't even have ruby 1.9.1 installed... On Jan 30, 8:43 am, Scott LaBounty slabou...@gmail.com wrote: When I tried something similar, I didn't have much luck with migrating a stack. Try creating a new project with 1.9.2 initially and then your push. That may work better. Scott On Sun, Jan 30, 2011 at 12:40 AM, Jason Preston jasonp...@gmail.com wrote: I've put the output from $ heroku logs on pastie for reference: http://pastie.org/1511022 I have an app that runs beautifully on ruby 1.9.2 and rails 3.0.3 in my local rvm environment, but after pushing to heroku and doing heroku stack:migrate to bamboo-mri-1.9.2 my app will not start. I don't really fully understand the output I'm getting from the logs, especially given that it appears to be trying to load something from ruby 1.9.1. Has anyone seen this before? Any idea why the app is crashing on heroku but running on local? I can't even tell what file it's trying to load and not finding...and WHY is it trying to load 1.9.1 if I'm running 1.9.2?? Any help would be much appreciated... -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com heroku%2bunsubscr...@googlegroups.comheroku%252bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- Scotthttp://steamcode.blogspot.com/ -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
getting the root of my domain pointed to proxy.heroku.com
This is really a dns question, but my provider isn't being very responsive. What dns record to I need to add, to make the root of my domain (wishgenies.com) point to proxy.heroku.com? I can create a cname for www.wishgenies.com, but I can't do that for the domain root. Thanks! -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: getting the root of my domain pointed to proxy.heroku.com
You can't - you need to setup A records. http://docs.heroku.com/custom-domains#dns-setup On Sun, Jan 30, 2011 at 10:10 AM, JDeville jeffdevi...@gmail.com wrote: This is really a dns question, but my provider isn't being very responsive. What dns record to I need to add, to make the root of my domain (wishgenies.com) point to proxy.heroku.com? I can create a cname for www.wishgenies.com, but I can't do that for the domain root. Thanks! -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Help getting app to start running?
Interesting. I created an empty gemset, typed gem list and got: *** LOCAL GEMS *** rake (0.8.7) rubygems-update (1.4.2) So I started rails server and ran the app WITHOUT running bundle install, and everything worked. This puzzled me. So I typed: Sooper-2:Potluk Jasonp$ which ruby /Users/Jasonp/.rvm/rubies/ruby-1.9.2-p136/bin/ruby So far, so good. Then: Sooper-2:Potluk Jasonp$ which rails /usr/bin/rails which, I'm assuming, is why it's running locally. Does that make sense? I assume I'm supposed to have a rails install WITHIN rvm somehow. I'm going to try and figure out how to do that, and see if it runs locally. If not, then I at least have two consistently broken versions of my app, although if that's the case then I won't know why it isn't running locally either. Sigh. On Jan 30, 10:03 am, Oren Teich o...@heroku.com wrote: You seem to be missing whatever provides Digest. Does it run locally if you create a blank gem set in RVM (rvm create 1.9.2@blank - make sure you don't have default gems by running gem list in that gemset). Oren On Sun, Jan 30, 2011 at 9:56 AM, Jason Preston jasonp...@gmail.com wrote: Unfortunately it gives me the same error. I even went ahead and commented the group :development blockin my Gemfile just in case there was something I'm requiring for dev that is being left out of production and breaking it...no dice. Just for fun I tried migrating to 1.8.7 to see if it ran -- it does not. The logs produce the same output every time. Anything else I can provide that would help determine what it's even looking for? It boggles my mind that it runs locally - I don't even have ruby 1.9.1 installed... On Jan 30, 8:43 am, Scott LaBounty slabou...@gmail.com wrote: When I tried something similar, I didn't have much luck with migrating a stack. Try creating a new project with 1.9.2 initially and then your push. That may work better. Scott On Sun, Jan 30, 2011 at 12:40 AM, Jason Preston jasonp...@gmail.com wrote: I've put the output from $ heroku logs on pastie for reference: http://pastie.org/1511022 I have an app that runs beautifully on ruby 1.9.2 and rails 3.0.3 in my local rvm environment, but after pushing to heroku and doing heroku stack:migrate to bamboo-mri-1.9.2 my app will not start. I don't really fully understand the output I'm getting from the logs, especially given that it appears to be trying to load something from ruby 1.9.1. Has anyone seen this before? Any idea why the app is crashing on heroku but running on local? I can't even tell what file it's trying to load and not finding...and WHY is it trying to load 1.9.1 if I'm running 1.9.2?? Any help would be much appreciated... -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com heroku%2bunsubscr...@googlegroups.comheroku%252Bunsubscribe@googlegroups. com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- Scotthttp://steamcode.blogspot.com/ -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Downgrading newrelic
Thanks! On Sun, Jan 30, 2011 at 5:16 PM, Miles Smith mi...@vimae.com wrote: Try heroku addons:upgrade newrelic:silver Kindof opposite of what you'd think, but that's the way to do it. On Jan 30, 2011 7:17 AM, Helder Ribeiro hel...@gmail.com wrote: I'm using NewRelic Gold right now, and want to downgrade to Silver. If I do heroku addons:add newrelic:silver does that downgrade the same account (preserving data), or do I have to remove the gold addon and then add the silver? Thanks, Helder -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- umamao.com Respostas maduras meetup.com/gweb-unicamp Grupo de Criadores Web da Unicamp twitter.com/obvio171 Mobile: +55 19 9182-7595 -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
If WebSolr search stopped working for you in the past two hours...
About two hours ago I got a message through from Exceptional that a search failed with a RSolr::RequestError. Sure enough, search was down on my site. I checked the twitter feed of WebSolr: http://twitter.com/websolr It didn't seem a coincidence that about the time search stopped working on my site, they tweeted: A misconfiguration on one of our servers has a small number of indexes down. We're working on it. WebSolr has been rock solid for me in recent months and it was the first message on their Twitter feed since 22nd January. Their next Twitter message stated It's fixed now. But even though my account's status page indicated that my index looks ok, I was still getting errors. I was able to fix search on my site by going into the console and reindexing the articles on my site: heroku console Sunspot.index!(Article.all) Stephen PS: According to my accounts page, the number of documents in my index has somehow grown eight times after reindexing, but I'm not going to risk hitting the Destroy this index button and rebuilding it again right at this moment. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Help getting app to start running?
resolved: as part of my user model (built from scrach) I explicitly called require 'Digest' in order to do a one-way hash on user passwords, I'm guessing that was the issue. I discovered that as I fixed my ruby/rails local dev environment, then made a NEW rails app, manually re-generated the models and controllers, and cut-pasted code in segments, deploying periodically to heroku to check that it would work...it now does. Thanks for the help guidance! On Jan 30, 11:09 am, Jason Preston jasonp...@gmail.com wrote: Interesting. I created an empty gemset, typed gem list and got: *** LOCAL GEMS *** rake (0.8.7) rubygems-update (1.4.2) So I started rails server and ran the app WITHOUT running bundle install, and everything worked. This puzzled me. So I typed: Sooper-2:Potluk Jasonp$ which ruby /Users/Jasonp/.rvm/rubies/ruby-1.9.2-p136/bin/ruby So far, so good. Then: Sooper-2:Potluk Jasonp$ which rails /usr/bin/rails which, I'm assuming, is why it's running locally. Does that make sense? I assume I'm supposed to have a rails install WITHIN rvm somehow. I'm going to try and figure out how to do that, and see if it runs locally. If not, then I at least have two consistently broken versions of my app, although if that's the case then I won't know why it isn't running locally either. Sigh. On Jan 30, 10:03 am, Oren Teich o...@heroku.com wrote: You seem to be missing whatever provides Digest. Does it run locally if you create a blank gem set in RVM (rvm create 1.9.2@blank - make sure you don't have default gems by running gem list in that gemset). Oren On Sun, Jan 30, 2011 at 9:56 AM, Jason Preston jasonp...@gmail.com wrote: Unfortunately it gives me the same error. I even went ahead and commented the group :development blockin my Gemfile just in case there was something I'm requiring for dev that is being left out of production and breaking it...no dice. Just for fun I tried migrating to 1.8.7 to see if it ran -- it does not. The logs produce the same output every time. Anything else I can provide that would help determine what it's even looking for? It boggles my mind that it runs locally - I don't even have ruby 1.9.1 installed... On Jan 30, 8:43 am, Scott LaBounty slabou...@gmail.com wrote: When I tried something similar, I didn't have much luck with migrating a stack. Try creating a new project with 1.9.2 initially and then your push. That may work better. Scott On Sun, Jan 30, 2011 at 12:40 AM, Jason Preston jasonp...@gmail.com wrote: I've put the output from $ heroku logs on pastie for reference: http://pastie.org/1511022 I have an app that runs beautifully on ruby 1.9.2 and rails 3.0.3 in my local rvm environment, but after pushing to heroku and doing heroku stack:migrate to bamboo-mri-1.9.2 my app will not start. I don't really fully understand the output I'm getting from the logs, especially given that it appears to be trying to load something from ruby 1.9.1. Has anyone seen this before? Any idea why the app is crashing on heroku but running on local? I can't even tell what file it's trying to load and not finding...and WHY is it trying to load 1.9.1 if I'm running 1.9.2?? Any help would be much appreciated... -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com heroku%2bunsubscr...@googlegroups.comheroku%252Bunsubscribe@googlegroups. com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- Scotthttp://steamcode.blogspot.com/ -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: If WebSolr search stopped working for you in the past two hours...
Hi Stephen, Nick from Websolr here. Indeed, we did have a bit of a hiccup earlier today. The number of indexes affected was relatively small, as it occurred on only one server. Folks that were affected would have been those who added the Websolr add-on between mid-December and mid-January. Some more details, for those curious… It turns out that one of the other indexes on that server was improperly configured. Usually we can handle that case pretty gracefully, but this particular index exposed an edge case in Solr that we weren't previously aware of. Unfortunately, when we reloaded Solr this afternoon during the course of some normal maintenance, this particular configuration error prevented Solr from loading correctly. Hence the errors you experienced. We noticed the problem right away, and after a few minutes of troubleshooting were able to find and deploy a fix for the root cause. That fix has also since been deployed to all of our other servers to prevent this particular case from occurring again in the future. You mentioned some lingering issues… if anyone else experiences any persisting issues I encourage you to open a ticket at http://support.heroku.com/ or http://help.websolr.com/ with your WEBSOLR_URL so we can take a closer look. Also, the issue you mention with your number of documents being much larger than you expect sounds particularly puzzling… I'd definitely be curious to take a look at that, and can possibly help you migrate to a fresh index if that proves necessary. On Sun, Jan 30, 2011 at 4:57 PM, Stephen Cremin asianf...@gmail.com wrote: About two hours ago I got a message through from Exceptional that a search failed with a RSolr::RequestError. Sure enough, search was down on my site. I checked the twitter feed of WebSolr: http://twitter.com/websolr It didn't seem a coincidence that about the time search stopped working on my site, they tweeted: A misconfiguration on one of our servers has a small number of indexes down. We're working on it. WebSolr has been rock solid for me in recent months and it was the first message on their Twitter feed since 22nd January. Their next Twitter message stated It's fixed now. But even though my account's status page indicated that my index looks ok, I was still getting errors. I was able to fix search on my site by going into the console and reindexing the articles on my site: heroku console Sunspot.index!(Article.all) Stephen PS: According to my accounts page, the number of documents in my index has somehow grown eight times after reindexing, but I'm not going to risk hitting the Destroy this index button and rebuilding it again right at this moment. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- Nick Zadrozny http://websolr.com — hassle-free hosted search, powered by Apache Solr -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: If WebSolr search stopped working for you in the past two hours...
Thanks, Nick My search engine did go down again in the past hour and I had to re-index my records once more to fix that. I'm based in Asia where it's Monday morning and my site's busiest time so I'm not going to do anything drastic right now. I'll wipe the index and regenerate it overnight and contact your support if the problem hasn't resolved itself. I've been with you since May 2010, so it may be an unrelated problem. Stephen On 31 January 2011 10:59, Nick Zadrozny n...@onemorecloud.com wrote: Hi Stephen, Nick from Websolr here. Indeed, we did have a bit of a hiccup earlier today. The number of indexes affected was relatively small, as it occurred on only one server. Folks that were affected would have been those who added the Websolr add-on between mid-December and mid-January. Some more details, for those curious… It turns out that one of the other indexes on that server was improperly configured. Usually we can handle that case pretty gracefully, but this particular index exposed an edge case in Solr that we weren't previously aware of. Unfortunately, when we reloaded Solr this afternoon during the course of some normal maintenance, this particular configuration error prevented Solr from loading correctly. Hence the errors you experienced. We noticed the problem right away, and after a few minutes of troubleshooting were able to find and deploy a fix for the root cause. That fix has also since been deployed to all of our other servers to prevent this particular case from occurring again in the future. You mentioned some lingering issues… if anyone else experiences any persisting issues I encourage you to open a ticket at http://support.heroku.com/ or http://help.websolr.com/ with your WEBSOLR_URL so we can take a closer look. Also, the issue you mention with your number of documents being much larger than you expect sounds particularly puzzling… I'd definitely be curious to take a look at that, and can possibly help you migrate to a fresh index if that proves necessary. On Sun, Jan 30, 2011 at 4:57 PM, Stephen Cremin asianf...@gmail.comwrote: About two hours ago I got a message through from Exceptional that a search failed with a RSolr::RequestError. Sure enough, search was down on my site. I checked the twitter feed of WebSolr: http://twitter.com/websolr It didn't seem a coincidence that about the time search stopped working on my site, they tweeted: A misconfiguration on one of our servers has a small number of indexes down. We're working on it. WebSolr has been rock solid for me in recent months and it was the first message on their Twitter feed since 22nd January. Their next Twitter message stated It's fixed now. But even though my account's status page indicated that my index looks ok, I was still getting errors. I was able to fix search on my site by going into the console and reindexing the articles on my site: heroku console Sunspot.index!(Article.all) Stephen PS: According to my accounts page, the number of documents in my index has somehow grown eight times after reindexing, but I'm not going to risk hitting the Destroy this index button and rebuilding it again right at this moment. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- Nick Zadrozny http://websolr.com — hassle-free hosted search, powered by Apache Solr -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: If WebSolr search stopped working for you in the past two hours...
A few more thoughts— It's always handy to harden your applications against potential downtime with any third-party service. Here's how you can accomplish that if you're using Websolr: 1. Queue your writes Elijah Miller has a module to use with DelayedJob: https://gist.github.com/392468 Mat Brown (author of Sunspot) uses the following with Resque: http://gist.github.com/659188 My own version is simple but less comprehensive: http://gist.github.com/530800 Queuing your writes is important lest the Sunspot ActiveRecord callbacks prevent your object from creating or saving successfully. Also, writes to Solr can typically take anywhere from 20–200ms, and there is generally no point in waiting for that to finish before rendering your response. 2. Rescue exceptions for your reads In your controllers, use rescue_from RSolr::RequestError to render a custom action, so your users can see something a bit less disorienting than a 500 message, and you can report the exception in a more controlled fashion. We try to stay on top of announcing outages on our Twitter account, so it's worth checking http://twitter.com/websolr if you notice anything funky going on. If you don't see anything posted up there, you can always feel free to open a ticket and let us know what you're seeing. -- Nick Zadrozny http://websolr.com — hassle-free hosted search, powered by Apache Solr -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Why does Heroku always find unresolved dependencies?
Anyone can help me? This doesn't always happen. My other apps do not find unresolved dependencies every time I deploy, but I don't know what is the difference between them and this. On Jan 30, 5:53 am, Volkan Unsal spockspla...@gmail.com wrote: This is from my deployment message. I dunno...is it normal? Writing objects: 100% (13/13), 1.88 KiB, done. Total 13 (delta 10), reused 0 (delta 0) - Heroku receiving push - Rails app detected - Detected Rails is not set to serve static_assets Installing rails3_serve_static_assets... done - Gemfile detected, running Bundler version 1.0.7 Unresolved dependencies detected; Installing... Using --without test:development:staging Fetching source index forhttp://rubygems.org/ On Jan 29, 6:50 am, Volkan Unsal spockspla...@gmail.com wrote: I haven't installed any gems since the last time I deployed, but Heroku keeps thinking there is something new I suppose, and that significantly slows down my deployment time. How can I make sure that I don't get this message? Unresolved dependencies detected; Installing... -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Why does Heroku always find unresolved dependencies?
Are you using Bundler? Sent from my iPhone On Jan 31, 2011, at 1:14 AM, Volkan Unsal spockspla...@gmail.com wrote: Anyone can help me? This doesn't always happen. My other apps do not find unresolved dependencies every time I deploy, but I don't know what is the difference between them and this. On Jan 30, 5:53 am, Volkan Unsal spockspla...@gmail.com wrote: This is from my deployment message. I dunno...is it normal? Writing objects: 100% (13/13), 1.88 KiB, done. Total 13 (delta 10), reused 0 (delta 0) - Heroku receiving push - Rails app detected - Detected Rails is not set to serve static_assets Installing rails3_serve_static_assets... done - Gemfile detected, running Bundler version 1.0.7 Unresolved dependencies detected; Installing... Using --without test:development:staging Fetching source index forhttp://rubygems.org/ On Jan 29, 6:50 am, Volkan Unsal spockspla...@gmail.com wrote: I haven't installed any gems since the last time I deployed, but Heroku keeps thinking there is something new I suppose, and that significantly slows down my deployment time. How can I make sure that I don't get this message? Unresolved dependencies detected; Installing... -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
