Gibberish for hostname in logs since I put on 2.1.4

Moosecall

all of my log entries are showing the following gibberish instead of the hostname

CPE00e06f126c0f-CM8c04ff1ae6a4 lighttpd[77441]: (connections.c.137) (warning) close: 17 Connection reset by peer

I tried changing the hostname to something else and back but still the same. The hostname does seem to show up properly in an SSH session however.

Any ideas?

Moosecall

So this morning I SSH into the firewall and now the prompt is messed up as well

[2.1.4-RELEASE][admin@CPE00e06f126c0f-CM8c04ff1ae6a4]/root(1):

editing the hostname under the general setup tab fixed it, but logs still messed up.

jimp

Perhaps it's being set by DHCP?

clog /var/log/dhcpd.log  | grep -i hostname

Moosecall

Looks like it is DHCP

[2.1.4-RELEASE][admin@CPE00e06f126c0f-CM8c04ff1ae6a4]/root(1): clog /var/log/dhcpd.log | grep -i hostname
Jul 6 05:41:13 lucius dhclient: New Hostname (re0): CPE00e06f126c0f-CM8c04ff1ae6a4
Jul 7 05:41:13 lucius dhclient: New Hostname (re0): CPE00e06f126c0f-CM8c04ff1ae6a4

re0 is my WAN so that is probably the hostname being assigned by my ISP, I guess something changed in 2.1.4 that impacted this? Better question is how to make pfsense ignore that hostname and just use the one I give it. If it matters I am running a 6rd tunnel to my ISP on the WAN as well.

jimp

garga put in a fix for this last night, you can use the System Patches package to apply the patch to correct the behavior.

https://github.com/pfsense/pfsense/commit/7b15d22967a9f9fefe7b8b11fa2d68c762c55219

Moosecall

That did the trick, thank you.