You are here
I am trying to Restore a TKLBAM image that started on Bare Metal with 2 Network Cards enabled. Moving to (via restore) VMWare Instance with one Network Card enabled. (All 32bit).
I get a "complete" no error Restore in Webmin, but when I reboot, my Control Console gives me an error (not able to determine IP Address). Apache not running. Pretty much disfunctional image.
Right now I will install from ISO Wheezy (as the Bare Metal was Squeeze ISO). I will then do sequential installs.. Magento Files, Databases (no packages) to see how we can rectify.
Any thoughts on the IP problem after restore? I started with the same primary IP address. The second IP was not being used on Bare Metal but I could see that it was available to be configured.
Error in TurnKey Linux
Error in TurnKey Linux Configuration Console
Caught exception
(Then 88%) so I don't believe I am seeing the end of the error.
This was on the ISO. This time I also crashed in Database restore. With the Non ISO restore I did not crash at ISO restore but it looks like my /usr/lib/confconsole is getting whacked by restore. I need to work on the "Limits" to exclude any update to that set of folders it seems.
Will try turnkey-init
I tired to reinitialize with turnkey-init. Didn't seem to change anything. In Webmin there were two network interfaces showing. One (ETH0) set to Static IP, the other (ETH1) to DHCP.
I tried deleteding ETH1 but no effect.
Just did a test new install, both interfaces show up in a Virtual Server.
The issue seems to be "Default" IP. Somehow this is either "destroyed" when TKLBAM-Restore runs.
After Restore I was able to get in via WebMin and WebShell. Starting Apache was giving an error (syntax, line 208 of apache.conf). I commented out the line and was able to get Apache started.
Still Magento was not starting. Somehow the system was not opening the main Magento Database.
Working on hand crafted restore next (or fixing my original server which keeps hanging).
So what if I did a TKLBAM
So what if I did a TKLBAM Restore and added the "limits= -/usr/" so that nothing in the USR directory was overwritten. It seems the Error are in /usr/bin/ and /usr/lib/. See below. Where else might the IP address be overwritten in TKLBAM restore? I have not ever seen the situation otherwise.
Up and running (haven't yet tried the "-/usr/" command yet
I sequentially ran tklbam restore for the following
-- skip-database --skip-packages --limits= /var/magento
-- skip-database --skip-packages --limits= /etc/ssl
-- skip-database --skip-packages --limits= /etc/apache 2
-- skip-files --skip-packages --limits= mysql:magento
Apache would not start, so Commented out line 208 referencing httpd.conf (need to find out what that is).
Apache then startded
After this I ran a special "magento cleanup" which clears cache and session files.
Shutdown, Added Ram to Config. Starte
Did not get the error on the ConfigConsole I was getting.
Was able to get into Magento Admin and Magento Front End.
I expect I need to look at etc/php5 as well as the aforementioned httpd.conf file (was it in old system?)
Looks like we are (hopefully at least) back in business.
FWIW /etc/apache2/httpd.conf is default Apache conf
If you look at the default Apache setup (as used in RHEL/CentOS/etc) the config is somewhat different and the httpd.conf file is the main config file. Debian (and derivatives such as Ubuntu) do things a little differently and split the Apache config up into separate files (such as apache2.conf, ports.conf, etc). However the httpd.conf file is still read by Apache to allow backward compatibility.
From what I can figure, Webmin edits httpd.conf (as Webmin is a general Linux Admin UI and does it that way so it is compatible with RHEL/CentOS and Debian. So I assume that at some point you have used Webmin to configure Apache and it has included the changes you made in the httpd.conf file. Obviously somewhere along the line, the config in httpd.conf is clashing with some other Apache setting somewhere else (in one of the other Debian style Apache config files). I suggest that you have a look at your httpd.conf file and compare it to the other relevant Apache conf files.
Thank you Jeremy
I am not sure if I was using httpd.conf earlier. It is not in the current build though the reference seemed to show up when I ran TKLBAM so it must be in the old server (I have not gone to the CoLo to turn it on).
Likely this was an old setup from Ubuntu that kept together in Squeeze. New build is Wheezy and it made it through.
The subjects of the Default IP reference was confounding. I will still try a tklbam using limits= -/usr to see what happens. So far though my Magento install has kept running w/out visible errors for a day now which was goal #1.
Great!
Glad that your v13 instance is all systems go! :)
Add new comment