feins Posted March 21, 2023 Share Posted March 21, 2023 Dear Community recently my server start to behave funny like crash or all CPU Processor at 100% until i need to do a force restart and so on. What i notice that after reboot i notice such output from the Syslog terminal. Mar 21 01:20:08 TS-P500 root: plugin: setting: /tmp/unassigned.devices/add-smb - mode to 0770 Mar 21 01:20:08 TS-P500 root: plugin: running: anonymous Mar 21 01:20:08 TS-P500 root: plugin: unassigned.devices.plg updated Mar 21 01:20:32 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 21 01:21:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 01:39:32 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 21 01:42:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 02:02:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 02:19:34 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 21 02:23:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 02:33:35 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 21 02:35:35 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 21 02:45:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 03:05:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 03:15:38 TS-P500 emhttpd: spinning down /dev/sdg Mar 21 03:23:42 TS-P500 emhttpd: read SMART /dev/sdg Mar 21 03:26:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 04:39:54 TS-P500 emhttpd: spinning down /dev/sdg Mar 21 04:44:12 TS-P500 emhttpd: read SMART /dev/sdg Mar 21 04:45:23 TS-P500 crond[1737]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Mar 21 04:46:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 04:59:18 TS-P500 emhttpd: spinning down /dev/sdg Mar 21 05:04:23 TS-P500 emhttpd: read SMART /dev/sdg Mar 21 05:06:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 05:19:30 TS-P500 emhttpd: spinning down /dev/sdg Mar 21 05:24:40 TS-P500 emhttpd: read SMART /dev/sdg Mar 21 05:27:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 05:41:38 TS-P500 emhttpd: spinning down /dev/sdg Mar 21 05:43:45 TS-P500 emhttpd: read SMART /dev/sdg Mar 21 05:48:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 05:58:52 TS-P500 emhttpd: spinning down /dev/sdg Mar 21 06:00:01 TS-P500 Docker Auto Update: Community Applications Docker Autoupdate running Mar 21 06:00:01 TS-P500 Docker Auto Update: Checking for available updates Mar 21 06:04:37 TS-P500 Docker Auto Update: No updates will be installed Mar 21 06:04:37 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 06:05:13 TS-P500 emhttpd: read SMART /dev/sdg Mar 21 06:20:20 TS-P500 emhttpd: spinning down /dev/sdg Mar 21 06:25:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 06:27:41 TS-P500 emhttpd: read SMART /dev/sdg Mar 21 06:42:47 TS-P500 emhttpd: spinning down /dev/sdg Mar 21 06:46:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 06:49:35 TS-P500 emhttpd: read SMART /dev/sdg Mar 21 07:04:42 TS-P500 emhttpd: spinning down /dev/sdg Mar 21 07:07:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 07:11:59 TS-P500 emhttpd: read SMART /dev/sdg Mar 21 07:28:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 07:29:25 TS-P500 emhttpd: spinning down /dev/sdg Mar 21 07:35:54 TS-P500 emhttpd: read SMART /dev/sdg Mar 21 07:48:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 07:51:01 TS-P500 emhttpd: spinning down /dev/sdg Mar 21 07:58:40 TS-P500 emhttpd: read SMART /dev/sdg Mar 21 08:09:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 08:13:45 TS-P500 emhttpd: spinning down /dev/sdg Mar 21 08:16:09 TS-P500 emhttpd: read SMART /dev/sdg Mar 21 08:30:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 08:42:56 TS-P500 emhttpd: spinning down /dev/sdg Mar 21 08:51:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 09:06:03 TS-P500 emhttpd: read SMART /dev/sdg Mar 21 09:11:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 09:32:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 09:53:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 10:14:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 10:35:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 10:50:17 TS-P500 emhttpd: spinning down /dev/sdg Mar 21 10:56:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 11:16:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 11:32:48 TS-P500 webGUI: Successful login user root from 10.10.2.127 Mar 21 11:33:24 TS-P500 kernel: mdcmd (37): set md_num_stripes 1280 Mar 21 11:33:24 TS-P500 kernel: mdcmd (38): set md_queue_limit 80 Mar 21 11:33:24 TS-P500 kernel: mdcmd (39): set md_sync_limit 5 Mar 21 11:33:24 TS-P500 kernel: mdcmd (40): set md_write_method Mar 21 11:34:04 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 21 11:34:27 TS-P500 kernel: md: sync done. time=38009sec Mar 21 11:34:27 TS-P500 kernel: md: recovery thread: exit status: 0 Mar 21 11:35:04 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 21 11:37:40 TS-P500 emhttpd: read SMART /dev/sdg Mar 21 11:38:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 11:49:29 TS-P500 emhttpd: spinning down /dev/sdd Mar 21 11:52:46 TS-P500 emhttpd: spinning down /dev/sdg Mar 21 11:58:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 Mar 21 11:59:05 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 21 12:00:05 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 21 12:01:05 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 21 12:02:05 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 21 12:03:06 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 21 12:05:06 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 21 12:06:06 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 21 12:11:06 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 21 12:12:03 TS-P500 emhttpd: read SMART /dev/sdd Mar 21 12:12:06 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update ts-p500-diagnostics-20230321-1211.zip Quote Link to comment
ljm42 Posted March 23, 2023 Share Posted March 23, 2023 Let's fix this first: On 3/20/2023 at 9:15 PM, feins said: crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 This error means there is an invalid custom contab in the CA Update Applications plugin. This website should be able to help you fix the crontab expression: https://crontab.guru/ if you aren't sure, post a screenshot of what you're putting into the plugin and let us know what you are trying to do with it. Quote Link to comment
feins Posted March 23, 2023 Author Share Posted March 23, 2023 3 hours ago, ljm42 said: Let's fix this first: This error means there is an invalid custom contab in the CA Update Applications plugin. This website should be able to help you fix the crontab expression: https://crontab.guru/ if you aren't sure, post a screenshot of what you're putting into the plugin and let us know what you are trying to do with it. I didn't add any Custom (cron expression) at all and here is the screenshot of my CA Update Application plugin. Quote Link to comment
Squid Posted March 23, 2023 Share Posted March 23, 2023 What is the output of each of these commands crontab -l and cat /etc/cron.d/root Quote Link to comment
feins Posted March 25, 2023 Author Share Posted March 25, 2023 On 3/23/2023 at 5:45 PM, Squid said: What is the output of each of these commands crontab -l and cat /etc/cron.d/root Here's the output from crontab -l root@TS-P500:~# crontab -l # If you don't want the output of a cron job mailed to you, you have to direct # any output to /dev/null. We'll do this here since these jobs should run # properly on a newly installed system. If a script fails, run-parts will # mail a notice to root. # # Run the hourly, daily, weekly, and monthly cron jobs. # Jobs that need different timing may be entered into the crontab as before, # but most really don't need greater granularity than this. If the exact # times of the hourly, daily, weekly, and monthly cron jobs do not suit your # needs, feel free to adjust them. # # Run hourly cron jobs at 47 minutes after the hour: 47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null # # Run daily cron jobs at 4:40 every day: 40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null # # Run weekly cron jobs at 4:30 on the first day of the week: 30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null # # Run monthly cron jobs at 4:20 on the first day of the month: 20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null 0 3 * * 1 /usr/local/emhttp/plugins/ca.backup2/scripts/backup.php &>/dev/null 2>&1 28 8 * * * /usr/local/emhttp/plugins/nvidia-driver/include/update-check.sh &>/dev/null 2>&1 root@TS-P500:~# and here's the output for cat /etc/cron.d/root root@TS-P500:~# cat /etc/cron.d/root # Generated docker monitoring schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate check &> /dev/null # Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated mover schedule: 40 3 * * * /usr/local/sbin/mover &> /dev/null # Generated parity check schedule: 0 0 1 * * /usr/local/sbin/mdcmd check NOCORRECT &> /dev/null # Generated plugins version check schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null # Generated Unraid OS update check schedule: 11 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null # Generated cron settings for docker autoupdates 0 6 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateDocker.php >/dev/null 2>&1 # Generated cron settings for plugin autoupdates 0 0 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 # CRON for CA background scanning of applications 50 * * * * php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2>&1 # Generated file integrity check schedule: 0 3 * * 2 bash /boot/config/plugins/dynamix.file.integrity/integrity-check.sh &> /dev/null # Generated system data collection schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null root@TS-P500:~# Quote Link to comment
Solution Squid Posted March 25, 2023 Solution Share Posted March 25, 2023 There's absolutely nothing wrong with that expresion. Have you tried rebooting? Quote Link to comment
feins Posted March 26, 2023 Author Share Posted March 26, 2023 15 hours ago, Squid said: There's absolutely nothing wrong with that expresion. Have you tried rebooting? That's funny, Before this ive rebooted the Server before posting the Syslog where I notice some of my CPU are at 100% and the server are not responding and very lagging. Today i just check on the syslog again and notice all the error are no more. text error warn system array login Mar 25 20:12:58 TS-P500 avahi-daemon[8587]: Registering new address record for fe80::dcbf:67ff:fe13:3570 on vethb94c914.*. Mar 25 20:13:03 TS-P500 kernel: docker0: port 5(vethb94c914) entered disabled state Mar 25 20:13:03 TS-P500 kernel: vethe26bc6e: renamed from eth0 Mar 25 20:13:03 TS-P500 avahi-daemon[8587]: Interface vethb94c914.IPv6 no longer relevant for mDNS. Mar 25 20:13:03 TS-P500 avahi-daemon[8587]: Leaving mDNS multicast group on interface vethb94c914.IPv6 with address fe80::dcbf:67ff:fe13:3570. Mar 25 20:13:03 TS-P500 kernel: docker0: port 5(vethb94c914) entered disabled state Mar 25 20:13:03 TS-P500 kernel: device vethb94c914 left promiscuous mode Mar 25 20:13:03 TS-P500 kernel: docker0: port 5(vethb94c914) entered disabled state Mar 25 20:13:03 TS-P500 avahi-daemon[8587]: Withdrawing address record for fe80::dcbf:67ff:fe13:3570 on vethb94c914. Mar 25 22:22:19 TS-P500 webGUI: Successful login user root from 10.10.2.127 Mar 25 22:32:02 TS-P500 emhttpd: read SMART /dev/sde Mar 25 22:34:23 TS-P500 root: plugin: running: anonymous Mar 25 22:34:23 TS-P500 root: plugin: creating: /boot/config/plugins/dynamix.file.manager/dynamix.file.manager.txz - downloading from URL https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.file.manager.txz Mar 25 22:34:27 TS-P500 root: plugin: checking: /boot/config/plugins/dynamix.file.manager/dynamix.file.manager.txz - MD5 Mar 25 22:34:27 TS-P500 root: plugin: running: /boot/config/plugins/dynamix.file.manager/dynamix.file.manager.txz Mar 25 22:34:28 TS-P500 root: plugin: running: anonymous Mar 25 22:34:30 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 25 22:34:34 TS-P500 root: plugin: dynamix.file.manager.plg updated Mar 25 22:55:52 TS-P500 emhttpd: read SMART /dev/sdd Mar 25 23:13:32 TS-P500 emhttpd: spinning down /dev/sdd Mar 26 00:00:01 TS-P500 Plugin Auto Update: Checking for available plugin updates Mar 26 00:01:37 TS-P500 Plugin Auto Update: Community Applications Plugin Auto Update finished Mar 26 00:07:50 TS-P500 emhttpd: spinning down /dev/sde Mar 26 02:03:58 TS-P500 emhttpd: read SMART /dev/sdg Mar 26 02:04:09 TS-P500 emhttpd: read SMART /dev/sdf Mar 26 02:14:16 TS-P500 emhttpd: read SMART /dev/sde Mar 26 02:19:05 TS-P500 emhttpd: spinning down /dev/sdg Mar 26 02:20:18 TS-P500 emhttpd: spinning down /dev/sdf Mar 26 02:29:29 TS-P500 emhttpd: spinning down /dev/sde Mar 26 03:19:29 TS-P500 emhttpd: read SMART /dev/sde Mar 26 03:34:40 TS-P500 emhttpd: spinning down /dev/sde Mar 26 03:40:16 TS-P500 crond[1725]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Mar 26 04:40:05 TS-P500 apcupsd[7683]: apcupsd exiting, signal 15 Mar 26 04:40:05 TS-P500 apcupsd[7683]: apcupsd shutdown succeeded Mar 26 04:40:07 TS-P500 apcupsd[29382]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded Mar 26 04:40:07 TS-P500 apcupsd[29382]: NIS server startup succeeded Mar 26 05:37:21 TS-P500 emhttpd: read SMART /dev/sde Mar 26 05:37:45 TS-P500 emhttpd: read SMART /dev/sdi Mar 26 05:54:50 TS-P500 emhttpd: spinning down /dev/sde Mar 26 05:54:50 TS-P500 emhttpd: spinning down /dev/sdi Mar 26 06:00:01 TS-P500 Docker Auto Update: Community Applications Docker Autoupdate running Mar 26 06:00:01 TS-P500 Docker Auto Update: Checking for available updates Mar 26 06:04:35 TS-P500 Docker Auto Update: No updates will be installed Mar 26 06:32:03 TS-P500 nginx: 2023/03/26 06:32:03 [crit] 7889#7889: *381228 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 106.75.223.209, server: 0.0.0.0:2443 Mar 26 09:39:50 TS-P500 webGUI: Successful login user root from 10.10.2.127 Mar 26 09:46:04 TS-P500 kernel: docker0: port 5(veth0d3315d) entered blocking state Mar 26 09:46:04 TS-P500 kernel: docker0: port 5(veth0d3315d) entered disabled state Mar 26 09:46:04 TS-P500 kernel: device veth0d3315d entered promiscuous mode Mar 26 09:46:05 TS-P500 kernel: eth0: renamed from vethbe929c2 Mar 26 09:46:05 TS-P500 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth0d3315d: link becomes ready Mar 26 09:46:05 TS-P500 kernel: docker0: port 5(veth0d3315d) entered blocking state Mar 26 09:46:05 TS-P500 kernel: docker0: port 5(veth0d3315d) entered forwarding state Mar 26 09:46:06 TS-P500 avahi-daemon[8587]: Joining mDNS multicast group on interface veth0d3315d.IPv6 with address fe80::e0b2:b1ff:fee3:d172. Mar 26 09:46:06 TS-P500 avahi-daemon[8587]: New relevant interface veth0d3315d.IPv6 for mDNS. Mar 26 09:46:06 TS-P500 avahi-daemon[8587]: Registering new address record for fe80::e0b2:b1ff:fee3:d172 on veth0d3315d.*. Mar 26 09:46:17 TS-P500 kernel: docker0: port 6(veth0baf29d) entered blocking state Mar 26 09:46:17 TS-P500 kernel: docker0: port 6(veth0baf29d) entered disabled state Mar 26 09:46:17 TS-P500 kernel: device veth0baf29d entered promiscuous mode Mar 26 09:46:17 TS-P500 kernel: docker0: port 6(veth0baf29d) entered blocking state Mar 26 09:46:17 TS-P500 kernel: docker0: port 6(veth0baf29d) entered forwarding state Mar 26 09:46:17 TS-P500 kernel: docker0: port 6(veth0baf29d) entered disabled state Mar 26 09:46:17 TS-P500 kernel: eth0: renamed from veth790bf06 Mar 26 09:46:17 TS-P500 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth0baf29d: link becomes ready Mar 26 09:46:17 TS-P500 kernel: docker0: port 6(veth0baf29d) entered blocking state Mar 26 09:46:17 TS-P500 kernel: docker0: port 6(veth0baf29d) entered forwarding state Mar 26 09:46:18 TS-P500 emhttpd: read SMART /dev/sde Mar 26 09:46:18 TS-P500 avahi-daemon[8587]: Joining mDNS multicast group on interface veth0baf29d.IPv6 with address fe80::b81d:acff:fe95:8abb. Mar 26 09:46:18 TS-P500 avahi-daemon[8587]: New relevant interface veth0baf29d.IPv6 for mDNS. Mar 26 09:46:18 TS-P500 avahi-daemon[8587]: Registering new address record for fe80::b81d:acff:fe95:8abb on veth0baf29d.*. Mar 26 09:46:26 TS-P500 emhttpd: read SMART /dev/sdg Mar 26 09:46:29 TS-P500 emhttpd: read SMART /dev/sdi Mar 26 10:19:08 TS-P500 emhttpd: spinning down /dev/sde Mar 26 11:17:30 TS-P500 kernel: usb 3-5.4: new full-speed USB device number 10 using xhci_hcd Mar 26 11:17:30 TS-P500 kernel: usb 3-5.4: device descriptor read/64, error -32 Mar 26 11:17:31 TS-P500 kernel: usb 3-5.4: device descriptor read/64, error -32 Mar 26 11:17:31 TS-P500 kernel: usb 3-5.4: new full-speed USB device number 11 using xhci_hcd Mar 26 11:17:31 TS-P500 kernel: cdc_acm 3-5.4:1.0: ttyACM0: USB ACM device Mar 26 11:17:31 TS-P500 kernel: usbcore: registered new interface driver cdc_acm Mar 26 11:17:31 TS-P500 kernel: cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters Mar 26 12:32:20 TS-P500 emhttpd: read SMART /dev/sde Mar 26 12:35:51 TS-P500 emhttpd: read SMART /dev/sdd Mar 26 12:51:35 TS-P500 emhttpd: spinning down /dev/sdd Mar 26 13:28:58 TS-P500 emhttpd: read SMART /dev/sdd Mar 26 13:43:24 TS-P500 emhttpd: spinning down /dev/sde Mar 26 13:57:36 TS-P500 emhttpd: spinning down /dev/sdd Mar 26 14:52:31 TS-P500 kernel: usb 3-5.4: USB disconnect, device number 11 Mar 26 16:17:24 TS-P500 emhttpd: read SMART /dev/sde Mar 26 16:29:52 TS-P500 emhttpd: read SMART /dev/sdd Mar 26 16:33:16 TS-P500 webGUI: Successful login user root from 10.10.2.127 Mar 26 16:41:17 TS-P500 emhttpd: spinning down /dev/sde Mar 26 16:45:01 TS-P500 emhttpd: spinning down /dev/sdd 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.