B
bhelmick
Guest
I have a very interesting problem that cropped up on my box last night. (RedHat Enterprise 4 with Plesk 7.5.4)
I changed the backup settings for all of my domains to backup to a local repository as I’ve been having numerous problems getting the remote backup feature to work reliably, but that’s not the point of the post. I came into the office this morning to find that three of my 21 domains are disabled. When I tried to enable them I received the following error message:
“Unable to activate/deactivate domain: domainmng failed: domainmng: /usr/local/psa/admin/bin/tomcatmng execution failed:
/var/tomcat4/conf/server.xml:196633: parser error: Extra content at the end of the document
</Server>
^
Tomcatmng: Document /var/tomcat4/conf/server.xml not parsed successfully
Domainmng: Error while turn on tomcat service on domain promoonly.comâ€
The only changes to this server I have made within the last several weeks is the backup settings for my domains. Last night was the first time the system was running the backup where the destination was the local repository. How this is relevant to the above problem is beyond me, and the reason for my post.
The problem was easy to fix, I just removed a redundant </Server> entry from the Server.xml file just as the error indicated. But I’m very concerned about what caused this problem for several reasons. First, I DO NOT have a license for TomCat on my server. So why on Earth did this error occur in the first place? Why does Plesk need to start TomCat if I don’t even own a license for it? Secondly, how could TomCat have a problem like this out of the blue, especially if nothing is configured to use it? Thirdly, considering all that has been changed is backup settings, how is this relevant to the error given by Tomcat?
I’ve attached the server.xml file to this email. It’s important to note that the file contains so much whitespace that it’s 750k uncompressed. Why? I have no idea, I'm hoping someone here can offer an expalantion. Any insight as to why this happened would be helpful. Thanks!
EDIT: Forum did not accept my attachment. I've placed a link here.
I changed the backup settings for all of my domains to backup to a local repository as I’ve been having numerous problems getting the remote backup feature to work reliably, but that’s not the point of the post. I came into the office this morning to find that three of my 21 domains are disabled. When I tried to enable them I received the following error message:
“Unable to activate/deactivate domain: domainmng failed: domainmng: /usr/local/psa/admin/bin/tomcatmng execution failed:
/var/tomcat4/conf/server.xml:196633: parser error: Extra content at the end of the document
</Server>
^
Tomcatmng: Document /var/tomcat4/conf/server.xml not parsed successfully
Domainmng: Error while turn on tomcat service on domain promoonly.comâ€
The only changes to this server I have made within the last several weeks is the backup settings for my domains. Last night was the first time the system was running the backup where the destination was the local repository. How this is relevant to the above problem is beyond me, and the reason for my post.
The problem was easy to fix, I just removed a redundant </Server> entry from the Server.xml file just as the error indicated. But I’m very concerned about what caused this problem for several reasons. First, I DO NOT have a license for TomCat on my server. So why on Earth did this error occur in the first place? Why does Plesk need to start TomCat if I don’t even own a license for it? Secondly, how could TomCat have a problem like this out of the blue, especially if nothing is configured to use it? Thirdly, considering all that has been changed is backup settings, how is this relevant to the error given by Tomcat?
I’ve attached the server.xml file to this email. It’s important to note that the file contains so much whitespace that it’s 750k uncompressed. Why? I have no idea, I'm hoping someone here can offer an expalantion. Any insight as to why this happened would be helpful. Thanks!
EDIT: Forum did not accept my attachment. I've placed a link here.