public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Restarting dhcp or adding a host leads to "could not parse line"-errors in '/var/log messages'
Date: Sat, 13 Jul 2019 10:20:26 +0200	[thread overview]
Message-ID: <c6d58414-47ec-e8ed-ccd2-1a50dfe486cf@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2918 bytes --]

Hi,

Sorry, but we're at it again...

DHCP-Configuration:
No addresspool, only fixed leases, working fine, no problems during
operation. And I mean it. NO problems! All clients are operational.

But a few days after adding a new host to fixed leases, I stumbled upon
a whole lot of error lines in '/var/log/messages'. One host, one line.

***SNIP***
dhcp[3480]: Could not parse line: on,[HOSTADRESS],[HOSTNAME],localdomain,on
***SNAP***

Today I tested this on a testmachine with a fresh install (Core 134):

- Activated dhcp (dhcp.cgi), added two fixed leases, just for fun.
- Added one host (hosts.cgi), page reloads and stays "Waiting for ...".
- Added second host (hosts,cgi), page reloads and stays "Waiting for
..." and the new host is not shown. No errors in
'/var/log/httpd/error_log/'!

- After playing a while with the testmachine I looked at
'/var/log/messages' and found a lot of 'could not parse line' errors
again. One error line for each host. Seems to be the same on my
production machine. ;-(

***SNIP***
dhcp[3480]: Could not parse line: on,192.168.100.50,test1,localdomain,on
dhcp[3480]: Could not parse line: on,192.168.100.50,test1,localdomain,on
dhcp[3480]: Could not parse line: on,192.168.100.50,test1,localdomain,on
dhcp[3480]: Could not parse line: on,192.168.100.50,test1,localdomain,on
dhcp[3480]: Could not parse line: on,192.168.100.50,test,localdomain,on
dhcp[3480]: Could not parse line: on,192.168.100.50,test1,localdomain,on
dhcp[3480]: Could not parse line: on,192.168.100.50,test,localdomain,on
dhcp[3480]: Could not parse line: on,192.168.100.51,test1,localdomain,on
dhcp[3480]: Could not parse line: on,192.168.100.50,test,localdomain,on
dhcp[3480]: Could not parse line: on,192.168.100.51,test1,localdomain,on
dhcp[3480]: Could not parse line: on,192.168.100.50,test,localdomain,on
dhcp[3480]: Could not parse line: on,192.168.100.51,test1,localdomain,on
dhcp[3480]: Could not parse line: on,192.168.100.53,test3,localdomain,on
***SNAP***

And this happens every time I restart 'dhcp' or add/edit a host.

Current '/var/ipfire/main/hosts' on testmachine contains:

***SNIP***
on,192.168.100.50,test0,localdomain,on
on,192.168.100.51,test1,localdomain,on
on,192.168.100.52,test2,localdomain,on
***SNAP***

Restarting 'dhcp' or editing a host gives me (e.g):

***SNIP***
11:06:50 dhcpd: Wrote 0 deleted host decls to leases file.
11:06:50 dhcpd: Wrote 0 new dynamic host decls to leases file.
11:06:50 dhcpd: Wrote 0 leases to leases file.
11:06:50 dhcpd: Server starting service.
11:06:50 dhcp[9159]: Could not parse line:
on,192.168.100.50,test0,localdomain,on
11:06:50 dhcp[9159]: Could not parse line:
on,192.168.100.51,test1,localdomain,on
11:06:50 dhcp[9159]: Could not parse line:
on,192.168.100.52,test2,localdomain,on
***SNAP***

'dhcp' and fixed leases are working though!

Can anyone confirm or has a hint were to look? I didn't find a grip on
this yet.

Best,
Matthias

             reply	other threads:[~2019-07-13  8:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-13  8:20 Matthias Fischer [this message]
2019-07-13 10:57 ` Matthias Fischer
2019-07-13 11:12   ` Matthias Fischer
2019-07-14 14:38     ` [PATCH] unbound-dhcp-leases-bridge: handle PTR generation parameter Peter Müller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c6d58414-47ec-e8ed-ccd2-1a50dfe486cf@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox