Failed to read file ~/tmp/remaster-root/proc/*, creating empty file

Do you have the console window you created still open?

background: while working in the chrooted environment UCK
mounts - among other directories - /proc; from the looks of it
mksquashfs tries to pack /proc with little success...

Make sure you have all console windows and the package
manager closed before you continue the build process.

----- Original message -----
> New question #111133 on Ubuntu Customization Kit:
> https://answers.launchpad.net/uck/+question/111133
>
> I am using UCK 2.2.0 (SVN, May 14th, 2010) on Ubuntu 10.04, "Linux
> 2.6.32-22-generic-pae"  with the same ISO (ubuntu-10.04-desktop-i386.iso)
>
> I select "de" alone for any language question, I remove the windows stuff and I
> use the package-manager to install GIMP, use the console to create an empty file
> via "touch" and I use "sudo touch ~/tmp/remaster-root/from-outside-chroot" to
> create a file from the host-system.
>
> Then I continue the build process and all goes well until mksquashfs starts.
> After a short while (~2% into the progress) the screen gets flooded with
> messages like:
>
> --8<-------------------------------------------------------------------------------------------------
> Failed to read file /home/stw/tmp/remaster-root/proc/irq/5/spurious, creating
> empty file
>
> Failed to read file /home/stw/tmp/remaster-root/proc/irq/6/smp_affinity,
> creating empty file
>
> Failed to read file /home/stw/tmp/remaster-root/proc/irq/6/spurious, creating
> empty file
>
> Failed to read file /home/stw/tmp/remaster-root/proc/irq/7/smp_affinity,
> creating empty file
>
> Failed to read file /home/stw/tmp/remaster-root/proc/irq/7/spurious, creating
> empty file
>
> Failed to read file /home/stw/tmp/remaster-root/proc/irq/8/smp_affinity,
> creating empty file
> --8<-------------------------------------------------------------------------------------------------
>
> In "top" I see the mksquaschfs-process running for another while, then it
> disappears, but no more output is comming from UCK.
>
> --8<-------------------------------------------------------------------------------------------------
> stw@ten-o-four:/srv/home/stw-10.04$ ps ax | grep uck
>  1904 pts/0      S+        0:00 /bin/bash /usr/bin/uck-gui
>  1996 pts/0      S+        0:00 /bin/bash /usr/bin/uck-gui
>  1998 pts/0      S+        0:00 bash /usr/bin/uck-remaster
> /srv/home/stw-10.04/Guest-PC/ubuntu-10.04-desktop-i386.iso
> /home/stw/tmp/customization-scripts  4745 pts/0      S+        0:00 /bin/bash
> /usr/bin/uck-remaster-pack-rootfs -c /home/stw/tmp  5106 pts/2      S+        0:00
> grep --color=auto uck
> --8<-------------------------------------------------------------------------------------------------
>
> When I hit CTRL-C, I get the Build-Failure dialog box.
>
> Now I cannot remove ~/tmp until the next reboot. Not even as root.
>
> This is reproducable. I tried about 5 or 6 times. Three times I have seen the
> mysquashfs-progressbar between the errors, it stopped at 6%, 8% and 9%.
>
> If you need any more information, I will happily provide it.
>
>
>
> --
> You received this question notification because you are an answer
> contact for Ubuntu Customization Kit.

The console windows are all closed (except the one that opens to collect the password for sudo, where also the staus messages are being printed - if I close that one, it kills UCK), but sys and proc are not being unmounted.

Problem is solved by manually unmounting sys and proc before closing the chroot-console.
If this cannot be done automatically, there should be some kind of message that tells the user to do so himself.

Should I create a bug report?

Again: Thanks for this really usefull piece of software!

Stefan,

the umounts *should* be done automatically when the last window (except the console running the build.log ;-) is closed. If this does not happen, I would consider it a bug worth reporting,

BUT: I've been running UCK for quite some time and it has not happend to me.

I would definitely need your help (i.e. a precise script of the actions you perform in the console window for starters) to debug this.

If you are willing to spend the time to provide this information until I get to the point of being able to reproduce the problem, open up a bug report. I'm willing to spend the time to analyze and fix the issue but, unless I can reproduce it, I'm at a loss.

All I do is:

  * Start package manager, install GIMP, close package manager
  * Start console, "touch inside.chroot" and hit ctrl-d to exit the session.
  * On the host-system "touch ~/tmp/rebuild-root/outside.chroot" without changing into the directory. I even closed that terminal-window :)
  * Then I continue the build.

Could it be due to the CTRL-D instead of the explicit "exit"?

If you (or someone else) need any more specifics (logfiles, etc.) I am willing to spend more time investigating. It's the least I can contribute to help development

I'll try this tomorrow, although I cannot see any problems with the
commands you execute off hand. Can you please provide the complete
build.log file - it could contain further hints as to what goes wrong.

The build.log as well as the "interaction" in the terminal window can be found here:

http://stefan.waidele.info/UCK-fail.tgz
(more than 14MB of text, so I compressed to ~620KB. Nice ratio :)

Actions exactly as described above: Installed GIMP with package manager, "touch inside.chroot", "exit", "sudo touch ~/rebuild-root/outside.chroot" (in other window), continue build.

Then I watched with "top" until "mksquashfs" dissappeared.

Then Ctrl-C to get the build-failed dialog.

Just had a look at your build.logs: Looks as usual up to the point where the umounts should be happening
where there is: nothing... really weird! Looks as if the code to umount just weren't there/executed at all.

Here's the fragment that's missing from your build log, but is in mine (I've now run uck-gui twice - once in an english virtual machine, once in a german one - worked both times):

...
Processing triggers for python-central ...
CHOICE='Run package manager'
Starting package application...
CHOICE='Run console application'
Starting console application...

(gnome-terminal:4613): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
CHOICE='Continue building'
Done
Removing generated machine uuid...
Removing generated resolv.conf...
Unmounting /home/wjg/tmp/remaster-root/tmp/customization-scripts...
Unmounting /home/wjg/tmp/remaster-root/var/cache/apt...
Unmounting /home/wjg/tmp/remaster-root/root...
Unmounting /home/wjg/tmp/remaster-root/tmp...
Unmounting /home/wjg/tmp/remaster-root/var/run...
Unmounting /home/wjg/tmp/remaster-root/dev/pts...
Unmounting /home/wjg/tmp/remaster-root/sys...
Unmounting /home/wjg/tmp/remaster-root/proc...
Cleaning up temporary directories...
Running ISO customization script /home/wjg/tmp/customization-scripts/customize_iso...
...

Can you please check the md5sum for /usr/lib/uck/remaster-live-cd.sh (as this is where all the logic really is implemented)?

It should give you the following output:
df574710551f2581a3284d6f6c4eff59 /usr/lib/uck/remaster-live-cd.sh

As additional question: What type of file system is you rebuild-root on? NFS? Crypted? (BTW: I assume that ~/rebuild-root/ is actually ~/tmp/remaster-root/ because that is the default (which cannot be changed easily ;-))

1. Yes, whenever I wrote re*-root, it should have been ~/tmp/remaster-root/

2. The checksum is different:
876232d0dcb3e4cefa476d9606f2748f /usr/lib/uck/remaster-live-cd.sh
So, I guess we have the source of our problem - although I don't know how I got that buggy version of the script (or, more likely: How I messed it up.)

3. /home is a symlink to /srv/home, which is ext3 on a local harddrive. Not encrypted.

I guess I need to wipe everyting concerning UCK from my harddrive and install again.

Probably easier: Get a fresh copy of the 2.2.0 .deb from
http://uck.sourceforge.net/
Installing that should give you a clean slate.

I got this error from a misplaced double-quotation mark.