roboko Posted February 26, 2019 Share Posted February 26, 2019 Hi, could you make me some hint, what's wrong? My VM based on Debian linux still crashing daily. No need to publish it, it could be issue with my config or hardware, but I am not sure what to repair. Thanks a lot. R. nas-diagnostics-20190226-1847.zip Quote Link to comment
limetech Posted February 28, 2019 Share Posted February 28, 2019 Looking at syslog, trouble begins here: Feb 25 23:00:04 nas bunker: Verify task for disk4 started, total files size 1.10 TB Feb 25 23:00:04 nas sSMTP[1796]: Creating SSL connection to host Feb 25 23:00:04 nas sSMTP[1796]: SSL connection using ECDHE-RSA-AES256-GCM-SHA384 Feb 25 23:00:05 nas sSMTP[1796]: Sent mail for [email protected] (221 2.0.0 Bye) uid=0 username=xxx outbytes=659 Feb 25 23:17:27 nas emhttpd: error: get_temperature, 4050: Resource temporarily unavailable (11): popen: /usr/sbin/smartctl -n standby -A /dev/sdm Feb 25 23:17:27 nas emhttpd: error: get_temperature, 4050: Resource temporarily unavailable (11): popen: /usr/sbin/smartctl -n standby -A /dev/sdq Feb 25 23:17:27 nas emhttpd: error: get_temperature, 4050: Resource temporarily unavailable (11): popen: /usr/sbin/smartctl -n standby -A /dev/sdf Feb 25 23:17:27 nas emhttpd: error: get_temperature, 4050: Resource temporarily unavailable (11): popen: /usr/sbin/smartctl -n standby -A /dev/sds Feb 25 23:17:27 nas emhttpd: error: get_temperature, 4050: Resource temporarily unavailable (11): popen: /usr/sbin/smartctl -n standby -A /dev/sdn Feb 25 23:17:27 nas emhttpd: error: get_temperature, 4050: Resource temporarily unavailable (11): popen: /usr/sbin/smartctl -n standby -A /dev/sdt Not sure what that "Resource temporarily unavailable" means - probably an out-of-memory condition. What is that 'Verify task for disk4 started' referring to? Maybe that is consuming all available RAM? Quote Link to comment
rlust Posted March 5, 2019 Share Posted March 5, 2019 I just upgraded to 6.6.7, and now getting VM crashing or failing to start with the following error. internal error: process exited while connecting to monitor: sh: fork: retry: Resource temporarily unavailable qemu: pthread_create: Resource temporarily unavailable Quote Link to comment
roboko Posted March 5, 2019 Author Share Posted March 5, 2019 Unfortunately still having this issue. I am trying to isolate error, but till now without success. After reboot some time cca 1 hour with issue, but then some strange lines in dmesg appears: ... Mar 5 21:40:52 nas kernel: br1: port 1(eth1) entered blocking state Mar 5 21:40:52 nas kernel: br1: port 1(eth1) entered forwarding state ... may be it is not connect with the issue, but in 6.6.1 there was nothing like that in dmesg 😞 Quote Link to comment
John_M Posted March 6, 2019 Share Posted March 6, 2019 On 2/28/2019 at 5:16 PM, limetech said: What is that 'Verify task for disk4 started' referring to? It looks like the Dynamix File Integrity plugin running a scheduled checksum check. 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.