Upgrading from Etch to Lenny - Revision history

Glenn: catspec

2011-10-21T21:23:07Z

catspec

Glenn: spelling

2011-10-21T20:22:13Z

spelling

Glenn: +cat

2011-10-21T19:20:20Z

+cat

78.43.22.87: Link to Installation_on_Debian

2009-08-09T13:26:47Z

Link to Installation_on_Debian

138.38.108.253: mnemoc explained this to me on the IRC channel and I though I'd document it so he didn't get sick of saying it.

2009-03-30T18:21:15Z

mnemoc explained this to me on the IRC channel and I though I'd document it so he didn't get sick of saying it.

New page

Problem : You've upgraded from Etch to Lenny, guests start just fine but hang when trying to connect to 127.0.0.1 (in my case it was Courier imapd, however FAM and most other things that access portmap will likely also break).

Cause : The Debian vserver kernel in Etch used a 2.0 series patch, while Lenny uses a 2.3 series patch. Between the two some impressive work was done and they way loopback addresses was handled was changed. The Debian Lenny kernel has CONFIG_VSERVER_AUTO_LBACK set, so it maps all guest access to 127.0.0.1 automagically and in a way that JFW (mostly). The file /etc/vservers/$VSERVERNAME/interfaces/lback contains the IP address that it is mapped to (for the given VSERVER).

Solution : To get the same behavior as the default Etch kernel, you will need to put the 'public' IP of the vserver into lback (i.e. cat /etc/vservers/$VSERVERNAME/interfaces/0/ip > /etc/vservers/$VSERVERNAME/interfaces/lback ). Then restart the vserver and everything should work as expected.

← Older revision		Revision as of 21:23, 21 October 2011
Line 7:		Line 7:
	See [[Installation_on_Debian]] for other issues.		See [[Installation_on_Debian]] for other issues.

−	[[Category:~~Documentation~~]]	+	[[Category:Migration]]

← Older revision		Revision as of 19:20, 21 October 2011
Line 6:		Line 6:

	See [[Installation_on_Debian]] for other issues.		See [[Installation_on_Debian]] for other issues.
		+
		+	[[Category:Documentation]]

← Older revision		Revision as of 13:26, 9 August 2009
Line 4:		Line 4:

	Solution : To get the same behavior as the default Etch kernel, you will need to put the 'public' IP of the vserver into lback (i.e. cat /etc/vservers/$VSERVERNAME/interfaces/0/ip > /etc/vservers/$VSERVERNAME/interfaces/lback ). Then restart the vserver and everything should work as expected.		Solution : To get the same behavior as the default Etch kernel, you will need to put the 'public' IP of the vserver into lback (i.e. cat /etc/vservers/$VSERVERNAME/interfaces/0/ip > /etc/vservers/$VSERVERNAME/interfaces/lback ). Then restart the vserver and everything should work as expected.
		+
		+	See [[Installation_on_Debian]] for other issues.

@@ Line 1: / Line 1: @@
 Problem : You've upgraded from Etch to Lenny, guests start just fine but hang when trying to connect to 127.0.0.1 (in my case it was Courier imapd, however FAM and most other things that access portmap will likely also break).
-Cause : The Debian vserver kernel in Etch used a 2.0 series patch, while Lenny uses a 2.3 series patch.  Between the two some impressive work was done and they way loopback addresses was handled was changed.  The Debian Lenny kernel has CONFIG_VSERVER_AUTO_LBACK set, so it maps all guest access to 127.0.0.1 automagically and in a way that JFW (mostly).  The file /etc/vservers/$VSERVERNAME/interfaces/lback contains the IP address that it is mapped to (for the given VSERVER).
+Cause : The Debian vserver kernel in Etch used a 2.0 series patch, while Lenny uses a 2.3 series patch.  Between the two some impressive work was done and the way loopback addresses was handled was changed.  The Debian Lenny kernel has CONFIG_VSERVER_AUTO_LBACK set, so it maps all guest access to 127.0.0.1 automagically and in a way that JFW (mostly).  The file /etc/vservers/$VSERVERNAME/interfaces/lback contains the IP address that it is mapped to (for the given VSERVER).
 Solution : To get the same behavior as the default Etch kernel, you will need to put the 'public' IP of the vserver into lback (i.e. cat /etc/vservers/$VSERVERNAME/interfaces/0/ip > /etc/vservers/$VSERVERNAME/interfaces/lback ).  Then restart the vserver and everything should work as expected.