canni86 Posted April 21, 2022 Share Posted April 21, 2022 (edited) Hi folks, I'm experiencing a really annoying issue with my server, every morning my server becomes unresponsive, physical login to machine fails with "fork resource unavailable" message. I need to hard reset my server to make it operate for another day. Below a snippet from logs showing "blacklisted device" errors before forking problem? I have plus license purchased for this stick. Apr 21 01:20:18 Tower kernel: md: sync done. time=26926sec Apr 21 01:20:18 Tower kernel: md: recovery thread: exit status: 0 Apr 21 03:40:01 Tower crond[1850]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Apr 21 05:32:58 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:33:01 Tower emhttpd: Plus key detected, GUID: FFFF-5678-9901-005643239138 FILE: /boot/config/Plus.key Apr 21 05:33:11 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:33:31 Tower emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) Apr 21 05:33:32 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:34:01 Tower emhttpd: Plus key detected, GUID: FFFF-5678-9901-005643239138 FILE: /boot/config/Plus.key Apr 21 05:34:04 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:34:07 Tower emhttpd: Plus key detected, GUID: FFFF-5678-9901-005643239138 FILE: /boot/config/Plus.key Apr 21 05:34:08 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:34:28 Tower emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) Apr 21 05:34:29 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:34:58 Tower emhttpd: Plus key detected, GUID: FFFF-5678-9901-005643239138 FILE: /boot/config/Plus.key Apr 21 05:34:59 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:35:01 Tower crond[1850]: unable to fork (user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null) Apr 21 05:35:02 Tower emhttpd: Plus key detected, GUID: FFFF-5678-9901-005643239138 FILE: /boot/config/Plus.key Apr 21 05:35:03 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:35:06 Tower emhttpd: Plus key detected, GUID: FFFF-5678-9901-005643239138 FILE: /boot/config/Plus.key Apr 21 05:35:22 Tower emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) Apr 21 05:35:23 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:35:52 Tower emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) Apr 21 05:36:01 Tower crond[1850]: unable to fork (user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null) Apr 21 05:36:09 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:36:38 Tower emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) Apr 21 05:36:55 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:37:01 Tower crond[1850]: unable to fork (user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null) Apr 21 05:37:24 Tower emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) Apr 21 05:37:41 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:38:01 Tower crond[1850]: unable to fork (user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null) Apr 21 05:38:10 Tower emhttpd: Plus key detected, GUID: FFFF-5678-9901-005643239138 FILE: /boot/config/Plus.key Apr 21 05:38:11 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:38:14 Tower emhttpd: Plus key detected, GUID: FFFF-5678-9901-005643239138 FILE: /boot/config/Plus.key Apr 21 05:38:15 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:38:18 Tower emhttpd: Plus key detected, GUID: FFFF-5678-9901-005643239138 FILE: /boot/config/Plus.key Apr 21 05:38:19 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:38:39 Tower emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) Apr 21 05:38:40 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:39:01 Tower crond[1850]: unable to fork (user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null) Apr 21 05:39:09 Tower emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) Apr 21 05:39:26 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:39:56 Tower emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) Apr 21 05:40:01 Tower crond[1850]: unable to fork (user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null) Apr 21 05:40:13 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:40:42 Tower emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) Apr 21 05:40:59 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:41:01 Tower crond[1850]: unable to fork (user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null) Apr 21 05:41:28 Tower emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) Apr 21 05:41:29 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:41:45 Tower emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) Apr 21 05:41:46 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:42:01 Tower crond[1850]: unable to fork (user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null) Apr 21 05:42:15 Tower emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) Apr 21 05:42:32 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:43:01 Tower emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) Apr 21 05:43:02 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:43:21 Tower crond[1850]: exit status 254 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null Apr 21 05:43:21 Tower sSMTP[2575]: Creating SSL connection to host Apr 21 05:43:21 Tower sSMTP[2575]: SSL connection using TLS_AES_256_GCM_SHA384 Apr 21 05:43:22 Tower sSMTP[2575]: Authorization failed (535 5.7.8 https://support.google.com/mail/?p=BadCredentials r3-20020aa7cb83000000b0041b573e2654sm10760032edt.94 - gsmtp) Apr 21 05:43:37 Tower emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) Apr 21 05:44:01 Tower crond[1850]: unable to fork (user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null) Apr 21 05:45:01 Tower crond[1850]: unable to fork (user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null) Apr 21 05:46:01 Tower crond[1850]: unable to fork (user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null) Apr 21 05:46:51 Tower emhttpd: Plus key detected, GUID: FFFF-5678-9901-005643239138 FILE: /boot/config/Plus.key Apr 21 05:46:52 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) Apr 21 05:47:01 Tower crond[1850]: unable to fork (user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null) Apr 21 05:47:01 Tower crond[1850]: unable to fork (user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null) Apr 21 05:47:12 Tower emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) Apr 21 05:47:13 Tower emhttpd: Unregistered - flash device error (ENOFLASH7) tower-diagnostics-anon-20220421-1606.zip Edited August 10, 2022 by canni86 Quote Link to comment
Solution Squid Posted April 21, 2022 Solution Share Posted April 21, 2022 Nothing super obvious, but based on the tasks currently running, see if restarting Shinobi before you go to bed makes a difference. root 12317 0.0 0.0 0 0 ? Zs 16:05 0:00 | \_ [ffmpeg] <defunct> Quote Link to comment
canni86 Posted April 21, 2022 Author Share Posted April 21, 2022 I'll try today, thx Quote Link to comment
canni86 Posted April 24, 2022 Author Share Posted April 24, 2022 Thx @Squid shinobi container is a root cause here, stopping it solves the problem, I'll try to dig around how can I make it more stable probably in a separate thread Quote Link to comment
Squid Posted April 24, 2022 Share Posted April 24, 2022 Yeah, I've never seen in diagnostics "defunct" next to a process, and ffmeg had a lot of defunct processes, so assumed that as time went on more and more and more kept showing up via shinobi and that eventually crashed the system. Restarting it daily may help, but it's not the real solution. 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.