Rails 将挂起任何请求

发布于 2025-01-11 06:02:57 字数 1185 浏览 7 评论 0原文

对于 Rails 6.0.3.5 API，运行 rails s 时，这是我得到的输出：

    rails s
    /home/fito/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/railties-6.0.3.6/lib/rails/app_loader.rb:53: warning: Insecure world writable dir /mnt/c in PATH, mode 040777
    => Booting Puma
    => Rails 6.0.3.5 application starting in development 
    => Run `rails server --help` for more startup options
    Puma starting in single mode...
    * Version 3.12.6 (ruby 2.6.5-p114), codename: Llamas in Pajamas
    * Min threads: 5, max threads: 5
    * Environment: development
    * Listening on tcp://localhost:3000
    Use Ctrl-C to stop

并且，在发送任何查询后，它只是挂起，没有向终端或development.log 文件提供任何其他输出：

例如，当向 localhost:3000 地址发送简单的 GET 查询时：

Started GET "/" for ::1 at 2022-03-01 10:52:35 -0500
Started GET "/" for ::1 at 2022-03-01 10:52:56 -0500

发送任何请求后都会出现一个新的日志行，但没有其他行打印到输出或日志文件中，我真的不知道如何调试问题是因为这。我已经尝试将这一行添加到development.rb 文件中：

  config.eager_load = true

这并没有解决挂起问题。

我将提供所需的任何其他信息。

原文

For a rails 6.0.3.5 API, when running rails s this is the output I get:

    rails s
    /home/fito/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/railties-6.0.3.6/lib/rails/app_loader.rb:53: warning: Insecure world writable dir /mnt/c in PATH, mode 040777
    => Booting Puma
    => Rails 6.0.3.5 application starting in development 
    => Run `rails server --help` for more startup options
    Puma starting in single mode...
    * Version 3.12.6 (ruby 2.6.5-p114), codename: Llamas in Pajamas
    * Min threads: 5, max threads: 5
    * Environment: development
    * Listening on tcp://localhost:3000
    Use Ctrl-C to stop

And, after sending any query, it just hangs without any additional output to the terminal or to the development.log file:

For example, when sending simple GET queries to the localhost:3000 address:

Started GET "/" for ::1 at 2022-03-01 10:52:35 -0500
Started GET "/" for ::1 at 2022-03-01 10:52:56 -0500

A new log line appears after sending any request, but no additional lines are printed to the output or to the log files and I really don't know how to debug the issue because of this. I already tried adding this line to the development.rb file: