GUI And direct access does not respond

[peterpkcg]

Hi, (using 8.3.0)
I was disabling some tuneables because of performance issues. (are those settings "live" or do they need a reboot?? i would have guessed reboot)
But when I disabled one, don't remember which one, then I got an error message in the web-GUI. "An error occurred"

So I tried closing the window and opened a new, now It doesn't even show the login, only "Connection failed".

As I have a screen connected i went checking it out.
mountd can't delete exports for /mnt/ invalid argument

Ok... I tapped a key on the keyboard and got my 11 choices.

Tried to enter shell, nothing happend.

Sooooo, what should I do now? I can't turn my system off to see if that will resolve my problem. (well, yeah with the power-button, but thats not good i hear (duh)

Shares are working still, both smb and afp, so i'm making a backup as we speak.


So to sum it up.
Shares - working
Web-gui not working
Direct access not working
SSH disabled for the time being, (never again)


Thanks

 

[peterpkcg]

Had to go rogue and terminate it by power-button, did it when I was quite sure there was no activity on the disks.
Web-GUI is fine again.

But the tuneables, when I disable one, it takes a really long time for it to respond. And then, is it disabled, or will it be disabled on the next reboot?

 

[jgreco]

There are people who run into the incredibly-long-update issue, like you and me, and there are people who have apparently never seen it. It has something to do with FreeBSD accessing the USB storage doing I-know-not-what and it seems to be worse if the machine's been running a long time. I got fed up with USB drive keys a while back (because I've also seen them go corrupt) and fixed it by using real storage and now it isn't an issue, though the scripts themselves sometimes also take a while to run.

Tunables are things that only take effect after a reboot. They're essentially shoved into /boot/loader.conf.local

Sysctls are things that take effect immediately.

Both can totally hose your system so have a backup of your working config and a spare USB key handy.

 

[peterpkcg]

Thanks for the reply jgreco.
It had been running for a good 40 days. This server is at work, but I have a freenas at home as well, tunables seem to be slow on that one also.
If i would edit loader.conf.local directly without going through the Web-GUI, would that be faster?

Anyhow, everything seems to be OK, for now...

 

[jgreco]

FreeNAS stores everything into its database so that you can download a single file and then upload it onto a new system without fuss. This is how hardware upgrades are handled, but also how software updates occur. It is really best not to edit loader.conf by hand, and I'm fairly certain that changes to loader.conf.local would be wiped out as part of the rc process. If you just want to *test* a change, you can stop FreeNAS during boot (it only gives you ~2 seconds to do so) and enter changes at the loader prompt directly, which will only affect the current boot cycle. If you like your change, then you'll still need to configure it into FreeNAS so it survives reboots.

 

[peterpkcg]

I see, well, i'm not that interested. As long as it's running and my colleagues doesn't yell at me for to long, I'm happy.