Rootstock fails in Lucid when more than 2 packages are given as seed.

Bug #585810 reported by Arvind Singh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
RootStock
New
Undecided
Unassigned

Bug Description

Rootstock version: rootstock-0.1.99.3
Here is my command line:
sudo ./rootstock --fqdn beagleboard --login ubuntu --password beagle --imagesize 4G --swapsize 512 --components "main,universe,multiverse" --seed openssh-server,build-essential,apache2,postgresql-server-dev-8.4,postgresql-contrib,sqlite3,libsqlite3-dev --dist lucid --serial ttyS2 --kernel-image http://rcn-ee.net/deb/kernel/beagle/lucid/v2.6.32.11-l13/linux-image-2.6.32.11-l13_1.0lucid_armel.deb
Fails with:
/bin/installer: line 55: 157 Segmentation fault apt-get -y install openssh-server build-essential apache2 postgresql-server-dev-8.4 postgresql-contrib sqlite3 libsqlite3-dev
E: Second stage build in Virtual Machine failed !
E: Please see the log to see what went wrong.
I: Cleaning up...
../rootstock: line 54: 5051 Killed qemu-system-arm $QEMUOPTS -append "${APPEND}" > $QEMUFIFO 2>&1
....
I: A logfile was saved as /home/asingh/met/v_4_1_0/ubuntu-sd/rootstock-201005260742.log
I: done ...
mkimage: Can't open ./vmlinuz-*: No such file or directory
This succeeds if I just give 2 packages as seed.
This was and is all working in Jaunty without any issues.

Revision history for this message
Oliver Grawert (ogra) wrote :

thanks, can you please attach the log file too ?

Revision history for this message
Arvind Singh (aaroh) wrote :

Please find log attached.

Thanks.

Revision history for this message
Arvind Singh (aaroh) wrote :

Please find attached log for working command.

Revision history for this message
Arvind Singh (aaroh) wrote :

Sorry above log for this commnet. Thanks.

This worked ok:

sudo ./rootstock --fqdn beagleboard --login ubuntu --password beagle --imagesize 4G --swapsize 256 --components "main,universe,multiverse" --seed openssh-server,build-essential --dist lucid --serial ttyS2 --kernel-image http://rcn-ee.net/deb/kernel/beagle/lucid/v2.6.32.11-l13/linux-image-2.6.32.11-l13_1.0lucid_armel.deb

As soon as I add one more package after build-essential it either hangs or crashes.

Please find the log for this attached.

Thanks again.

Revision history for this message
Arvind Singh (aaroh) wrote :

Hi Guys,

If somebody has any pointers on this, I would be more than happy to try.

Thanks.

Revision history for this message
Arvind Singh (aaroh) wrote :

So I reduced the swapsize and now it goes past apt but I get his error,

Setting up build-essential (11.4build1) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
I: Virtual Machine done
I: Creating tarball from rootfs
I: Mounting temporary Image
/usr/bin/rootstock: line 195: 29713 Segmentation fault qemu-system-arm $QEMUOPTS -append "${APPEND}" > $QEMUFIFO 2>&1
I: ARM rootfs created as /home/asingh/test/armel-rootfs-201006031142.tgz
I: Extracting vmlinuz from *.deb
cp: cannot stat `/tmp/tmp.UeWoUGFQpZ/tmpmount/boot/initrd.img-*': No such file or directory

It seems like this bug# 570588

https://bugs.launchpad.net/ubuntu/+source/rootstock/+bug/570588

Revision history for this message
Arvind Singh (aaroh) wrote :

Hi Guys,

Finally sanity is back and my rootstock command is working similar to 9.04 without segmentation fault with more than 2 packages as seed,

In function: setup_kernel_image()
I commented out these lines,

#Hack dpkg -i fails, no postinstall script is run anyways, so lets just extract it.
    #KERNEL_IMAGE_CMD="dpkg -x /tmp/$KERNEL_IMG /"

    #KERNEL_IMG_REL=${KERNEL_IMG##*linux-image-}
    #KERNEL_IMG_REL=${KERNEL_IMG_REL/_*_armel.deb}
    #KERNEL_IMG_REL=${KERNEL_IMG_REL%%_*}

    #KERNEL_IMAGE_CREATE_INITRAMFS="update-initramfs -c -k $KERNEL_IMG_REL"

I think these are added in new release and were not there in Ubuntu 9.04.
These lines crash the installer script.
I dont need initrd and I can install the downloaded kernel after reboot from /tmp by myself by just adding dpkg -i command to /etc/rc.local and then reboot.

I hope this helps someone who is stuck, till this bug is properly fixed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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