I had a previous installation of PVE 1.8, of an OpenVZ container with the base Debian 6, running a CollabNet Subversion Edge server.
To perform an update to PVE 2.1 I backed up the container on an NFS resource, and everything went fine on restore. I restarted then the SVN Edge console (a Java web console), and I found myself with a frozen java process, no more responding. Logs weren't useful, they showed nothing interesting happening, as it was confirmed on a discussion on SVN Edge help forum -- see http://subversion.open.collab.net/ds/viewMessage.do?dsForumId=3&dsMessageId=459184
I tried switching from Debian to Centos 5.6, but the behavior was exactly the same, no action, no messages.
Then I tried installing a base Debian 6 in a KVM virtual machine, instead of an OpenVZ container. Everything started working flawlessly!
Now, the only thing I can think of is some issue about the interaction between Java and OpenVZ...
The only two requirements for SVN Edge are python and java (see http://www.collab.net/lightbox/download_info/60/31), and for Debian I installed packages python2.6 and sun-java6-jre (from the non-free repository), plus adding an environment variable JAVA_HOME -- SVN Edge distribution tgz can be uncompressed in a directory and simply launched.
Anyone can confirm similar Java related issues?
I don't ask for a workaround, since I don't feel so confident that there already is one
~Lou
[EDIT]
I tried to install and run an alternative application to Subversion Edge, named "uberSVN" (http://www.ubersvn.com/).
Unfortunately the result is the same, since this alternative runs with Java as well: I have the Java machine dead again.
This makes me think I won't ever run any Java based server on this microserver, if it's managed by PVE 2.1 ...
[EDIT]
I eventually had to downgrade to PVE 1.9, the latest that does run Java properly: with 2.1 I couldn't run anything with Java, in an OpenVZ container!
To perform an update to PVE 2.1 I backed up the container on an NFS resource, and everything went fine on restore. I restarted then the SVN Edge console (a Java web console), and I found myself with a frozen java process, no more responding. Logs weren't useful, they showed nothing interesting happening, as it was confirmed on a discussion on SVN Edge help forum -- see http://subversion.open.collab.net/ds/viewMessage.do?dsForumId=3&dsMessageId=459184
I tried switching from Debian to Centos 5.6, but the behavior was exactly the same, no action, no messages.
Then I tried installing a base Debian 6 in a KVM virtual machine, instead of an OpenVZ container. Everything started working flawlessly!
Now, the only thing I can think of is some issue about the interaction between Java and OpenVZ...
The only two requirements for SVN Edge are python and java (see http://www.collab.net/lightbox/download_info/60/31), and for Debian I installed packages python2.6 and sun-java6-jre (from the non-free repository), plus adding an environment variable JAVA_HOME -- SVN Edge distribution tgz can be uncompressed in a directory and simply launched.
Anyone can confirm similar Java related issues?
I don't ask for a workaround, since I don't feel so confident that there already is one
~Lou
[EDIT]
I tried to install and run an alternative application to Subversion Edge, named "uberSVN" (http://www.ubersvn.com/).
Unfortunately the result is the same, since this alternative runs with Java as well: I have the Java machine dead again.
This makes me think I won't ever run any Java based server on this microserver, if it's managed by PVE 2.1 ...
[EDIT]
I eventually had to downgrade to PVE 1.9, the latest that does run Java properly: with 2.1 I couldn't run anything with Java, in an OpenVZ container!
Last edited: