DAQ Trouble Shooting Guide: A list of solutions to problems you may see.


Question:I get an error that looks like this:

make -C ./caen/server -I ./caen/server
make[2]: Entering directory `/homes/joel/DAQPackage/src/csrc/org/cdms/caen/server'
source ../../../../../../configuration/users/makesource; \
c++ -O3 -fPIC -Wall -fpermissive -DNDEBUG -shared -I . -I ../idl \
        -I $local_include \
        -I $java_location/include -I $java_location/include/linux \
        -I ../../../../../../lib/jlib -I ../../../../../../lib/clib \
        -I ../../../../../../lib/clib/org/cdms/caen/idl \
        -o ../../../../../../lib/jlib/libCAENServer.so \
        ../../../../../../lib/clib/org/cdms/caen/idl/CDMS.o \
        ../../../../../../lib/clib/org/cdms/caen/idl/CDMS_skel.o \
        ../../../../../../lib/clib/org/cdms/caen/idl/ErrorInfo.o \
        ../../../../../../lib/clib/org/cdms/caen/idl/ErrorInfo_skel.o \
        ./libcaenhvwrap.so ./libsy1527.so -lOB -lJTC -lpthread -lCosNaming \
        -lCosEvent ./CAENServerImp.cpp
Missing name for redirect.
make[2]: *** [../../../../../../lib/jlib/libCAENServer.so] Error 1
make[2]: Leaving directory `/homes/joel/DAQPackage/src/csrc/org/cdms/caen/server'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/homes/joel/DAQPackage/src/csrc/org/cdms'
make: *** [all] Error 2
What is going on?

Answer:Check your DAQPackage/configuration/user/makesource file to make sure that you have set your daqpackage variable to point to the location of your software package. For example: setenv daqpackage /homes/joel/DAQPackage.


Question:I get an error that looks like this when I try to run a startup script:

[joel@baryon scripts]$ shutdown interlock
[1] 2579
[joel@baryon scripts]$ export: Command not found.
export: Command not found.
ORBacus_location: Undefined variable.
What is going on?

Answer:Check your DAQPackage/configuration/user/makesource file to make sure that you have set your daqpackage variable to point to the location of your software package. For example: setenv daqpackage /homes/joel/DAQPackage.


Question:I get an error that looks like this when I try to start the rmi registry mycomputer.mylocation.edu:

rmiservices.script
Initializing Naming Service: please wait..
Naming Service should run on: cdms.physics.ucsb.edu
You are trying to run on: baryon.physics.ucsb.edu
Please run it on: cdms.physics.ucsb.edu
This server will die immediately.
What is going on?

Answer:Make sure that runsource specifies the rmi_services_location to be mycomputer.mylocation.edu. If runsouce specifies a different rmi_services_location, the rmi naming service will recognize that you are attempting to start it in the wrong location and return the above error.


Question:I get an error that looks like this when I try to run a startup script:

java.rmi.server.ExportException: Port already in use: 1099; nested exception is: 
        java.net.BindException: Address already in use
        at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:243)
        at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:178)
        at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
        at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
        at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:145)
        at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
        at sun.rmi.registry.RegistryImpl.(RegistryImpl.java:78)
        at sun.rmi.registry.RegistryImpl.main(RegistryImpl.java:317)
Caused by: java.net.BindException: Address already in use
        at java.net.PlainSocketImpl.socketBind(Native Method)
        at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:321)
        at java.net.ServerSocket.bind(ServerSocket.java:308)
        at java.net.ServerSocket.bind(ServerSocket.java:266)
        at java.net.ServerSocket.(ServerSocket.java:182)
        at java.net.ServerSocket.(ServerSocket.java:94)
        at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:27)
        at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:306)
        at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:615)
        at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:231)
        ... 7 more
What is going on?

Answer:All that this warning message is saying is that an rmiregistry has already been started on this computer. For example, if you have already started the ConfigManger server and now try to start the RunControl server, you will get this warning, since both the ConfigManager and RunControl startup scripts currently attempt to start the rmiregistry before starting the respective servers. In this example, when the RunControl startup script attempts to create an rmiregistry it will not damage the rmiregistry that the ConfigManager startup script already created, however the RunControl startup script will fail to creat a new rmiregistry. This is NOT a problem IF you are running both servers from the SAME location as the rmiregistry, since they can both attach themselves to the SAME rmiregistry.









Last updated 7/19/02. Questions? Comments? Email: joel@hep.ucsb.edu.