WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Can tinylinux be used as a stable DNS  (Read 6011 times)

Online Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11305
Re: Can tinylinux be used as a stable DNS
« Reply #15 on: April 18, 2023, 11:23:36 PM »
Hi zbs888
...
Code: [Select]
tail /var/log/kernel.log
Apr 19 09:40:07 localhost kernel: myshell (521604): drop_caches: 3
Apr 19 09:51:41 localhost kernel: myshell (527294): drop_caches: 3
Apr 19 10:00:06 localhost kernel: myshell (532878): drop_caches: 3
Apr 19 10:10:17 localhost kernel: myshell (538907): drop_caches: 3
Apr 19 10:20:18 localhost kernel: myshell (547089): drop_caches: 3
Apr 19 10:32:05 localhost kernel: myshell (556228): drop_caches: 3
Apr 19 10:40:06 localhost kernel: myshell (566220): drop_caches: 3
Apr 19 10:50:12 localhost kernel: myshell (576719): drop_caches: 3
...
Why are you constantly dropping caches?

Offline zbs888

  • Newbie
  • *
  • Posts: 42
Re: Can tinylinux be used as a stable DNS
« Reply #16 on: April 18, 2023, 11:42:25 PM »
Hi zbs888
...
Code: [Select]
tail /var/log/kernel.log
Apr 19 09:40:07 localhost kernel: myshell (521604): drop_caches: 3
Apr 19 09:51:41 localhost kernel: myshell (527294): drop_caches: 3
Apr 19 10:00:06 localhost kernel: myshell (532878): drop_caches: 3
Apr 19 10:10:17 localhost kernel: myshell (538907): drop_caches: 3
Apr 19 10:20:18 localhost kernel: myshell (547089): drop_caches: 3
Apr 19 10:32:05 localhost kernel: myshell (556228): drop_caches: 3
Apr 19 10:40:06 localhost kernel: myshell (566220): drop_caches: 3
Apr 19 10:50:12 localhost kernel: myshell (576719): drop_caches: 3
...
Why are you constantly dropping caches?

Dear sir,i am a newbie to Linux.Just because I need to migrate, process, analyze, and store a large number of DNS logs in the database every few minutes, I think clearing the cache every time I finish running this myshell and enter the city is beneficial for keeping the system with more cache to handle other things.

Online Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11305
Re: Can tinylinux be used as a stable DNS
« Reply #17 on: April 19, 2023, 12:01:26 PM »
Hi zbs888
... is beneficial for keeping the system with more cache to handle other things.
The problem with that is it clears the entire cache. You might be clearing large
amounts of frequently used data when you do this. The system will then need to
fetch that data again which may impact the systems response time.

Your system appears to have about 32 Gbytes of RAM, so I doubt you will run out of cache.

Offline zbs888

  • Newbie
  • *
  • Posts: 42
Re: Can tinylinux be used as a stable DNS
« Reply #18 on: April 19, 2023, 08:40:25 PM »
Hi zbs888
... is beneficial for keeping the system with more cache to handle other things.
The problem with that is it clears the entire cache. You might be clearing large
amounts of frequently used data when you do this. The system will then need to
fetch that data again which may impact the systems response time.

Your system appears to have about 32 Gbytes of RAM, so I doubt you will run out of cache.
Hi,Rich,thanks for your help.
Do you mean this problem occurs because I clear the cache every 10 minutes? My system has more than 32GB and 16GB of memory, and the operating mechanism of each machine is the same. I have found that this problem occurs intermittently as many people use it. May I ask if you need to perform any further diagnostic actions to determine the cause of the problem?

Online Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11305
Re: Can tinylinux be used as a stable DNS
« Reply #19 on: April 19, 2023, 09:13:05 PM »
Hi zbs888
... Do you mean this problem occurs because I clear the cache every 10 minutes? ...
I don't know that, but it may be contributing to the problem.

The operating system will flush older unused entries on its own if it needs more space.


Offline zbs888

  • Newbie
  • *
  • Posts: 42
Re: Can tinylinux be used as a stable DNS
« Reply #20 on: April 19, 2023, 09:25:55 PM »
Hi zbs888
... Do you mean this problem occurs because I clear the cache every 10 minutes? ...
I don't know that, but it may be contributing to the problem.

The operating system will flush older unused entries on its own if it needs more space.
Thanks,Rich.I removed Dorp_ Is there anything else to pay attention to when checking the cache script that still has issues?
Code: [Select]
vmstat 1
procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu-----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa st
 1  0      0 24534844   8176 2198516    0    0    47    84   36   22  4  3 92  1  0
 0  0      0 24534844   8176 2198516    0    0     0     0  215   60  0  0 100  0  0
 0  0      0 24534844   8176 2198516    0    0     0     0  240   52  0  0 100  0  0
 0  0      0 24534844   8176 2198516    0    0     0     0  253   44  0  0 100  0  0
 0  0      0 24534592   8176 2198516    0    0     0     8  305   74  0  0 100  0  0
 0  0      0 24534592   8176 2198516    0    0     0     0  319   82  0  0 100  0  0
 0  0      0 24534592   8176 2198516    0    0     0     0  370   73  0  0 100  0  0
 0  0      0 24534592   8176 2198516    0    0     0     0  363   48  0  0 100  0  0
 0  0      0 24534592   8176 2198516    0    0     0     0  409   68  0  0 100  0  0
 0  0      0 24534592   8176 2198516    0    0     0     0  389   86  0  0 100  0  0
 0  0      0 24534592   8180 2198512    0    0     0     4  322   83  0  0 99  0  0
 0  0      0 24534592   8180 2198512    0    0     0     0  373   70  0  0 100  0  0
 0  0      0 24534592   8180 2198512    0    0     0     0  324   52  0  0 100  0  0
 0  0      0 24534592   8180 2198512    0    0     0     0  278   39  0  0 100  0  0


and my crond.log:
Code: [Select]
Apr 20 09:20:00 localhost crond[2490]: USER root pid 408819 cmd /root/shell1
Apr 20 09:21:00 localhost crond[2490]: USER root pid 412708 cmd /root/shell2
Apr 20 09:21:00 localhost crond[2490]: USER root pid 412709 cmd /root/shell3
Apr 20 09:21:00 localhost crond[2490]: USER root pid 412710 cmd /root/shell4
Apr 20 09:22:00 localhost crond[2490]: USER root pid 413146 cmd /root/shell2
Apr 20 09:22:00 localhost crond[2490]: USER root pid 413147 cmd /root/shell3
Apr 20 09:22:00 localhost crond[2490]: USER root pid 413148 cmd /root/shell4
Apr 20 09:23:00 localhost crond[2490]: USER root pid 413589 cmd /root/shell2
Apr 20 09:26:25 localhost crond[2490]: USER root pid 413900 cmd /root/shell3
Apr 20 09:26:25 localhost crond[2490]: USER root pid 413902 cmd /root/shell4
Apr 20 09:26:30 localhost crond[2490]: user root: process already running: /root/shell3
Apr 20 09:26:30 localhost crond[2490]: user root: process already running: /root/shell4
Apr 20 09:26:30 localhost crond[2490]: user root: process already running: /root/shell3
Apr 20 09:26:30 localhost crond[2490]: user root: process already running: /root/shell4
Apr 20 09:26:30 localhost crond[2490]: user root: process already running: /root/shell3
Apr 20 09:26:30 localhost crond[2490]: user root: process already running: /root/shell4
Apr 20 09:26:30 localhost crond[2490]: USER root pid 414214 cmd /root/shell5
Apr 20 09:26:30 localhost crond[2490]: USER root pid 414215 cmd /root/shell6
Apr 20 09:26:30 localhost crond[2490]: USER root pid 414216 cmd /root/shell2
Apr 20 09:27:00 localhost crond[2490]: USER root pid 414538 cmd /root/shell2
« Last Edit: April 19, 2023, 09:32:45 PM by zbs888 »

Online Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11305
Re: Can tinylinux be used as a stable DNS
« Reply #21 on: April 19, 2023, 09:48:37 PM »
Hi zbs888
... Is there anything else to pay attention to when checking the cache script that still has issues? ...
I haven't seen your  cache script  so I can't answer that.

Offline zbs888

  • Newbie
  • *
  • Posts: 42
Re: Can tinylinux be used as a stable DNS
« Reply #22 on: April 19, 2023, 10:07:16 PM »
Hi zbs888
... Is there anything else to pay attention to when checking the cache script that still has issues? ...
I haven't seen your  cache script  so I can't answer that.
Sorry,sir.What I mean is, what other commands do I need to use to check for potential issues?I don't have a clue at all

Online Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11305
Re: Can tinylinux be used as a stable DNS
« Reply #23 on: April 19, 2023, 10:34:14 PM »
Hi zbs888
Add the boot code  syslog  to your boot loader.
When the system faults, grab a copy of  /var/log/messages  and
attach it to your next post. Maybe it will contain something interesting.

Offline zbs888

  • Newbie
  • *
  • Posts: 42
Re: Can tinylinux be used as a stable DNS
« Reply #24 on: April 19, 2023, 11:12:47 PM »
Hi zbs888
Add the boot code  syslog  to your boot loader.
When the system faults, grab a copy of  /var/log/messages  and
attach it to your next post. Maybe it will contain something interesting.
This fault occurs every few tens of minutes. Below is some information about the time the fault occurred. Could you please help me take a look.


Code: [Select]
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz64 panic=3 noapic acpi=ht console=ttyS1,115200 console=ttyS0,115200

Code: [Select]
tail /var/log/messages.log
Apr 20 10:17:16 localhost named[2441]: none:104: 'max-cache-size 90%' - setting to 28952MB (out of 32169MB)
Apr 20 10:17:16 localhost named[2441]: set up managed keys zone for view UNICOM-user, file 'ab05e628ff9a962c.mkeys'
Apr 20 10:17:16 localhost named[2441]: none:104: 'max-cache-size 90%' - setting to 28952MB (out of 32169MB)
Apr 20 10:17:16 localhost named[2441]: set up managed keys zone for view CMCC-user, file '0d52e9253c2aad60.mkeys'
Apr 20 10:17:16 localhost named[2441]: none:104: 'max-cache-size 90%' - setting to 28952MB (out of 32169MB)
Apr 20 10:17:16 localhost named[2441]: set up managed keys zone for view any-user, file 'any-user.mkeys'
Apr 20 10:17:16 localhost named[2441]: none:104: 'max-cache-size 90%' - setting to 28952MB (out of 32169MB)
Apr 20 10:17:16 localhost named[2441]: command channel listening on 127.0.0.1#953
Apr 20 10:17:17 localhost kernel: igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Apr 20 10:18:05 localhost kernel: floppy0: no floppy controllers found


Code: [Select]
tail /var/log/kernel.log
Apr 20 10:16:58 localhost kernel: igb 0000:02:00.0 eth0: renamed from lan1
Apr 20 10:16:58 localhost kernel: igb 0000:03:00.0 eth1: renamed from lan2
Apr 20 10:16:58 localhost kernel: igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Apr 20 10:17:06 localhost kernel: NET: Registered protocol family 10
Apr 20 10:17:06 localhost kernel: Segment Routing with IPv6
Apr 20 10:17:09 localhost kernel: igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Apr 20 10:17:09 localhost kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Apr 20 10:17:13 localhost kernel: ip_local_port_range: prefer different parity for start/end values.
Apr 20 10:17:17 localhost kernel: igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Apr 20 10:18:05 localhost kernel: floppy0: no floppy controllers found


Offline zbs888

  • Newbie
  • *
  • Posts: 42
Re: Can tinylinux be used as a stable DNS
« Reply #25 on: April 24, 2023, 02:57:38 AM »
Hi zbs888
Add the boot code  syslog  to your boot loader.
When the system faults, grab a copy of  /var/log/messages  and
attach it to your next post. Maybe it will contain something interesting.
Code: [Select]
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz64 panic=3 console=ttyS1,115200 console=ttyS0,115200 syslog processor.max_cstate=0 nohz=off intel_idle.max_cstate=0 idle=halt idle=nomwait selinux=0

Code: [Select]
tail kernel.log
Apr 24 10:47:09 localhost kernel: igb 0000:03:00.0 eth2: igb: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Apr 24 10:47:10 localhost kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
Apr 24 10:47:14 localhost kernel: ip_local_port_range: prefer different parity for start/end values.
Apr 24 10:47:17 localhost kernel: igb 0000:03:00.0 eth2: igb: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Apr 24 10:48:05 localhost kernel: floppy0: no floppy controllers found
Apr 24 11:23:25 localhost kernel: igb 0000:03:00.0 eth2: igb: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Apr 24 11:25:20 localhost kernel: TCP: request_sock_TCP: Possible SYN flooding on port 53. Sending cookies.  Check SNMP counters.
Apr 24 11:44:53 localhost kernel: TCP: request_sock_TCP: Possible SYN flooding on port 53. Sending cookies.  Check SNMP counters.
Apr 24 12:43:48 localhost kernel: TCP: request_sock_TCP: Possible SYN flooding on port 53. Sending cookies.  Check SNMP counters.
Apr 24 13:50:22 localhost kernel: TCP: request_sock_TCP: Possible SYN flooding on port 53. Sending cookies.  Check SNMP counters.


I added syslog in grub.conf,when the system faults ,/var/log/message and kernel.log,show nothing.
And i want to lock cpu freq,so i edit my grub.conf " processor.max_cstate=0 nohz=off intel_idle.max_cstate=0 idle=halt idle=nomwait" and reboot,but it's look not work,why?
Code: [Select]
# cat /proc/cpuinfo | grep 'cpu M'
cpu MHz : 968.333
cpu MHz : 974.472
cpu MHz : 961.290
cpu MHz : 949.197
cpu MHz : 955.121
cpu MHz : 959.014
cpu MHz : 963.917
cpu MHz : 940.815
# cat /proc/cpuinfo | grep 'cpu M'
cpu MHz : 1073.077
cpu MHz : 1087.866
cpu MHz : 1061.614
cpu MHz : 1079.117
cpu MHz : 1069.619
cpu MHz : 1057.048
cpu MHz : 1095.803
cpu MHz : 1074.776
# cat /proc/cpuinfo | grep 'cpu M'
cpu MHz : 1040.258
cpu MHz : 1062.527
cpu MHz : 1022.373
cpu MHz : 998.141
cpu MHz : 977.028
cpu MHz : 1057.740
cpu MHz : 1035.175
cpu MHz : 1020.519


Code: [Select]
#  cat /sys/devices/system/cpu/cpuidle/current_driver
none
cat /sys/module/intel_idle/parameters/max_cstate
0


Still wating for resolve the question

Online Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11305
Re: Can tinylinux be used as a stable DNS
« Reply #26 on: April 24, 2023, 12:52:53 PM »
Hi zbs888
Hi zbs888
Add the boot code  syslog  to your boot loader.
When the system faults, grab a copy of  /var/log/messages  and
attach it to your next post. Maybe it will contain something interesting.

 ----- Snip -----

I added syslog in grub.conf,when the system faults ,/var/log/message and kernel.log,show nothing. ...
Are you saying  /var/log/messages  is empty?
Or
Are you saying you looked at  /var/log/messages  and decided it contained nothing important?

Quote
Code: [Select]
Apr 24 11:25:20 localhost kernel: TCP: request_sock_TCP: Possible SYN flooding on port 53. Sending cookies.  Check SNMP counters.
Apr 24 11:44:53 localhost kernel: TCP: request_sock_TCP: Possible SYN flooding on port 53. Sending cookies.  Check SNMP counters.
Apr 24 12:43:48 localhost kernel: TCP: request_sock_TCP: Possible SYN flooding on port 53. Sending cookies.  Check SNMP counters.
Apr 24 13:50:22 localhost kernel: TCP: request_sock_TCP: Possible SYN flooding on port 53. Sending cookies.  Check SNMP counters.
That looks kind of interesting.
What does this command return:
Code: [Select]
sudo sysctl -a 2>&1 | grep -Ei "_syn|backlog|somax|abort"

Offline zbs888

  • Newbie
  • *
  • Posts: 42
Re: Can tinylinux be used as a stable DNS
« Reply #27 on: April 24, 2023, 08:45:21 PM »
Hi zbs888
Hi zbs888
Add the boot code  syslog  to your boot loader.
When the system faults, grab a copy of  /var/log/messages  and
attach it to your next post. Maybe it will contain something interesting.

 ----- Snip -----

I added syslog in grub.conf,when the system faults ,/var/log/message and kernel.log,show nothing. ...
Are you saying  /var/log/messages  is empty?
Or
Are you saying you looked at  /var/log/messages  and decided it contained nothing important?

Quote
Code: [Select]
Apr 24 11:25:20 localhost kernel: TCP: request_sock_TCP: Possible SYN flooding on port 53. Sending cookies.  Check SNMP counters.
Apr 24 11:44:53 localhost kernel: TCP: request_sock_TCP: Possible SYN flooding on port 53. Sending cookies.  Check SNMP counters.
Apr 24 12:43:48 localhost kernel: TCP: request_sock_TCP: Possible SYN flooding on port 53. Sending cookies.  Check SNMP counters.
Apr 24 13:50:22 localhost kernel: TCP: request_sock_TCP: Possible SYN flooding on port 53. Sending cookies.  Check SNMP counters.
That looks kind of interesting.
What does this command return:
Code: [Select]
sudo sysctl -a 2>&1 | grep -Ei "_syn|backlog|somax|abort"
Hi,rich,/var/log/messages save normal named startup message,nothing about any error messages.
Code: [Select]
sysctl -a 2>&1 | grep -Ei "_syn|backlog|somax|abort"
net.core.netdev_max_backlog = 32768
net.core.somaxconn = 32768
net.ipv4.fib_sync_mem = 524288
net.ipv4.tcp_abort_on_overflow = 1
net.ipv4.tcp_max_syn_backlog = 262144
net.ipv4.tcp_syn_retries = 2
net.ipv4.tcp_synack_retries = 2
net.ipv4.tcp_syncookies = 1
net.netfilter.nf_conntrack_tcp_timeout_syn_recv = 5
net.netfilter.nf_conntrack_tcp_timeout_syn_sent = 5

Online Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11305
Re: Can tinylinux be used as a stable DNS
« Reply #28 on: April 24, 2023, 10:21:10 PM »
Hi zbs888
Most of that looks OK.  net.ipv4.tcp_abort_on_overflow  should
probably be set to zero:
Code: [Select]
sudo sysctl -w net.ipv4.tcp_abort_on_overflow=0
Unless you really need IPv6 try adding the boot code:
Code: [Select]
disable_ipv6=1
You might want to check the  config  files for software that uses
the network connection.
Look for settings that involve:
number of connections
queues
backlog

Offline zbs888

  • Newbie
  • *
  • Posts: 42
