CSCvk25565 - RV34x <error>dnsmasq: failed to parse lease database, invalid line

[PaulHammons]

I am experiencing this on build 1.0.2.16 also.  Same error message:  dnsmasq: failed to parse lease database, invalid line:

[cwatson]

I have this problem on Firmware Version 1.0.02.16 as well.

dnsmasq: failed to parse lease database, invalid line: [ [[ addr2line aps_load_stats ar as asdclient avc-deviceos-metadata.sh avc-metadata.sh awk basename blink_usb1.sh blink_usb2.sh board_check.sh boardutil bootup_Upgrade bunzip2 bwmgmt-trigger bwmgmtd bzcat c++filt c2s-rpc call_home_agent callhome....

[PaulHammons]

Still happening on firmware 1.0.03.15

[pgrey]

Yeah, the bug itself: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvk25565, is closed, with status "Terminated".

The bug makes it look like it's just a "customer irritation", but what it doesn't capture, is that it FILLS THE SMALL-ISH LOG, with these failures, making it tricky to diagnose "real issues".

Can anyone with an active (probably business) account please request to re-activate it? I'm using my RV340 on in a residential setup, so I'm not paying the $/year, for the filtering features (and the ability to file issues).

[Mark30]

Still happens on 1.0.03.18.

I don't know if Cisco is just sitting back asleep at the wheel but every product in the RV series of routers have so many bus I don't know where to start listing them all.

[kkiesow]

I just upgraded to 1.0.03.19 and I still have this issue. This is filling up my syslog server. Please address this!

[PaulHammons]

Same here, still filling all my logs with this useless data.  The update was supposed to fix it, and didn't.

[pgrey]

This 100% fixed it, for me, making the logs VERY usable, at long-last (with or without a syslog-server).

Did you reboot ALL your router(s), switch(es), and other network control devices (AP-controllers, etc), after upgrading?  There could be something else, that's repeating these, or causing other (possibly actual) DNSMasq messages...

For me, I went from 3-4/minute of the false DNSMasq errors, to maybe a few messages an hour, if that, sometimes I go a couple of hours in-between

This is using warning-level, as the log-level, obviously if you have "info" or "debug" messages enabled, you'll still see a LOT of "noise", or possibly real errors -those messages are great for other debugging, at times, but if they're enabled, constantly, the logs get a but unwieldy, again.

I was pretty hyper-critical of this bug (I put details into several threads here, and talked to Cisco), but I'm actually fine with the bug being closed here, it sure appears to be fixed, to me.

[PaulHammons]

Here is my entire log for the last 24 hours, alerts or higher.  Definitely not fixed and still flooding my logs.  Maybe less often than before.

2020-09-13T18:06:13-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-13T18:06:13-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600091808 74:81:14:6b:ce:5b 192.168.1.120 ...
2020-09-13T18:35:17-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-13T18:35:17-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600098620 64:16:66:02:da:6e 192.168.1.140 ...
2020-09-13T17:37:09-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-13T17:37:09-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600091808 74:81:14:6b:ce:5b 192.168.1.120 ...
2020-09-13T09:21:57-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-13T09:21:57-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600051456 74:81:14:6b:ce:5b 192.168.1.120 ...
2020-09-13T09:44:27-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-13T09:44:27-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600051456 74:81:14:6b:ce:5b 192.168.1.120 ...
2020-09-13T08:24:46-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-13T08:24:46-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600051456 74:81:14:6b:ce:5b 192.168.1.120 ...
2020-09-13T08:52:54-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-13T08:52:54-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600051456 74:81:14:6b:ce:5b 192.168.1.120 ...
2020-09-13T07:06:56-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-13T07:06:56-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600051456 74:81:14:6b:ce:5b 192.168.1.120 ...
2020-09-13T07:35:59-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-13T07:35:59-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600051456 74:81:14:6b:ce:5b 192.168.1.120 ...
2020-09-13T07:58:30-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-13T07:58:30-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600051456 74:81:14:6b:ce:5b 192.168.1.120 ...
2020-09-13T06:40:40-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-13T06:40:40-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600051456 74:81:14:6b:ce:5b 192.168.1.120 ...
2020-09-12T23:51:33-04:00 <alert>Webfilter: INFO : Freeing old LocalDB memory !!!!
2020-09-12T23:51:33-04:00 <alert>Webfilter: INFO : Updated LocalDB memory !!!!
2020-09-12T22:25:32-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-12T22:25:32-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600009431 b8:81:98:3e:34:4c 192.168.1.125 ...
2020-09-12T21:03:56-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-12T21:03:56-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600009431 b8:81:98:3e:34:4c 192.168.1.125 ...
2020-09-12T21:33:00-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-12T21:33:00-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600009431 b8:81:98:3e:34:4c 192.168.1.125 ...
2020-09-12T21:59:16-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-12T21:59:16-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600009431 b8:81:98:3e:34:4c 192.168.1.125 ...
2020-09-12T20:08:36-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-12T20:08:36-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600009431 b8:81:98:3e:34:4c 192.168.1.125 ...
2020-09-12T20:37:40-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-12T20:37:40-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600009431 b8:81:98:3e:34:4c 192.168.1.125 ...
2020-09-12T19:10:27-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-12T19:10:27-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600009431 b8:81:98:3e:34:4c 192.168.1.125 ...
2020-09-12T19:38:35-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-12T19:38:35-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600009431 b8:81:98:3e:34:4c 192.168.1.125 ...
2020-09-12T19:53:35-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-12T19:53:35-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600009431 b8:81:98:3e:34:4c 192.168.1.125 ...
2020-09-12T18:02:55-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-12T18:02:55-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600004922 b8:d7:af:86:7d:ae 192.168.1.103 ...
2020-09-12T18:17:55-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-12T18:17:55-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600004922 b8:d7:af:86:7d:ae 192.168.1.103 ...
2020-09-12T18:40:26-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-12T18:40:26-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600009431 b8:81:98:3e:34:4c 192.168.1.125 ...
2020-09-12T18:55:26-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-12T18:55:26-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600009431 b8:81:98:3e:34:4c 192.168.1.125 ...
2020-09-12T17:19:47-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-12T17:19:47-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600004922 b8:d7:af:86:7d:ae 192.168.1.103 ...
2020-09-12T17:47:54-04:00 <error>dnsmasq: failed to allocate -1 bytes
2020-09-12T17:47:54-04:00 <error>dnsmasq: failed to parse lease database, invalid line: 01:00:12:4e:29:01:57 1600004922 b8:d7:af:86:7d:ae 192.168.1.103 ...

[pgrey]

Pretty sure those are valid, at least the ones with the MAC mentioned (I'd be looking at that MAC/IP, to see if something is "odd" there, too).

Before the fix, you'd get 3-4/minute (sometimes more, before I did a reset/restore, on an older firmware, I was getting about 20/minute).

So, at 24 hours of logging, you'd get ~5000 DNSMasq (mostly false) warnings, assuming about 3.5/minute (close enough for this).

Also, previously, these were false-warnings, not errors, the ones that stacked up, and hosed the logs.

DNS is going to log some issues, for failures, until you sort out what that MAC/IP issue is...

[cybergrl74]

I too see these issues on RV345 firmware 1.00.03.20

restarted all switches and router and still same errors

Cisco needs to step in here!

[nagrajk1969]

Hi All

Since this issue is happening,I had this point that came in my mind:

1. have you also enabled/configured DHCPv6 server (on the lan-vlans-side) on the router for multiple IPv6 Hosts to get configured thru the dhcpv6??

2. If yes, in case you do have IPv6 hosts also in your network, Do you see the issue if you use Router-Advertisement instead?