I have done some research and it seems that this is a common problem and I just installed the latest Ubuntu today on my computer. However, for some reason when I click the shut down button it always restarts instead of shutting down. I have already tried all those terminal commands to shut it down, but those don't work either. It always restarts itself.. Is there anyway I can power it off without having to resort to manually holding my computer's power button?
Edit:
I tried those grub update things too, but the commands I get from the forums don't seem to work anyways so that's also one solution that wouldn't work.
try this one on the terminal:
sudo init 0
Related
Ever since I ran the command dnscmd /Config /SocketPoolSize 9100 my Win'2008R2 dc is not working properly and is stuck for hrs at Applying Computer Settings after rebooting before it finally logs in. Obviously 9100 was a big mistake but I figured by re-running the same command but specifying 2500 (default) that things would be fine. I was wrong.
So I've deleted the SocketPoolSize afterwards directly from the registry in SYSTEM\CurrentControlSet\services\DNS\Parameters in hopes of undoing it but the system still takes hrs before I can finally login. I have a feeling that the dnscmd command I ran and reverted is just coincidence and perhaps something else is causing Exchange service to get stuck with "Starting"
This is also preventing some services from starting (ie: Exchange 2010 - not best practice on DC, I know but it was never a problem).
Is there anything else that happens after running that command? Is there a way I can undo it using the same command or some other (rather than thru the registry)?
Turns out it had nothing to do with the dnscmd command I ran. I forgot that days ago I temporarily disabled Tcpipv6 on the network adapter but never rebooted until today after running the dnscmd. This incorrectly lead me to believe it was something to do with dnscmd.
I'm building a Chrome extension for a client. Everything has always run smoothly on my end, but when they run it on their computer, there has always been little glitches that were never repeatable (so annoying). Yesterday, I finially nailed down (hopefully) the last piece of the puzzle—on there machine, the extenssion is restarting itself mid browsing session. I know I never explicitly coded this in myself, and I have never experienced it on my own machine. To clarify, the type of restart that's happening (as there are at least 3 different types of restarts) seems to be the same as refreshing the background page—storage is kept in tact and onInstall handlers are not run. Anyone have any idea what could be causing such an issue?
The code is too big to post here, but I can try to post some snippits of it if anyone wants to see where a specific API is used or something.
It's been a while but I'm pretty sure the problem was what I speculated about in the comments. I needed to set persistent to true in my manifest.json. Having it set to false means the background script "goes to sleep". I believe it going to sleep and waking back up was the restart I was experiencing.
I don't have Sudo access, so currently i can't install 'Forever' https://www.npmjs.com/package/forever
Instead i am simply using 'Screen'.
I am running a node.js server, at a random point, the node server stops, and screen exits. I cannot seem to collect any error data on this. I seem to be completely unaware of why its happening and cannot think of a way to catch what is happening. It doesn't happen often (maybe 1 time per day). When i load putty back up and login to my Apache server through terminal, i type screen -x or screen -r and it tells me there are no screens attached. The node server process definitely stops because the app it runs stops working.
Obviously i can't post all the code here, there is tons of it. But everything appears to work wonderfully, except every now and then, something goes wrong and it closes the attached screen.
If there was a problem with the node server, i would expect a crash, and the attached screen would stay attached. There would be an error outputted to the terminal for me to see when i open it. But in this case, it totally closes the attached screen.
Does anybody know what kind of error can cause this?
On a side note, is there an alternative to 'Forever' that can be installed without Sudo access?
My node version wasn't correct which is why Forever wasn't installing. I didn't need SUDO after all. I am now using Forever and hopefully this will shed light on what is going on as i have a out.log file which should catch whatever the problem is. :-)
TortoiseSVN application is running very slow.
Ít waits too long when trying to open Repo-browser or updating. It keeps showing the message "Please wait while the repository browser is initializing".
Then after waiting for 10 mins or so, it shows up the credential window, and then again a long wait.
I installed command line sliksuberversion, and updates from command line using subversion run as normal, from which I deduced that there is no OS or network related issue.
I enabled debugLogs, and got the following:
The timestamps show the delay. Eventually the server connection times out, due to the delay.
Please suggest.
Thanks for your suggestions and time on this. The issue was traced to ICMP not accessible in server machine, because it was not different subnet. I was able to ping the machine using domain name, but not by IP (this statement is correct, and it was not the other way round). What was surprising was the subversion was working fine, but not tortoise, which probably indicates that tortoisesvn has an additional network step (ping or something else) in their process over subversion. Thanks again.
I encountered the same. It worked before, and started after I was moved from cubicles to cubicles with maybe network reset although my IP address remains the same.
It works again after run ipconfig /renew and restart TortoiseSVN client.
I'm having a slightly weird, repeatable, but unexplainable problem with screen.
I'm using ansible/vagrant to build a consistent dev environment for my company, and as a slightly showy finishing touch it starts the dev server running in a screen session so the frontend devs don't need to bother logging in and manually starting the process, but backend devs can log in and take control.
However, one of the systems - despite being built from scratch - ends up with an immediately dead screen (it doesn't log anything to screenlog). Running the command manually works fine.
(the command being)
screen -L -d -m bash -c /home/vagrant/run_screen_server.sh
I've even gone to the point of nuking everything vagrant/virtualbox related on the system, making sure it's installing a clean, nightly box. Exactly the same source box works all the other machines.
Are there any other debugging steps I can be taking or is there something I'm missing?
I'm right now trying to do the same with my setup and hit the same problem.
Further testing has shown, that sleep 1 right after calling the screen helped. It seems the ssh script that ansible calls exits before the screen call is fully detached (or something else, that would explain that the sleep 1 helps)
I've also found Can't get Fabric's detached screen session example to work with the same suggestion.