Re: [Fedora-livecd-list] Failed to create LiveCD

[Adam M. Dutko]

David,

     Unfortunately the error:

rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run
database recovery
Error installing packages
Error during installation...

fills the entire screen buffer and then some... I don't know of a way, other
than redirecting stdout to capture all of the information.  Considering it
takes a long, long time to build on my system it will take a little while to
do it that way.  I will capture the input and get back to you soon.  Another
interesting thing that happens, the above error occurs at the same time as
an I/O error related to the loopback device.  The following isn't an exact
duplicate but it is how it appears in my messages log:

/var/log/messages:Jan  7 21:11:37 laptop kernel: Buffer I/O error on device
loop0, logical block 772842
/var/log/messages:Jan  7 21:11:37 laptop kernel: lost page write due to I/O
error on loop0

I'm on the following... (uname -a)

Linux laptop.dux-linux.org 2.6.15-1.2054_FC5 #1 Tue Mar 14 15:48:33 EST 2006
i686 i686 i386 GNU/Linux

Here is my SELinux conf file:

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#       enforcing - SELinux security policy is enforced.
#       permissive - SELinux prints warnings instead of enforcing.
#       disabled - SELinux is fully disabled.
SELINUX=enforcing
# SELINUXTYPE= type of policy in use. Possible values are:
#       targeted - Only targeted network daemons are protected.
#       strict - Full SELinux protection.
SELINUXTYPE=targeted

I will do the following:

     1) Redirect stdout on the next build to capture the error and post my
findings.
     2) Turn off SELINUX (set to SELINUX=disabled), then redirect stdout on
a different build to see if I can get the error again, and post my findings.
     3) I will provide the complete I/O error in the the same post as 1 and
2.


Also, to reference your suggestion vnpenguin...

[amd59c@laptop python]$ rpm -ql kernel | grep squashfs
/lib/modules/2.6.15-1.2054_FC5/kernel/fs/squashfs
/lib/modules/2.6.15-1.2054_FC5/kernel/fs/squashfs/squashfs.ko

The kernel I am on appears to have squashfs support.  :-)

Thank you for your help David, Thomas and vnpenguin.

-Adam

Failed to create LiveCD

[Thomas Chung]

On 1/8/07, Adam Dutko <dutko.adam(a)gmail.com&gt; wrote:
>  ...
>  Also, to reference your suggestion vnpenguin...
>
>  [amd59c@laptop python]$ rpm -ql kernel | grep squashfs
>  /lib/modules/2.6.15- 1.2054_FC5/kernel/fs/squashfs
>  /lib/modules/2.6.15-1.2054_FC5/kernel/fs/squashfs/squashfs.ko
>
>  The kernel I am on appears to have squashfs support.  :-) 
Hmm, it seems you're running on FC5.
I don't know current livecd-tools support FC5. According to David's README.
http://gitweb.freedesktop.org/?p=users/david/livecd-tools.git;a=blob_plai...
"...and this should work on any FC6 system."
Regards,
-- 
Thomas Chung
http://fedoraproject.org/wiki/ThomasChung

Failed to create LiveCD

[David Zeuthen]

On Mon, 2007-01-08 at 15:21 -0800, Thomas Chung wrote:
>  On 1/8/07, Adam Dutko <dutko.adam(a)gmail.com&gt; wrote:
>  > ...
>  > Also, to reference your suggestion vnpenguin...
>  >
>  > [amd59c@laptop python]$ rpm -ql kernel | grep squashfs
>  > /lib/modules/2.6.15- 1.2054_FC5/kernel/fs/squashfs
>  > /lib/modules/2.6.15-1.2054_FC5/kernel/fs/squashfs/squashfs.ko
>  >
>  > The kernel I am on appears to have squashfs support.  :-)
>  
>  Hmm, it seems you're running on FC5.
>  I don't know current livecd-tools support FC5. According to David's README.
>  http://gitweb.freedesktop.org/?p=users/david/livecd-tools.git;a=blob_plai...
>  "...and this should work on any FC6 system."
>  Regards, 
It should work on FC3 or later (the pilgrim tools for OLPC that this is
based on is running on RHEL4 which is a downstream of FC3) but I haven't
tested on anything but FC6 and Rawhide.

     David

Failed to create LiveCD

[David Zeuthen]

On Mon, 2007-01-08 at 18:17 -0500, Adam Dutko wrote:
>  /var/log/messages:Jan  7 21:11:37 laptop kernel: Buffer I/O error on
>  device loop0, logical block 772842
>  /var/log/messages:Jan  7 21:11:37 laptop kernel: lost page write due
>  to I/O error on loop0 
The response from kernel people to a _loop device_ experiencing I/O
errors was: "cute". They suggested your system is either OOM or you're
running of disk space / disk quota. Is this the case?

Note that the files backing the loop devices are sparse files so the
creation of them works even when you don't have enough free space. The
reason for sparse files is that we don't have to spend time writing 4GB
of zero's to a file.

      David

Failed to create LiveCD

[David Zeuthen]

On Mon, 2007-01-08 at 18:45 -0500, David Zeuthen wrote:
>  On Mon, 2007-01-08 at 18:17 -0500, Adam Dutko wrote:
>  > /var/log/messages:Jan  7 21:11:37 laptop kernel: Buffer I/O error on
>  > device loop0, logical block 772842
>  > /var/log/messages:Jan  7 21:11:37 laptop kernel: lost page write due
>  > to I/O error on loop0
>  
>  The response from kernel people to a _loop device_ experiencing I/O
>  errors was: "cute". They suggested your system is either OOM or you're
>  running of disk space / disk quota. Is this the case? 
I meant "running out of", of course.

     David

Failed to create LiveCD

[Vnpenguin]

On 1/9/07, Adam Dutko <dutko.adam(a)gmail.com&gt; wrote:
>  Here is my SELinux conf file:
>
>  # This file controls the state of SELinux on the system.
>  # SELINUX= can take one of these three values:
>  #       enforcing - SELinux security policy is enforced.
>  #       permissive - SELinux prints warnings instead of enforcing.
>  #       disabled - SELinux is fully disabled.
>  SELINUX=enforcing
>  # SELINUXTYPE= type of policy in use. Possible values are:
>  #       targeted - Only targeted network daemons are protected.
>  #       strict - Full SELinux protection.
>  SELINUXTYPE=targeted
>
>  I will do the following:
>
>       1) Redirect stdout on the next build to capture the error and post my
>  findings.
>       2) Turn off SELINUX (set to SELINUX=disabled), then redirect stdout on
>  a different build to see if I can get the error again, and post my findings. 
I make livecd on updated FC6 with SELINUX=disabled. It's ok.

-- 
http://vnoss.org

Failed to create LiveCD

[David Zeuthen]

On Tue, 2007-01-09 at 06:45 +0100, Vnpenguin wrote:
>  I make livecd on updated FC6 with SELINUX=disabled. It's ok.
Interesting. Does the live CD boot with SELinux enabled in targeted mode
and does it work as expected?

     David

Failed to create LiveCD

[Vnpenguin]

On 1/9/07, David Zeuthen <davidz(a)redhat.com&gt; wrote:
>  On Tue, 2007-01-09 at 06:45 +0100, Vnpenguin wrote:
>  > I make livecd on updated FC6 with SELINUX=disabled. It's ok.
>
>  Interesting. Does the live CD boot with SELinux enabled in targeted mode
>  and does it work as expected?
>  
In my customized script, I added:

	cat <<EOF > /etc/selinux/config
SELINUX=disabled
SELINUXTYPE=targeted
SETLOCALDEFS=0
EOF

I never use SELinux before on my desktop. So I turn off it too for my
livecd. It works like my daily desktop, so I could say "ok" :)

Cheers,
-- 
http://vnoss.org

Failed to create LiveCD

[David Zeuthen]

On Tue, 2007-01-09 at 06:55 +0100, Vnpenguin wrote:
>  On 1/9/07, David Zeuthen <davidz(a)redhat.com&gt; wrote:
>  > On Tue, 2007-01-09 at 06:45 +0100, Vnpenguin wrote:
>  > > I make livecd on updated FC6 with SELINUX=disabled. It's ok.
>  >
>  > Interesting. Does the live CD boot with SELinux enabled in targeted mode
>  > and does it work as expected?
>  >
>  
>  In my customized script, I added:
>  
>  	cat <<EOF > /etc/selinux/config
>  SELINUX=disabled
>  SELINUXTYPE=targeted
>  SETLOCALDEFS=0
>  EOF
>  
>  I never use SELinux before on my desktop. So I turn off it too for my
>  livecd. It works like my daily desktop, so I could say "ok" :) 
SELinux brings lots of security features [1], it's definitely not
something we're going to disable in any official fedora live CD. If it
breaks something we definitely want to know so disabling it is bordering
counter-constructive :-)

So... I take that it didn't work for you unless you disabled SELinux on
the livecd or is it possible you can try to build an image on your FC6
box with SELinux but without the lines above and tell us what works and
what doesn't? Thanks!

     David

[1] : ... and, sure, SELinux can manage to be a major pain in the neck
sometimes. It's much better these days than just a year or two ago..

Failed to create LiveCD

[Vnpenguin]

On 1/9/07, David Zeuthen <davidz(a)redhat.com&gt; wrote:
>  SELinux brings lots of security features [1], it's definitely not
>  something we're going to disable in any official fedora live CD. If it
>  breaks something we definitely want to know so disabling it is bordering
>  counter-constructive :-)
>
>  So... I take that it didn't work for you unless you disabled SELinux on
>  the livecd or is it possible you can try to build an image on your FC6
>  box with SELinux but without the lines above and tell us what works and
>  what doesn't? Thanks!
>  
Sorry, I dont use SElinux so I can not test it.
Maybe another person in this list can do it.

-- 
http://vnoss.org

Failed to create LiveCD

[Thomas Chung]

On 1/10/07, Vnpenguin <vnpenguin(a)vnoss.org&gt; wrote:
>  On 1/9/07, David Zeuthen <davidz(a)redhat.com&gt; wrote:
>  >
>  > SELinux brings lots of security features [1], it's definitely not
>  > something we're going to disable in any official fedora live CD. If it
>  > breaks something we definitely want to know so disabling it is bordering
>  > counter-constructive :-)
>  >
>  > So... I take that it didn't work for you unless you disabled SELinux on
>  > the livecd or is it possible you can try to build an image on your FC6
>  > box with SELinux but without the lines above and tell us what works and
>  > what doesn't? Thanks!
>  >
>
>  Sorry, I dont use SElinux so I can not test it.
>  Maybe another person in this list can do it. 
I just was able to build one successfully with selinux enforcing option.
Latest updates as of today were included.
Regards,
-- 
Thomas Chung
http://fedoraproject.org/wiki/ThomasChung