过时会话问题?SSL会话中无法分配新会话

I’m not sure what’s up here; it might be a bug. I have a couple of sites that are getting spurious errors like these:

2021/09/29 12:46:34 [alert] 11364#11364: *1226080 could not allocate new session in SSL session shared cache "SSL" while SSL handshaking, client: x.x.42.250, server: 0.0.0.0:443

One one of them I contrived to increase max sessions like this:

  after_bundle_exec:
    - replace:
       filename: "/etc/nginx/nginx.conf"
       from: "  worker_connections 768;"
       to: "  worker_connections 1280;"
  after_letsencrypt:
    - replace:
       filename: "/etc/nginx/letsencrypt.conf"
       from: "  worker_connections 768;"
       to: "  worker_connections 1280;"

I thought that it had fixed it (didn’t see any such errors the next day), but now I’m seeing them again on that site.

This is somewhat out of my wheelhouse, but my best guess is that somehow a bunch of connections are staying active rather than being dropped and nginx is running out of sessions?

Both are standard installs and don’t have especially high traffic. One is a 4GB something on AWS the other an 8GB DO droplet (about 40K pageviews/day). I’ve got other sites with much more traffic and I don’t remember ever seeing this before, so I’m wondering if there is something new going on here.

又发生这种情况了。我看到 /etc/nginx/conf.d/discourse.conf 中的 ssl_session_timeout 设置为 1d。为什么它会从 默认值10m 更改为这个值?

我也在日志中看到了这些——数量不多但它们确实出现了。你是否找到了关于那个配置更改的任何信息,或者你是否为自己改回了更短的时间范围?

我们可以将缓存大小从 1MB 增加到大约 40MB。据我所知,它需要与超时时间同步,而我们只增加了一个而没有增加另一个。

2 个赞

这说得通。改变缓存大小这件事有人处理了吗?