{"id":1515,"date":"2019-04-23T22:34:51","date_gmt":"2019-04-24T02:34:51","guid":{"rendered":"http:\/\/mikemartinezonline.com\/blog\/?p=1515"},"modified":"2019-04-23T22:34:51","modified_gmt":"2019-04-24T02:34:51","slug":"stop-unresponsive-service-via-command-line-windows-some-linux-distros","status":"publish","type":"post","link":"https:\/\/mikemartinezonline.com\/blog\/2019\/04\/23\/stop-unresponsive-service-via-command-line-windows-some-linux-distros\/","title":{"rendered":"Stop unresponsive service via command line. (Windows & some Linux distros)"},"content":{"rendered":"

In Windows:<\/font><\/strong><\/p>\n

If you have a service that is not responding or showing pending in Windows services that you are unable to stop, use the following directions to force the service to stop.<\/p>\n

    \n
  1. Click the Start <\/strong>menu <\/li>\n
  2. Click Run <\/strong>or in the search bar type services.msc<\/strong><\/li>\n
  3. Press Enter<\/strong><\/li>\n
  4. Look for the service and check the Properties <\/strong>and identify its service name <\/li>\n
  5. Once found, open a command prompt. Type sc queryex [servicename]<\/strong>. <\/li>\n
  6. Press Enter<\/strong><\/li>\n
  7. Identify the PID <\/li>\n
  8. In the same command prompt type taskkill \/pid [pid number] \/f<\/strong><\/li>\n
  9. Press Enter<\/strong><\/li>\n<\/ol>\n

    In Linux (Ubuntu for example)<\/font><\/strong><\/p>\n

    1. Open the System Monitor app. In the Processes tab, scroll down the list until you find the unresponsive app.<\/p>\n

    \"Use<\/p>\n

    2. Right click on it and select \u201cKill Process\u201d.<\/p>\n

    Once confirmed, this will kill the unresponsive application.<\/p>\n

    Via Command line:<\/font><\/strong><\/p>\n

    Open terminal<\/p>\n

    Enter the command to show currently running services.<\/b> Type ls \/etc\/init.d<\/kbd> into Terminal and press \u21b5 Enter<\/kbd>. This will bring up a list of currently running services and their corresponding command names.<\/p>\n

    If this command doesn’t work, try ls \/etc\/rc.d\/<\/kbd> instead.<\/p>\n

    Find the command name of the service that you want to restart.<\/b> You’ll typically find the name of the service (e.g., "Apache") on the left side of the screen, while the command name (e.g., "httpd" or "apache2", depending on your Linux distribution) will appear on the right side.<\/p>\n

    Enter the restart command.<\/b> Type sudo systemctl restart service<\/kbd> into Terminal, making sure to replace the service<\/kbd> part of the command with the command name of the service, and press \u21b5 Enter<\/kbd>.<\/p>\n

    For example, to restart Apache on Ubuntu Linux, you would type sudo systemctl restart apache2<\/kbd> into Terminal.<\/p>\n

    Enter your password when prompted.<\/b> Type in the password that you use for your superuser account, then press \u21b5 Enter<\/kbd>. This should restart the process.<\/p>\n

    If the service doesn’t restart after doing this, try typing in sudo systemctl stop service<\/kbd>, pressing \u21b5 Enter<\/kbd>, and then entering sudo systemctl start service<\/kbd>.<\/p>\n

    To list running services in the command line:<\/p>\n

    Use this command:<\/p>\n

    service –status-all<\/p>\n

    Here\u2019s an example of what this looks like on an Ubuntu 16.04.2 LTS system:<\/p>\n

    root> service –status-all Example:<\/p>\n

    [ + ] apache-htcacheclean<\/p>\n

    [ + ] apache2<\/p>\n

    [ + ] apparmor<\/p>\n

    [ – ] bootmisc.sh<\/p>\n

    [ – ] checkfs.sh<\/p>\n

    [ – ] checkroot-bootclean.sh<\/p>\n

    [ – ] checkroot.sh<\/p>\n

    [ + ] console-setup<\/p>\n

    [ + ] cron<\/p>\n

    [ + ] dbus<\/p>\n

    [ – ] hostname.sh<\/p>\n

    [ – ] hwclock.sh<\/p>\n

    [ + ] irqbalance<\/p>\n

    [ + ] keyboard-setup<\/p>\n

    [ – ] killprocs<\/p>\n

    [ + ] kmod<\/p>\n

    [ – ] mountall-bootclean.sh<\/p>\n

    [ – ] mountall.sh<\/p>\n

    [ – ] mountdevsubfs.sh<\/p>\n

    [ – ] mountkernfs.sh<\/p>\n

    [ – ] mountnfs-bootclean.sh<\/p>\n

    [ – ] mountnfs.sh<\/p>\n

    [ + ] mysql<\/p>\n

    [ + ] networking<\/p>\n

    [ + ] nginx<\/p>\n

    [ + ] ondemand<\/p>\n

    [ – ] plymouth<\/p>\n

    [ – ] plymouth-log<\/p>\n

    [ + ] procps<\/p>\n

    [ + ] rc.local<\/p>\n

    [ + ] resolvconf<\/p>\n

    [ – ] rsync<\/p>\n

    [ + ] rsyslog<\/p>\n

    [ – ] sendsigs<\/p>\n

    [ + ] ssh<\/p>\n

    [ + ] sysstat<\/p>\n

    [ + ] udev<\/p>\n

    [ + ] ufw<\/p>\n

    [ – ] umountfs<\/p>\n

    [ – ] umountnfs.sh<\/p>\n

    [ – ] umountroot<\/p>\n

    [ + ] urandom<\/p>\n

    [ – ] uuidd<\/p>\n

    The meaning of the Ubuntu service command output<\/p>\n

    From the Ubuntu Linux service man page:<\/p>\n

    service –status-all runs all init scripts, in alphabetical order, with the status command. The status is:<\/p>\n

    [ + ] for running services<\/p>\n

    [ – ] for stopped services<\/p>\n

    [ ? ] for services without a ‘status’ command<\/p>\n

    This option only calls status for sysvinit jobs; upstart jobs can be queried in a similar manner with initctl list. <\/p>\n

    Some services are managed by Upstart. You can check the status of all Upstart<\/i><\/b> services with sudo initctl list<\/i><\/b>. Any service managed by Upstart will also show in the list provided by service –status-all<\/i><\/b> but will be marked with a<\/i><\/b> ?<\/p>\n

    [Note: Running with\/without sudo can make a difference.<\/p>\n

    Some services in \/var\/run\/ have read access only to root user. Those services show status [-] without sudo, and [+] with sudo.]<\/p>\n","protected":false},"excerpt":{"rendered":"

    In Windows: If you have a service that is not responding or showing pending in Windows services that you are unable to stop, use the following directions to force the service to stop. Click the Start menu Click Run or in the search bar type services.msc Press Enter Look for the service and check the … Continue reading “Stop unresponsive service via command line. (Windows & some Linux distros)”<\/span><\/a><\/p>\n","protected":false},"author":587,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[175,13,11,256,15,218],"tags":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/mikemartinezonline.com\/blog\/wp-json\/wp\/v2\/posts\/1515"}],"collection":[{"href":"https:\/\/mikemartinezonline.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mikemartinezonline.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mikemartinezonline.com\/blog\/wp-json\/wp\/v2\/users\/587"}],"replies":[{"embeddable":true,"href":"https:\/\/mikemartinezonline.com\/blog\/wp-json\/wp\/v2\/comments?post=1515"}],"version-history":[{"count":1,"href":"https:\/\/mikemartinezonline.com\/blog\/wp-json\/wp\/v2\/posts\/1515\/revisions"}],"predecessor-version":[{"id":1516,"href":"https:\/\/mikemartinezonline.com\/blog\/wp-json\/wp\/v2\/posts\/1515\/revisions\/1516"}],"wp:attachment":[{"href":"https:\/\/mikemartinezonline.com\/blog\/wp-json\/wp\/v2\/media?parent=1515"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mikemartinezonline.com\/blog\/wp-json\/wp\/v2\/categories?post=1515"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mikemartinezonline.com\/blog\/wp-json\/wp\/v2\/tags?post=1515"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}