[Bug 107188] Re: [patch] Upgrade tool crashed with Cannot allocate memory
OMG its Michael! Thank goodness your here! Forgive my moronic meddling, I obviously have absolutely no clue what I am doing. I went over my patch again and realized that my changes to the commit retry loops: -currentRetry = 0 fprogress = self._view.getFetchProgress() iprogress = self._view.getInstallProgress(self.cache) # retry the fetching in case of errors maxRetries = self.config.getint(Network,MaxRetries) -while currentRetry maxRetries: +for currentRetry in range(maxRetries): ... except IOError, e: # fetch failed, will be retried logging.error(IOError in cache.commit(): '%s'. Retrying (currentTry: %s) % (e,currentRetry)) -currentRetry += 1 do absolutely nothing. :-D I somehow convinced myself that if an error other than a IOError were thrown, it would be magically caught by the try/catch statement and ignored, resulting in an infinite loop. This is obviously not the case, as erroneous exceptions are immediately passed up to DistUpgradeViewKDE and handled by _handleException. So that wasn't doing anything. No infinite loop. That leaves: -self[key].markUpgrade() +self[key].markInstall() as the only line which could have made any difference. (And it did for me and a few others for some reason.) What's interesting is that method call is only made in the section of the commit function that checks the state of the main metapackages (kubuntu-desktop, ubuntu-desktop, edubuntu-desktop, etc.). After looking back through my own logs and the logs that others have posted, I noticed that one commonality between some of them was kubuntu-desktop indicated that is wan't installed. In my case, kubuntu-desktop was accidentally removed accidentally by adept a while back when I replaced the ubuntu OO.o packages with ones from a third party repository to fix a font display issue. But this doesn't totally explain everything because the code that reports kubuntu-desktop as not being installed: if not metaPkgInstalled(): logging.debug(none of the '%s' meta-pkgs installed % metapkgs) for key in metapkgs: deps_found = True for pkg in self.config.getlist(key,KeyDependencies): deps_found = self.has_key(pkg) and self[pkg].isInstalled if deps_found: logging.debug(guessing '%s' as missing meta-pkg % key) try: self[key].markInstall() occurs after the line that the patch changes. What I do know is that the difference between my failure logs and my success logs is the kubuntu- desktop metapackage being reported as installed in my successful logs right where the error occurs in my failure logs. So far my only way to reliably test this has been to load Feisty installs onto my two sandbox towers and run them through the update process until they throw the error. Its a crude method of testing though and takes forever. I'm going to reload Feisty again on one of my tower, as both got to Gutsy despite my inept patch attempt, and give your patch a try. It makes sense to explicitly declare AutoDestroy as it is the KDEInstallProgressAdapter forks that seem to be causing the trouble, but I was under the impression that AutoDestroy was enabled by default. What would you recommend as the best way to get usable debugging output? pdb, strace, or even gdb? I don't usually code in python so I'm not familiar with the debugging methods. Many Thanks, BigPick -- [patch] Upgrade tool crashed with Cannot allocate memory https://bugs.launchpad.net/bugs/107188 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory
Alright, time for an update on my meddling. In my earlier investigation into this problem I avoided looking at the python-apt code utilized by the update-manager as this would broaden the scope of the fix to another package. This week, after exhausting all other possible explanations for the second memory leak as reported by Christian Assig and others, I dove in. I identified a possible memory leak in the commit() function in cache.py, and wrote an experimental patch. I will submit this as a new bug against the python-apt package in a moment. Anyone interested in helping resolve this issue, or checking my work, should take a look. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory https://bugs.launchpad.net/bugs/107188 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory
Bug filed, linky: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/159638 -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory https://bugs.launchpad.net/bugs/107188 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159638] Re: Possible Infinite Loop in commit() Method
** Attachment added: Experimental Patch http://launchpadlibrarian.net/10254282/python-apt-0.7.3.1bigpick5.patch -- Possible Infinite Loop in commit() Method https://bugs.launchpad.net/bugs/159638 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159638] Possible Infinite Loop in commit() Method
Public bug reported: Binary package hint: python-apt This bug is related to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/107188 In researching possible causes of the memory leak exceptions reported by some users attempting to upgrade using the upgrade-manager tool, a possible infinite loop resulting in memory leakage was identified in the commit() method of the Cache class in apt/cache.py. The method in question fetched and installed the required archives within a while loop, breaking from this loop only in the event of installArchives ResultCompleted or ResultFailed. The intended function of this loop was assumed to be to attempt repeating the installation if installArchives returned a value of ResultIncomplete. However, in some cases ResultIncomplete is returned due to an unmet condition of the installation, resulting in an infinite loop. A possible source of unmet conditions is a failure in fetching the archives to be installed; a situation not tested for within the loop. I am also submitting an experimental patch I used to resolve this issue on my machine. In the patch a check is added on the return value of _fetchArchives() before calling installArchives(), in an effort to stop the installation going forward without all pre-conditions being met. The fetching and installing of archives is removed from the loop, and a return value of ResultIncomplete causes a new type of system error to be raised. This was done because I believe it would be better to have the calling program make the decision to re-attempt installation rather than doing so automatically. The final change is just a response to the FIXME in the markUpgrade() function of apt/package.py. As described in the above update-manager bug report, the failure of markUpgrade() to raise an exception caused unexpected behavior in the update-manager code. The patch was written for the python-apt-0.7.3.1ubuntu4 source version. ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New -- Possible Infinite Loop in commit() Method https://bugs.launchpad.net/bugs/159638 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
All right, I am completely frustrated. First at my inability to fix the second memory leak and second by the total lack of developer input on this issue. My current working thoery is that commit() function in the Cache class of the python-apt library runs into an infinite loop if an archive install returns a result of Incomplete. My inability to replicate this error, and lack of familiarity with the python-apt library have thwarted my attempts to fix the problem. For now, I am just going to post the third revision of my patch, which is essentially a regression. The patch no longer alters the types of Exceptions caught by the programs try/catch statements as this was mainly an attempt at getting more information. This revision just has the single memory leak fix. I am incredibly displeased and disgusted by this entire situation. ** Attachment added: BigPick dist-upgrade patch rev 3 http://launchpadlibrarian.net/10180893/gutsy-dist-upgrade_bigpick_0.3.patch -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) https://bugs.launchpad.net/bugs/107188 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
Many thanks for the help you guys. I would also like to thank John and Christian Assig for their efforts so far. FerranRius's comment is very prudent and correct however, this upgrade should not be attempted whatsoever by anyone who uses their machine for work, school, or other important operations. The patch I posted is simply the fix I came up with for my situation when I attempted to upgrade Feisty on the laptop I use around campus. I never thought I'd be thankful for dual-booting windows, and to be honest, I resent the need to rely on it. Luckily, I have two old towers I use as sandboxes for messing around with networking and various Unix installations. One is an Intel/nVidia, the other is AMD/ATI, both failed the upgrade and became unbootable (so I'm 0 for 3), making them perfect candidates for trying to fix this. Currently there are two memory leaks occurring as far as I can tell, only one of which I have identified and addressed in the patch. The second appears to be coming from the fetching of backport archives, which occurs prior to the main upgrade. I am unable to replicate this leak on my machines, so I have relied on the work of Christian Assig to track this down. He deserves many thanks for bearing with my sophomoric efforts. Although this patch does not fix the second leak, Christian did report dist-upgrade faied gracefully instead of crashing by bringing up an error window and attempting to recover and reset the system. I need to repeat that I am not an official developer. I am a user with just enough information to make me dangerous. Nonetheless, I greatly appreciate your efforts to assist me in solving this critical issue. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) https://bugs.launchpad.net/bugs/107188 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155922] Re: Getting Upgrade prerequisites failed
You have just hit the bane of all of our existences currently. For more info check out: https://bugs.launchpad.net/bugs/107188 This is the main thread for the problem. https://bugs.launchpad.net/bugs/154493 The thread I first responded to. If you would like to help me with this problem try out the patch I posted and let me know how it goes. Beyond that I think we have solved your initial problem. I would recommend at least subscribing to the main thread at https://bugs.launchpad.net/bugs/107188 so that you can keep up with developments. -- Getting Upgrade prerequisites failed https://bugs.launchpad.net/bugs/155922 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155922] Re: Getting Upgrade prerequisites failed
I'm really glad to hear that! I would greatly appreciate it if you could post your results in using the patch, and the log files in /var/log/dist-upgrade/ to the https://bugs.launchpad.net/bugs/154493 thread. This will greatly assist my efforts in fixing these lingering issues. -- Getting Upgrade prerequisites failed https://bugs.launchpad.net/bugs/155922 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156508] Re: userconfig groups and privileges hard to use, fix included
I can confirm that this script works as advertised. This script resolves one of my biggest pet peeves with the user management in Kubuntu. I love the ability to assign permissions and groups upon user creation. -- userconfig groups and privileges hard to use, fix included https://bugs.launchpad.net/bugs/156508 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
I am pleased to report that using the above patch, my second sandbox tower was finally able to upgrade using the dist-upgrade.py script without error. I will run the test again on my other sandbox tower as soon as I revert it back to a Feisty install. Right now, I need to go to bed. While this result bodes well, I still need you all to try out the patch and report your results back here. Doing so will greatly aid in the resolution of other errors that still may be lurking. If you need some help applying the patch I posted instructions in the other bug report linked above, just make sure you download the second patch revision instead of the one used in the example. Once you have run the patch, successful or not, please post the log files located in /var/log/dist- upgrade/. I am not a developer, I am just a lowly peon user who had his install corrupted when the update-manager crashed. As such I need your assistance in getting this patch tested and, if successful, pushed to the higher-ups. Thank you for your help. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) https://bugs.launchpad.net/bugs/107188 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155922] Re: Getting Upgrade prerequisites failed
Blerg. Forgot the link. I need to go to bed. http://mh.archive.ubuntu.com/ubuntu/dists/gutsy/main/binary-i386/Packages.gz That is one of the Package lists that you error log indicated could not be downloaded. -- Getting Upgrade prerequisites failed https://bugs.launchpad.net/bugs/155922 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154493] Re: Distribution Upgrade fails to complete -- Cannot allocate memory
Well its a step in the right direction. The program is now failing more gracefully and is at least able to attempt recovery. This indicates that the infinite loop has been resolved, but the memory leak persists. I'm going to take a closer look at how the scripts are handling child processes. -- Distribution Upgrade fails to complete -- Cannot allocate memory https://bugs.launchpad.net/bugs/154493 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154493] Re: Distribution Upgrade fails to complete -- Cannot allocate memory
Hey Christian, could you do me the favor of posting the logs of your latest attempt. I'm having trouble finding the source of the error you described. Many thanks for helping fix this bug! -- Distribution Upgrade fails to complete -- Cannot allocate memory https://bugs.launchpad.net/bugs/154493 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155922] Re: Getting Upgrade prerequisites failed
Does the computer you are attempting to upgrade have a proxy server between it and the internet? Say like a workplace firewall/proxy? -- Getting Upgrade prerequisites failed https://bugs.launchpad.net/bugs/155922 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155922] Re: Getting Upgrade prerequisites failed
Typically, web-browsers such as Firefox have their own proxy settings. The global network proxy setting in Gnome may not be transferring over to KDE due to an oddity in knetworkmanager. Try setting up your proxy in KDE using knetworkmanager (should show up in the system tray automatically at boot), and trying the update again. Thank you for your patience with this issue, I wish I had a more definitive solution for you. -- Getting Upgrade prerequisites failed https://bugs.launchpad.net/bugs/155922 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154493] Re: Distribution Upgrade fails to complete -- Cannot allocate memory
Well those logs look very promising. As expected the patch stops the script from going into an infinite loop, however it did not solve the memory leak. 2007-10-23 18:34:55,490 INFO cache.commit() 2007-10-23 18:34:59,375 ERROR Unhandled exception in cache.commit(): '[Errno 12] Cannot allocate memory'. Retrying (currentRetry: 0) 2007-10-23 18:34:59,375 INFO cache.commit() 2007-10-23 18:35:01,607 ERROR Unhandled exception in cache.commit(): '[Errno 12] Cannot allocate memory'. Retrying (currentRetry: 1) 2007-10-23 18:35:01,607 INFO cache.commit() 2007-10-23 18:35:02,279 ERROR Unhandled exception in cache.commit(): '[Errno 12] Cannot allocate memory'. Retrying (currentRetry: 2) This clearly shows that somewhere, something is raising exceptions of a type other than SystemError, which most of the try/catch checks are looking for. So I have gone ahead and updated the patch to switch some of the try/catches to look for the more general Exception type instead of the specific System Error type. Not all have been changed, only those that I suspect are behaving badly. This will serve the dual purpose of helping the script to recover from these exceptions earlier, and it will properly log these exceptions. Unfortunately, I am unable to replicate this error on my machines, so I would greatly appreciate if you would download this new patch and, going through the same procedure in the above example, test the upgrade utility again. This particular patch probably won't fix the issue, but it will help identify what we need to do. When applying the patch, I recommend using a fresh extraction of gutsy.tar.gz; when the upgrade tool runs lots of changes are to the directory that might freak out the patch. ** Attachment added: dist-upgrade patch rev 2 http://launchpadlibrarian.net/10142497/gutsy-dist-upgrade_bigpick_0.2.patch -- Distribution Upgrade fails to complete -- Cannot allocate memory https://bugs.launchpad.net/bugs/154493 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155922] Re: Getting Upgrade prerequisites failed
** Changed in: adept (Ubuntu) Assignee: (unassigned) = BigPick (wpickard) -- Getting Upgrade prerequisites failed https://bugs.launchpad.net/bugs/155922 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154806] Re: 7.04 -- 7.10 upgrade tool crashed; out-of-memory
** Changed in: update-manager (Ubuntu) Assignee: (unassigned) = BigPick (wpickard) -- 7.04 -- 7.10 upgrade tool crashed; out-of-memory https://bugs.launchpad.net/bugs/154806 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
Hello fellow frustrated users. I also ran into this problem earlier. I have been working on a patch that resolves a major memory leak in the dist-upgrade scripts. Certain raised exceptions are causing infinite loops to occur. Currently, I have only been able to resolve one of these infinite loops, but the memory leak still remains. On the plus side, the upgrade is able to gracefully fail with the current patch and attempt recovery instead of just exiting. I would love to have some of you all test it out and post your resulting logs. It will greatly help diagnose the problem. For full info see this other bug: https://bugs.launchpad.net/ubuntu/+source/adept/+bug/154493 ** Attachment added: BigPick dist-upgrade patch rev 2 http://launchpadlibrarian.net/10144385/gutsy-dist-upgrade_bigpick_0.2.patch -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) https://bugs.launchpad.net/bugs/107188 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155922] Re: Getting Upgrade prerequisites failed
Ah, that environment variable is the key. I apologize for the knetworkmanager suggestion, you are correct, there is no proxy setting in knetworkmanager (I have no clue why it doesn't). Obviously I know little about configuring proxies, but this how-to should be of some use: https://help.ubuntu.com/community/AptGetHowto Specifically Methods #2 and #3: Adding the following lines to ~/.bashrc will cause the http_proxy variable to be set automatically. This way, programs that you run manually from a terminal will know to use the proxy. http_proxy=http://yourproxyaddress:proxyport export http_proxy Just to be safe you should also use Method #2 and add the following line to /etc/apt/apt.conf Acquire::http::Proxy http://yourproxyaddress:proxyport;; -- Getting Upgrade prerequisites failed https://bugs.launchpad.net/bugs/155922 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154806] Re: 7.04 -- 7.10 upgrade tool crashed; out-of-memory
*** This bug is a duplicate of bug 107188 *** https://bugs.launchpad.net/bugs/107188 ** This bug has been marked a duplicate of bug 107188 [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) -- 7.04 -- 7.10 upgrade tool crashed; out-of-memory https://bugs.launchpad.net/bugs/154806 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154493] Re: Distribution Upgrade fails to complete -- Cannot allocate memory
*** This bug is a duplicate of bug 107188 *** https://bugs.launchpad.net/bugs/107188 ** This bug has been marked a duplicate of bug 107188 [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) -- Distribution Upgrade fails to complete -- Cannot allocate memory https://bugs.launchpad.net/bugs/154493 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154493] Re: Distribution Upgrade fails to complete -- Cannot allocate memory
My apologies, I was not clear. I was not able to complete the Distribution Upgrade Tool after changing the links, however I was able to boot the system successfully. At this point the system is running perfectly, including compiz fusion, which is a pleasant surprise considering the amount of pain and agony usually required to get this laptop fully operational. The only remaining side effect is that adept still shows the Version Upgrade button. Sadly, clicking on that Version Upgrade button still results in the tool telling me that there are no upgrades available, asking me to file a bug report, then closing unexpectedly leaving behind the broken links. Its a vicious cycle. I'm just going to save myself some pain for now and refrain from pressing that little magic button of agony. The broken links may be an oddity of my system only. I have never heard of this occurring before. But the failure of the Distribution Upgrade Tool remains almost identical to what you described. -- Distribution Upgrade fails to complete -- Cannot allocate memory https://bugs.launchpad.net/bugs/154493 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154493] Re: Distribution Upgrade fails to complete -- Cannot allocate memory
I have identified the error and written a patch to the dist-update scripts. The error is very serious in nature and is likely causing many other bugs, crashes and corruptions. As indicated in the error logs, the Distribution Upgrade Tool exits due to an out of memory error when trying to spawn a thread. This low memory condition is caused by an infinite loop in the doUpdate() method in the DistUpgradeControler class. The infinite loop in turn, is a result of an incomplete markUpgrade() method in /usr/lib/python2.5/site- packages/apt/package.py. The loop is incremented upon reception of an IOError Exception, however this exception is not thrown as expected. The loop is designed to terminate if no Exception is received, but an Exception of a type other than IOError is sometimes returned resulting in an endless loop. To fix these issues, the patch replaces the reference to the stub markUpgrade() method with markInstall(). While not ideal, the result is the same. Additionally, I added some robustness to the maxRetries loops in DistUpgradeControler.py by converting them to 'for' loops. A fall-back 'except' was also added to the loops purely for the purposes of debugging. To use this patch, download the Gutsy dist-upgrade script package from http://archive.ubuntu.com/ubuntu/dists/gutsy/main/dist-upgrader- all/0.81/gutsy.tar.gz, extract and apply the patch. The just navigate to the extracted directory and run ./dist-upgrade.py. ** Attachment added: dist-upgrade patch http://launchpadlibrarian.net/10123821/gusty-dist-upgrade.patch -- Distribution Upgrade fails to complete -- Cannot allocate memory https://bugs.launchpad.net/bugs/154493 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154493] Re: Distribution Upgrade fails to complete -- Cannot allocate memory
An example will help. What we want to do is manually download the dist- upgrade scripts from the archives without adept. We are then going to patch this script, and run it locally. Adept does the exact same thing, except it stores the dist-upgrade scripts in a temporary folder that is removed once the scripts exit. We need the scripts to stick around. (I also just realized I misspelled the patch name. Oh well.) Example: ~$ wget http://archive.ubuntu.com/ubuntu/dists/gutsy/main/dist-upgrader-all/0.81/gutsy.tar.gz ~$ mkdir gutsy ~$ cd gutsy ~/gutsy$ tar xzvf ../gutsy.tar.gz ~/gutsy$ wget http://launchpadlibrarian.net/10123821/gusty-dist-upgrade.patch ~/gutsy$ patch -p1 gusty-dist-upgrade.patch ~/gutsy$ sudo ./dist-upgrade.py -- Distribution Upgrade fails to complete -- Cannot allocate memory https://bugs.launchpad.net/bugs/154493 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154493] Re: Distribution Upgrade fails to complete -- Cannot allocate memory
Bug described is dangerous memory leak in dist-upgrade. Bug confirmed and reproducible. Possible patch uploaded. ** Changed in: adept (Ubuntu) Assignee: (unassigned) = BigPick (wpickard) Status: New = In Progress -- Distribution Upgrade fails to complete -- Cannot allocate memory https://bugs.launchpad.net/bugs/154493 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154564] Re: Bug #76983 fix does not work! Feisty to Gutsy upgrade fails @ gpg verification
If you have the update-manager-core package installed, run do-release- upgrade. Full instructions at: https://help.ubuntu.com/community/GutsyUpgrades -- Bug #76983 fix does not work! Feisty to Gutsy upgrade fails @ gpg verification https://bugs.launchpad.net/bugs/154564 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155922] Re: Getting Upgrade prerequisites failed
You might need to try the attachment one more time. It does not seem to have taken. Thank you for your effort in helping track this problem down. -- Getting Upgrade prerequisites failed https://bugs.launchpad.net/bugs/155922 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154710] Re: Error during upgrade to Kubuntu 7.10 : Failed to fetch
Thank you for reporting this bug. Unfortunately, canonical's commercial repositories for Gusty are not yet operational. De-selecting the canonical gutsy commercial repositories should allow the upgrade to proceed normally. I'm sorry but I do not know when the repositories will become operational or why they have been delayed. -- Error during upgrade to Kubuntu 7.10 : Failed to fetch https://bugs.launchpad.net/bugs/154710 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154470] Re: non-existent /home/ crashes upgrade of Kubuntu 7.04 - 7.10
Thank you for submitting this bug. The /home directory does not appear to be a requirement of the dist- upgrade scripts. Although the /, /boot, /usr, /var, /home and archive directories are all checked for size, only /, /boot, /usr, /var, and the archive directories then have free space allocated. From what I can see, the /home reference should be changed to a HOME environmental variable reference. -- non-existent /home/ crashes upgrade of Kubuntu 7.04 - 7.10 https://bugs.launchpad.net/bugs/154470 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155922] Re: Getting Upgrade prerequisites failed
Try using the Add a comment/attachment button on Launchpad's web interface. If you just attach the file to an email reply, it will not show up for those not subscribed to this bug. If you are using the web interface, then something else wonky is happening. :-P -- Getting Upgrade prerequisites failed https://bugs.launchpad.net/bugs/155922 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 150878] Re: [kubuntu] Failed to upgrade Feisty - Gutsy
This bug is very similar, if not identical in nature to https://bugs.launchpad.net/ubuntu/+source/adept/+bug/154493 I posted the patch I used to get the scripts working in the other bug report. Let me know if they help solve your problem. -- [kubuntu] Failed to upgrade Feisty - Gutsy https://bugs.launchpad.net/bugs/150878 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155922] Re: Getting Upgrade prerequisites failed
Perfect! I'm looking at it now. -- Getting Upgrade prerequisites failed https://bugs.launchpad.net/bugs/155922 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155922] Re: Getting Upgrade prerequisites failed
Try accessing this link using your web-browser. You don't need to actually download the file, just make sure you can and no 403: Access Denied error comes up. If an error does come up, this indicates a connection problem between you and the archives. The error page that comes up in the web-browser might provide some more detailed information on why this error is occurring. If no error comes up, go ahead and try to run the update again. -- Getting Upgrade prerequisites failed https://bugs.launchpad.net/bugs/155922 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154493] Re: Distribution Upgrade fails to complete -- Cannot allocate memory
I can confirm this error. Identical circumstances. Upgrade Feisty - Gusty using adept Distribution Upgrade Tool. Tool goes through all steps until Installing the upgrades, at which point the tool closes unexpectedly. Upgrade was completed using aptitude, however some important scripts have obviously not been run as dbus is failing initialize properly at boot and requires manual restart to get Network Manager, guidance-power- manager and HAL related operations to run properly. Additionally, adept continues to show the Version Upgrade button even though aptitude full-upgrade and /etc/lsb-release report the upgrade is complete as mentioned above. ** Attachment added: Logs from /var/log/dist-upgrade. http://launchpadlibrarian.net/10110849/dist-upgrade-log.tar.bz2 -- Distribution Upgrade fails to complete -- Cannot allocate memory https://bugs.launchpad.net/bugs/154493 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154493] Re: Distribution Upgrade fails to complete -- Cannot allocate memory
UPDATE: The dbus problem was resolved. At some point during the upgrade the /etc/rc2.d/S12dbus link was changed to /etc/rc2.d/S50dbus. The /etc/rc2.d/S10acpid was also changed to /etc/rc2.d/S50acpid. These changes resulted in the dbus and acpid init scripts being called too late in boot process. At first I thought this was a freak accident, however I was surprised to find that these changes were repeated upon running the Distribution Upgrade Tool again. I am at a loss to explain why this is occurring. -- Distribution Upgrade fails to complete -- Cannot allocate memory https://bugs.launchpad.net/bugs/154493 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
