DAB Build Debian 7.1 Wheezy Template runtime errors in log of PVE 1.9

Discussion in 'Debian Appliance Builder' started by apmuthu, Sep 26, 2013.

  1. apmuthu

    apmuthu Member

    Joined:
    Feb 26, 2009
    Messages:
    744
    Likes Received:
    3
    Using DAB, built a debian 7.1 template on PVE 1.9

    dab.conf:
    Code:
    Suite: wheezy
    CacheDir: ../cache
    #Source: http://ftp.debian.org/debian SUITE main contrib
    #Source: http://ftp.debian.org/debian SUITE-updates main contrib
    #Source: http://security.debian.org SUITE/updates main contrib 
    Architecture: i386
    Name: debian-7.0-standard
    Version: 7.1-1
    Section: system
    Maintainer: Proxmox Support Team <support@proxmox.com>
    Infopage: http://pve.proxmox.com/wiki/Debian_7.0_Standard
    Description: Debian 7.0 (standard)
     A small Debian Wheezy system including all standard packages.
    
    Makefile:
    Code:
    
    
    BASEDIR:=$(shell dab basedir)
    
    all: info/init_ok
        dab bootstrap
        sed -e 's/^\s*1:2345:respawn/# 1:2345:respawn/' -i ${BASEDIR}/etc/inittab
        dab finalize
    
    info/init_ok: dab.conf
        dab init
        touch $@
    
    .PHONY: clean
    clean:
        dab clean
        rm -f *~
    
    .PHONY: dist-clean
    dist-clean:
        dab dist-clean
        rm -f *~
    
    
    When running an OpenVZ container based on this template, the init boot log shows:
    Code:
    INIT LOG    Online
    starting init logger
    INIT: version 2.88 booting
    stty: standard input: Invalid argument
    Using makefile-style concurrent boot in runlevel S.
    tcgetattr: Invalid argument
    [[36minfo[39;49m] Not setting System Clock.
    Activating swap...done.
    [....] Cleaning up temporary files... /tmp[?25l[?1c7[[32m ok [39;49m8[?25h[?0c.
    [....] Filesystem type 'simfs' is not supported. Skipping mount. ...[?25l[?1c7[warn[39;49m8[?25h[?0c [33m(warning).
    Fast boot enabled, so skipping file system check. ... (warning).
    [....] Mounting local filesystems...[?25l[?1c7[[32m ok [39;49m8[?25h[?0cdone.
    /etc/init.d/mountall.sh: 59: kill: Illegal number: 42 1
    [....] Activating swapfile swap...[?25l[?1c7[[32m ok [39;49m8[?25h[?0cdone.
    [....] Cleaning up temporary files...[?25l[?1c7[[32m ok [39;49m8[?25h[?0c.
    [....] Setting kernel variables ...[?25l[?1c7[[32m ok [39;49m8[?25h[?0cdone.
    [....] Configuring network interfaces...[?25l[?1c7[[32m ok [39;49m8[?25h[?0cdone.
    [....] Starting rpcbind daemon...[?25l[?1c7[[32m ok [39;49m8[?25h[?0c.
    [....] Cleaning up temporary files...[?25l[?1c7[[32m ok [39;49m8[?25h[?0c.
    [....] Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix[?25l[?1c7[[32m ok [39;49m8[?25h[?0c.
    INIT: Entering runlevel: 2
    stty: standard input: Invalid argument
    Using makefile-style concurrent boot in runlevel 2.
    tcgetattr: Invalid argument
    [....] Starting rpcbind daemon...[....] Already running.[?25l[?1c7[[32m ok [39;49m8[?25h[?0c.
    [....] Starting enhanced syslogd: rsyslogd[?25l[?1c7[[32m ok [39;49m8[?25h[?0c.
    [....] Starting deferred execution scheduler: atd[?25l[?1c7[[32m ok [39;49m8[?25h[?0c.
    [....] Starting periodic command scheduler: cron[?25l[?1c7[[32m ok [39;49m8[?25h[?0c.
    [....] Starting Postfix Mail Transport Agent: postfix[?25l[?1c7[[32m ok [39;49m8[?25h[?0c.
    generating ssh host keys
    [....] Starting OpenBSD Secure Shell server: sshd[?25l[?1c7[[32m ok [39;49m8[?25h[?0c.
    INIT: no more processes left in this runlevel
    
    The container runs normally.
    In the Makefile, if the sed statement is not there then respawning error occurs.

    The errors in the logs do not appear when running a container built using a similar DAB template for debian v6.0.7 with and without the sed statement in the Makefile.
     
    #1 apmuthu, Sep 26, 2013
    Last edited: Sep 26, 2013
  2. tom

    tom Proxmox Staff Member
    Staff Member

    Joined:
    Aug 29, 2006
    Messages:
    13,635
    Likes Received:
    418
    1.9 is VERY outdated. do not use it anymore as there are no security updates or bugfixes or support since a long time for this old version.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. apmuthu

    apmuthu Member

    Joined:
    Feb 26, 2009
    Messages:
    744
    Likes Received:
    3
    Very true Tom. The said host is in a secure trusted environment and is used for migration and testing only. The guest was being compiled for such use only, before migrating to a live environment which is far away and inaccessible remotely by policy. The local hardware is old and will not possibly run predictably or be stable or run at all on PVE 3.1.

    The post was to elicit any ideas as to why this might be happening.

    Anyone running PVE 1.9 on Wheezy? PVE 1.9 has been stable and well tested in production and no major support/update is envisaged for it as it just manages the Web GUI for the guests. Also it is lightweight and well documented and amenable to customisation easily.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice