July 5, 20197 yr Hi all, This is my second time attempting to setup unRAID (recreated the flash drive each time). First boot goes well, setup goes well, even got my RAID all setup, etc. Then I reboot and though unRAID terminal boots up there's no web GUI to connect to. I can ping the machine, I can SSH into it, no problem. But no web server seems to be running. I looked around the forum but couldn't find an exact gift. Diagnostics attached below. I see a couple of errors that seem relevant around php-fpm but have no idea how to address them or what in my fairly vanilla config might've caused that. emhttpd: shcmd (24): /etc/rc.d/rc.php-fpm start php-fpm[4457]: [ERROR] An another FPM instance seems to already listen on /var/run/php5-fpm.sock php-fpm[4457]: [ERROR] FPM initialization failed root: Starting php-fpm [ERROR] An another FPM instance seems to already listen on /var/run/php5-fpm.sock root: [ERROR] FPM initialization failed root: failed Thank you for your time! beast-diagnostics-20190705-0102.zip
July 5, 20196 yr Author Yup, having SSH'd in I can ping 8.8.8.8. If I boot up in GUI mode I can navigate the internet. Just seems to be a web server issue.
July 5, 20196 yr Author Btw, I get the following warnings when running diagnostics, jic that helps: Warning: file(/var/local/emhttp/diskload.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 89 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 91 Warning: implode(): Invalid arguments passed in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 100 done.
July 5, 20196 yr Author Ok, so in safe mode I do get the webgui. There's no emhttpd error as cited above. Any ideas? I haven't added plugins or anything yet. At most I configured email notifications. Not sure what else could be interfering. Thanks!
July 5, 20196 yr Author Update: booted in safe mode, then rebooted in normal mode, GUI worked after that. No idea why.
July 6, 20196 yr Community Expert Probably simply rebooting at all did the trick. Are you booting from a USB2 port? USB2 is often more reliable for booting with some motherboards.
Archived
This topic is now archived and is closed to further replies.