Hans Harder's picture

Well I got LXC working with the new OpenVZ 12.1 tar file of TKL core

But I am unsure what the new feature (subject) does, and before starting to hack things out, I better ask first :)

When I am now starting a fresh TKLcore inside LXC, I get after the login a dialog screen...  But that shows only some info and a Quit option...  

TurnKey Linux Configuration Console

          ────────CORE appliance services───────────────────┐
         │ Web shell:                 │
Webmin:                            │
SSH/SFTP:   root@ (port 22)                           │
         │                                                          │
         │ TKLBAM (Backup and Migration):  NOT INITIALIZED          │
         │                                                          │
         │                                                          │
         │          TurnKey Backups and Cloud Deployment            │
https://hub.turnkeylinux.org                                        │
         │                         < Quit >       

No screenshot, just a simple copy paste of the ascii...

is this normal.... or did I messed things up and is there a way to get the configuration screen

Hans Harder's picture

Well with a LAMP version it first asks for the Mysql password and then shows the screen.

So it seems ok....but somehow .....

Anyway LXC is working ok with the new OpenVz files, core and lamp just work after some small adaptions.  I will post the conversion script tomorrow after I cleaned it up.

QUOTE:  ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol

Hans Harder's picture

Seems that it works if debian is the host...

But on a RH6 box, i get when login in :

Last login: Mon Jun 17 15:33:29 UTC 2013 on console
Welcome to Core, TurnKey Linux 12.1 / Debian 6.0.7 Squeeze

  System information (as of Mon Jun 17 15:34:46 2013)

    System load:  0.16               Memory usage:  8%
    Processes:    12                 Swap usage:    0%
    Usage of /:   63.9% of 19.69GB   IP address for eth0:

  TKLBAM (Backup and Migration):  NOT INITIALIZED

    To initialize TKLBAM, run the "tklbam-init" command to link this
    system to your TurnKey Hub account. For details see the man page or
    go to:


Please set a terminal type.
Traceback (most recent call last):
  File "/usr/lib/inithooks/bin/screen_session.py", line 69, in <module>
  File "/usr/lib/inithooks/bin/screen_session.py", line 66, in main
  File "/usr/lib/inithooks/bin/screen_session.py", line 58, in screen_session
  File "/usr/lib/inithooks/bin/screen_session.py", line 51, in session_create
    executil.system("screen -S ", session_key, "--", *command)
  File "/usr/lib/python2.6/dist-packages/executil.py", line 56, in system
    raise ExecError(command, exitcode)
executil.ExecError: non-zero exitcode (1) for command: screen -S  'a0b1a04bd31e511611f42696c0d0e94c'  '--'  '/bin/bash'  '-c'  'turnkey-init && (chmod -x /root/.profile.d/turnkey-init-firstlogin; [ -x /etc/init.d/turnkey-init-fence ] && (update-rc.d turnkey-init-fence remove; /etc/init.d/turnkey-init-fence stop))'

Debian GNU/Linux 6.0 core console

core login:

That happens when I login using the console connection,,, when I login again it repeats...
If I connect to it with a ssh session, it gives me the dialog screens and it works like a charm...

QUOTE:  ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol

Add new comment