hades Posted February 27, 2015 Share Posted February 27, 2015 Hello, I set up the BitTorrent Sync Docker about a week ago, and configured several shares which then worked OK. This morning I was checking the version number and playing around with ownCloud, when the unRAID web-interface froze, a refresh just put the browser into "waiting for server..." mode, and nothing happened for dozens of minutes. Without the web-server, I ssh'd into the server and initiated a reboot. Now the server's back, the web-interface is back. The server kicked off a parity-check, which sucks (takes 1.5-2 days), but whatever. I wanted to check my BitTorrent Sync docker, so went into the interface, and noticed that it is missing. Only ownCloud was showing (I only had those two). I added it back, and the unRAID docker page seemed to remember my settings, so I was happy. It's now added back, but the thing isn't working. The BitTorrent Sync interface is empty, completely empty, no menus, nothing. My other Sync clients don't see the unRAID server either. What do I do? I don't want to re-configure everything from scratch. Thank you. Link to comment
hades Posted February 27, 2015 Author Share Posted February 27, 2015 Weirdly enough, the Docker came alive after about 30 minutes, and is now working OK. All the shares are still intact. No idea what happened. Thanks. Link to comment
hades Posted February 28, 2015 Author Share Posted February 28, 2015 This morning, without touching anything, the BTSync docker died. It wasn't in any of the peer-lists for the other sync partners, nor was the UI showing anything. I attempted to stop the docker through the unRAID UI, and that promptly crashed the entire unRAID UI. Now the web-interface won't load. I searched and searched on this forum to see how to restart the webUI, but found nothing. I again had to power down the machine, which means the parity build is once again going to restart. Is there a way to restart the webUI without rebooting? For now I'll delete my two Dockers, and play around with them when I have the time and just run the BTSync client on my Windows server. Thank you. Link to comment
hades Posted February 28, 2015 Author Share Posted February 28, 2015 Rebooted. Local console is up and can log on, browse through files. - webUI not up - can't SSH into the server - array not reachable through samba - me pissed Thank you. Link to comment
hades Posted February 28, 2015 Author Share Posted February 28, 2015 Another reboot. Same thing as before. IP address is correct. Help?!?! Thank you. Link to comment
HellDiverUK Posted February 28, 2015 Share Posted February 28, 2015 5 posts and not a syslog to be seen... Link to comment
hades Posted February 28, 2015 Author Share Posted February 28, 2015 5 posts and not a syslog to be seen... Fair enough... Apologize if my main priority has been to get my server usable. The reboots destroyed the logs, forgot that until now. The server took about 2-3 minutes, but became accessible from the Windows systems. I've removed the dockers now as the problem started when I installed the BTSync docker. I'll add it back in a few days after I've verified that the system is stable once again. It would be a nice thing to use. Now, how do I restart the webUI without rebooting? I now face a 3 day parity build again, and do not wish to interrupt it under any circumstances. Thank you. Link to comment
jonp Posted February 28, 2015 Share Posted February 28, 2015 The following command will safely reboot the system from command line: powerdown -r now Link to comment
itimpi Posted February 28, 2015 Share Posted February 28, 2015 Now, how do I restart the webUI without rebooting? I now face a 3 day parity build again, and do not wish to interrupt it under any circumstances. Unfortunately you cannot as the emhttp process is not restartable. The GUI has not been restartable for releases after 4.7 (i.e. v5 and v6). Link to comment
Squid Posted February 28, 2015 Share Posted February 28, 2015 I now face a 3 day parity build again, and do not wish to interrupt it under any circumstances. Completely OT, but why is a rebuild taking 3 days? Link to comment
HellDiverUK Posted February 28, 2015 Share Posted February 28, 2015 Yeah, seems slow. Even on my test rig, a G1610T (dual 2.3GHz) with 2GB RAM it'll build partity on a 5TB disk in a little over 8 hours. Link to comment
Squid Posted February 28, 2015 Share Posted February 28, 2015 For all we know, the problems are related. Without a syslog can't really tell Link to comment
hades Posted March 1, 2015 Author Share Posted March 1, 2015 Attached is a syslog. Docker: Evaluating backup alternatives. Thought I would install the Crashplan docker, so I added it from the docker repository. It's been about 15 minutes without an update to the UI. I can't even load a fresh copy of the UI. Parity: It's doing a parity verification. No idea why it's so slow. Usually it's half that time (@30mb/s or so). There are 10 disks in there, some attached to SATA cards, probably the cards are slow. ? Question: I have a pre-clear in progress, this I can check from the console through which I kicked off the task. How can I check the status of the parity verification without the UI? Is there a log entry I can keep an eye out for? I don't want to reboot it until I know it is finished. Thank you. syslog.zip Link to comment
hades Posted March 3, 2015 Author Share Posted March 3, 2015 Hello, Any thoughts on how I can check the progress of my parity verification without access to the webUI? I don't want to reboot until it's done as I don't want to restart the verification. Thanks. Link to comment
Squid Posted March 3, 2015 Share Posted March 3, 2015 grep mdResync= /var/local/emhttp/var.ini If that value is > 0, a parity check is still in progress. You can get the current position by grep mdResyncPos= /var/local/emhttp/var.ini and the number of corrections its done by grep mdResyncCorr= /var/local/emhttp/var.ini Link to comment
hades Posted March 3, 2015 Author Share Posted March 3, 2015 Thank you for these commands. This is what I see: root@winserver:/var/log# grep mdResync= /var/local/emhttp/var.ini mdResync="2930266532" root@winserver:/var/log# grep mdResyncPos= /var/local/emhttp/var.ini mdResyncPos="1087523760" root@winserver:/var/log# grep mdResyncCorr= /var/local/emhttp/var.ini mdResyncCorr="1" root@winserver:/var/log# However, this is identical to what I saw ~12 hours ago. So what does this mean? Thank you. Link to comment
hades Posted March 3, 2015 Author Share Posted March 3, 2015 The following command will safely reboot the system from command line: powerdown -r now Thank you for this. I am confident that the parity check ran through as the syslog states that the drives have spun down. However, when I run this script, nothing happens, I just keep looking at a blank cursor. I checked the script out, and see that it relies on getting two pages from the unRAID website. How does it do this if the website is completely unresponsive (hence my need to do this via command-line)? My theory is that it doesn't, and just sits there. Is there another clean way of shutting unRAID down from the command line? Thank you. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.