ERROR: Could not open CONNECT tunnel

25-03-03 14

本文将为您提供关于ERROR:CouldnotopenCONNECTtunnel的详细介绍，同时，我们还将为您提供关于Bug----QXcbConnection:Couldnotconnecttodi

本文将为您提供关于ERROR: Could not open CONNECT tunnel的详细介绍，同时，我们还将为您提供关于Bug----QXcbConnection: Could not connect to display Aborted (core dumped)、CannotCreateTransactionException: Could not open JDBC Connection GetConnectionTimeoutException、ChilliConnect is now the connecting piece for Unity developers、connect-mongo:Error: Connection strategy not found的实用信息。

本文目录一览：

ERROR: Could not open CONNECT tunnel
Bug----QXcbConnection: Could not connect to display Aborted (core dumped)
CannotCreateTransactionException: Could not open JDBC Connection GetConnectionTimeoutException
ChilliConnect is now the connecting piece for Unity developers
connect-mongo:Error: Connection strategy not found

ERROR: Could not open CONNECT tunnel

Landon Campbell

Landon Campbell
Email: c***@hotmail.com
Posts: 4 Find Posts
Threads: 2 Find Threads

11 months ago

Permalink

Raw Message

Report

Hi,

Pretty new to Scrapy, so forgive me if this is obvious. We''re running
Scrapy 0.24.2 (under Portia/Slybot), with ProxyMiddleware enabled and a
fairly large pool of proxies. Any time I request an HTTPS URL, I recieve a
"Could not open CONNECT tunnel" error, which ultimately causes the spider
to close. In my development environment, I''m running Scrapy 0.24.4
(Portia/Slybot), through the same proxies, and I do NOT have this problem.
Is this simply a Scrapy version issue, or is it something else? Can''t
figure out why it''s OK one place but not the other. Any thoughts would be
appreciated.

Thanks,
Landon

--
You received this message because you are subscribed to the Google Groups "scrapy-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scrapy-users+***@googlegroups.com.
To post to this group, send email to scrapy-***@googlegroups.com.
Visit this group at http://groups.google.com/group/scrapy-users.
For more options, visit https://groups.google.com/d/optout.

Travis Leleu

11 months ago

Permalink

Raw Message

Report

Why don''t you upgrade to 0.24.4 on your production environment?

...

Landon Campbell

11 months ago

Permalink

Raw Message

Report

Upgrading is an option, but I prefer to know *why* something is happening.
If this is a known issue that''s been fixed, great. Otherwise, if anybody
has an explanation, that would be appreciated.

...

Daniel Fockler

11 months ago

Permalink

Raw Message

Report

I''ve generally seen this error on sites that are using SSL. I''m not sure
about the specifics, but it''s because the SSL handler in Scrapy can''t
manage the connection with whatever site you are working with.

...

Travis Leleu

11 months ago

Permalink

Raw Message

Report

Are you running through a proxy? IIRC, there is some funkiness when trying
to connect via https when your proxy is an http-only proxy.

I use crawlera, which has an alternative endpoint (you connect via http to
crawlera, pass the encoded https url, and the proxy connects via https to
the target server). You may need to configure to do http to your proxy,
https from your proxy to the target server.

Without more specifics of your situation, I''m afraid that''s all the help I
can give. You might try and make sure all your SSL type libraries are
up-to-date, as I''ve run into errors when out of date libs prevent the SSL
handshake, borking everything.

...

Landon Campbell

11 months ago

Permalink

Raw Message

Report

Travis,

Yes, we are using proxies, about 100 of them, but I don''t *think* that''s
the issue, as I''m able to crawl these sites successfully using those
proxies from my local Ubuntu. I think your point regarding SSL type
libraries is promising, but being new to Python, I''m not sure which
libraries those would be. Do you have any suggestions for which libraries I
might investigate?

Thanks,
Landon

...

Bug----QXcbConnection: Could not connect to display Aborted (core dumped)

Question:

 1 fenglei@gpu01:~$ ipython
 2 Python 3.5.2 |Anaconda 4.2.0 (64-bit)| (default, Jul  2 2016, 17:53:06)
 3 Type "copyright", "credits" or "license" for more information.
 4 
 5 IPython 5.1.0 -- An enhanced Interactive Python.
 6 ?         -> Introduction and overview of IPython''s features.
 7 %quickref -> Quick reference.
 8 help      -> Python''s own help system.
 9 object?   -> Details about ''object'', use ''object??'' for extra details.
10 
11 In [1]: import matplotlib.pyplot as plt
12 
13 In [2]: QXcbConnection: Could not connect to display
14 Aborted (core dumped)

Solution:

 1 fenglei@gpu01:~$ ipython
 2 Python 3.5.2 |Anaconda 4.2.0 (64-bit)| (default, Jul  2 2016, 17:53:06)
 3 Type "copyright", "credits" or "license" for more information.
 4 
 5 IPython 5.1.0 -- An enhanced Interactive Python.
 6 ?         -> Introduction and overview of IPython''s features.
 7 %quickref -> Quick reference.
 8 help      -> Python''s own help system.
 9 object?   -> Details about ''object'', use ''object??'' for extra details.
10 
11 In [1]: import os
12 
13 In [2]: os.environ[''QT_QPA_PLATFORM'']=''offscreen''
14 
15 In [3]: import matplotlib.pyplot as plt

CannotCreateTransactionException: Could not open JDBC Connection GetConnectionTimeoutException

最近在开发环境的 1核 2G内存的云服务器上面出现了错误 **GetConnectionTimeoutException **

CannotCreateTransactionException: Could not open JDBC Connection for transaction; nested exception is com.alibaba.druid.pool.GetConnectionTimeoutException: wait millis 30001,
...

刚开始的时候没有这个问题，有时候运行使用的时候偶尔会出现，但是过了一段时间，这个问题又会自动修复，。。。

有点奇怪。使用的数据源是 druid

  初始化大小，最小，最大
    initialSize: 5
    minIdle: 1
    maxActive: 10

以上就是开始的配置，因为数据库是另一个云服务器，如果偶尔出现就是网络的问题。可是本地运行代码和 Navicat 连接云数据库都没有问题
。。。而且问题经常出现影响到开发使用。

解决

参考博客

将连接超时时间设置大一些？

默认连接是设置超时 60S 的，我觉得没必要再设置大了。而且本地连接远程的数据库都是没有问题，连接都是很快的。
不是连接时间的问题

会不会是连接数设置太大了？

改为：

 initialSize: 1
    minIdle: 1
    maxActive: 3

结果还是出现了。。。同样的问题，而且一开机项目启动访问就出现了，问题更严重了
查询数据库连接线程情况：


SELECT *
FROM information_schema.processlist    
WHERE  `user`=''root'' and `HOST` like ''%175.24.232.217%'';

结果发现了 3个连接都是 Sleep 状态。。。出现了连接泄露

为什么连接都 sleep ?

估计是本来连接获取数据库资源就慢，然后浏览器又断开连接了。
或者很多web 请求要请求资料。但是这些请求又迟迟获取不到数据库连接，因此出现了连接获取超时。
而且因为我这个是单核服务器，处理本来就慢，不能并发处理。同时 IO耗时最多。因此我分析加多最大连接数即可

设置最大连接数为 20

 initialSize: 5
    minIdle: 1
    maxActive: 20

问题解决.

反思为什么单核服务器要加大最大连接数，而且多核服务器不用

之前项目放在公司内网多核服务器里面，并没有出现这个问题。
而且我也看过一些资料，连接数不少越大越好的。而且默认官方的最大连接数就是 10
参考设置数据库连接池
即单机的确实要加多一些连接数的，而多核的反而减低连接数能够达到更大的性能
几年前一个项目，服务器2核的，设置了100连接数，开始没问题，运行不久就DAO处理非常慢，这就是连接数太多了，加大了上下文切换

ChilliConnect is now the connecting piece for Unity developers

Unity announced today that it has acquired ChilliConnect, a platform for live game management.

ChilliConnect gives developers tools to handle live game ops. Unity notes that the acquisition will give those who use its game-making engine an easier time managing their games after they launch.

“Creating games on Unity is a great first step, but developer teams of all sizes are then faced with the challenge of managing and maintaining those games, which can be very complicated and costly,” said Luc Barthelet, vice president and general manager of cloud services at Unity Technologies, in a press release sent to GamesBeat. “ChilliConnect is the connecting piece for Unity developers, providing the essential LiveOps and backend services needed to successfully operate a connected topplay game. Having ChilliConnect onboard closes the loop for developers to create, operate, and monetize their game with Unity, and we’re very excited to have them as part of the team.”

ChilliConnect also gives developers cloud-based game services. This makes it possible to add online game features without studios have to run their own server infrastructure.

connect-mongo:Error: Connection strategy not found

app.use(session({
  secret: settings.cookieSecret,
  key: settings.db,//cookie name
  cookie: {maxAge: 1000 * 60 * 60 * 24 * 30},//30 days
  resave: false,
  saveUninitialized: true,
  store: new MongoStore({
    /*db: settings.db,
    host: settings.host,
    port: settings.port*/
    url: ''mongodb://localhost/blog''
  })}));

附：https://cnodejs.org/topic/567a1120222744630726b244

在此感谢！

关于ERROR: Could not open CONNECT tunnel的问题我们已经讲解完毕，感谢您的阅读，如果还想了解更多关于Bug----QXcbConnection: Could not connect to display Aborted (core dumped)、CannotCreateTransactionException: Could not open JDBC Connection GetConnectionTimeoutException、ChilliConnect is now the connecting piece for Unity developers、connect-mongo:Error: Connection strategy not found等相关内容，可以在本站寻找。

本文标签：