Messages

1

24.7 Production Series / Re: 24.7.6 unbound no longer showing client queries

« on: October 11, 2024, 06:51:06 am »

Ouch, that makes my issue look pretty tame. Unbound is running for me and appears to be working aside from pulling up logs for specific clients. I'll keep an eye out for that too.

Just clarifying, but you're saying you also are experiencing my issue?

2

24.7 Production Series / 24.7.6 unbound no longer showing client queries

« on: October 11, 2024, 04:48:05 am »

Hi,

After the update, individual client queries are not displayed when clicking to show details of individual clients. I'm able to see Unbound queries under "Details" as they come in, but when I click on a client on the "Overview" page, it shows "No results found".

3

24.1 Legacy Series / Re: Kernel panic at 3am daily and during health checks

« on: August 01, 2024, 07:50:28 pm »

I used your tutorial successfully, but no change in behavior.

Great news though: I updated to the latest 24.7_9 firmware offered to me, and the kernel panics have disappeared! I wish I knew exactly what in the update solved the issue, but it might just continue to be a mystery.

4

24.1 Legacy Series / Re: Kernel panic at 3am daily and during health checks

« on: July 16, 2024, 08:01:43 pm »

I had the chance to swap RAM with my other box, and the issue persists with different RAM on the same machine, which appears to rule out the RAM.

I noticed I did not attach the entire panic report, so maybe this will be of some use to somebody.

5

24.1 Legacy Series / Re: Kernel panic at 3am daily and during health checks

« on: July 12, 2024, 08:55:15 am »

Apologies, been busy but still experiencing issues here.

Output:

SMBIOS 3.3 present.

Handle 0x000A, DMI type 17, 40 bytes
Memory Device
   Array Handle: 0x0009
   Error Information Handle: Not Provided
   Total Width: 64 bits
   Data Width: 64 bits
   Size: 32 GB
   Form Factor: SODIMM
   Set: None
   Locator: Channel-1-DIMM-0
   Bank Locator: BANK 0
   Type: DDR4
   Type Detail: Unknown Synchronous
   Speed: 3200 MT/s
   Manufacturer: Kingston
   Serial Number: a6229aae
   Asset Tag: Channel-1-DIMM-0-AssetTag
   Part Number: KF3200C20S4/32GX
   Rank: 2
   Configured Memory Speed: 3200 MT/s
   Minimum Voltage: 1.2 V
   Maximum Voltage: 1.2 V
   Configured Voltage: 1.2 V

Same RAM as my other box. Coreboot is a newer version I believe, but will need to verify that when I get the chance. I will not be able to attempt a RAM swap anytime soon, but that could end up being a time-saving answer in the long run.

I'm wondering (if)/hoping it's a configuration issue. Anything else I can provide to help the troubleshoot?

Thanks for your help

6

24.1 Legacy Series / Re: Kernel panic at 3am daily and during health checks

« on: July 02, 2024, 11:59:29 pm »

Thank you!! 

It does not display anything I can tell being useful for us besides BIOS version. I attached screenshot.

But I know I am using x2 16 GB Kingston Impact DDR4-3200 SO-DIMM modules.

7

24.1 Legacy Series / Kernel panic at 3am daily and during health checks

« on: July 02, 2024, 10:49:15 pm »

Hi,

I've noticed a few different threads with folks having similar symptoms, but I'll add my issue here separately. I attached the log of the panic and can share more if needed. I would like some assistance because I'm afraid that the frequent panics will end up damaging my installation or hardware.

I have a Protectli VP2420 with the latest firmware. In fact, it's a brand new box. It's experiencing kernel panics daily at 3am. A reproducible kernel panic also occurs during a health check when checking packages. I assume they are related.

I am only using ACME and Chrony plugins, and Suratica. I am using a LAGG with VLANs. It is connected to a Unifi switch->Unifi Pro 6 (wireless), which is sending tagged/untagged traffic to Protectli.

On an unrelated note, I have another box with the same exact hardware and firmware, but different configuration (using Zenarmor and Suratica). I have been using this box for 6 months with no issues. It is not experiencing kernel panics. It is not using VLANs or LAGG.

Thank you for your help!