dpkg killed when removing python packages












1















I'm trying to fix a dpkg error with one of my packages, python-zope.hookable.
The dpgk -l command looks like this:



 pFR python-zope.hookable                          4.0.4-4build2               amd64                       Hookable object support


However, when I run sudo dpkg -P --force-all python-zope.hookable, I mysteriously get this output:



dpkg: python-zope.hookable: dependency problems, but removing anyway as you requested:
python-zope.component depends on python-zope.hookable; however:
Package python-zope.hookable is to be removed.

dpkg: warning: overriding problem because --force enabled:
dpkg: warning: package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
(Reading database ... 871356 files and directories currently installed.)
Removing python-zope.hookable (4.0.4-4build2) ...
Killed
E: namespace:121: cannot remove /usr/lib/python2.7/dist-packages/zope/__init__.py



Creating an empty file at /usr/lib/python2.7/dist-packages/zope/__init__.py simply gives the same error, but without the last line. I suspect this is an issue with all python packages on my machine installed with dpkg, though I dare not test it.



This issue is preventing me from running apt-get install and apt-get remove, and dpkg --configure -a does not seem to change anything.



I'm really at my wits' end, and I'm open to drastic solutions.










share|improve this question







New contributor




Fred is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    The 'killed' indicates the process was killed by some other user or system - it's entirely possible that the system was attempting to remove it but took up too much memory and the system issued a "KILL" command to stop the process. Check the /var/log/syslog for any traces of 'process killed' or 'oom-killer' or such.

    – Thomas Ward
    2 days ago











  • Yes you are right. Syslog shows memory issues. I managed to resolve it after resizing the VPS.

    – Fred
    2 days ago











  • I've made a revision of my comment as an answer. If you wish you can accept it.

    – Thomas Ward
    2 days ago
















1















I'm trying to fix a dpkg error with one of my packages, python-zope.hookable.
The dpgk -l command looks like this:



 pFR python-zope.hookable                          4.0.4-4build2               amd64                       Hookable object support


However, when I run sudo dpkg -P --force-all python-zope.hookable, I mysteriously get this output:



dpkg: python-zope.hookable: dependency problems, but removing anyway as you requested:
python-zope.component depends on python-zope.hookable; however:
Package python-zope.hookable is to be removed.

dpkg: warning: overriding problem because --force enabled:
dpkg: warning: package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
(Reading database ... 871356 files and directories currently installed.)
Removing python-zope.hookable (4.0.4-4build2) ...
Killed
E: namespace:121: cannot remove /usr/lib/python2.7/dist-packages/zope/__init__.py



Creating an empty file at /usr/lib/python2.7/dist-packages/zope/__init__.py simply gives the same error, but without the last line. I suspect this is an issue with all python packages on my machine installed with dpkg, though I dare not test it.



This issue is preventing me from running apt-get install and apt-get remove, and dpkg --configure -a does not seem to change anything.



I'm really at my wits' end, and I'm open to drastic solutions.










share|improve this question







New contributor




Fred is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    The 'killed' indicates the process was killed by some other user or system - it's entirely possible that the system was attempting to remove it but took up too much memory and the system issued a "KILL" command to stop the process. Check the /var/log/syslog for any traces of 'process killed' or 'oom-killer' or such.

    – Thomas Ward
    2 days ago











  • Yes you are right. Syslog shows memory issues. I managed to resolve it after resizing the VPS.

    – Fred
    2 days ago











  • I've made a revision of my comment as an answer. If you wish you can accept it.

    – Thomas Ward
    2 days ago














1












1








1








I'm trying to fix a dpkg error with one of my packages, python-zope.hookable.
The dpgk -l command looks like this:



 pFR python-zope.hookable                          4.0.4-4build2               amd64                       Hookable object support


However, when I run sudo dpkg -P --force-all python-zope.hookable, I mysteriously get this output:



dpkg: python-zope.hookable: dependency problems, but removing anyway as you requested:
python-zope.component depends on python-zope.hookable; however:
Package python-zope.hookable is to be removed.

dpkg: warning: overriding problem because --force enabled:
dpkg: warning: package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
(Reading database ... 871356 files and directories currently installed.)
Removing python-zope.hookable (4.0.4-4build2) ...
Killed
E: namespace:121: cannot remove /usr/lib/python2.7/dist-packages/zope/__init__.py



Creating an empty file at /usr/lib/python2.7/dist-packages/zope/__init__.py simply gives the same error, but without the last line. I suspect this is an issue with all python packages on my machine installed with dpkg, though I dare not test it.



This issue is preventing me from running apt-get install and apt-get remove, and dpkg --configure -a does not seem to change anything.



I'm really at my wits' end, and I'm open to drastic solutions.










share|improve this question







New contributor




Fred is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I'm trying to fix a dpkg error with one of my packages, python-zope.hookable.
The dpgk -l command looks like this:



 pFR python-zope.hookable                          4.0.4-4build2               amd64                       Hookable object support


However, when I run sudo dpkg -P --force-all python-zope.hookable, I mysteriously get this output:



dpkg: python-zope.hookable: dependency problems, but removing anyway as you requested:
python-zope.component depends on python-zope.hookable; however:
Package python-zope.hookable is to be removed.

dpkg: warning: overriding problem because --force enabled:
dpkg: warning: package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
(Reading database ... 871356 files and directories currently installed.)
Removing python-zope.hookable (4.0.4-4build2) ...
Killed
E: namespace:121: cannot remove /usr/lib/python2.7/dist-packages/zope/__init__.py



Creating an empty file at /usr/lib/python2.7/dist-packages/zope/__init__.py simply gives the same error, but without the last line. I suspect this is an issue with all python packages on my machine installed with dpkg, though I dare not test it.



This issue is preventing me from running apt-get install and apt-get remove, and dpkg --configure -a does not seem to change anything.



I'm really at my wits' end, and I'm open to drastic solutions.







apt package-management dpkg






share|improve this question







New contributor




Fred is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Fred is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Fred is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 2 days ago









FredFred

82




82




New contributor




Fred is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Fred is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Fred is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 1





    The 'killed' indicates the process was killed by some other user or system - it's entirely possible that the system was attempting to remove it but took up too much memory and the system issued a "KILL" command to stop the process. Check the /var/log/syslog for any traces of 'process killed' or 'oom-killer' or such.

    – Thomas Ward
    2 days ago











  • Yes you are right. Syslog shows memory issues. I managed to resolve it after resizing the VPS.

    – Fred
    2 days ago











  • I've made a revision of my comment as an answer. If you wish you can accept it.

    – Thomas Ward
    2 days ago














  • 1





    The 'killed' indicates the process was killed by some other user or system - it's entirely possible that the system was attempting to remove it but took up too much memory and the system issued a "KILL" command to stop the process. Check the /var/log/syslog for any traces of 'process killed' or 'oom-killer' or such.

    – Thomas Ward
    2 days ago











  • Yes you are right. Syslog shows memory issues. I managed to resolve it after resizing the VPS.

    – Fred
    2 days ago











  • I've made a revision of my comment as an answer. If you wish you can accept it.

    – Thomas Ward
    2 days ago








1




1





The 'killed' indicates the process was killed by some other user or system - it's entirely possible that the system was attempting to remove it but took up too much memory and the system issued a "KILL" command to stop the process. Check the /var/log/syslog for any traces of 'process killed' or 'oom-killer' or such.

– Thomas Ward
2 days ago





The 'killed' indicates the process was killed by some other user or system - it's entirely possible that the system was attempting to remove it but took up too much memory and the system issued a "KILL" command to stop the process. Check the /var/log/syslog for any traces of 'process killed' or 'oom-killer' or such.

– Thomas Ward
2 days ago













Yes you are right. Syslog shows memory issues. I managed to resolve it after resizing the VPS.

– Fred
2 days ago





Yes you are right. Syslog shows memory issues. I managed to resolve it after resizing the VPS.

– Fred
2 days ago













I've made a revision of my comment as an answer. If you wish you can accept it.

– Thomas Ward
2 days ago





I've made a revision of my comment as an answer. If you wish you can accept it.

– Thomas Ward
2 days ago










2 Answers
2






active

oldest

votes


















0














Typically, the Killed message indicates the process was killed by some other user or system. This is either because of administrative, or automated, intervention and happens usually because over-used CPU or over-extended RAM and the system trying to free up resources for the system to run.



It's entirely possible that the system was attempting to remove it but took up too much memory and the system issued a "KILL" command to stop the process. I asked you to check the /var/log/syslog for any traces of 'process killed' or 'oom-killer' or such. Your comments in response to me on the question indicated the system was using the Out of Memory Killer or similar process because you were over-using the RAM and the system was trying to avoid running out of resources.



Therefore, the core problem was you did not have enough memory available to run everything on the system.



I would suggest evaluating all that's running and determine whether the RAM and specs you had gotten in the VPS are actually suitable; there can be cases where they aren't going to be and you'll need a larger VPS like you figured out here.






share|improve this answer































    0














    Since you wrote: "I'm really at my wits' end, and I'm open to drastic solutions."



    I'd suggest removing the block of the corresponding package from /var/lib/dpkg/status



    this should do the trick






    share|improve this answer
























    • I managed to avoid the system kill by increasing memory instead of doing this, though this sounds like a very useful trick that I could use in the future!

      – Fred
      2 days ago











    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',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });






    Fred is a new contributor. Be nice, and check out our Code of Conduct.










    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1113546%2fdpkg-killed-when-removing-python-packages%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Typically, the Killed message indicates the process was killed by some other user or system. This is either because of administrative, or automated, intervention and happens usually because over-used CPU or over-extended RAM and the system trying to free up resources for the system to run.



    It's entirely possible that the system was attempting to remove it but took up too much memory and the system issued a "KILL" command to stop the process. I asked you to check the /var/log/syslog for any traces of 'process killed' or 'oom-killer' or such. Your comments in response to me on the question indicated the system was using the Out of Memory Killer or similar process because you were over-using the RAM and the system was trying to avoid running out of resources.



    Therefore, the core problem was you did not have enough memory available to run everything on the system.



    I would suggest evaluating all that's running and determine whether the RAM and specs you had gotten in the VPS are actually suitable; there can be cases where they aren't going to be and you'll need a larger VPS like you figured out here.






    share|improve this answer




























      0














      Typically, the Killed message indicates the process was killed by some other user or system. This is either because of administrative, or automated, intervention and happens usually because over-used CPU or over-extended RAM and the system trying to free up resources for the system to run.



      It's entirely possible that the system was attempting to remove it but took up too much memory and the system issued a "KILL" command to stop the process. I asked you to check the /var/log/syslog for any traces of 'process killed' or 'oom-killer' or such. Your comments in response to me on the question indicated the system was using the Out of Memory Killer or similar process because you were over-using the RAM and the system was trying to avoid running out of resources.



      Therefore, the core problem was you did not have enough memory available to run everything on the system.



      I would suggest evaluating all that's running and determine whether the RAM and specs you had gotten in the VPS are actually suitable; there can be cases where they aren't going to be and you'll need a larger VPS like you figured out here.






      share|improve this answer


























        0












        0








        0







        Typically, the Killed message indicates the process was killed by some other user or system. This is either because of administrative, or automated, intervention and happens usually because over-used CPU or over-extended RAM and the system trying to free up resources for the system to run.



        It's entirely possible that the system was attempting to remove it but took up too much memory and the system issued a "KILL" command to stop the process. I asked you to check the /var/log/syslog for any traces of 'process killed' or 'oom-killer' or such. Your comments in response to me on the question indicated the system was using the Out of Memory Killer or similar process because you were over-using the RAM and the system was trying to avoid running out of resources.



        Therefore, the core problem was you did not have enough memory available to run everything on the system.



        I would suggest evaluating all that's running and determine whether the RAM and specs you had gotten in the VPS are actually suitable; there can be cases where they aren't going to be and you'll need a larger VPS like you figured out here.






        share|improve this answer













        Typically, the Killed message indicates the process was killed by some other user or system. This is either because of administrative, or automated, intervention and happens usually because over-used CPU or over-extended RAM and the system trying to free up resources for the system to run.



        It's entirely possible that the system was attempting to remove it but took up too much memory and the system issued a "KILL" command to stop the process. I asked you to check the /var/log/syslog for any traces of 'process killed' or 'oom-killer' or such. Your comments in response to me on the question indicated the system was using the Out of Memory Killer or similar process because you were over-using the RAM and the system was trying to avoid running out of resources.



        Therefore, the core problem was you did not have enough memory available to run everything on the system.



        I would suggest evaluating all that's running and determine whether the RAM and specs you had gotten in the VPS are actually suitable; there can be cases where they aren't going to be and you'll need a larger VPS like you figured out here.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 2 days ago









        Thomas WardThomas Ward

        44.1k23122174




        44.1k23122174

























            0














            Since you wrote: "I'm really at my wits' end, and I'm open to drastic solutions."



            I'd suggest removing the block of the corresponding package from /var/lib/dpkg/status



            this should do the trick






            share|improve this answer
























            • I managed to avoid the system kill by increasing memory instead of doing this, though this sounds like a very useful trick that I could use in the future!

              – Fred
              2 days ago
















            0














            Since you wrote: "I'm really at my wits' end, and I'm open to drastic solutions."



            I'd suggest removing the block of the corresponding package from /var/lib/dpkg/status



            this should do the trick






            share|improve this answer
























            • I managed to avoid the system kill by increasing memory instead of doing this, though this sounds like a very useful trick that I could use in the future!

              – Fred
              2 days ago














            0












            0








            0







            Since you wrote: "I'm really at my wits' end, and I'm open to drastic solutions."



            I'd suggest removing the block of the corresponding package from /var/lib/dpkg/status



            this should do the trick






            share|improve this answer













            Since you wrote: "I'm really at my wits' end, and I'm open to drastic solutions."



            I'd suggest removing the block of the corresponding package from /var/lib/dpkg/status



            this should do the trick







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered 2 days ago









            Alex BarchiesiAlex Barchiesi

            413




            413













            • I managed to avoid the system kill by increasing memory instead of doing this, though this sounds like a very useful trick that I could use in the future!

              – Fred
              2 days ago



















            • I managed to avoid the system kill by increasing memory instead of doing this, though this sounds like a very useful trick that I could use in the future!

              – Fred
              2 days ago

















            I managed to avoid the system kill by increasing memory instead of doing this, though this sounds like a very useful trick that I could use in the future!

            – Fred
            2 days ago





            I managed to avoid the system kill by increasing memory instead of doing this, though this sounds like a very useful trick that I could use in the future!

            – Fred
            2 days ago










            Fred is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            Fred is a new contributor. Be nice, and check out our Code of Conduct.













            Fred is a new contributor. Be nice, and check out our Code of Conduct.












            Fred is a new contributor. Be nice, and check out our Code of Conduct.
















            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1113546%2fdpkg-killed-when-removing-python-packages%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            數位音樂下載

            When can things happen in Etherscan, such as the picture below?

            格利澤436b