Re: Can tinylinux be used as a stable DNS
« Reply #29 on: April 25, 2023, 08:48:26 PM »
Hi zbs888
Most of that looks OK.  net.ipv4.tcp_abort_on_overflow  should
probably be set to zero:
Code: [Select]
sudo sysctl -w net.ipv4.tcp_abort_on_overflow=0
Unless you really need IPv6 try adding the boot code:
Code: [Select]
disable_ipv6=1
You might want to check the  config  files for software that uses
the network connection.
Look for settings that involve:
number of connections
queues
backlog
Hi,rich.
I found that after adding syslog to the grub.conf file, there is the following information about MCE in the /var/log/kernel files and /var/log/messages in the past few days. I don't know what the situation is. At present, the frequency of BIND and CROND service freezes is about 30-40 minutes, lasting 4-5 minutes each time. However, this frequency does not match the mce information in the kernel file, which is really confusing.
Code: [Select]
/var/log/kernel.log
Apr 25 15:31:23 localhost kernel: mce: CPU3: Core temperature above threshold, cpu clock throttled (total events = 3167)
Apr 25 15:31:23 localhost kernel: mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 4653)
Apr 25 15:31:23 localhost kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 4653)
Apr 25 15:31:23 localhost kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 4653)
Apr 25 15:31:23 localhost kernel: mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 4647)
Apr 25 15:31:23 localhost kernel: mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 4650)
Apr 25 15:31:23 localhost kernel: mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 4651)
Apr 25 15:31:23 localhost kernel: mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 4652)
Apr 25 15:31:23 localhost kernel: mce: CPU1: Package temperature/speed normal
Apr 25 15:31:23 localhost kernel: mce: CPU7: Package temperature/speed normal
Apr 25 15:31:23 localhost kernel: mce: CPU2: Package temperature/speed normal
Apr 25 15:31:23 localhost kernel: mce: CPU4: Package temperature/speed normal
Apr 25 15:31:23 localhost kernel: mce: CPU5: Package temperature/speed normal
Apr 25 15:31:23 localhost kernel: mce: CPU6: Package temperature/speed normal
Apr 25 15:31:23 localhost kernel: mce: CPU3: Core temperature/speed normal
Apr 25 15:31:23 localhost kernel: mce: CPU0: Package temperature/speed normal
Apr 25 16:01:28 localhost kernel: mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 262)
Apr 25 16:01:28 localhost kernel: mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 4988)
Apr 25 16:01:28 localhost kernel: mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 4989)
Apr 25 16:01:28 localhost kernel: mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 4988)
Apr 25 16:01:28 localhost kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 4989)
Apr 25 16:01:28 localhost kernel: mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 4987)
Apr 25 16:01:28 localhost kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 4989)
Apr 25 16:01:28 localhost kernel: mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 4986)
Apr 25 16:01:28 localhost kernel: mce: CPU6: Package temperature/speed normal
Apr 25 16:01:28 localhost kernel: mce: CPU3: Package temperature/speed normal
Apr 25 16:01:28 localhost kernel: mce: CPU1: Package temperature/speed normal
Apr 25 16:01:28 localhost kernel: mce: CPU0: Package temperature/speed normal
Apr 25 16:01:28 localhost kernel: mce: CPU5: Package temperature/speed normal
Apr 25 16:01:28 localhost kernel: mce: CPU4: Package temperature/speed normal
Apr 25 16:01:28 localhost kernel: mce: CPU2: Core temperature/speed normal
Apr 25 16:01:28 localhost kernel: mce: CPU7: Package temperature/speed normal
Apr 25 16:26:05 localhost kernel: floppy0: no floppy controllers found
Apr 25 16:33:43 localhost kernel: floppy0: no floppy controllers found
Apr 26 00:01:03 localhost kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 287)
Apr 26 00:01:03 localhost kernel: mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 4989)
Apr 26 00:01:03 localhost kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 4992)
Apr 26 00:01:03 localhost kernel: mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 4990)
Apr 26 00:01:03 localhost kernel: mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 4985)
Apr 26 00:01:03 localhost kernel: mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 4992)
Apr 26 00:01:03 localhost kernel: mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 4991)
Apr 26 00:01:03 localhost kernel: mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 4991)
Apr 26 00:01:03 localhost kernel: mce: CPU5: Package temperature/speed normal
Apr 26 00:01:03 localhost kernel: mce: CPU4: Package temperature/speed normal
Apr 26 00:01:03 localhost kernel: mce: CPU7: Package temperature/speed normal
Apr 26 00:01:03 localhost kernel: mce: CPU3: Package temperature/speed normal
Apr 26 00:01:03 localhost kernel: mce: CPU2: Package temperature/speed normal
Apr 26 00:01:03 localhost kernel: mce: CPU6: Package temperature/speed normal
Apr 26 00:01:03 localhost kernel: mce: CPU0: Core temperature/speed normal
Apr 26 00:01:03 localhost kernel: mce: CPU1: Package temperature/speed normal

Code: [Select]
/var/log/messages.log
Apr 26 00:01:02 localhost named[483136]: compiled by GCC 9.2.0
Apr 26 00:01:02 localhost named[483136]: compiled with OpenSSL version: OpenSSL 1.1.1f  31 Mar 2020
Apr 26 00:01:02 localhost named[483136]: linked to OpenSSL version: OpenSSL 1.1.1f  31 Mar 2020
Apr 26 00:01:02 localhost named[483136]: compiled with libxml2 version: 2.9.7
Apr 26 00:01:02 localhost named[483136]: linked to libxml2 version: 20907
Apr 26 00:01:02 localhost named[483136]: compiled with libjson-c version: 0.11
Apr 26 00:01:02 localhost named[483136]: linked to libjson-c version: 0.11
Apr 26 00:01:02 localhost named[483136]: compiled with zlib version: 1.2.11
Apr 26 00:01:02 localhost named[483136]: linked to zlib version: 1.2.11
Apr 26 00:01:02 localhost named[483136]: threads support is enabled
Apr 26 00:01:02 localhost named[483136]: ----------------------------------------------------
Apr 26 00:01:02 localhost named[483136]: BIND 9 is maintained by Internet Systems Consortium,
Apr 26 00:01:02 localhost named[483136]: Inc. (ISC), a non-profit 501(c)(3) public-benefit
Apr 26 00:01:02 localhost named[483136]: corporation.  Support and training for BIND 9 are
Apr 26 00:01:02 localhost named[483136]: available at https://www.isc.org/support
Apr 26 00:01:02 localhost named[483136]: ----------------------------------------------------
Apr 26 00:01:02 localhost named[483136]: adjusted limit on open files from 100000 to 1048576
Apr 26 00:01:02 localhost named[483136]: found 8 CPUs, using 8 worker threads
Apr 26 00:01:02 localhost named[483136]: using 7 UDP listeners per interface
Apr 26 00:01:02 localhost named[483136]: using up to 21000 sockets
Apr 26 00:01:02 localhost named[483136]: loading configuration from '/opt/bind9/etc/named.conf'
Apr 26 00:01:02 localhost named[483136]: reading built-in trust anchors from file '/opt/bind9/etc/bind.keys'
Apr 26 00:01:02 localhost named[483136]: using default UDP/IPv4 port range: [9000, 65000]
Apr 26 00:01:02 localhost named[483136]: using default UDP/IPv6 port range: [9000, 65000]
Apr 26 00:01:02 localhost named[483136]: listening on IPv6 interfaces, port 53
Apr 26 00:01:02 localhost named[483136]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 26 00:01:02 localhost named[483136]: listening on IPv4 interface lo:1, 202.194.98.98#53
Apr 26 00:01:02 localhost named[483136]: listening on IPv4 interface eth2, 202.194.97.134#53
Apr 26 00:01:02 localhost named[483136]: listening on IPv4 interface eth3, 192.168.1.110#53
Apr 26 00:01:02 localhost named[483136]: generating session key for dynamic DNS
Apr 26 00:01:02 localhost named[483136]: sizing zone task pool based on 2845 zones
Apr 26 00:01:02 localhost named[483136]: none:104: 'max-cache-size 90%' - setting to 57995MB (out of 64439MB)
Apr 26 00:01:02 localhost named[483136]: set up managed keys zone for view SDCERNET-user, file 'aafee67691ba58de.mkeys'
Apr 26 00:01:02 localhost named[483136]: none:104: 'max-cache-size 90%' - setting to 57995MB (out of 64439MB)
Apr 26 00:01:02 localhost named[483136]: set up managed keys zone for view EDU-user, file 'd0cc50c716520045.mkeys'
Apr 26 00:01:02 localhost named[483136]: none:104: 'max-cache-size 90%' - setting to 57995MB (out of 64439MB)
Apr 26 00:01:02 localhost named[483136]: set up managed keys zone for view TELECOM-user, file '2ff95fc2a86c198f.mkeys'
Apr 26 00:01:02 localhost named[483136]: none:104: 'max-cache-size 90%' - setting to 57995MB (out of 64439MB)
Apr 26 00:01:02 localhost named[483136]: set up managed keys zone for view UNICOM-user, file 'ab05e628ff9a962c.mkeys'
Apr 26 00:01:02 localhost named[483136]: none:104: 'max-cache-size 90%' - setting to 57995MB (out of 64439MB)
Apr 26 00:01:02 localhost named[483136]: set up managed keys zone for view CMCC-user, file '0d52e9253c2aad60.mkeys'
Apr 26 00:01:02 localhost named[483136]: none:104: 'max-cache-size 90%' - setting to 57995MB (out of 64439MB)
Apr 26 00:01:02 localhost named[483136]: set up managed keys zone for view any-user, file 'any-user.mkeys'
Apr 26 00:01:02 localhost named[483136]: none:104: 'max-cache-size 90%' - setting to 57995MB (out of 64439MB)
Apr 26 00:01:02 localhost named[483136]: command channel listening on 127.0.0.1#953
Apr 26 00:01:03 localhost kernel: mce: CPU5: Package temperature/speed normal
Apr 26 00:01:03 localhost kernel: mce: CPU4: Package temperature/speed normal
Apr 26 00:01:03 localhost kernel: mce: CPU7: Package temperature/speed normal
Apr 26 00:01:03 localhost kernel: mce: CPU3: Package temperature/speed normal
Apr 26 00:01:03 localhost kernel: mce: CPU2: Package temperature/speed normal
Apr 26 00:01:03 localhost kernel: mce: CPU6: Package temperature/speed normal
Apr 26 00:01:03 localhost kernel: mce: CPU0: Core temperature/speed normal
Apr 26 00:01:03 localhost kernel: mce: CPU1: Package temperature/speed normal


Code: [Select]
dmesg
[23726.715413] mce: CPU0: Package temperature/speed normal
[25531.425320] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 262)
[25531.425321] mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 4988)
[25531.425322] mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 4989)
[25531.425363] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 4988)
[25531.425364] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 4989)
[25531.425366] mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 4987)
[25531.425367] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 4989)
[25531.425368] mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 4986)
[25531.426350] mce: CPU6: Package temperature/speed normal
[25531.426352] mce: CPU3: Package temperature/speed normal
[25531.426353] mce: CPU1: Package temperature/speed normal
[25531.426353] mce: CPU0: Package temperature/speed normal
[25531.426354] mce: CPU5: Package temperature/speed normal
[25531.426355] mce: CPU4: Package temperature/speed normal
[25531.432933] mce: CPU2: Core temperature/speed normal
[25531.440852] mce: CPU7: Package temperature/speed normal
[27008.886266] floppy0: no floppy controllers found
[27466.693450] floppy0: no floppy controllers found
[54306.838281] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 287)
[54306.838282] mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 4989)
[54306.838283] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 4992)
[54306.838284] mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 4990)
[54306.838321] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 4985)
[54306.838323] mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 4992)
[54306.838324] mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 4991)
[54306.838325] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 4991)
[54306.839300] mce: CPU5: Package temperature/speed normal
[54306.839301] mce: CPU4: Package temperature/speed normal
[54306.839322] mce: CPU7: Package temperature/speed normal
[54306.839359] mce: CPU3: Package temperature/speed normal
[54306.839359] mce: CPU2: Package temperature/speed normal
[54306.839360] mce: CPU6: Package temperature/speed normal
[54306.845887] mce: CPU0: Core temperature/speed normal
[54306.853799] mce: CPU1: Package temperature/speed normal

Code: [Select]
Today's fault occurred at:
2023-04-26 01:25:00-@127.0.0.1
2023-04-26 01:37:00-@127.0.0.1
2023-04-26 01:38:00-@127.0.0.1
2023-04-26 01:39:00-@127.0.0.1
2023-04-26 01:40:00-@127.0.0.1
2023-04-26 01:45:00-@127.0.0.1
2023-04-26 01:47:00-@127.0.0.1
2023-04-26 01:48:00-@127.0.0.1
2023-04-26 01:49:00-@127.0.0.1
2023-04-26 01:50:00-@127.0.0.1
2023-04-26 02:09:00-@127.0.0.1
2023-04-26 02:10:00-@127.0.0.1
2023-04-26 02:14:00-@127.0.0.1
2023-04-26 02:15:00-@127.0.0.1
2023-04-26 03:04:00-@127.0.0.1
2023-04-26 03:05:00-@127.0.0.1
2023-04-26 04:03:01-@127.0.0.1
2023-04-26 04:04:01-@127.0.0.1
2023-04-26 04:05:01-@127.0.0.1
2023-04-26 04:18:01-@127.0.0.1
2023-04-26 04:19:01-@127.0.0.1
2023-04-26 04:20:01-@127.0.0.1
2023-04-26 05:54:01-@127.0.0.1
2023-04-26 05:55:01-@127.0.0.1
2023-04-26 07:19:01-@127.0.0.1
2023-04-26 07:20:01-@127.0.0.1
2023-04-26 07:40:01-@127.0.0.1
2023-04-26 08:00:01-@127.0.0.1
2023-04-26 08:24:01-@127.0.0.1
2023-04-26 08:25:01-@127.0.0.1
2023-04-26 08:43:01-@127.0.0.1
2023-04-26 08:44:01-@127.0.0.1
2023-04-26 08:45:01-@127.0.0.1