Re: [Sqlgrey-users] IPv6 issue

On 03/17/2018 09:42:41 PM, Will Lowe wrote:

> I recently upgraded my Fedora distro server to 27 and rebuilt my mail 
> server. But when I try to start sqlgrey I get the following:
> 
> 
> Mar 17 17:05:29 www.xxxxxxxxx.xxx systemd[1]: Started SQLgrey Postfix 
> Grey-listing Policy service.
> Mar 17 17:05:29 www.xxxxxxxxx.xxx sqlgrey[30294]: Resolved 
> [localhost]:2501 to [127.0.0.1]:2501, IPv4
> Mar 17 17:05:29 www.xxxxxxxxx.xxx sqlgrey[30294]: Resolved 
> [localhost]:2501 to [::1]:2501, IPv6
> Mar 17 17:05:29 www.xxxxxxxxx.xxx sqlgrey[30294]: Binding to TCP port 
> 2501 on host 127.0.0.1 with IPv4
> Mar 17 17:05:29 www.xxxxxxxxx.xxx sqlgrey[30294]: Binding to TCP port 
> 2501 on host ::1 with IPv6
> Mar 17 17:05:29 www.xxxxxxxxx.xxx sqlgrey[30294]: 2018/03/17-17:05:29 
> Can't connect to TCP port 2501 on ::1 [Address family not supported 
> by
> 
> protocol]
>                                                           at line 64
> in 
> file /usr/local/share/perl5/Net/Server/Proto/TCP.pm
> Mar 17 17:05:29 www.xxxxxxxxx.xxx sqlgrey[30294]: 2018/03/17-17:05:29 
> Server closing!
> Mar 17 17:05:29 www.xxxxxxxxx.xxx systemd[1]: sqlgrey.service: Main 
> process exited, code=exited, status=1/FAILURE
> Mar 17 17:05:29 www.xxxxxxxxx.xxx systemd[1]: sqlgrey.service: Unit 
> entered failed state.
> Mar 17 17:05:29 www.xxxxxxxxx.xxx systemd[1]: sqlgrey.service: Failed 
> with result 'exit-code'.
> 
> I have IPv6 disabled on this server. Is there an option I can use to 
> cause sqlgrey to not bind to an IPv6 address?

Use the "inet" config option and write 127.0.0.1 instead of
localhost.  Or use a  Unix socket which is slightly more secure and 
efficient.

Karl <ko...@me...>
Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein