Puma::Server::UNPACK_TCP_STATE_FROM_TCP_INFO [英] Puma::Server::UNPACK_TCP_STATE_FROM_TCP_INFO

问题描述

我成功地在我的 FreeBSD 服务器上安装了一个 rails 应用程序，但是当我测试 rails s -e production 或 rails s -e development 时，我得到 Read: # 发送请求后来自 Puma 服务器

I succefully installed a rails app on my FreeBSD server but when I test rails s -e production or rails s -e development I get Read: #<NameError: uninitialized constant Puma::Server::UNPACK_TCP_STATE_FROM_TCP_INFO> from the Puma server after sending request

我在某处错过了一步?

附注.我将 Rails6 与 SqlLite3 一起使用

PS. I use Rails6 with SqlLite3

config/puma.rb

config/puma.rb

# Puma can serve each request in a thread from an internal thread pool.
# The `threads` method setting takes two numbers: a minimum and maximum.
# Any libraries that use thread pools should be configured to match
# the maximum value specified for Puma. Default is set to 5 threads for minimum
# and maximum; this matches the default thread size of Active Record.
#
max_threads_count = ENV.fetch("RAILS_MAX_THREADS") { 5 }
min_threads_count = ENV.fetch("RAILS_MIN_THREADS") { max_threads_count }
threads min_threads_count, max_threads_count

# Specifies the `port` that Puma will listen on to receive requests; default is 3000.
#
port        ENV.fetch("PORT") { 3000 }

# Specifies the `environment` that Puma will run in.
#
environment ENV.fetch("RAILS_ENV") { "development" }

# Specifies the `pidfile` that Puma will use.
pidfile ENV.fetch("PIDFILE") { "tmp/pids/server.pid" }

# Specifies the number of `workers` to boot in clustered mode.
# Workers are forked web server processes. If using threads and workers together
# the concurrency of the application would be max `threads` * `workers`.
# Workers do not work on JRuby or Windows (both of which do not support
# processes).
#
# workers ENV.fetch("WEB_CONCURRENCY") { 2 }

# Use the `preload_app!` method when specifying a `workers` number.
# This directive tells Puma to first boot the application and load code
# before forking the application. This takes advantage of Copy On Write
# process behavior so workers use less memory.
#
# preload_app!

# Allow puma to be restarted by `rails restart` command.
plugin :tmp_restart

推荐答案

我刚刚制作了似乎有效的猴子补丁.(这个问题发生在 FreeBSD 上，而不是在 Mac OS X 上)

I just made monkey patch that seems to work. (This problem happens on FreeBSD, not on Mac OS X)

将此内容放在初始化文件中.例如:config/initializers/puma_missing_constant_monkey_patch.rb.

Place this content in an initializer file. For example: config/initializers/puma_missing_constant_monkey_patch.rb.

Rails.application.config.after_initialize do
  if defined?(::Puma) && !Object.const_defined?('Puma::Server::UNPACK_TCP_STATE_FROM_TCP_INFO')
    ::Puma::Server::UNPACK_TCP_STATE_FROM_TCP_INFO = "C".freeze
  end
end

它只是定义了缺失的常量.我不知道它是否会破坏其他东西.另一方面，Puma 使用未定义的常量.这个常量在 Puma (lib/puma/server.rb) 中的定义是有条件的.

It just defines the missing constant. I've got no clue if it breaks something else. On the other hand Puma uses a constant that isn't defined. The define of this constant in Puma (lib/puma/server.rb) is conditional.

这篇关于Puma::Server::UNPACK_TCP_STATE_FROM_TCP_INFO的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！