System Log filling up fast

[Munce31]

Hi 

 

My log on my dashboard is showing at 79% full. I ran the diagnostics (I've attached this) and have found that a PCIE bus error is spamming my syslog. 

Jul  3 07:25:35 Hawkie kernel: pcieport 0000:00:1b.4:   device [8086:a32c] error status/mask=00000001/00002000
Jul  3 07:25:35 Hawkie kernel: pcieport 0000:00:1b.4:    [ 0] RxErr                  (First)
Jul  3 07:25:36 Hawkie kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4
Jul  3 07:25:36 Hawkie kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Jul  3 07:25:36 Hawkie kernel: pcieport 0000:00:1b.4:   device [8086:a32c] error status/mask=00000001/00002000
Jul  3 07:25:36 Hawkie kernel: pcieport 0000:00:1b.4:    [ 0] RxErr                  (First)
Jul  3 07:25:39 Hawkie kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4
Jul  3 07:25:39 Hawkie kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)

 

Device [8086:a32c] is in reference to the following:

IOMMU group 7:[8086:a32c] 00:1b.4 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 (rev f0)

My question is: How can I find out what is plugged into port #21 and stop it from spamming my syslog files?

 

Thanks in advance,

Munce31

hawkie-diagnostics-20190703-1057.zip

[BRiT]

You could attempt a reboot to get back to sanity and then at the beginning of a normal system boot up there might be a devices list in the syslog, hopefully something more than what the lspci command provides.

 

All the syslog included are just that error message over and over.

Edited July 3, 2019 by BRiT

[Munce31]

21 hours ago, BRiT said:

You could attempt a reboot to get back to sanity and then at the beginning of a normal system boot up there might be a devices list in the syslog, hopefully something more than what the lspci command provides.

 

All the syslog included are just that error message over and over.

I rebooted the server. This has appeared to fix it.

 

It has been at least 24 hours and the log file remains at 1% of capacity.

 

Hopefully it stays that way for a while.

 

Thanks👍

[BRiT]

Now that you're back at a sanity point, try the following commands, to show by connection in a tree format. You might need additional information from a basic 'lspci' to add context to the tree format (-t), sometimes it might only display the ids, but sometimes it will include enough info when -v is also specified.

 

lspci -tv

[Munce31]

On 7/4/2019 at 11:45 PM, BRiT said:

Now that you're back at a sanity point, try the following commands, to show by connection in a tree format. You might need additional information from a basic 'lspci' to add context to the tree format (-t), sometimes it might only display the ids, but sometimes it will include enough info when -v is also specified.

 

lspci -tv

Hi BRiT

 

My log still remains at 1% of capacity, which is good. 

 

However, I did run the command you specified:

-[0000:00]-+-00.0  Intel Corporation 8th Gen Core 8-core Desktop Processor Host Bridge/DRAM Registers [Coffee Lake S]
           +-02.0  Intel Corporation UHD Graphics 630 (Desktop 9 Series)
           +-12.0  Intel Corporation Cannon Lake PCH Thermal Controller
           +-14.0  Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller
           +-14.2  Intel Corporation Cannon Lake PCH Shared SRAM
           +-14.3  Intel Corporation Wireless-AC 9560 [Jefferson Peak]
           +-16.0  Intel Corporation Cannon Lake PCH HECI Controller
           +-17.0  Intel Corporation Cannon Lake PCH SATA AHCI Controller
           +-1b.0-[01]--
           +-1b.4-[02]----00.0  Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981
           +-1c.0-[03]--
           +-1d.0-[04]----00.0  Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981
           +-1f.0  Intel Corporation Z390 Chipset LPC/eSPI Controller
           +-1f.3  Intel Corporation Cannon Lake PCH cAVS
           +-1f.4  Intel Corporation Cannon Lake PCH SMBus Controller
           +-1f.5  Intel Corporation Cannon Lake PCH SPI Controller
           \-1f.6  Intel Corporation Ethernet Connection (7) I219-V

Appears to be one of my NVme SSD's. As the log hasn't gone crazy, i'll continue to monitor and report back here if the log starts to go crazy again. 

 

Thanks