- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- ASE: local Director Error: connect to Director on ...
Operating System - Tru64 Unix
1754282
Members
3176
Online
108813
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2009 07:09 PM
04-01-2009 07:09 PM
ASE: local Director Error: connect to Director on localhost failed
Cluster: 2 GS60E+RA800
OS: 4.0F
ASE: 1.6
ORACLE8i: OPS
When 1 system crash for hardware error. The other system can not be connected use oracle client program. Only restart oracle listener can fix this problem.
This problem will not occur when 1 system shutdown normally.
The following are daemon logs from the good system when the other machines crash.
Mar 28 21:50:36 gs60e01 ASE: mcgs60e01 Agent Notice: agent on mcgs60e02 should start director, but isn't in RUN state
Mar 28 21:50:36 gs60e01 ASE: mcgs60e01 Agent Notice: starting a new director
Mar 28 21:50:36 gs60e01 ASE: mcgs60e01 Agent Notice: client process hung up during connect phase
Mar 28 21:50:37 gs60e01 ASE: mcgs60e01 AseMgr Error: Director hasn't started up yet or local network is disconnected ...
Mar 28 21:50:52 gs60e01 last message repeated 3 times
Mar 28 21:50:57 gs60e01 ASE: local Director Error: timeout connecting to Director on localhost
Mar 28 21:50:57 gs60e01 ASE: local Director Error: connect to Director on localhost failed
Mar 28 21:50:57 gs60e01 ASE: local Director Notice: acceptConnect: not accepting connections!
Mar 28 21:50:58 gs60e01 last message repeated 9052 times
Mar 28 21:50:58 gs60e01 ASE: local Director ***ALERT: Member mcgs60e02 is not available
Mar 28 21:50:58 gs60e01 ASE: local Director Notice: acceptConnect: not accepting connections!
Mar 28 21:51:05 gs60e01 last message repeated 44957 times
Mar 28 21:51:05 gs60e01 ASE: mcgs60e01 AseMgr Notice: reconnected to director
Mar 28 21:51:05 gs60e01 ASE: mcgs60e01 Director Notice: client process hung up during connect phase
Seems asedirector can not be started when the other system crash.
Does anyone has solution for this situation?
Thanks!
Guo ShangZhong
OS: 4.0F
ASE: 1.6
ORACLE8i: OPS
When 1 system crash for hardware error. The other system can not be connected use oracle client program. Only restart oracle listener can fix this problem.
This problem will not occur when 1 system shutdown normally.
The following are daemon logs from the good system when the other machines crash.
Mar 28 21:50:36 gs60e01 ASE: mcgs60e01 Agent Notice: agent on mcgs60e02 should start director, but isn't in RUN state
Mar 28 21:50:36 gs60e01 ASE: mcgs60e01 Agent Notice: starting a new director
Mar 28 21:50:36 gs60e01 ASE: mcgs60e01 Agent Notice: client process hung up during connect phase
Mar 28 21:50:37 gs60e01 ASE: mcgs60e01 AseMgr Error: Director hasn't started up yet or local network is disconnected ...
Mar 28 21:50:52 gs60e01 last message repeated 3 times
Mar 28 21:50:57 gs60e01 ASE: local Director Error: timeout connecting to Director on localhost
Mar 28 21:50:57 gs60e01 ASE: local Director Error: connect to Director on localhost failed
Mar 28 21:50:57 gs60e01 ASE: local Director Notice: acceptConnect: not accepting connections!
Mar 28 21:50:58 gs60e01 last message repeated 9052 times
Mar 28 21:50:58 gs60e01 ASE: local Director ***ALERT: Member mcgs60e02 is not available
Mar 28 21:50:58 gs60e01 ASE: local Director Notice: acceptConnect: not accepting connections!
Mar 28 21:51:05 gs60e01 last message repeated 44957 times
Mar 28 21:51:05 gs60e01 ASE: mcgs60e01 AseMgr Notice: reconnected to director
Mar 28 21:51:05 gs60e01 ASE: mcgs60e01 Director Notice: client process hung up during connect phase
Seems asedirector can not be started when the other system crash.
Does anyone has solution for this situation?
Thanks!
Guo ShangZhong
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP