Problematic Programs - Revision history

Glenn: +Category:Software under linux-vserver

2011-10-21T20:43:47Z

2011-10-21T20:35:03Z

topsort

2011-10-21T18:48:53Z

+cat

2011-06-13T20:56:56Z

another problem with ejabberd, and the solution

2009-12-16T03:45:35Z

‎nagios issues

2009-03-22T15:33:36Z

2009-02-12T12:16:01Z

‎ejabberd

2009-02-03T22:29:58Z

‎Bind9 on Debian GNU/Linux Woody (3.0), Sarge (3.1), Etch (4.0)

2009-02-01T10:57:55Z

‎ejabberd

2008-11-04T16:11:27Z

‎Update (11/04/08)...

← Older revision		Revision as of 20:43, 21 October 2011
Line 597:		Line 597:
	Only do it if you just want your FAIserver in a seperate tree from main server.		Only do it if you just want your FAIserver in a seperate tree from main server.

		+	[[Category:Software under linux-vserver\| ]]
	[[Category:Documentation\| ]]		[[Category:Documentation\| ]]

← Older revision		Revision as of 20:35, 21 October 2011
Line 597:		Line 597:
	Only do it if you just want your FAIserver in a seperate tree from main server.		Only do it if you just want your FAIserver in a seperate tree from main server.

−	[[Category:Documentation]]	+	[[Category:Documentation\| ]]

← Older revision		Revision as of 18:48, 21 October 2011
Line 596:		Line 596:
	</div>		</div>
	Only do it if you just want your FAIserver in a seperate tree from main server.		Only do it if you just want your FAIserver in a seperate tree from main server.
		+
		+	[[Category:Documentation]]

← Older revision		Revision as of 20:56, 13 June 2011
Line 557:		Line 557:

	The Jabber server from the jabber package also works.		The Jabber server from the jabber package also works.
		+
		+	Other problem, which seems to happen with (at least) erlang R14B : epmd has been modified and accepts some commands only from 127/8, which causes problems. Details and solution can be found here : http://www.ejabberd.im/node/3709.
		+	In case this page becomes unavailable, the solution is to change network flags on the vserver, as follow (run these on the host) :
		+
		+	nattribute --set --nid vserver_name --flag ~single_ip
		+	echo "~single_ip" > /etc/vservers/vserver_name/nflags
		+

	=== VMware Server ===		=== VMware Server ===

@@ Line 479: / Line 479: @@
 This happens if you have the xineplug_inp_smb.so plugin. Delete it and everything is fine.
-=== 127.0.0.1 issues ===
+=== nagios ===
-I had problems with an application that wanted me to access it on 127.0.0.1 and AS 127.0.0.1 to be able to do its configuration. A simple tweak solved the problem. I renamed the default interface directory "0" in /etc/vservers/server/interfaces to "1" and created interface 0 as :
+Compiling nagios-1.4 within a vserver requires an explicit lo with 127.0.0.1, otherwise it hangs during the configure with "checking for ICMP ping syntax..."
-<pre>
-dev lo
+on older kernels, which do not support loopback isolation (separate 127.0.0.1) and use 'localhost' mapped to the first guest IP you can work around this by adding 127.0.0.1 to the interfaces (temporarily) but make sure to remove it afterwards.
-ip 127.0.0.1
-mask 255.0.0.0
-name lo
-</pre>
-now interface "1" is the default created interface by the vserver build script with a local adress like 192.168.1.2 and interface "0" is the loopback. I can now telnet on 127.0.0.1 and it sees that im connecting to 127.0.0.1 from 127.0.0.1
 <div style="color: red;">
 note: nagios is broken, because it uses a hardcoded 127.0.0.1, and this change (which is not needed with newer kernels providing lback remapping) will affect guest security and should not be used lightly (Bertl)

← Older revision		Revision as of 15:33, 22 March 2009
Line 580:		Line 580:
	The ntpd daemon needs to set the hardware time and can't do that from inside a vserver by default.		The ntpd daemon needs to set the hardware time and can't do that from inside a vserver by default.
	Allow CAP_SYS_TIME and ntpd will be happy.		Allow CAP_SYS_TIME and ntpd will be happy.
		+
		+	=== FAI server / fai-setup ===
		+	FAI Server / fai-setup
		+	fai-setup wants to create some devices and needs to mount proc.
		+
		+	bcapabilities:
		+	MKNOD
		+	ccapabilities:
		+	SECURE_MOUNT
		+	SECURE_REMOUNT
		+	BINARY_MOUNT
		+	<div style="color: red;">
		+	WARNING: this configuration reduces security big time
		+	</div>
		+	Only do it if you just want your FAIserver in a seperate tree from main server.

@@ Line 558: / Line 558: @@
 === ejabberd ===
-ejabberd does not work properly in a Linux-VServer guest under Debian Etch. The server eventually stops accepting connections. Also, it's not possible to control ejabberd with ejabberdctl.  The Jabber server from the jabber package works though.
+ejabberd does not work properly in a Linux-VServer guest under Debian Etch. The server eventually stops accepting connections. Also, it's not possible to control ejabberd with ejabberdctl.
-Newer versions of ejabberd (2.0.x) don't seem to have this problem. On Debian Etch a newer version can be installed from etch-backports ([http://backports.org/dokuwiki/doku.php?id=instructions backports.org])
+Newer versions of ejabberd (2.0.x) don't seem to have this problem. On Debian Etch a newer version can be installed from etch-backports ([http://backports.org/dokuwiki/doku.php?id=instructions backports.org]).
 === VMware Server ===

@@ Line 257: / Line 257: @@
 echo "bind9 hold" | dpkg --set-selections
 </pre>
 The last line is to set the package "on hold", so it is not touched by the update process. you have to take care of security holes by yourself now!

@@ Line 454: / Line 454: @@
 </pre>
 That tells named to start with the debug level globally set to 10.
-<br>
+<br><br>
 I also tinkered a little more and found that you can remove all of the db. files in /etc/bind and in /etc/bind/named.conf except for db.local and db.root. In other words, you don't need to configure or keep db.0, db.127, db.255, db.empty, nor do you need them referenced in named.conf.
 <br><br>