My Oracle Support Banner

MDVOP - 2.4 Linux Version Printing Information to the Console (Doc ID 2392972.1)

Last updated on MAY 07, 2018

Applies to:

StorageTek Service Delivery Platform (SDP2) - Version 2.4.0 to 2.4.0 [Release 2.0]
Information in this document applies to any platform.


When the Linux version of MDVOP 2.4 is started from the command line, it doesn't return the prompt after starting the client. Instead, it continues to print information to that terminal.

Sample output below shows the issue with starting mdvop and the messages continuing to get sent to the console:

[xxx@xxxxxx mdvop]$ ./mdvop
Starting mdvop
[xxx@xxxxxx mdvop]$ Mon Apr 30 09:10:57.964 2018 MDT [1] INFO at addEntry(): Command line parameters =
Mon Apr 30 09:10:58.021 2018 MDT [1] INFO at addEntry(): Wrote to /home/xxx/.mdvop//tmp/run_mdvop: #!/bin/sh
cd /home/xxx/xxx/mdvop/
"/home/xxx/xxx/mdvop/java/bin/java" -classpath "lib:lib/VOP.jar:lib/AbsoluteLayout.jar:lib/AdventNetLogging.jar:lib/AdventNetSnmp.jar:lib/appframework-1.0.3.jar:lib/ASR.jar:lib/bcprov-jdk16-1.46.jar:lib/beansbinding-1.2.1.jar:lib/borland.jar:lib/cds.jar:lib/cfmtclient.jar:lib/CommonCode.jar:lib/commons-logging-1.1.1.jar:lib/commons-net-3.4.jar:lib/CST.jar:lib/DAO.jar:lib/DCMP.jar:lib/DTSping.jar:lib/ept.jar:lib/EventHeader.jar:lib/EventMonitor.jar:lib/httpclient-4.2.5.jar:lib/httpclient.jar:lib/httpcore-4.2.4.jar:lib/IFS.jar:lib/jcert.jar:lib/Jelo.jar:lib/jersey-apache-client-1.19.jar:lib/jersey-client-1.10.jar:lib/jersey-core-1.10.jar:lib/jersey-multipart-1.10.jar:lib/jsch-0.1.52.jar:lib/jsse.jar:lib/LibraryProbe.jar:lib/log4j-1.2.17.jar:lib/MainLib.jar:lib/maverick-1.6.14.jar:lib/SFTP.jar:lib/slf4j-api-1.7.2.jar:lib/slf4j-nop-1.7.2.jar:lib/SNMP.jar:lib/TDP.jar:lib/TEQCommon.jar:lib/Test_Tape_Drive.jar:lib/Transport-Client-3.1.1.jar:lib/VOP.jar:lib/VSM.jar:lib/xmlParserAPIs.jar:lib/xmlparserv2.jar" -Dapplication.user.home="/home/xxx" com.storagetek.vop.VOPmain.MDVOPMain "/home/xxx/.mdvop/configurations/empty_configuration.xml"

Mon Apr 30 09:10:58.022 2018 MDT [1] INFO at addEntry(): Restarting MDVOP - iteration: 1
Mon Apr 30 09:10:58.022 2018 MDT [1] INFO at addEntry(): launch: /home/xxx/.mdvop//tmp/run_mdvop
Mon Apr 30 09:10:58.025 2018 MDT [1] INFO at addEntry(): my Exec String = /home/xxx/.mdvop//tmp/run_mdvop
Mon Apr 30 09:10:58.513 2018 MDT [12] INFO at addEntry(): OUTPUT: ConfigurationClass.setConfiguration = /home/xxx/.mdvop/configurations/empty_configuration.xml
Mon Apr 30 09:10:59.530 2018 MDT [1] INFO at addEntry(): waitUntilDone(): Before wait()

 Below is what the command line interface (CLI) output should have looked like, after starting MDVOP 2.4 from the linux command line:

[xxx@xxxxxx mdvop]$ ./mdvop
Starting mdvop
[xxx@xxxxxx mdvop]$




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.