Matthew Roberts's picture


We installed a fresh Turnkey Wordpress and did a restore from our cloud backup, after matching the network configuration on the adapters. Once it reboots the console comes up with this error below:
Traceback (most recent call last):?  
 ?File "/usr/bin/confconsole", line 470, in loop?  
 ?new_dialog = method()?  
 ?File "/usr/bin/confconsole", line 225, in usage?  
 ?ifname = self._get_default_nic()?  
 ?File "/usr/bin/confconsole", line 141, in?  
 ?if ifname and _validip(ifname):?  
 ?File "/usr/bin/confconsole", line 135, in _validip?  
 ?ip = ifutil.get_ipconf(ifname)[0]?  
 ?File "/usr/lib/confconsole/", line 233, in?  
 ?net = InterfaceInfo(ifname)?  
 ?File "/usr/lib/python2.6/dist-packages/",?  
 ?line 85, in __init__?  
Though we're able to reach our wordpress sites, this error on the console is a little bit of a concern.
Please advise,
Jeremy Davis's picture

I don't recall, but I wouldn't have thought that TKLBAM would include networking info by default (at least it shouldn't IMO).

Matthew Roberts's picture


I'm unsure, exactly what you mean as to any modifications. 


Basically installed a new TKL Wordpress version. And ran tklbam-restore. I manually set our network interfaces before doing the restore and got this error. I also tried restoring without adding all of our network interfaces, and the same thing occurs.

Thanks Jeremy.

Jeremy Davis's picture

Ie did you run a default backup or did you customise your backup and include additional files?

If not I've got no idea. My backups work ok last time I tested (although perhaps I should test again?

Matthew Roberts's picture


I did not modify the backup, it was just a fresh install of wordpress and a tklbam-restore then this error pops up. Just looking for what this error even means to be honest and any suggestions on how to resolve.

Jeremy Davis's picture

And can't say I've ever encountered this issue. Obviously it's not ideal, but I wouldn't worry too much seeing as everything else seems to be working.

When referring to your backup I meant at the time you created the backup; whether you ran the default backup or whether you tweaked the TKLBAM backup config (or used switches etc) to include additional files/directories/etc in your original backup. I was guessing that perhaps you have included something in your backup that ideally shouldn't be there and is overwriting something it shouldn't when you restore (and thus breaking confconsole).

One thing you could try is simply removing confconsole and reinstalling it, like this:

apt-get update
apt-get remove --purge confconsole
apt-get install confconsole

Matthew Roberts's picture


I'm unsure, I was just placed in charge of managing a few TKL boxes at random. I'm not sure if anything was modified to those backups.

But thank you greatly! Removing and installing the confconsole worked.

Jeremy Davis's picture

But by the sounds of things I suspect that there are files included in your backup (that have been added by the previous maintainer) that ideally shouldn't be in there and that is where your problem has occurred.

Personally I'd be inclined to run a fresh backup and test it.

Drew Ruggles's picture

Yeah, just ran in to the exact same message, though I know how it happened, I'm not sure how to fix it.

Had to reinstall host OS (Mac OS X 10.8.3), Virtualbox (ain't no stinkin' Proxmox for Mac out there, Jeremy... ;-), then started loading VMs, one of which is my TKL LAMP stack. When it would boot, I received Network errors, similar to ones found in this thread. I went in to vi and edited the confconsole.conf file to remove the "#" in front of the 

default_nic eth0

because each time I started, ConfConsole said Networking was not set up. It was trying to configure eth2, which I have on the motherboard, but it's not configured (nor is there a LAN cable plugged in to it), so I wanted it to use eth0, and thought this might force the issue... Except the only issue it forced was the same error. See screenshot of stuck confconsole. Hitting < OK > simply returns to the same screen.

Now it's stuck. I can hit F7 to get out of confconsole, but I don't have a command line as it appears to be stuck during the startup. See screenshot.

What do I have to do to get to a command line where I can repair the confconsole.conf file?

Thanks. Drew

Drew Ruggles's picture

Hit [ Esc ] at stuck ConfConsole. Asked if I really wanted to Quit? Ya, sure, ya betcha. Command prompt.

All good. Back to figuring out the network issue...


Add new comment