DAB jessie builds fail

apmuthu

Well-Known Member
Feb 26, 2009
807
8
58
Chennai - India & Singapore
github.com
The page http://pve.proxmox.com/wiki/Debian_8.0_Standard has yet to be made though the dab-pve-appliances build files have been released.
DAB Build fails in both minimal and standard versions of the i386 build for jessie (debian-8.0):

Code:
# make

allocated VE 90000
dab init
download: http://ftp.debian.org/debian/dists/jessie/Release
download: http://ftp.debian.org/debian/dists/jessie/Release.gpg
download: http://ftp.debian.org/debian/dists/jessie/main/binary-i386/Packages.gz
download: http://ftp.debian.org/debian/dists/jessie/contrib/binary-i386/Packages.gz
download: http://ftp.debian.org/debian/dists/jessie-updates/Release
download: http://ftp.debian.org/debian/dists/jessie-updates/Release.gpg
download: http://ftp.debian.org/debian/dists/jessie-updates/main/binary-i386/Packages.gz
download: http://ftp.debian.org/debian/dists/jessie-updates/contrib/binary-i386/Packages.gz
download: http://ftp.debian.org/debian/dists/jessie-backports/Release
download: http://ftp.debian.org/debian/dists/jessie-backports/Release.gpg
download: http://ftp.debian.org/debian/dists/jessie-backports/main/binary-i386/Packages.gz
download: http://ftp.debian.org/debian/dists/jessie-backports/contrib/binary-i386/Packages.gz
download: http://security.debian.org/dists/jessie/updates/Release
download: http://security.debian.org/dists/jessie/updates/Release.gpg
download: http://security.debian.org/dists/jessie/updates/main/binary-i386/Packages.gz
download: http://security.debian.org/dists/jessie/updates/contrib/binary-i386/Packages.gz
touch info/init_ok
dab bootstrap --minimal
initialize VE 90000
generating available package list
package 'systemd' depends on exclusion ' udev'
package 'systemd' depends on exclusion ' udev'
make: *** [all] Error 25

This will probably have something to do with systemd being used in it since
In April 2012, the source tree for udev (a device manager for the Linux kernel, which handles the /dev directory and all user space actions when adding/removing devices, including firmware loading) was merged into systemd.[7]
.

Any fixes - ref?


 
Last edited:
Thanks Dietmar. DAB.pm stands fixed in the Git except for "MySQL skip grant tables" that needs jessie to be added.
Code:
@@ -1504,7 +1518,7 @@ sub ve_mysql_bootstrap {
 
     my $suite = $self->{config}->{suite};
  
-    if ($suite eq 'squeeze' || $suite eq 'wheezy' ) {
+    if ($suite eq 'squeeze' || $suite eq 'wheezy') {
        $cmd = "/usr/sbin/mysqld --bootstrap --user=mysql --skip-grant-tables";
 
     } else {
should have been:
Code:
@@ -1504,7 +1518,7 @@ sub ve_mysql_bootstrap {
 
     my $suite = $self->{config}->{suite};
  
-    if ($suite eq 'squeeze' || $suite eq 'wheezy' ) {
+    if ($suite eq 'squeeze' || $suite eq 'wheezy' || $suite eq 'jessie') {
        $cmd = "/usr/sbin/mysqld --bootstrap --user=mysql --skip-grant-tables";
 
     } else {
 
Jessie runs Apache v2.4 whilst Wheezy was on v2.2. This breaks a lot.
The default site is now 000-default.
Inside the directory for webroot the following are needed:
Code:
#        # Ref: http://httpd.apache.org/docs/current/upgrading.html
#        # New directive needed in Apache 2.4.3:
        Require all granted

The following perl warnings pop up during a DAB Build (dab exec):

Code:
# a2dissite 000-default

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = (unset),
        LC_ALL = (unset),
        LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Site 000-default disabled.
To activate the new configuration, you need to run:
  service apache2 reload

Upgrading from Apache 2.2 to 2.4 requires that the apache conf file has the .conf extension now.

Are we going to stay with Apache 2.2 in DAB or should we now build for Apache 2.4?
 
Last edited:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").

Please set LANG=C to avoid such warnings. You can do that in the Makefile

export LC_ALL:=C
 
In the Makefile, will the following do:
export LC_ALL:=C
or must it be
dab exec export LC_ALL:=C

Will the export only be visible in the container or will it propagate to the host and need to be reset there?

===

On actually building a DAB jessie based template, the following resulted:

dab exec export LC_ALL:=C
Code:
dab exec export LC_ALL:=C/sbin/defenv: 10: exec: export: not found
ve_exec failed - status 127
ve_exec failed - status 127
make: *** [all] Error 127

export LC_ALL:=C (Error Reference)
Code:
export LC_ALL:=C
/bin/sh: 1: export: LC_ALL:: bad variable name
make: *** [all] Error 2

export LC_ALL=C (without the colon) did not raise any errors. (Reference).
 
Last edited:
/usr/sbin/dab in DAB v1.2-7 and v1.2-6 have:
Code:
$ENV{'LC_ALL'} = 'C';

Hence is export LC_ALL=C useful in the Makefile?
Warnings anyway are suppressed. Any way of knowing if the warning appears when export is used in the Makefile.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!