| Summary | Trying to stop Orbix 6.3 Notification Service gives error. Running the "itadmin process stop" command gives error. |
|---|---|
| Article Number | 27077 |
| Environment | Orbix 6.3 |
| Question/Problem Description | Trying to stop Orbix 6.3 Notification Service gives error. Orbix node daemon, locator daemon, naming server daemon and notification server gets automatically rebooted. Running the "itadmin process stop" and Kill command also gives error. |
| Clarifying Information | Running the Notify command gives error: > itadmin process stop iona_services.notify.hostname (ERROR: Target process NOT stopped: NotConnected (IDL:iona.com/IT_LocatorAdmin/ActiveProcess/NotConnected:1.0)) Command to see if notification process is active: > hostname:/system_x/startorbix/var/">aldc.att.com/dbs/notify>; > itadmin process list -active > iona_services.naming.hostname > iona_services.notify.hostname (Orbix thinks process is active)
Command to see if process is active.
> ps -eaf | grep iona Kill command generated errors. > itadmin process kill -signal 15 iona_services.notify.hostname
ERROR: Target process NOT killed: IDL:omg.org/CORBA/TRANSIENT:1.0: minor = 0x495403D8 (IT_ATLI2_IP:CONNECTION_REFUSED), completion E
Removing the lock file in /system_x/startorbix/var/xxx.xxx.xxx/dbs/notify and trying to start did not help. |
| Error Message | ERROR: Target process NOT killed: IDL:omg.org/CORBA/TRANSIENT:1.0: minor = 0x495403D8 (IT_ATLI2_IP:CONNECTION_REFUSED), completion E |
| Defect/Enhancement Number | |
| Cause | Error in the script is causing Orbix node daemon, locator daemon, naming server daemon and notification server to be automatically rebooted. |
| Resolution | Check whether there is a script that is starting the services automatically. |
| Workaround | |
| Notes | |
| Attachment |
| Created date: | 07 December 2011 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 12 May 2012 |
| First Published date: | 07 December 2011 |
#KnowledgeDocs
#Orbix
