Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Openscape 4000 Assistance V7 - RDS Session Management login issue
- Thread starter Rsanga
- Start date
Three things to try
I'm going to edit my first comment here. I said make a "procadmin -l" to list the processes and then a "procadmin -t" and a "procadmin -s" to terminate and start the RDS process(es) once you'd identified it/them.
But I just checked and it seems RDS isn't listed in procadmin -l. If you make a "procadmin -l" on an Assistant that is not running RDS, then add it via Base Admin/Application Control, and make another procadmin -l - the output is exactly the same.
With RDS installed but not running, grepping for rds in "ps" (not "procadmin") shows this
Assistant-linux:/home/engr # ps -ef | grep rds
root 12251 28764 0 23:20 pts/4 00:00:00 grep rds
Then with RDS running, you get this
Assistant-linux:/home/engr # ps -ef | grep rds
rds 15499 1 0 23:29 ? 00:00:00 ctrlmain
rds 15531 1 0 23:29 ? 00:00:00 TdsServer
rds 15563 1 0 23:29 ? 00:00:00 rds-ui
rds 15606 1 0 23:29 ? 00:00:00 Trc_Control Trc_Control.cfg
root 15778 28764 0 23:29 pts/4 00:00:00 grep rds
If you make a kill -9 on those RDS processes, they are restarted the next time you open RDS. So you could try that (kill -9 15499 etc). But there might not be any RDS processes running, you need to check.
Or, you could go to Base Admin/Application Control, and untick, submit, then tick, submit, on RDS, and see if that helps.
Or, just try rebooting the Assistant from Assistant GUI, or from ssh to Assistant, give it an init 6. This will not affect call processing.
I'm going to edit my first comment here. I said make a "procadmin -l" to list the processes and then a "procadmin -t" and a "procadmin -s" to terminate and start the RDS process(es) once you'd identified it/them.
But I just checked and it seems RDS isn't listed in procadmin -l. If you make a "procadmin -l" on an Assistant that is not running RDS, then add it via Base Admin/Application Control, and make another procadmin -l - the output is exactly the same.
With RDS installed but not running, grepping for rds in "ps" (not "procadmin") shows this
Assistant-linux:/home/engr # ps -ef | grep rds
root 12251 28764 0 23:20 pts/4 00:00:00 grep rds
Then with RDS running, you get this
Assistant-linux:/home/engr # ps -ef | grep rds
rds 15499 1 0 23:29 ? 00:00:00 ctrlmain
rds 15531 1 0 23:29 ? 00:00:00 TdsServer
rds 15563 1 0 23:29 ? 00:00:00 rds-ui
rds 15606 1 0 23:29 ? 00:00:00 Trc_Control Trc_Control.cfg
root 15778 28764 0 23:29 pts/4 00:00:00 grep rds
If you make a kill -9 on those RDS processes, they are restarted the next time you open RDS. So you could try that (kill -9 15499 etc). But there might not be any RDS processes running, you need to check.
Or, you could go to Base Admin/Application Control, and untick, submit, then tick, submit, on RDS, and see if that helps.
Or, just try rebooting the Assistant from Assistant GUI, or from ssh to Assistant, give it an init 6. This will not affect call processing.
- Status
Similar threads
- Locked
- Question