Not logged in : Login

About: How Do I Interpret Request Broker Logs? -- Answer     Goto   Sponge   NotDistinct   Permalink

An Entity of Type : schema:Answer, within Data Space : www.openlinksw.com associated with source document(s)
QRcode icon
http://www.openlinksw.com/describe/?url=https%3A%2F%2Fdata.openlinksw.com%2Foplweb%2Ffaq%2Fuda%2F9aebf97b7a684d0d49dde800bedc9c4f%23this

AttributesValues
name
  • How Do I Interpret Request Broker Logs? -- Answer
category
  • ODBC
  • JDBC
  • UDA
text
  • Use the following guidelines to interpret Request Broker Log files. Tue Oct 15 2002 Make sure the log date corresponds to the occurrence of the problem. 12:25:46 using rule-book /home/openlink/32bit/v42/bin/oplrqb.ini Check the path to oplrqb.ini. Insure that the correct file is referenced. Users can encounter problems, when they have multiple, Multi-Tier installations. Specifically, users will notice that the wrong agents are spawned and the wrong environment variables may be employed. 12:25:46 bound UDP protocol to 0.0.0.0.60001 Check for UDP and "address in use" errors. Use netstat -a & the services file to debug any problems that occur with the UDP port. Likewise, insure that UDP is enabled on the client and server machines that produce UDP broadcast errors. 12:25:46 bound TCP protocol to 0.0.0.0.5000 Check for "address already in use" and other TCP port problems. Use netstat -a & the services file to debug any problems that may occur. In the event of a port conflict, users may change the Broker's Listen port. Users will find the Listen parameter in the [Protocol TCP] section of oplrqb.ini. 12:25:46 using UDP address 192.168.11.116.0 for IPC Check for UDP and "address in use" errors. Use netstat -a & the services file to debug any problems that occur with the UDP port. Likewise, insure that UDP is enabled on the client and server machines that produce UDP broadcast errors. 12:25:46 request broker started by openlink Brokers started by root may cause resource problems or Progress "login by batch" errors. Search for "batch" and resource related problems later in the file. 12:25:46 spawning /home/openlink/32bit/v42/bin/w3config/www_sv www_sv www_sv powers the Admin Assistant. Moreover, it uses the HttpPort passed in the www_sv.ini file. If "address" or other TCP port usage problems occur, run netstat -a and services to debug port conflicts. If necessary, have the user change the HttpPort in ~/openlink/bin/w3config/www_sv.ini file. 12:25:46 started persistent www_sv (pid=12219) 12:25:53 example.com called (*******) 12:25:53 request: domain=Progress 91C database=demo.db serveropts= 12:25:53 connectopts=-S pro91c -N tcp -H **** user= demo_user=unix readonly=0 These parameters are read from the Data Source Name. Check for inappropriate values. Additionally, watch for "Broker cannot resolve your request" errors. "Request" errors occur when the Domain name passed in this parameter list does not appear in the [Domain Aliases] section of oplrqb.ini. Users must create the appropriate in oplrqb.ini or choose an existing alias. 12:25:53 application=odbctest processid=12220 12:25:53 solve mapping: pro91c:demo:blank:other:example.com:odbctest:rw 12:25:53 using mapping: pro91c:*:*:*:*:*:* The Broker takes the abbreviated form of the domain alias and searches for matches in the [Mapping Rules] section of oplrqb.ini. The Broker will use the appropriate rule to prohibit or permit access to the database. Users may encounter "Mapping not found" errors, if their alias does not have an associated rule. Additionally, users may inadvertently create complex rules, which restrict their ability to connect. 12:25:53 using [generic_pro91c] ServerProgram=pro91c_sv Most mapping rules will point the Broker to a [generic] agent configuration section. This section passes the name of the database agent that is written in the database's CLI. It passes the location of database-specific environment variables, and it passes hard-coded connection parameters. Problems will occur on this line, if the agent configuration section does not exist in oplrqb.ini. 12:25:53 connect params: domain=Progress 91C db=demo.db serveropts=-T /tmp -d mdy -TB 31 -TM 31 -q -NL readonly=0 12:25:53 connectopts=-S pro91c -N tcp -H oplushp2 user= demo_user=unix machine=example.com application=odbctest This line shows the final list of parameters that will be used to establish the connection. In essence, the Broker tosses out specific Data Source Name parameters if corresponding parameters are hard-coded in oplrqb.ini. These hard-coded parameters can result in problems, if the user forgets they exist. Typically, users will discover that they are connected to the wrong database, they are authenticated as the wrong user, or they are restricted to read-only access. They may also experience authentication problems, which arise when OPSYSLOGIN is enabled. OPSYSLOGIN uses operating system parameters to authenticate. It does not recognize the typical database username and password. 12:25:53 spawning /home/openlink/32bit/v42/bin/pro91c_sv generic_pro91c This line shows the agent that is spawned for the connection. Problems occur if permissions prohibit spawning. Problems also occur when the agent is not compatible with the operating system or the agent cannot be found. 12:25:53 setting Environment PROGRESS91C 12:25:53 change environment 'CURSOR_SENSITIVITY' -> 'LOW' 12:25:53 change environment 'DLC' -> '/dbs2/progress/v91c' 12:25:53 change environment 'PROCFG' -> '/dbs2/progress/v91c/progress.cfg' The [generic] agent configuration section contains an Environment parameter. This parameter passes the location of an [Environment] section. This [Environment] section passes database-specific environment variables that are needed to establish the connection. Problems arise when the [Environment] section does not exist in oplrqb.ini. 12:25:53 asking agent for server handle "Server handle" errors occur when the preceding environment variables are incorrect. If environment variables are correct, consult the OPIE knowledge-base for additional information. 12:25:53 got it! 12:25:53 asking agent for connection handle "Connection handle" errors occur when connection parameters are incorrect. If the parameters are correct, consult OPIE for additional information. 12:25:53 got it! 12:25:53 accepted blank@example.com.odbctest At this point, your user is connected to the database. However, a wide array of produce and database errors may occur at this point. Consult OPIE for the nature and description of these errors.
type
is acceptedAnswer of
Faceted Search & Find service v1.17_git110 as of Apr 06 2022


Alternative Linked Data Documents: iSPARQL | ODE     Content Formats:   [cxml] [csv]     RDF   [text] [turtle] [ld+json] [rdf+json] [rdf+xml]     ODATA   [atom+xml] [odata+json]     Microdata   [microdata+json] [html]    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 08.03.3322 as of Apr 19 2022, on Linux (x86_64-generic-linux-glibc25), Single-Server Edition (30 GB total memory, 20 GB memory in use)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2022 OpenLink Software