Peter Michalak's picture
Peter Michalak - Thu, 2013/10/17 - 16:07

Hi there,

I have a problem building new appliance (based on LAMP) and wondering if there are some ways how to debug what is happening, the output which I get when running make is:

(see attached file)

I've tried to delete that file, but I still get the same error. Can I turn on some more detailed loging or is there any other way how I can find out what's wrong?

Thank you.

 

-Peter

Forum: 
Support
Tags: 
lamp
tkldev
Alon Swartz's picture

Alon Swartz - Thu, 2013/10/17 - 17:01

I came across this myself at the beginning of the week. I'll first explain what you need to do to fix the problem, then I'll try and explain what caused it.

Fixing the issue:

You first need to clean any broken builds (make clean), Make sure that the bootstrap isn't mounted (mount), but make clean should handle that.

Update the bootstrap (there are 2 ways you could do this):

1. Manually upgrade the bootstrap

cd /turnkey/fab/bootstraps
CODENAME=$(lsb_release -s -c)
fab-chroot $CODENAME
  apt-get update
  apt-get -y upgrade
  exit

2. Download the updated bootstrap

cd /turnkey/fab/bootstraps
CODENAME=$(lsb_release -s -c)
rm -rf $CODENAME

# follow https://github.com/turnkeylinux-apps/tkldev/blob/master/docs/setup.rst#1-bootstrap

 

What caused the issue:

When fab installs the plan in build/root.build it temporarily short-circuits a number of files, one of them being used to start services. Debian released a number of updates over the weekend (when Debian 7.2 was released). One of the packages overrode fab's short-circuit, and so some services were being started.

When build/root.build is complete, even if services are running fab will kill them before moving onto build/root.patched. But, the problem arised that the dev mount bind into build/root.build wasn't unmounted, which caused a little havoc.

We'll be looking into a way handle these type of things in future, but in the meantime we've updated the bootstraps, and hopefully the above fixes will get you (and others) going again...

Peter Michalak's picture

Peter Michalak - Fri, 2013/10/18 - 09:06

Hi Alan,

thank you for proposed fix and explanation. I've tried the first solution, but that didn't seem to have any effect:

root@tkldev products/lamp# cd /turnkey/fab/bootstraps/
root@tkldev fab/bootstraps# CODENAME=$(lsb_release -s -c)
root@tkldev fab/bootstraps# fab-chroot $CODENAME
root@tkldev:/# apt-get update
Reading package lists... Done
root@tkldev:/# apt-get -y upgrade
Reading package lists... Done
Building dependency tree... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@tkldev:/# exit
exit
 
(I did `make clean` before, but make ended up with the same error as the last time)
 
Then the second solution, I've removed the wheezy folder downloaded bootstrap as you are saying and after make I've hit the same problem. This time I'm attaching full log as it might be something in there (ok I don't see the option to attach the file so output is here: http://pastebin.com/HEx1fqwS). 
I've followed your steps few times, but no luck. I might just go with your latest 13.0rc3 version and try to build from there : ).
Alon Swartz's picture

Alon Swartz - Fri, 2013/10/18 - 10:17

The bootstrap doesn't include a sources.list nor resolv.conf, so you'll need to add those if you're going route #1:

CODENAME=$(lsb_release -s -c)
cd /turnkey/fab/bootstraps

cat >$CODENAME/etc/apt/sources.list.d/sources.list<<EOF
deb http://cdn.debian.net/debian $CODENAME main
deb http://security.debian.org/ $CODENAME/updates main
EOF

cat >$CODENAME/etc/resolv.conf<<EOF
nameserver 8.8.8.8
nameserver 8.8.4.4
EOF

fab-chroot $CODENAME "apt-get update"
fab-chroot $CODENAME "DEBIAN_FRONTEND=noninteractive apt-get -y upgrade"

rm $CODENAME/etc/apt/sources.list.d/sources.list
rm $CODENAME/etc/resolv.conf

But, its very important to clean any broken builds, and make sure nothing is mounted. If make clean fails, it should tell you why and hopefully how to fix it.

Peter Michalak's picture

Peter Michalak - Fri, 2013/10/18 - 11:27

Thank you for help, my tkldev environment is producing ISOs again!

Have a great weekend!

-Peter

Add new comment