comet424 Posted April 1, 2020 Share Posted April 1, 2020 hi couple things.. unraid only running 7 days and logs are full.. is there a way empty the logs without having to reboot unraid? also I check the log errors and I get these maybe you guys know what it means? Mar 29 00:09:02 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 Mar 29 00:09:02 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952857088 csum 0x9b48269f expected csum 0x3d7debcd mirror 1 Mar 29 00:09:02 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952914432 csum 0xb2de8b91 expected csum 0x2a169799 mirror 1 Mar 29 00:09:02 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 Mar 29 00:09:02 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952914432 csum 0xb2de8b91 expected csum 0x2a169799 mirror 1 Mar 29 00:13:25 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 21419339776 csum 0x1b1eb939 expected csum 0xce94e2c2 mirror 1 Mar 29 00:13:25 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 21419339776 csum 0x1b1eb939 expected csum 0xce94e2c2 mirror 1 Mar 29 00:13:26 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 21439676416 csum 0xd2da5dd2 expected csum 0x802d2c9b mirror 1 Mar 29 00:13:26 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 21439709184 csum 0xecaeae07 expected csum 0x8e35480d mirror 1 Mar 29 00:13:26 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 21439676416 csum 0xd2da5dd2 expected csum 0x802d2c9b mirror 1 Mar 29 00:13:26 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 21439774720 csum 0xea5a1644 expected csum 0xdef78dc4 mirror 1 Mar 29 00:13:26 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 21439709184 csum 0xecaeae07 expected csum 0x8e35480d mirror 1 Mar 29 00:13:26 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 21439709184 csum 0xecaeae07 expected csum 0x8e35480d mirror 1 Mar 29 00:13:26 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 21440200704 csum 0xd0dea10e expected csum 0x6be48f6c mirror 1 Mar 29 06:04:56 Tower kernel: print_req_error: I/O error, dev sda, sector 1071938328 Mar 29 10:57:29 Tower nginx: 2020/03/29 10:57:29 [error] 8997#8997: *829732 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.47, server: , request: "POST /plugins/dynamix.docker.manager/include/DockerUpdate.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "tower", referrer: "http://tower/Docker" Mar 29 13:20:50 Tower kernel: print_req_error: I/O error, dev sda, sector 1071938328 Mar 29 20:36:59 Tower kernel: transmission-da[22947]: segfault at 18 ip 000055ce5fe05a2c sp 00001491d69b27e0 error 6 in transmission-daemon[55ce5fde6000+4b000] Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 4096 bytes) in /usr/local/emhttp/plugins/dynamix/include/Syslog.php on line 20 while creating this files.. the log file I don't think shows all my errors and Main dashboard went from 100% down to 72% dunno how it did it.. and dunno if the diagnostic show anything tower-syslog-20200401-0237.zip tower-diagnostics-20200331-2236.zip Quote Link to comment
comet424 Posted April 1, 2020 Author Share Posted April 1, 2020 (edited) trying to view the log file again I get Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 4096 bytes) in /usr/local/emhttp/plugins/dynamix/include/Syslog.php on line 20 and I know I have a bad 2TB hard drive hooked up to a USB enclosure Im guessing that's the error above as it failts crc error or so.. as I use it still for copying files etc Edited April 1, 2020 by comet424 Quote Link to comment
JorgeB Posted April 1, 2020 Share Posted April 1, 2020 Syslog is getting flooded with these: Mar 29 22:35:30 Tower kernel: x86/PAT: ipmi-sensors:6345 map pfn expected mapping type uncached-minus for [mem 0xd943f000-0xd943ffff], got write-back ### [PREVIOUS LINE REPEATED 29 TIMES] ### Mar 29 22:35:49 Tower kernel: x86/PAT: ipmi-sensors:7517 map pfn expected mapping type uncached-minus for [mem 0xd943f000-0xd943ffff], got write-back Don't see anything else, try clearing that then reboot and post new diags. Quote Link to comment
comet424 Posted April 1, 2020 Author Share Posted April 1, 2020 do you know what that is? how do I clear that? I know I asked for help under dynamix temperature sensors didn't get help I had temperature setting working for a MSI x570 board I finally got the settings to work but I had to switch boards due to defectiveness and switched to a ASUS TUF board x570 but the sensors do not work works fine in bios and windows just not unraid… tried to get more help but no one seems to be able to help... as the proper sensors are not working and what I googled.. unraid doesn't run the right kernel yet or something so sensors don't work 100% right … how do I clear that ? as I think ipmi-sensors is temperature setting I set in the go file? I also noticed that unraid does some hard drive scanning or something before you get the login screen on console side I never noticed before either takes like 1 min or so ill have to send a picture as im sure I just confused you Quote Link to comment
JorgeB Posted April 1, 2020 Share Posted April 1, 2020 That looks more like IPMI plugin related, and your board doesn't have IPMI, so if that's installed remove it. Quote Link to comment
comet424 Posted April 1, 2020 Author Share Posted April 1, 2020 and I just checked went from 72 to 91% log fill and when I goto system logs I still get this error Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 4096 bytes) in /usr/local/emhttp/plugins/dynamix/include/Syslog.php on line 20 Quote Link to comment
comet424 Posted April 1, 2020 Author Share Posted April 1, 2020 ok just a sec ill go check Quote Link to comment
comet424 Posted April 1, 2020 Author Share Posted April 1, 2020 ok ya I have it running as it was a one that said it can detect temperatures... ill go uninstall it Quote Link to comment
comet424 Posted April 1, 2020 Author Share Posted April 1, 2020 is there anything else I need to check for? or just do a reboot and hope for the best? Quote Link to comment
JorgeB Posted April 1, 2020 Share Posted April 1, 2020 Just now, comet424 said: as it was a one that said it can detect temperatures. It can if the board has IPMI, usually only server boards have that, e.g. some Supermicro and Asrock Rack boards. Quote Link to comment
comet424 Posted April 1, 2020 Author Share Posted April 1, 2020 ya I hada Asus WS PRO board I was testing of a friend it had IPMI least in the bios never got to try it just built him the computer for him ok gonna reboot now.. maybe temperature will be fixed lol Quote Link to comment
comet424 Posted April 1, 2020 Author Share Posted April 1, 2020 so I rebooted.. I cant get my pic off the phone I took of the console of some errors and the like timer or hard drive checking it does but logs I see bunch of errors not sure where its pointing ipmi but I know my 192.168.0.47 is my desktop computer... but I get these pr 1 08:53:10 Tower kernel: Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA Apr 1 08:53:10 Tower kernel: tsc: Fast TSC calibration failed Apr 1 08:53:10 Tower kernel: ACPI: Early table checksum verification disabled Apr 1 08:53:10 Tower kernel: floppy0: no floppy controllers found Apr 1 08:53:10 Tower kernel: usb 5-1: device descriptor read/64, error -110 Apr 1 08:53:10 Tower kernel: random: 7 urandom warning(s) missed due to ratelimiting Apr 1 08:53:10 Tower kernel: ccp 0000:0a:00.1: psp initialization failed Apr 1 08:53:12 Tower rpc.statd[1921]: Failed to read /var/lib/nfs/state: Success Apr 1 08:53:19 Tower kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20180810/utaddress-204) Apr 1 08:53:19 Tower root: Interface "tunl0" added. Warning: no bandwidth limit has been set. Apr 1 08:53:19 Tower root: Interface "ip_vti0" added. Warning: no bandwidth limit has been set. Apr 1 08:53:19 Tower root: Interface "gretap0" added. Warning: no bandwidth limit has been set. Apr 1 08:53:19 Tower root: Interface "br0" added. Warning: no bandwidth limit has been set. Apr 1 08:53:19 Tower root: Interface "gre0" added. Warning: no bandwidth limit has been set. Apr 1 08:53:19 Tower root: Interface "erspan0" added. Warning: no bandwidth limit has been set. Apr 1 08:53:19 Tower root: Warning: parse_ini_file(/var/local/emhttp/var.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php on line 56 Apr 1 08:53:19 Tower root: Warning: Division by zero in /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php on line 62 Apr 1 08:55:49 Tower root: error: /webGui/include/ProcessStatus.php: wrong csrf_token Apr 1 08:55:56 Tower nginx: 2020/04/01 08:55:56 [error] 11330#11330: *75 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 08:56:17 Tower nginx: 2020/04/01 08:56:17 [error] 11330#11330: *189 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 08:56:38 Tower nginx: 2020/04/01 08:56:38 [error] 11330#11330: *289 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 08:56:59 Tower nginx: 2020/04/01 08:56:59 [error] 11330#11330: *390 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 08:57:20 Tower nginx: 2020/04/01 08:57:20 [error] 11330#11330: *488 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 08:57:41 Tower nginx: 2020/04/01 08:57:41 [error] 11330#11330: *568 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 08:58:02 Tower nginx: 2020/04/01 08:58:02 [error] 11330#11330: *639 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 08:58:23 Tower nginx: 2020/04/01 08:58:23 [error] 11330#11330: *729 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 08:58:44 Tower nginx: 2020/04/01 08:58:44 [error] 11330#11330: *805 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 08:59:05 Tower nginx: 2020/04/01 08:59:05 [error] 11330#11330: *887 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 08:59:26 Tower nginx: 2020/04/01 08:59:26 [error] 11330#11330: *980 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 08:59:47 Tower nginx: 2020/04/01 08:59:47 [error] 11330#11330: *1070 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 09:00:08 Tower nginx: 2020/04/01 09:00:08 [error] 11330#11330: *1156 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 09:00:29 Tower nginx: 2020/04/01 09:00:29 [error] 11330#11330: *1244 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 09:00:50 Tower nginx: 2020/04/01 09:00:50 [error] 11330#11330: *1327 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 09:01:11 Tower nginx: 2020/04/01 09:01:11 [error] 11330#11330: *1417 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 09:01:32 Tower nginx: 2020/04/01 09:01:32 [error] 11330#11330: *1496 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 09:01:53 Tower nginx: 2020/04/01 09:01:53 [error] 11330#11330: *1576 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 09:02:14 Tower nginx: 2020/04/01 09:02:14 [error] 11330#11330: *1653 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 09:02:35 Tower nginx: 2020/04/01 09:02:35 [error] 11330#11330: *1730 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 09:02:56 Tower nginx: 2020/04/01 09:02:56 [error] 11330#11330: *1814 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 09:03:17 Tower nginx: 2020/04/01 09:03:17 [error] 11330#11330: *1902 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 09:03:38 Tower nginx: 2020/04/01 09:03:38 [error] 11330#11330: *1983 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 09:03:59 Tower nginx: 2020/04/01 09:03:59 [error] 11330#11330: *2065 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 09:04:20 Tower nginx: 2020/04/01 09:04:20 [error] 11330#11330: *2149 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 09:04:41 Tower nginx: 2020/04/01 09:04:41 [error] 11330#11330: *2238 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 09:05:02 Tower nginx: 2020/04/01 09:05:02 [error] 11330#11330: *2318 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Apr 1 09:05:23 Tower nginx: 2020/04/01 09:05:23 [error] 11330#11330: *2399 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.47, server: , request: "GET /plugins/ipmi/include/ipmi_helpers.php?action=ipmidash HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Dashboard" Quote Link to comment
comet424 Posted April 1, 2020 Author Share Posted April 1, 2020 so I just checked again the warnings not increasing just the error one keeps increasing tower-syslog-20200401-1342.zip tower-diagnostics-20200401-0942.zip Quote Link to comment
trurl Posted April 1, 2020 Share Posted April 1, 2020 Diagnostics already includes the syslog since the last reboot, so unless you are posting an additional syslog captured by Syslog Server there is no need to attach syslog with diagnostics. Looks like something is still expecting to access something related to that ipmi plugin. Close all browsers on all computers that may be accessing your server, including any mobile apps. Try again after clearing browser cache. It is really best if you work with your server from a single tab on a single browser on a single computer, otherwise the webUI can get out of sync between the different tabs/browsers/computers. Quote Link to comment
comet424 Posted April 1, 2020 Author Share Posted April 1, 2020 ah ok.. on the sys log I didn't know.. as it has that option for sys log download my bad as for server.. I only have 1 tab open on the desktop computer with the ip 192.168.0.47 one im replying to this forum and only have 1 tab nad no other phone or anything connected to server except my Xbox One its connected to the Plex Server on the Unraid. but ill try a reboot on everything.... shut it all down then back up Quote Link to comment
comet424 Posted April 2, 2020 Author Share Posted April 2, 2020 (edited) so couple questions.. I haven't rebooted my server with that 2tb Seagate out to see if that's the xfered is gone as im guessing that and my 4tb external Is just a smart check on those drives as that's what I guess but the 2 errors below it failed to connect to hypervision what is that? failed to connect to libvirt folder is that important file location what do I uninstall and install so my current errors I get is Apr 1 22:46:39 Tower kernel: Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA Apr 1 22:46:39 Tower kernel: tsc: Fast TSC calibration failed Apr 1 22:46:39 Tower kernel: ACPI: Early table checksum verification disabled Apr 1 22:46:39 Tower kernel: floppy0: no floppy controllers found Apr 1 22:46:39 Tower kernel: usb 5-1: device descriptor read/64, error -110 Apr 1 22:46:39 Tower kernel: random: 6 urandom warning(s) missed due to ratelimiting Apr 1 22:46:39 Tower kernel: ccp 0000:0a:00.1: psp initialization failed Apr 1 22:46:42 Tower rpc.statd[1898]: Failed to read /var/lib/nfs/state: Success Apr 1 22:46:50 Tower kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20180810/utaddress-204) Apr 1 22:46:50 Tower root: Interface "tunl0" added. Warning: no bandwidth limit has been set. Apr 1 22:46:50 Tower root: Interface "ip_vti0" added. Warning: no bandwidth limit has been set. Apr 1 22:46:50 Tower root: Interface "gretap0" added. Warning: no bandwidth limit has been set. Apr 1 22:46:50 Tower root: Interface "br0" added. Warning: no bandwidth limit has been set. Apr 1 22:46:50 Tower root: Interface "gre0" added. Warning: no bandwidth limit has been set. Apr 1 22:46:50 Tower root: Interface "erspan0" added. Warning: no bandwidth limit has been set. Apr 1 22:46:50 Tower root: Warning: parse_ini_file(/var/local/emhttp/var.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php on line 56 Apr 1 22:46:50 Tower root: Warning: Division by zero in /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php on line 62 Apr 1 22:52:36 Tower ntpd[1928]: frequency error 584 PPM exceeds tolerance 500 PPM what is the usb 5-1 errpr amd the freqiiemcy errpr 584 ppm exceeds.. what are those errors? and how I fine any of these other issues.. or are they just warrenys… and whats wrong with the parity check? does that mean my files in jeopardy? Edited April 2, 2020 by comet424 Quote Link to comment
Squid Posted April 2, 2020 Share Posted April 2, 2020 The parity check error is a long standing issue with the parity check plugin. Only does that error on boot up of the server, and nothing to worry about. ntpd error is that your server's time that it is setting is out by approximately ~45 seconds per day. Quote Link to comment
comet424 Posted April 2, 2020 Author Share Posted April 2, 2020 (edited) oh ok so that's good nothing serious now I tried googling no one has an answer since 2007 people been asking .. but error kernel: usb 5-1: device descriptor read/64, error -110 is this serious as I couldn't find an answer everyone is stumped.. but the writters of Linux should know what that error means though right? or is it an error you can just ignore too and is this error serious or can be ignored? ntpd[1780]: frequency error 748 PPM exceeds tolerance 500 PPM Edited April 2, 2020 by comet424 Quote Link to comment
comet424 Posted April 2, 2020 Author Share Posted April 2, 2020 soo I been working on 2 servers and mixed up things I guess.. gonna try to delete my messages from the other topic so it doesn't confuse me more and other people so is the PPM serious? is USB 5-1 Serious... is the Xfered? what is that what about the 2 errors below it... as I not sure if that xfered is a smart check of usb hard drives of my unassigned drives or what not I just taking a guess sorry everyone if I confused you too Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.