使用 Radiant(RoR CMS)进行 500 秒、超时和重定向循环

发布于 2024-09-28 13:03:07 字数 1748 浏览 5 评论 0原文

我正在努力建立并运行一个简单的 CMS 网站,但无法通过安装阶段。我已经断断续续地研究这个项目超过 4 天了,我对这个项目感到精疲力尽,失去了动力。

总结一下我的痛苦:无论我做什么,我都会不断遇到重定向循环和 FCGI 超时。不幸的是,我从未接触过 Ruby、RoR 应用程序或 CGI,因此我缺乏解决这个问题的调试经验。

一些详细信息

  • 主机:Godaddy 共享 Linux、SSH 访问、非 java 服务器
  • Ruby 版本:2.2.2
  • Gem 版本:1.8(根据 帮助
  • 我所有网站的托管根目录是 /var/chroot/home/content/i/h/a/[name]/html/ 。这确实有一个 .htaccess 文件,但它不会影响任何内容
  • 我的域名指向 /var/chroot/home/content/i/h/a/[name]/html/ radiant.domain.biz/public/

您出现以下两个错误。 默认 .htaccess 文件会发生这种情况:

[2010 年 10 月 20 日星期三 16:39:13] [错误] [客户端 [ip]] mod_rewrite:已达到内部重定向的最大数量。假设配置错误。如有必要,请使用“RewriteOptions MaxRedirects”增加限制。

这是一个库存的 .htaccess,甚至在其他网站上也被推荐,所以这个循环真的让我很困惑。不知道为什么,我几乎放弃了为什么,因为我无权访问重写日志,并且由于资源有限,我没有必要的开发环境设置。

所以我修改了它并在重写引擎打开后立即放置 RewriteBase / 并得到了:

[2010 年 10 月 20 日星期三 16:40:25] [错误] [客户端 [ip]] FastCGI: 通讯 使用(动态)服务器 “/var/chroot/home/content/i/h/a/[名称]/html/radiant.domain.biz/public/dispatch.fcgi” 中止:(第一次读取)空闲超时(60 秒)

[2010 年 10 月 20 日星期三 16:40:25] [错误] [客户端 [ip]] FastCGI: 收到不完整的标头(0 字节) 从服务器 “/var/chroot/home/content/i/h/a/[名称]/html/radiant.domain.biz/public/dispatch.fcgi”

我认为这意味着它只是部分工作,但启动时出现问题。我已经验证了我的database.yml 设置,它们都很好。我在开发和生产模式下进行了测试,但无济于事,并且日志文件都是空的。

我能想到的唯一可能做的事情是我试图手动修复尝试安装时遇到的错误。我确实设法通过 修复它指南在这里,但它可能会损坏某些东西。我不确定是什么。

这真的让我很困惑,因为我以前从未处理过这种错误。所以对于我的问题:什么会导致这种错误以及如何修复它?

I'm struggling to get a simple CMS website up and running but can't get past the installation stage. I've been working on this off and on over 4 days and am getting burnt out and demotivated on the project.

To summerise my pains: I keep getting Redirect loops and FCGI timeouts no matter what I do. Unfortunatly I've never touched Ruby, RoR apps, or CGI so I lack the debugging experience to figure this out.

Some details

  • Host: Godaddy Shared Linux, SSH access, Non-java server
  • Ruby version: 2.2.2
  • Gem version: 1.8 (manually set per Help)
  • Hosting root for all my sites is /var/chroot/home/content/i/h/a/[name]/html/ . This does have an .htaccess file but it doesn't affect anything
  • My domain points to /var/chroot/home/content/i/h/a/[name]/html/
    radiant.domain.biz/public/

You have the following two errors that occur. This occurs with the default .htaccess file:

[Wed Oct 20 16:39:13 2010] [error] [client [ip]] mod_rewrite: maximum number of internal redirects reached. Assuming configuration error. Use 'RewriteOptions MaxRedirects' to increase the limit if neccessary.

This is a stock .htaccess thats even recommended on other sites, so the loop really confuses me. No idea why, and I've pretty much given up on why since I don't have access to a rewrite log and I don't have a necessary dev environment setup due to limited resources.

So I modified it and just put RewriteBase / right after the rewrite engine turns on and got this:

[Wed Oct 20 16:40:25 2010] [error]
[client [ip]] FastCGI: comm
with (dynamic) server
"/var/chroot/home/content/i/h/a/[name]/html/radiant.domain.biz/public/dispatch.fcgi"
aborted: (first read) idle timeout (60
sec)

[Wed Oct 20 16:40:25 2010]
[error] [client [ip]] FastCGI:
incomplete headers (0 bytes) received
from server
"/var/chroot/home/content/i/h/a/[name]/html/radiant.domain.biz/public/dispatch.fcgi"

I assume that means its just partially working but somethings wrong when starting up. I've verified my database.yml settings and they are all good. I've tested when in dev and production mode to no avail, and the log files are all empty.

The only thing I can think of that might of done something is a bug I tried to manually fix an error I encountered when trying to install. I did manage to fix it by following the guide here, but it may of broken something. I'm not sure what though.

This really confuses me as I've never dealt with this kind of error before. So for my question: What would cause this kind of error and how can I fix it?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

抱着落日 2024-10-05 13:03:07

如果您确实想使用 Radiant,您可以考虑使用 Heroku,它们是一个 Rails 托管平台,提供免费产品,能够处理 Radiant 安装。我的个人网站就使用了这样的设置。

他们在 http:// blog.heroku.com/archives/2009/3/26/radiant_cms_in_5_minutes_or_less/

显然,您需要首先使用 Heroku 帐户进行排序,但这也非常简单。

如果你能完全避免的话,我真的不会使用 GoDaddy 作为托管提供商,而且我真的不明白你有什么理由不能移动托管服务商。即使您通过他们注册了域名,您仍然可以在其他地方托管您的网站,这正是我所做的。

If you really want to use Radiant, you could look at using Heroku, they are a Rails could hosting platform, with a free product that is more than capable of handling a Radiant installation. I use just such a setup for my personal website.

They have a quick quide to getting Radiant setup on a heroku account at http://blog.heroku.com/archives/2009/3/26/radiant_cms_in_5_minutes_or_less/

Obviously you'll need to get sorted with a Heroku account first, but that's pretty simple as well.

I really wouldn't use GoDaddy as a hosting provider if you can at all avoid it, and I don't really see any reason why you can't move hoster. Even if you have a domain registered through them you can still host your site somewhere else, that's exactly what I do.

不喜欢何必死缠烂打 2024-10-05 13:03:07

不推荐使用 FCGI,并且在 Linux 上很少见。这表明 godaddy 可能不是一个可行的 Rails 主机。有很多证据支持这一说法。请阅读此帖子:http://www.sitepoint.com/forums/showthread。 php?t=666111。类似的还有很多。谷歌搜索“rails godaddy”时,大多数人都会遇到问题。

我会认真考虑切换到更加支持 Rails 的主机,或者如果您确实被锁定在一家托管公司,而托管不是他们的主要业务,请考虑他们的按钮式 CMS 安装之一(可能基于 PHP)。

我唯一能想到的另一件事是运行一个更常见的独立 Rails 服务器,比如 Mongrel,并为其设置反向代理,但我不确定 godaddy 是否有办法让你做到这一点。

FCGI is not recommended, and is very uncommon on linux. This is a sign that godaddy may not be a viable Rails host. There is much evidence to back up this claim. Please read this thread: http://www.sitepoint.com/forums/showthread.php?t=666111. There are many others like it. Google searches for 'rails godaddy' bring up mostly people having problems.

I'd seriously think about switching to a more Rails-aware host, or if you really are locked in to a hosting company where hosting is not their primary business, consider one of their pushbutton CMS installations (likely PHP-based).

The only other thing I can think of to try is running a more common standalone rails server like Mongrel and setting up a reverse proxy to it, but I'm not sure if godaddy will have the means for you to do that.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文