000011663 - How to verify who is connected to RSA Database using progress utils

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000011663
Applies ToAuthentication Manager 6.1.2
Solaris 10
sdadmin
processes still connected. (2262)
IssueHow to verify who is connected to RSA Database using progress utils
Customer runs sdconnect shutdown and if user is logged onto sdadmin they will see error. "

Message: Stopping RSA Authentication Manager.

Message: RSA Authentication Manager stop operation completed

               Copyright 1994 - 2007 by RSA Security Inc.

                     RSA Authentication Manager 6.1.2

 

                       ---ALL RIGHTS RESERVED---

Message: Stopping Automated Audit Log Maintenance.

Message: Stopping Administration Daemon.

Message: Stopping Offline Auth Data Daemon. Please wait.

Message: Stopping Job Executor Daemon.

Message: Stopping Quick Admin Daemon.

Message: Stopping all replication processes. Please wait.

Message: Stopping server database broker.

Please, be patient, it can take a few minutes.

Shutdown is executing. (1613)

00:03:29 1 processes still connected. (2262)

00:03:59 1 processes still connected. (2262)

00:07:59 1 processes still connected. (2262)

00:12:59 1 processes still connected. (2262)

00:17:59 1 processes still connected. (2262)

00:32:59 1 processes still connected. (2262)

00:47:59 1 processes still connected. (2262)

01:02:58 1 processes still connected. (2262)

01:17:58 1 processes still connected. (2262)

01:32:58 1 processes still connected. (2262)

CauseThis is caused by the sdadmin being logged onto the console, they will see a response box that they need to ackknolegs
Resolution

The output is from running proshut as shown below.

If there are connections, the exit status is 2.

If there are no connections the exit status is 0.

 

[root@tux bin]# /opt/ace/rdbms/bin/proshut /opt/ace/data/sdserv -bn

usr    pid    time of login           user id     tty                  Limbo?

  7  14138 Mon Jun 21 13:44:42 2010   apw                              no

  8  14141 Mon Jun 21 13:44:42 2010   biw                              no

106   1356 Mon Jun 21 14:10:18 2010   Administrator                      no

 

[root@tux bin]# echo $?

2

 

What you probably want, though, is the following command.

 

[root@tux bin]# /opt/ace/rdbms/bin/proshut /opt/ace/data/sdserv -C list

usr    pid    time of login           user id     tty                  Limbo?

  7  17276 Mon Jun 21 14:29:24 2010   apw                              no

  8  17279 Mon Jun 21 14:29:25 2010   biw                              no

  9  17298 Mon Jun 21 14:29:28 2010   root        batch                no

 10  17303 Mon Jun 21 14:29:30 2010   root        batch                no

 11  17308 Mon Jun 21 14:29:32 2010   root        batch                no

 12  17531 Mon Jun 21 14:29:37 2010   root        batch                no

 

[root@tux bin]# echo $?

0

 

[root@tux bin]# /opt/ace/rdbms/bin/proshut /opt/ace/data/sdserv -C list

usr    pid    time of login           user id     tty                  Limbo?

  7  17276 Mon Jun 21 14:29:24 2010   apw                              no

  8  17279 Mon Jun 21 14:29:25 2010   biw                              no

  9  17298 Mon Jun 21 14:29:28 2010   root        batch                no

 10  17303 Mon Jun 21 14:29:30 2010   root        batch                no

 11  17308 Mon Jun 21 14:29:32 2010   root        batch                no

 12  17531 Mon Jun 21 14:29:37 2010   root        batch                no

106   1572 Mon Jun 21 14:35:30 2010   Administrator                      no

 

[root@tux bin]# echo $?

0

 

In the first case,  there are no users connected.

In the second case, there is one user connected.

 

Legacy Article IDa54252

Attachments

    Outcomes