Results 1 to 5 of 5

Thread: A start job is running

  1. #1
    Junior Member
    Join Date
    Feb 2017
    Posts
    5

    A start job is running

    Hello everyone,

    I am fairly new to the Kali distro and to the Linux world. I have some experience from 10 years ago when I was on highschool, but since that time nothing.
    I installed Kali and when booting after GRUB ( when services are starting ), its stuck on: " A Start Job is running for: ** and here are 4 services **

    - LSB: thin initscript
    - Account Services
    - Network Manager
    - Authenticate and Authorize users to run privileged tasks

    The Countdown is set to 90 sec, after 90 sec it will go to other services and than again to these 4 and again 90 sec timer.

    When i press CTRL C or ESC it will pass with OK checkmark.

    After boot it will work normally as it should but I am puzzled why is this time there and how to fix it ?
    I was also browsing forum but did not find any solution here nor on any other website.
    Anyone can assist with this ?

    So far i love Kali and trying to learn new things.

    Thanks for your help.

    EDIT:
    Hello all, sorry for not providing enough info, i have already received warning.

    Kali distro is one I downloaded from the site itself, 64bit: Version 2016.2 64bit
    Hardware is stock: DELL Latitude E6230 SSD Drive, 16GB RAM
    Last edited by m4stic; 2017-02-02 at 07:39 PM.

  2. #2
    Senior Member
    Join Date
    Apr 2013
    Location
    in a computer
    Posts
    524
    On what hardware do you have Kali installed? Sounds like there might be some incompatibilities.

  3. #3
    Junior Member
    Join Date
    Feb 2017
    Posts
    5
    Hello Grid, thanks for reacting, please check my update on post.
    Also I have run the update for packages and issue disappeared by itself - seems resolved now.

    I am still interested on the what the solution could be,

  4. #4
    Senior Member
    Join Date
    Apr 2013
    Location
    in a computer
    Posts
    524
    Glad it's working for you. Have a look in /var/log, and the output of dmesg. Hopefully that will give you some clues as to what went wrong.

  5. #5
    Junior Member
    Join Date
    Feb 2017
    Posts
    5
    thanks buddy let me test and I will put results here for others to see.. i am sorry but i wont be able to analyze a log as I am fairly new to the linux problem

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •