Displays Ubik status information relevant to the specified DFS database server
Synopsis
udebug -rpcgroup RPC_server_group [-server machine] [-long] [-help]
Options
-rpcgroup RPC_server_group
Specifies the RPC server group of the Ubik database servers whose status information you want to display. By convention, this is
/.:/fs for the flserver processes and /.:/subsys/dce/dfs/bak for the bakserver processes.
-server machine
Names the machine containing the database server whose Ubik status information is to be displayed; if a machine name is omitted, the command uses the
name of the local machine. Specify the server machine using the full DCE pathname, abbreviated host name, or IP address.
-long
Directs the command to provide additional information about the other database servers in the specified RPC server group. This flag is not necessary if the
server specified with the -server option is the Ubik synchronization site because the information about the other database servers is provided automatically.
-help
Prints the online help for this command. All other valid options specified with this option are ignored.
Description
The udebug command displays Ubik status information on the specified server in the specified RPC server group. If the specified server is the
synchronization site or the -long flag is used with the command, the command displays information on all of the servers in the RPC server group.
Privilege Required
No privileges are required.
Output
The output for the udebug command always provides the following information for the specified database server:
· The IP address of the specified server machine. In the first example, this is 192.56.207.146.
· The difference in seconds between the clock on the specified server machine and the machine on which the udebug command was run. In the first example, this is 0.
Note: If the message ****clock may be bad appears, the difference between the two clocks is greater than 40 seconds, and you must synchronize the clocks on all of the server machines in the RPC server group.
· The IP address of the server machine that this server voted for to be the synchronization site and the time that the vote was cast. In the first example, this is 192.56.207.26 at -10.
Note: Unless noted otherwise, all time is calculated and displayed as the number of seconds before (negative) or after (positive) the current time according to the clock on the local machine on which the udebug command is run.
· The time at which the last round of sync-site voting began. In the first example, this is -11.
· The version of the database in use on this server machine. In the first example, this is 750478963.1.
· Whether the server is the synchronization site; if it is, the duration of the synchronization site status and the number of servers in the RPC server group are also provided. In the first example, the message I am not sync site indicates that the server is not the sync site.
· If the server is not the synchronization site, the following information is displayed:
- The IP address of the lowest server in the RPC server group and the time that a beacon was last sent from that server to the specified server. In the first example, this is 192.56.207.26 at -10.
- The IP address of the synchronization site and the time that a beacon was last sent from that server. In the first example, this is 192.56.207.26 at -10.
If the server is the synchronization site, the current state of the server is displayed, using one of the following flags. In the second example, this is 1f.
- 1 Indicates that the server is the synchronization site.
- 3 Indicates that the server is the synchronization site and that it has found the latest version of the database.
- 7 Indicates that the server is the synchronization site and that it has fetched the latest version of the database.
- f Indicates that the server is the synchronization site and a quorum has been reached in the RPC server group, but the synchronization site has not distributed the latest version of the database to all servers in the RPC server group.
- 1f Indicates that server is the synchronization site, a quorum has been reached in the RPC server group, and the synchronization site has distributed the latest version of the database to all servers in the RPC server group.
· The version of the database in use at the synchronization site. In the first example, this is 750478963.1.
· The total number of database pages locked and the number of database pages locked for write purposes on the server. (Anything other than a 0 indicates database activity.) In the first example, this is 0 and 0.
· The time that the server was the synchronization site, if it ever has been, or a message indicating that the server has never been the synchronization site. In the first example, the message This server has never been sync site indicates that the server has never been the synchronization site.
If the udebug command specifies the synchronization site of the RPC server group or if the -long option is used with the command, the following additional information is displayed for each of the other database servers in the RPC server group:
· The IP address of each server machine. In the second example, the first server machine listed has the IP address 192.56.207.36.
· The version of the database in use on each server machine. (A 0.0 indicates that the server does not have a version of the database.) In the second example, the first server listed uses the database version 750478963.1.
· The last time a vote was received from this server by the server specified with the -server option. In the second example, the server with IP address 192.56.207.26 received a vote from the first server with IP address 192.56.207.36 at -8.
· The last time a beacon requesting a vote was sent to each server. In the second example, the first server received a beacon at -9.
· The last vote, yes or no, cast by each server. In the second example, the first server cast a yes vote.
· A flag (dbcurrent) indicating whether the version of the database in use on each server machine is current with the synchronization site; 0 indicates no, 1 indicates yes. In the second example, the first server has a current version of the database.
· A flag (up) indicating whether the corresponding server process on each server machine is up; 0 indicates no, 1 indicates yes. In the second example, the first server is up.
· A flag (beaconSince) indicating whether a response (vote) to the latest beacon was sent by each server to the synchronization site. In the second example, the first server sent a response to the latest beacon.
Examples
The following command displays information on a specified database server that is not a synchronization site:
$ udebug /.:/fs fs2
Host 192.56.207.146, his time is 0
Vote: Last yes vote for 192.56.207.26 at -10 (sync site); Last vote started
at -11
Local db version is 750478963.1
I am not sync site
Lowest host 192.56.207.26 at -10
Sync host 192.56.207.26 at -10
Sync site's db version is 750478963.1
0 locked pages, 0 of them for write
This server has never been sync site
The following command displays information on a specified database server that is a synchronization site; the output also provides information on the other database servers in the RPC server group:
$ udebug /.:/fs fs4
Host 192.56.207.26, his time is 0
Vote: Last yes vote for 192.56.207.26 at -9 (sync site); Last vote started
at -9
Local db version is 750478963.1
I am sync site until 81 (4 servers)
Recovery state 1f
Sync site's db version is 750478963.1
0 locked pages, 0 of them for write
This server last became sync site at -38195
Server 192.56.207.36: (db 750478963.1)
last vote rcvd at -8, last beacon sent at -9, last vote was yes
dbcurrent=1, up=1 beaconSince=1
Server 192.56.207.146: (db 750478963.1)
last vote rcvd at -8, last beacon sent at -9, last vote was yes
dbcurrent=1, up=1 beaconSince=1
Server 192.56.207.94: (db 750478963.1)
last vote rcvd at -8, last beacon sent at -9, last vote was yes
dbcurrent=1, up=1 beaconSince=1
Related Information
Commands: bakserver(8dfs)