Re: [Dnsmasq-discuss] dnsmasq dies after about 20 minutes

2019-05-14 Thread Roy Marples 

On 14/05/2019 04:54, Steve Lloyd wrote:
I am running dnsmasq on the lastest stretch on a rpi.  For some reason 
dnsmasq dies after about 20 minutes,  I can restart it and it will last 
another 20 minutes.  Any insight on how to fix this would be much 
appreciated.  Here is the status after it dies, followed by the 
resolvconf.conf


...

May 14 03:45:22 nifd.local systemd[1]: dnsmasq.service: Main process 
exited, code=killed, status=11/SEGV
May 14 03:45:22 nifd.local dnsmasq[4488]: /sbin/resolvconf: 7: 
/etc/resolvconf.conf: 208.67.222.123 : not found


...


*HERE IS MY resolvconf.conf file*
# Configuration for resolvconf(8)
# See resolvconf.conf(5) for details

resolv_conf=/etc/resolv.conf
# If you run a local name server, you should uncomment the below line and
# configure your subscribers configuration files below.
name_servers=10.0.1.81 208.67.222.123 208.67.220.123 185.228.168.10 
185.228.169.11


And there's the error. Let me quote resolvconf.conf(5)

DESCRIPTION
 resolvconf.conf is the configuration file for resolvconf(8).  The
 resolvconf.conf file is a shell script that is sourced by 
resolvconf(8),
 meaning that resolvconf.conf must contain valid shell commands. 
Listed
 below are the standard resolvconf.conf variables that may be set. 
If the
 values contain whitespace, wildcards or other special shell 
characters,
 ensure they are quoted and escaped correctly.  See the replace 
variable

 for an example on quoting.

So your line needs to read
name_servers="10.0.1.81 208.67.222.123 208.67.220.123 185.228.168.10 
185.228.169.11"


Roy

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] dnsmasq dies after about 20 minutes

2019-05-14 Thread Geert Stappers 
On Mon, May 13, 2019 at 09:54:27PM -0600, Steve Lloyd wrote:
> I am running dnsmasq on the lastest stretch on a rpi.  For some reason
> dnsmasq dies after about 20 minutes,  I can restart it and it will last
> another 20 minutes.
> Any insight on how to fix this would be much appreciated.

Seen that request.

What not can be seen, because not shown be original poster.

* Power supply of the RPi
* Power connector of the RPi
* How many devices (USB and "shields") are connected to the RPi
* The reason for FIVE name servers
* The reason for THREE resolvers

> Here is the status after it dies, followed by the resolvconf.conf
> 
> *systemctl status dnsmasq*
> â dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
>Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor 
> preset: enabled)
>Active: failed (Result: signal) since Tue 2019-05-14 03:45:22 UTC; 1min 0s 
> ago
>   Process: 4488 ExecStop=/etc/init.d/dnsmasq systemd-stop-resolvconf 
> (code=exited, status=0/SUCCESS)
>   Process: 2448 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf 
> (code=exited, status=0/SUCCESS)
>   Process: 2439 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, 
> status=0/SUCCESS)
>   Process: 2436 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, 
> status=0/SUCCESS)
>  Main PID: 2447 (code=killed, signal=SEGV)
> 
> May 14 03:45:22 nifd.local systemd[1]: dnsmasq.service: Main process exited, 
> code=killed, status=11/SEGV
> May 14 03:45:22 nifd.local dnsmasq[4488]: /sbin/resolvconf: 7: 
> /etc/resolvconf.conf: 208.67.222.123: not found
> May 14 03:45:22 nifd.local dnsmasq[4488]: /sbin/resolvconf: 7: 
> /etc/resolvconf.conf: 208.67.222.123: not found
> May 14 03:45:22 nifd.local dnsmasq[4488]: /sbin/resolvconf: 7: 
> /etc/resolvconf.conf: 208.67.222.123: not found
> May 14 03:45:22 nifd.local dnsmasq[4488]: Too few arguments.
> May 14 03:45:22 nifd.local dnsmasq[4488]: /sbin/resolvconf: 7: 
> /etc/resolvconf.conf: 208.67.222.123: not found
> May 14 03:45:22 nifd.local dnsmasq[4488]: /sbin/resolvconf: 7: 
> /etc/resolvconf.conf: 208.67.222.123: not found
> May 14 03:45:22 nifd.local dnsmasq[4488]: /sbin/resolvconf: 7: 
> /etc/resolvconf.conf: 208.67.222.123: not found
> May 14 03:45:22 nifd.local systemd[1]: dnsmasq.service: Unit entered failed 
> state.
> May 14 03:45:22 nifd.local systemd[1]: dnsmasq.service: Failed with result 
> 'signal'.
> 
> 
> *HERE IS MY resolvconf.conf file*
> # Configuration for resolvconf(8)
> # See resolvconf.conf(5) for details
> 
> resolv_conf=/etc/resolv.conf
> # If you run a local name server, you should uncomment the below line and
> # configure your subscribers configuration files below.
> name_servers=10.0.1.81 208.67.222.123 208.67.220.123 185.228.168.10 
> 185.228.169.11
> 
> # Mirror the Debian package defaults for the below resolvers
> # so that resolvconf integrates seemlessly.
> dnsmasq_resolv=/var/run/dnsmasq/resolv.conf
> pdnsd_conf=/etc/pdnsd.conf
> unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf



Groeten
Geert Stappers
-- 
Leven en laten leven

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

[Dnsmasq-discuss] dnsmasq dies after about 20 minutes

2019-05-13 Thread Steve Lloyd 
I am running dnsmasq on the lastest stretch on a rpi.  For some reason
dnsmasq dies after about 20 minutes,  I can restart it and it will last
another 20 minutes.  Any insight on how to fix this would be much
appreciated.  Here is the status after it dies, followed by the
resolvconf.conf

*systemctl status dnsmasq*
â dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
   Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor
preset: enabled)
   Active: failed (Result: signal) since Tue 2019-05-14 03:45:22 UTC; 1min
0s ago
  Process: 4488 ExecStop=/etc/init.d/dnsmasq systemd-stop-resolvconf
(code=exited, status=0/SUCCESS)
  Process: 2448 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf
(code=exited, status=0/SUCCESS)
  Process: 2439 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited,
status=0/SUCCESS)
  Process: 2436 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited,
status=0/SUCCESS)
 Main PID: 2447 (code=killed, signal=SEGV)

May 14 03:45:22 nifd.local systemd[1]: dnsmasq.service: Main process
exited, code=killed, status=11/SEGV
May 14 03:45:22 nifd.local dnsmasq[4488]: /sbin/resolvconf: 7:
/etc/resolvconf.conf: 208.67.222.123: not found
May 14 03:45:22 nifd.local dnsmasq[4488]: /sbin/resolvconf: 7:
/etc/resolvconf.conf: 208.67.222.123: not found
May 14 03:45:22 nifd.local dnsmasq[4488]: /sbin/resolvconf: 7:
/etc/resolvconf.conf: 208.67.222.123: not found
May 14 03:45:22 nifd.local dnsmasq[4488]: Too few arguments.
May 14 03:45:22 nifd.local dnsmasq[4488]: /sbin/resolvconf: 7:
/etc/resolvconf.conf: 208.67.222.123: not found
May 14 03:45:22 nifd.local dnsmasq[4488]: /sbin/resolvconf: 7:
/etc/resolvconf.conf: 208.67.222.123: not found
May 14 03:45:22 nifd.local dnsmasq[4488]: /sbin/resolvconf: 7:
/etc/resolvconf.conf: 208.67.222.123: not found
May 14 03:45:22 nifd.local systemd[1]: dnsmasq.service: Unit entered failed
state.
May 14 03:45:22 nifd.local systemd[1]: dnsmasq.service: Failed with result
'signal'.


*HERE IS MY resolvconf.conf file*
# Configuration for resolvconf(8)
# See resolvconf.conf(5) for details

resolv_conf=/etc/resolv.conf
# If you run a local name server, you should uncomment the below line and
# configure your subscribers configuration files below.
name_servers=10.0.1.81 208.67.222.123 208.67.220.123 185.228.168.10
185.228.169.11

# Mirror the Debian package defaults for the below resolvers
# so that resolvconf integrates seemlessly.
dnsmasq_resolv=/var/run/dnsmasq/resolv.conf
pdnsd_conf=/etc/pdnsd.conf
unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss