[out of memory] installer crashed cause: timezone

Bug #194130 reported by Azgarth
6
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 212, in <module>
    main()
  File "/usr/lib/ubiquity/bin/ubiquity", line 207, in main
    install(args[0])
  File "/usr/lib/ubiquity/bin/ubiquity", line 65, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 425, in run
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 776, in progress_loop
    (ret, realtb))
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
  File "/usr/share/ubiquity/install.py", line 1768, in <module>
    install.run()
  File "/usr/share/ubiquity/install.py", line 378, in run
    self.configure_timezone()
  File "/usr/share/ubiquity/install.py", line 972, in configure_timezone
    raise InstallStepError("TimezoneApply failed with code %d" % ret)
InstallStepError: TimezoneApply failed with code 1

using opengeu.
installing through the livecd, choosing amsterdam as timezone.
install halts at 87%, "configuring time zone..."

Revision history for this message
Azgarth (azgarth1) wrote :
Revision history for this message
Colin Watson (cjwatson) wrote :

The failures start with:

  Feb 21 21:35:45 ubuntu ubiquity: Unable to write mmap - msync (28 No space left on device)

It looks like you're out of memory, and admittedly ubiquity isn't detecting this as well as it might.

Revision history for this message
TerryG (tgalati4) wrote :

Triage to Incomplete pending verification of sufficient hard disk space to do proper installation. 2 to 2.5 GB is generally required for Ubuntu installs. If shy on hard disk space, all sorts of strange errors can happen.

Changed in ubiquity:
status: New → Incomplete
Revision history for this message
TerryG (tgalati4) wrote :

Marked to Confirmed. After more carefully reviewing your syslog file, I have a theory:

You have a 2.66 GHz Core 2 Duo, with 1 GB of RAM, 500 MB of swap, several large hard disks with Windows installed on one partition.
Syslog shows several errors trying to enumerate the NTFS partition. It's possible that enumeration problem caused a memory leak/fill up. Installation proceeded normally until some thread required more RAM (like setting up timezone and reading the timezone database).

Is it possible to disconnect the windows hard drive cable and try to reinstall on another physical disk drive? Perhaps you can do a scandisk on the windows drive and check it for errors. I don't have any windows machines that I can tinker with to test. The one XP Pro machine that I have has a Citrix client that I can't mess with.

Let us know what finally works to get a successful install.

Changed in ubiquity:
status: Incomplete → Confirmed
tags: added: ubiquity-1.6.8
tags: added: gutsy
Revision history for this message
Brian Murray (brian-murray) wrote : Traceback

Exception during installation:
Feb 21 21:37:55 ubuntu python: Traceback (most recent call last):
Feb 21 21:37:55 ubuntu python: File "/usr/share/ubiquity/install.py", line 1768, in <module>
Feb 21 21:37:55 ubuntu python: install.run()
Feb 21 21:37:55 ubuntu python: File "/usr/share/ubiquity/install.py", line 378, in run
Feb 21 21:37:55 ubuntu python: self.configure_timezone()
Feb 21 21:37:55 ubuntu python: File "/usr/share/ubiquity/install.py", line 972, in configure_timezone
Feb 21 21:37:55 ubuntu python: raise InstallStepError("TimezoneApply failed with code %d" % ret)
Feb 21 21:37:55 ubuntu python: InstallStepError: TimezoneApply failed with code 1
Feb 21 21:37:55 ubuntu python:

tags: added: installer-crash
Revision history for this message
Phillip Susi (psusi) wrote :

It looks like the cause of this was never really confirmed. Are you able to reproduce this?

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.