05-15-2012 06:42 AM
Hello,
After upgrading our detection server to 11.5, Vountu update and Vountu monitor services fail to start.
Enforce server has upgraded successfull as appearnt on the management console, while detection server status remains unknown since the services didnt run after upgrade.
From the logs it is clear that there is not any license related problem, on the VontuMonitor logs traces on failure to start JVM process is the cause of failure to start the service.
Can i please get an explanation of the problem and a solution to it.
Thanks
05-15-2012 06:51 AM
can you post the logs please?
05-15-2012 07:25 AM
Here is the content of the error from the logs
STATUS | wrapper | 2012/05/15 16:12:48 | --> Wrapper Started as Service
STATUS | wrapper | 2012/05/15 16:12:48 | Java Service Wrapper Standard Edition 64-bit 3.3.9
STATUS | wrapper | 2012/05/15 16:12:48 | Copyright (C) 1999-2009 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2012/05/15 16:12:48 | http://wrapper.tanukisoftware.org
STATUS | wrapper | 2012/05/15 16:12:48 | Licensed to Symantec Corp. for VontuMonitor
STATUS | wrapper | 2012/05/15 16:12:48 |
STATUS | wrapper | 2012/05/15 16:12:48 | Launching a JVM...
FATAL | wrapper | 2012/05/15 16:12:48 | Unable to execute Java command. The system cannot find the file specified. (0x2)
FATAL | wrapper | 2012/05/15 16:12:48 | "..\..\jre\bin\java" -Dcom.vontu.properties=../config/Protect.properties -Djava.util.logging.config.file=../config/MonitorLogging.properties -Djava.endorsed.dirs=../lib/endorsed -XX:+UseCompressedOops -Xms128m -Xmx256m -Djava.library.path="../lib/native;C:\Vontu\Protect\lib\native;;C:\Vontu\jre\bin;C:\Vontu\jre\bin\client;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\System Center Operations Manager 2007\\" -classpath "../lib/jar/aggregator.jar;../lib/jar/bloomfilter.jar;../lib/jar/boxmonitor.jar;../lib/jar/classificationapi.jar;../lib/jar/command.jar;../lib/jar/communication.jar;../lib/jar/condition.jar;../lib/jar/cracker.jar;../lib/jar/dataidentifier.jar;../lib/jar/detection.jar;../lib/jar/detectioninterfaces.jar;../lib/jar/detectionresponse.jar;../lib/jar/filereader.jar;../lib/jar/flexresponseapi.jar;../lib/jar/incident_conditions.jar;../lib/jar/incidenthandler.jar;../lib/jar/incidentresponse.jar;../lib/jar/itemcatalog.jar;../lib/jar/javatoxml.jar;../lib/jar/jceks.jar;../lib/jar/keystorehouse.jar;../lib/jar/keyworddetection.jar;../lib/jar/license.jar;../lib/jar/logging.jar;../lib/jar/logmanagement.jar;../lib/jar/messaging.jar;../lib/jar/model_ojb.jar;../lib/jar/model_common.jar;../lib/jar/model_data.jar;../lib/jar/model_data_enum.jar;../lib/jar/monitorapi.jar;../lib/jar/monitorcommunication.jar;../lib/jar/nlp.jar;../lib/jar/policycontroller.jar;../lib/jar/policydependencychecker.jar;../lib/jar/policyloader.jar;../lib/jar/profileindex.jar;../lib/jar/profileindexer.jar;../lib/jar/profiles.jar;../lib/jar/protocols.jar;../lib/jar/responseconfig.jar;../lib/jar/security.jar;../lib/jar/statistics.jar;../lib/jar/systempatterns.jar;../lib/jar/updater.jar;../lib/jar/unicodeconverter.jar;../lib/jar/urlconnections.jar;../lib/jar/vontu_utilities.jar;../lib/jar/vontukeystorehouse.jar;../plugins/classification.jar;../plugins/directorycrawler.jar;../plugins/discover.jar;../plugins/inline_smtp.jar;../plugins/icap.jar;../plugins/lotusnotescrawler.jar;../plugins/NCSO.jar;../plugins/network.jar;../plugins/Notes.jar;../plugins/packetcapture.jar;../lib/jar/activation.jar;../lib/jar/axis.jar;../lib/jar/axis-jaxrpc.jar;../lib/jar/axis-wsdl4j.jar;../lib/jar/cern.jar;../lib/jar/concurrent.jar;../lib/jar/commons-beanutils-1.7.0.jar;../lib/jar/commons-codec.jar;../lib/jar/commons-collections-3.1.jar;../lib/jar/commons-configuration-1.4.jar;../lib/jar/commons-dbcp-1.2.1.jar;../lib/jar/commons-discovery.jar;../lib/jar/commons-digester-1.7.jar;../lib/jar/commons-httpclient.jar;../lib/jar/commons-io-1.4.jar;../lib/jar/commons-lang-2.3.jar;../lib/jar/commons-logging.jar;../lib/jar/commons-pool-1.3.jar;../lib/jar/csvfile.jar;../lib/jar/derby.jar;../lib/jar/derbynet.jar;../lib/jar/entropycrawler.jar;../lib/jar/es_common.jar;../lib/jar/es_ecispi.jar;../lib/jar/es_exchangewebstore.jar;../lib/jar/es_sharepointom.jar;../lib/jar/fast-md5.jar;../lib/jar/icu4j-3_6.jar;../lib/jar/icu4j-charsets-3_6.jar;../lib/jar/javax.servlet.jar;../lib/jar/jcifs-1.3.11.jar;../lib/jar/jcs.jar;../lib/jar/jdom-1.0.jar;../lib/jar/jmime.jar;../lib/jar/jsafeJCE.jar;../lib/jar/KeyView.jar;../lib/jar/mail.jar;../lib/jar/org.mortbay.jetty.jar;../lib/jar/rngpack.jar;../lib/jar/scriptengine.jar;../lib/jar/slic.jar;../lib/jar/slide-webdavlib.jar;../lib/jar/spring-beans.jar;../lib/jar/spring-context.jar;../lib/jar/spring-core.jar;../lib/jar/symanteccrypto.jar;../lib/jar/symanteccrypto_intg.jar;../lib/jar/tar.jar;../lib/jar/tomcat/vontu-catalina.jar;../lib/jar/tomcat/commons-modeler-2.0.1.jar;../lib/jar/tomcat/tomcat-coyote.jar;../lib/jar/tomcat/tomcat-http.jar;../lib/jar/tomcat/tomcat-coyote.jar;../lib/jar/tomcat/tomcat-util.jar;../lib/jar/tomcat/naming-resources.jar;../lib/jar/tomcat/naming-factory.jar;../lib/jar/vontu.db-ojb-1.0.4.jar;../lib/jar/wrapper.jar;../lib/jar/jetty/jetty-jmx-7.3.1.v20110307.jar;../lib/jar/jetty/jetty-jndi-7.3.1.v20110307.jar;../lib/jar/jetty/jetty-plus-7.3.1.v20110307.jar;../lib/jar/jetty/jetty-rewrite-7.3.1.v20110307.jar;../lib/jar/jetty/jetty-security-7.3.1.v20110307.jar;../lib/jar/jetty/jetty-server-7.3.1.v20110307.jar;../lib/jar/jetty/jetty-servlet-7.3.1.v20110307.jar;../lib/jar/jetty/jetty-servlets-7.3.1.v20110307.jar;../lib/jar/jetty/jetty-util-7.3.1.v20110307.jar;../lib/jar/jetty/jetty-webapp-7.3.1.v20110307.jar;../lib/jar/jetty/jetty-xml-7.3.1.v20110307.jar;../lib/jar/jetty/servlet-api-2.5.jar;../lib/jar/metro/webservices-rt.jar;../lib/jar/jetty/jetty-ajp-7.3.1.v20110307.jar;../lib/jar/jetty/jetty-annotations-7.3.1.v20110307.jar;../lib/jar/jetty/jetty-client-7.3.1.v20110307.jar;../lib/jar/jetty/jetty-continuation-7.3.1.v20110307.jar;../lib/jar/jetty/jetty-deploy-7.3.1.v20110307.jar;../lib/jar/jetty/jetty-http-7.3.1.v20110307.jar;../lib/jar/jetty/jetty-io-7.3.1.v20110307.jar;../lib/jar/jetty/jetty-websocket-7.3.1.v20110307.jar" -Dwrapper.key="g9LJhoL_qXHLq337UFvnF9okMpKWd4X6" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=232 -Dwrapper.timer_slow_threshold="2" -Dwrapper.version="3.3.9-st" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp com.vontu.boxmonitor.BoxMonitor
ADVICE | wrapper | 2012/05/15 16:12:48 |
ADVICE | wrapper | 2012/05/15 16:12:48 | ------------------------------------------------------------------------
ADVICE | wrapper | 2012/05/15 16:12:48 | Advice:
ADVICE | wrapper | 2012/05/15 16:12:48 | Usually when the Wrapper fails to start the JVM process, it is because
ADVICE | wrapper | 2012/05/15 16:12:48 | of a problem with the value of the configured Java command. Currently:
ADVICE | wrapper | 2012/05/15 16:12:48 | wrapper.java.command=..\..\jre\bin\java
ADVICE | wrapper | 2012/05/15 16:12:48 | Please make sure that the PATH or any other referenced environment
ADVICE | wrapper | 2012/05/15 16:12:48 | variables are correctly defined for the current environment.
ADVICE | wrapper | 2012/05/15 16:12:48 | ------------------------------------------------------------------------
ADVICE | wrapper | 2012/05/15 16:12:48 |
05-15-2012 08:54 AM
whats the path of java installed directory?
05-16-2012 12:16 AM
C:\Program Files\Java
C:\Program Files\Java\jre7
C:\Program Files\Java\jdk1.7.0_04
and dlp on C:\Vontu
05-16-2012 02:12 AM
I have solved it, the jre folder under Vounto was corrupt and missing important files, i fixed this and now it is similar to enforce server and everything went well.
services started and status healthy.
Thanks
05-16-2012 02:25 AM
Seems not, detection server status is unknown now although services are running
please advice
05-21-2012 01:21 AM
Layla, was your DLP installation performed on physical server or in virtual environment?
Note to admins: this thread should be moved in Security section, not reside in Inside Symantec.
06-08-2012 02:12 AM
We are using Symantec DLP 11.1. server trying to upgrade to DLP 11.5. during the installation got the failed with the following error.
No Detection server found at c:\Vontu\protect\updates\..\..\monitor.ver
please help us to resolve this.
Regards,
Mohan
10-26-2012 10:47 AM
This is a known issue -- see https://kb-vontu.altiris.com/display/1n/index.asp?aid=55705 for more information.
Manually copying the \jre folder from the upgrade folder (say, \detectionupgrade11.6) to the DLP root folder (\Vontu or \SymantecDLP), replacing the existing, incomplete \jre folder in the process, may be an easier workaround than disabling UAC in some environments. Once this is done and the appropriate binaries are in place, the Vontu services will start normally.