“Unable to connect to Upstart” error when installing git-all

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
19
down vote

favorite
13












I am using 15.04.



So I'm working with git and I installed the standard version. I set up the ssh keys and was able to clone one of my repositories to the correct folder. Everything was working great and then I decided it was a good idea to install more packages. I ran sudo apt-get install git-all. I'm looking at error codes now having to deal with upstart.



start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
No apport report written because the error message indicates its a followup error from a previous failure.
dpkg: error processing package runit (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of git-daemon-run:
git-daemon-run depends on runit; however:
Package runit is not configured yet.

dpkg: error processing package git-daemon-run (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
runit
git-daemon-run
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is what happens when I even update/upgrade my system. At this point all I'm looking to do is be able to install software and update my current software. Is there any way I can potentially reverse this issue or at least correct it?



Edit: Thankfully this issue was solved only a day or two after it happened. The accepted answer worked perfectly and took care of my issue










share|improve this question



























    up vote
    19
    down vote

    favorite
    13












    I am using 15.04.



    So I'm working with git and I installed the standard version. I set up the ssh keys and was able to clone one of my repositories to the correct folder. Everything was working great and then I decided it was a good idea to install more packages. I ran sudo apt-get install git-all. I'm looking at error codes now having to deal with upstart.



    start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
    No apport report written because the error message indicates its a followup error from a previous failure.
    dpkg: error processing package runit (--configure):
    subprocess installed post-installation script returned error exit status 1
    dpkg: dependency problems prevent configuration of git-daemon-run:
    git-daemon-run depends on runit; however:
    Package runit is not configured yet.

    dpkg: error processing package git-daemon-run (--configure):
    dependency problems - leaving unconfigured
    Errors were encountered while processing:
    runit
    git-daemon-run
    E: Sub-process /usr/bin/dpkg returned an error code (1)


    This is what happens when I even update/upgrade my system. At this point all I'm looking to do is be able to install software and update my current software. Is there any way I can potentially reverse this issue or at least correct it?



    Edit: Thankfully this issue was solved only a day or two after it happened. The accepted answer worked perfectly and took care of my issue










    share|improve this question

























      up vote
      19
      down vote

      favorite
      13









      up vote
      19
      down vote

      favorite
      13






      13





      I am using 15.04.



      So I'm working with git and I installed the standard version. I set up the ssh keys and was able to clone one of my repositories to the correct folder. Everything was working great and then I decided it was a good idea to install more packages. I ran sudo apt-get install git-all. I'm looking at error codes now having to deal with upstart.



      start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
      No apport report written because the error message indicates its a followup error from a previous failure.
      dpkg: error processing package runit (--configure):
      subprocess installed post-installation script returned error exit status 1
      dpkg: dependency problems prevent configuration of git-daemon-run:
      git-daemon-run depends on runit; however:
      Package runit is not configured yet.

      dpkg: error processing package git-daemon-run (--configure):
      dependency problems - leaving unconfigured
      Errors were encountered while processing:
      runit
      git-daemon-run
      E: Sub-process /usr/bin/dpkg returned an error code (1)


      This is what happens when I even update/upgrade my system. At this point all I'm looking to do is be able to install software and update my current software. Is there any way I can potentially reverse this issue or at least correct it?



      Edit: Thankfully this issue was solved only a day or two after it happened. The accepted answer worked perfectly and took care of my issue










      share|improve this question















      I am using 15.04.



      So I'm working with git and I installed the standard version. I set up the ssh keys and was able to clone one of my repositories to the correct folder. Everything was working great and then I decided it was a good idea to install more packages. I ran sudo apt-get install git-all. I'm looking at error codes now having to deal with upstart.



      start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
      No apport report written because the error message indicates its a followup error from a previous failure.
      dpkg: error processing package runit (--configure):
      subprocess installed post-installation script returned error exit status 1
      dpkg: dependency problems prevent configuration of git-daemon-run:
      git-daemon-run depends on runit; however:
      Package runit is not configured yet.

      dpkg: error processing package git-daemon-run (--configure):
      dependency problems - leaving unconfigured
      Errors were encountered while processing:
      runit
      git-daemon-run
      E: Sub-process /usr/bin/dpkg returned an error code (1)


      This is what happens when I even update/upgrade my system. At this point all I'm looking to do is be able to install software and update my current software. Is there any way I can potentially reverse this issue or at least correct it?



      Edit: Thankfully this issue was solved only a day or two after it happened. The accepted answer worked perfectly and took care of my issue







      dpkg upstart git






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Sep 6 '16 at 20:25

























      asked Jun 3 '15 at 4:12









      Electronicks

      101116




      101116




















          5 Answers
          5






          active

          oldest

          votes

















          up vote
          12
          down vote



          accepted










          You'll need to forcibly remove runit. Running sudo dpkg -r runit should work. You might need to use one of the --force-* options.






          share|improve this answer
















          • 3




            git-daemon-run depended on runit so I removed it, then removed runit. Now testing to see if git still works. That did however fix my current issue!
            – Electronicks
            Jun 3 '15 at 4:35











          • git-daemon-run is probably for running a GIt server (as in having git:// links to your computer for remote access). I don't have runit installed and can use git.
            – saiarcot895
            Jun 3 '15 at 4:36










          • I had to do asudo apt-get remove --purge git-daemon-run after all that to stop all the 'unmet dependency' errors.
            – JasoonS
            Jun 26 '16 at 12:25

















          up vote
          21
          down vote













          It's happening because of this bug https://bugs.launchpad.net/ubuntu/+source/runit/+bug/1448164



          You need to remove runit and git-daemon-run. That should fix the problem.



          sudo apt-get purge runit git-daemon-run


          Don't forget to visit the bug report and clicking Yes, this bug affects me.




          git-all without error



          It seems you can have git-all with daemon support without failing on this error. git-all recommends either git-daemon-run or git-daemon-sysvinit package. apt was choosing git-daemon-run as first choice. But If you explicitly mention the package you want (i.e git-daemon-sysvinit), apt won't try to install git-daemon-run.



          All you need to do is



          sudo apt-get install git-all git-daemon-sysvinit


          Hope that helps.






          share|improve this answer






















          • You are right, thank you for the bug link.
            – Billal Begueradj
            Sep 2 '16 at 14:27






          • 2




            I got the bug link from this answer and the link to that answer from Zanna's comment below the question. Thanks to them. @BillalBEGUERADJ
            – Anwar
            Sep 2 '16 at 14:33


















          up vote
          5
          down vote













          Try:



          sudo apt update 
          sudo apt --purge remove git
          sudo apt install git


          instead.






          share|improve this answer





























            up vote
            2
            down vote













            Try uninstalling git-all, installing git-daemon-sysvinit, then installing git-all again. If you look at the package properties in Synaptic, you will find that git-all depends on either git-daemon-run or git-daemon-sysvinit. git-daemon-run is the one that gets installed by default for some reason, even though it's broken in Ubuntu 15.04 and up. (See https://bugs.launchpad.net/ubuntu/+source/runit/+bug/1448164) But if you install git-daemon-sysvinit manually first, then git-all's dependency will be satisfied, by a package that actually works. You can then install git-all, and everything should be fine.






            share|improve this answer


















            • 1




              I should have clarified that I was using a workstation and not trying to configure a git server at the time. But for anyone who runs across this and is, this is good info ^
              – Electronicks
              Sep 6 '16 at 20:28

















            up vote
            1
            down vote













            You are probably using Ubuntu under a virtual host. If so, you will need to modify initctl to return true using the following steps. First, you need to tell dpkg, that you are going to change the upstart package installation using:



            sudo dpkg-divert --local --rename --add /sbin/initctl


            Then, you need to create a dummy initctl as a link to true:



            ln -s /bin/true /sbin/initctl





            share|improve this answer




















            • I was not using a virtual host but thank you anyway
              – Electronicks
              Sep 6 '16 at 20:28










            Your Answer







            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "89"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f631615%2funable-to-connect-to-upstart-error-when-installing-git-all%23new-answer', 'question_page');

            );

            Post as a guest






























            5 Answers
            5






            active

            oldest

            votes








            5 Answers
            5






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            12
            down vote



            accepted










            You'll need to forcibly remove runit. Running sudo dpkg -r runit should work. You might need to use one of the --force-* options.






            share|improve this answer
















            • 3




              git-daemon-run depended on runit so I removed it, then removed runit. Now testing to see if git still works. That did however fix my current issue!
              – Electronicks
              Jun 3 '15 at 4:35











            • git-daemon-run is probably for running a GIt server (as in having git:// links to your computer for remote access). I don't have runit installed and can use git.
              – saiarcot895
              Jun 3 '15 at 4:36










            • I had to do asudo apt-get remove --purge git-daemon-run after all that to stop all the 'unmet dependency' errors.
              – JasoonS
              Jun 26 '16 at 12:25














            up vote
            12
            down vote



            accepted










            You'll need to forcibly remove runit. Running sudo dpkg -r runit should work. You might need to use one of the --force-* options.






            share|improve this answer
















            • 3




              git-daemon-run depended on runit so I removed it, then removed runit. Now testing to see if git still works. That did however fix my current issue!
              – Electronicks
              Jun 3 '15 at 4:35











            • git-daemon-run is probably for running a GIt server (as in having git:// links to your computer for remote access). I don't have runit installed and can use git.
              – saiarcot895
              Jun 3 '15 at 4:36










            • I had to do asudo apt-get remove --purge git-daemon-run after all that to stop all the 'unmet dependency' errors.
              – JasoonS
              Jun 26 '16 at 12:25












            up vote
            12
            down vote



            accepted







            up vote
            12
            down vote



            accepted






            You'll need to forcibly remove runit. Running sudo dpkg -r runit should work. You might need to use one of the --force-* options.






            share|improve this answer












            You'll need to forcibly remove runit. Running sudo dpkg -r runit should work. You might need to use one of the --force-* options.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jun 3 '15 at 4:24









            saiarcot895

            9,27422233




            9,27422233







            • 3




              git-daemon-run depended on runit so I removed it, then removed runit. Now testing to see if git still works. That did however fix my current issue!
              – Electronicks
              Jun 3 '15 at 4:35











            • git-daemon-run is probably for running a GIt server (as in having git:// links to your computer for remote access). I don't have runit installed and can use git.
              – saiarcot895
              Jun 3 '15 at 4:36










            • I had to do asudo apt-get remove --purge git-daemon-run after all that to stop all the 'unmet dependency' errors.
              – JasoonS
              Jun 26 '16 at 12:25












            • 3




              git-daemon-run depended on runit so I removed it, then removed runit. Now testing to see if git still works. That did however fix my current issue!
              – Electronicks
              Jun 3 '15 at 4:35











            • git-daemon-run is probably for running a GIt server (as in having git:// links to your computer for remote access). I don't have runit installed and can use git.
              – saiarcot895
              Jun 3 '15 at 4:36










            • I had to do asudo apt-get remove --purge git-daemon-run after all that to stop all the 'unmet dependency' errors.
              – JasoonS
              Jun 26 '16 at 12:25







            3




            3




            git-daemon-run depended on runit so I removed it, then removed runit. Now testing to see if git still works. That did however fix my current issue!
            – Electronicks
            Jun 3 '15 at 4:35





            git-daemon-run depended on runit so I removed it, then removed runit. Now testing to see if git still works. That did however fix my current issue!
            – Electronicks
            Jun 3 '15 at 4:35













            git-daemon-run is probably for running a GIt server (as in having git:// links to your computer for remote access). I don't have runit installed and can use git.
            – saiarcot895
            Jun 3 '15 at 4:36




            git-daemon-run is probably for running a GIt server (as in having git:// links to your computer for remote access). I don't have runit installed and can use git.
            – saiarcot895
            Jun 3 '15 at 4:36












            I had to do asudo apt-get remove --purge git-daemon-run after all that to stop all the 'unmet dependency' errors.
            – JasoonS
            Jun 26 '16 at 12:25




            I had to do asudo apt-get remove --purge git-daemon-run after all that to stop all the 'unmet dependency' errors.
            – JasoonS
            Jun 26 '16 at 12:25












            up vote
            21
            down vote













            It's happening because of this bug https://bugs.launchpad.net/ubuntu/+source/runit/+bug/1448164



            You need to remove runit and git-daemon-run. That should fix the problem.



            sudo apt-get purge runit git-daemon-run


            Don't forget to visit the bug report and clicking Yes, this bug affects me.




            git-all without error



            It seems you can have git-all with daemon support without failing on this error. git-all recommends either git-daemon-run or git-daemon-sysvinit package. apt was choosing git-daemon-run as first choice. But If you explicitly mention the package you want (i.e git-daemon-sysvinit), apt won't try to install git-daemon-run.



            All you need to do is



            sudo apt-get install git-all git-daemon-sysvinit


            Hope that helps.






            share|improve this answer






















            • You are right, thank you for the bug link.
              – Billal Begueradj
              Sep 2 '16 at 14:27






            • 2




              I got the bug link from this answer and the link to that answer from Zanna's comment below the question. Thanks to them. @BillalBEGUERADJ
              – Anwar
              Sep 2 '16 at 14:33















            up vote
            21
            down vote













            It's happening because of this bug https://bugs.launchpad.net/ubuntu/+source/runit/+bug/1448164



            You need to remove runit and git-daemon-run. That should fix the problem.



            sudo apt-get purge runit git-daemon-run


            Don't forget to visit the bug report and clicking Yes, this bug affects me.




            git-all without error



            It seems you can have git-all with daemon support without failing on this error. git-all recommends either git-daemon-run or git-daemon-sysvinit package. apt was choosing git-daemon-run as first choice. But If you explicitly mention the package you want (i.e git-daemon-sysvinit), apt won't try to install git-daemon-run.



            All you need to do is



            sudo apt-get install git-all git-daemon-sysvinit


            Hope that helps.






            share|improve this answer






















            • You are right, thank you for the bug link.
              – Billal Begueradj
              Sep 2 '16 at 14:27






            • 2




              I got the bug link from this answer and the link to that answer from Zanna's comment below the question. Thanks to them. @BillalBEGUERADJ
              – Anwar
              Sep 2 '16 at 14:33













            up vote
            21
            down vote










            up vote
            21
            down vote









            It's happening because of this bug https://bugs.launchpad.net/ubuntu/+source/runit/+bug/1448164



            You need to remove runit and git-daemon-run. That should fix the problem.



            sudo apt-get purge runit git-daemon-run


            Don't forget to visit the bug report and clicking Yes, this bug affects me.




            git-all without error



            It seems you can have git-all with daemon support without failing on this error. git-all recommends either git-daemon-run or git-daemon-sysvinit package. apt was choosing git-daemon-run as first choice. But If you explicitly mention the package you want (i.e git-daemon-sysvinit), apt won't try to install git-daemon-run.



            All you need to do is



            sudo apt-get install git-all git-daemon-sysvinit


            Hope that helps.






            share|improve this answer














            It's happening because of this bug https://bugs.launchpad.net/ubuntu/+source/runit/+bug/1448164



            You need to remove runit and git-daemon-run. That should fix the problem.



            sudo apt-get purge runit git-daemon-run


            Don't forget to visit the bug report and clicking Yes, this bug affects me.




            git-all without error



            It seems you can have git-all with daemon support without failing on this error. git-all recommends either git-daemon-run or git-daemon-sysvinit package. apt was choosing git-daemon-run as first choice. But If you explicitly mention the package you want (i.e git-daemon-sysvinit), apt won't try to install git-daemon-run.



            All you need to do is



            sudo apt-get install git-all git-daemon-sysvinit


            Hope that helps.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Sep 2 '16 at 14:50

























            answered Sep 2 '16 at 14:24









            Anwar

            54.7k20143249




            54.7k20143249











            • You are right, thank you for the bug link.
              – Billal Begueradj
              Sep 2 '16 at 14:27






            • 2




              I got the bug link from this answer and the link to that answer from Zanna's comment below the question. Thanks to them. @BillalBEGUERADJ
              – Anwar
              Sep 2 '16 at 14:33

















            • You are right, thank you for the bug link.
              – Billal Begueradj
              Sep 2 '16 at 14:27






            • 2




              I got the bug link from this answer and the link to that answer from Zanna's comment below the question. Thanks to them. @BillalBEGUERADJ
              – Anwar
              Sep 2 '16 at 14:33
















            You are right, thank you for the bug link.
            – Billal Begueradj
            Sep 2 '16 at 14:27




            You are right, thank you for the bug link.
            – Billal Begueradj
            Sep 2 '16 at 14:27




            2




            2




            I got the bug link from this answer and the link to that answer from Zanna's comment below the question. Thanks to them. @BillalBEGUERADJ
            – Anwar
            Sep 2 '16 at 14:33





            I got the bug link from this answer and the link to that answer from Zanna's comment below the question. Thanks to them. @BillalBEGUERADJ
            – Anwar
            Sep 2 '16 at 14:33











            up vote
            5
            down vote













            Try:



            sudo apt update 
            sudo apt --purge remove git
            sudo apt install git


            instead.






            share|improve this answer


























              up vote
              5
              down vote













              Try:



              sudo apt update 
              sudo apt --purge remove git
              sudo apt install git


              instead.






              share|improve this answer
























                up vote
                5
                down vote










                up vote
                5
                down vote









                Try:



                sudo apt update 
                sudo apt --purge remove git
                sudo apt install git


                instead.






                share|improve this answer














                Try:



                sudo apt update 
                sudo apt --purge remove git
                sudo apt install git


                instead.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Sep 2 '16 at 16:45







                user308164

















                answered Sep 2 '16 at 13:58









                Scott Deagan

                10818




                10818




















                    up vote
                    2
                    down vote













                    Try uninstalling git-all, installing git-daemon-sysvinit, then installing git-all again. If you look at the package properties in Synaptic, you will find that git-all depends on either git-daemon-run or git-daemon-sysvinit. git-daemon-run is the one that gets installed by default for some reason, even though it's broken in Ubuntu 15.04 and up. (See https://bugs.launchpad.net/ubuntu/+source/runit/+bug/1448164) But if you install git-daemon-sysvinit manually first, then git-all's dependency will be satisfied, by a package that actually works. You can then install git-all, and everything should be fine.






                    share|improve this answer


















                    • 1




                      I should have clarified that I was using a workstation and not trying to configure a git server at the time. But for anyone who runs across this and is, this is good info ^
                      – Electronicks
                      Sep 6 '16 at 20:28














                    up vote
                    2
                    down vote













                    Try uninstalling git-all, installing git-daemon-sysvinit, then installing git-all again. If you look at the package properties in Synaptic, you will find that git-all depends on either git-daemon-run or git-daemon-sysvinit. git-daemon-run is the one that gets installed by default for some reason, even though it's broken in Ubuntu 15.04 and up. (See https://bugs.launchpad.net/ubuntu/+source/runit/+bug/1448164) But if you install git-daemon-sysvinit manually first, then git-all's dependency will be satisfied, by a package that actually works. You can then install git-all, and everything should be fine.






                    share|improve this answer


















                    • 1




                      I should have clarified that I was using a workstation and not trying to configure a git server at the time. But for anyone who runs across this and is, this is good info ^
                      – Electronicks
                      Sep 6 '16 at 20:28












                    up vote
                    2
                    down vote










                    up vote
                    2
                    down vote









                    Try uninstalling git-all, installing git-daemon-sysvinit, then installing git-all again. If you look at the package properties in Synaptic, you will find that git-all depends on either git-daemon-run or git-daemon-sysvinit. git-daemon-run is the one that gets installed by default for some reason, even though it's broken in Ubuntu 15.04 and up. (See https://bugs.launchpad.net/ubuntu/+source/runit/+bug/1448164) But if you install git-daemon-sysvinit manually first, then git-all's dependency will be satisfied, by a package that actually works. You can then install git-all, and everything should be fine.






                    share|improve this answer














                    Try uninstalling git-all, installing git-daemon-sysvinit, then installing git-all again. If you look at the package properties in Synaptic, you will find that git-all depends on either git-daemon-run or git-daemon-sysvinit. git-daemon-run is the one that gets installed by default for some reason, even though it's broken in Ubuntu 15.04 and up. (See https://bugs.launchpad.net/ubuntu/+source/runit/+bug/1448164) But if you install git-daemon-sysvinit manually first, then git-all's dependency will be satisfied, by a package that actually works. You can then install git-all, and everything should be fine.







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Oct 9 '16 at 22:17

























                    answered Jul 9 '16 at 15:43









                    Stephen G Tuggy

                    29116




                    29116







                    • 1




                      I should have clarified that I was using a workstation and not trying to configure a git server at the time. But for anyone who runs across this and is, this is good info ^
                      – Electronicks
                      Sep 6 '16 at 20:28












                    • 1




                      I should have clarified that I was using a workstation and not trying to configure a git server at the time. But for anyone who runs across this and is, this is good info ^
                      – Electronicks
                      Sep 6 '16 at 20:28







                    1




                    1




                    I should have clarified that I was using a workstation and not trying to configure a git server at the time. But for anyone who runs across this and is, this is good info ^
                    – Electronicks
                    Sep 6 '16 at 20:28




                    I should have clarified that I was using a workstation and not trying to configure a git server at the time. But for anyone who runs across this and is, this is good info ^
                    – Electronicks
                    Sep 6 '16 at 20:28










                    up vote
                    1
                    down vote













                    You are probably using Ubuntu under a virtual host. If so, you will need to modify initctl to return true using the following steps. First, you need to tell dpkg, that you are going to change the upstart package installation using:



                    sudo dpkg-divert --local --rename --add /sbin/initctl


                    Then, you need to create a dummy initctl as a link to true:



                    ln -s /bin/true /sbin/initctl





                    share|improve this answer




















                    • I was not using a virtual host but thank you anyway
                      – Electronicks
                      Sep 6 '16 at 20:28














                    up vote
                    1
                    down vote













                    You are probably using Ubuntu under a virtual host. If so, you will need to modify initctl to return true using the following steps. First, you need to tell dpkg, that you are going to change the upstart package installation using:



                    sudo dpkg-divert --local --rename --add /sbin/initctl


                    Then, you need to create a dummy initctl as a link to true:



                    ln -s /bin/true /sbin/initctl





                    share|improve this answer




















                    • I was not using a virtual host but thank you anyway
                      – Electronicks
                      Sep 6 '16 at 20:28












                    up vote
                    1
                    down vote










                    up vote
                    1
                    down vote









                    You are probably using Ubuntu under a virtual host. If so, you will need to modify initctl to return true using the following steps. First, you need to tell dpkg, that you are going to change the upstart package installation using:



                    sudo dpkg-divert --local --rename --add /sbin/initctl


                    Then, you need to create a dummy initctl as a link to true:



                    ln -s /bin/true /sbin/initctl





                    share|improve this answer












                    You are probably using Ubuntu under a virtual host. If so, you will need to modify initctl to return true using the following steps. First, you need to tell dpkg, that you are going to change the upstart package installation using:



                    sudo dpkg-divert --local --rename --add /sbin/initctl


                    Then, you need to create a dummy initctl as a link to true:



                    ln -s /bin/true /sbin/initctl






                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Sep 4 '16 at 12:07









                    Rohan Khude

                    17015




                    17015











                    • I was not using a virtual host but thank you anyway
                      – Electronicks
                      Sep 6 '16 at 20:28
















                    • I was not using a virtual host but thank you anyway
                      – Electronicks
                      Sep 6 '16 at 20:28















                    I was not using a virtual host but thank you anyway
                    – Electronicks
                    Sep 6 '16 at 20:28




                    I was not using a virtual host but thank you anyway
                    – Electronicks
                    Sep 6 '16 at 20:28

















                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f631615%2funable-to-connect-to-upstart-error-when-installing-git-all%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    Trouble downloading packages list due to a “Hash sum mismatch” error

                    How do so many people here on Academia.SE, and in general, afford lavish higher education programs?

                    How do I move numbers in filenames, in a batch renaming operation?