Running milter proxy worker on a unix socket with self scan, can't connect to upstream

583 views
Skip to first unread message

David Wahlund

unread,
Aug 25, 2017, 6:27:05 AM8/25/17
to rspamd
Hi
Accordning to documentation. If I use the proxy worker in self scan mode I can disable the normal worker. However, the proxyworker is reporting connection problems to localhost. I thought the proxy would handle self scans "internally". 

2017-08-25 11:00:30 #91758(rspamd_proxy) rspamd_inet_address_connect: connect 127.0.0.1:11333 failed: 61, 'Connection refused'
2017-08-25 11:00:30 #91758(rspamd_proxy) <da759c>; proxy; proxy_send_master_message: cannot connect upstream: default(127.0.0.1)
2017-08-25 11:00:30 #91758(rspamd_proxy) rspamd_inet_address_connect: connect [::1]:11333 failed: 61, 'Connection refused'
2017-08-25 11:00:30 #91758(rspamd_proxy) <da759c>; proxy; proxy_send_master_message: cannot connect upstream: default(127.0.0.1)
2017-08-25 11:00:30 #91758(rspamd_proxy) rspamd_inet_address_connect: connect [::1]:11333 failed: 61, 'Connection refused'
2017-08-25 11:00:30 #91758(rspamd_proxy) <da759c>; proxy; proxy_send_master_message: cannot connect upstream: default(::1)
2017-08-25 11:00:30 #91758(rspamd_proxy) rspamd_inet_address_connect: connect 127.0.0.1:11333 failed: 61, 'Connection refused'
2017-08-25 11:00:30 #91758(rspamd_proxy) <da759c>; proxy; proxy_send_master_message: cannot connect upstream: default(::1)
2017-08-25 11:00:30 #91758(rspamd_proxy) rspamd_inet_address_connect: connect 127.0.0.1:11333 failed: 61, 'Connection refused'
2017-08-25 11:00:30 #91758(rspamd_proxy) <da759c>; proxy; proxy_send_master_message: cannot connect upstream: default(127.0.0.1)
2017-08-25 11:00:30 #91758(rspamd_proxy) <da759c>; proxy; proxy_send_master_message: cannot connect to upstream, maximum retries has been reached: 6

So, the 11333 port is the normal worker port. If I start the normal worker on that port eveything works fine. Does that mean I should NOT stop the normal worker?

Now, I want to use unix sockets. But setting hosts="/var/db/rspamd/worker.sock" gives the error:
2017-08-25 12:21:04 #6017(rspamd_proxy) rspamd_inet_address_connect: connect unix:/var/db/rspamd/worker.sock failed: 22, 'Invalid argument'
2017-08-25 12:21:04 #6017(rspamd_proxy) <4a1b5f>; proxy; proxy_send_master_message: cannot connect upstream: default(/var/db/rspamd/worker.sock)

How do I specify a socket upstream to the proxy worker?

-David

Thomas Leuxner

unread,
Aug 25, 2017, 12:10:15 PM8/25/17
to rsp...@googlegroups.com
* David Wahlund <david....@gmail.com> 2017.08.25 12:27:

> How do I specify a socket upstream to the proxy worker?

Hi David,

here are some examples:

https://www.rspamd.com/doc/workers/

Regards
Thomas
signature.asc

David Wahlund

unread,
Aug 25, 2017, 3:32:34 PM8/25/17
to rspamd, t...@leuxner.net


On Friday, August 25, 2017 at 6:10:15 PM UTC+2, Thomas Leuxner wrote:
* David Wahlund <david....@gmail.com> 2017.08.25 12:27:

> How do I specify a socket upstream to the proxy worker?

Hi David,

here are some examples:

Well, yea I know. I am using sockets. But I was wondering specifically about sockets for upstream connections from the proxy and whether I needed the normal worker or not.
 

https://www.rspamd.com/doc/workers/

Regards
Thomas

Patrick Pichon

unread,
Aug 28, 2017, 11:21:28 AM8/28/17
to rspamd, t...@leuxner.net
Valid question for redis server for instance .
Reply all
Reply to author
Forward
0 new messages