Unsolved
This post is more than 5 years old
1 Message
0
1241
AutoStart Agent Can't Start
Hi all!
I have met the problem "Agent service can't start ".and I have searched all the topics here ,there is no same situation .
It happens after the second node installed . When installation , it can get domain information from the first node .but after reboot ,the agent start then stop.
There is a message in log :FATAL: 0x1450e1c (01/28/13 16:18:57) ID00001495 Error getting license key: 10075 Please ensure that you are able to connect to any of the primary nodes, if so, restart all AutoStart Services.
I tried restart first node,reinstall the second node and no help , logs are below . thank you.
dbm_getProduct
INFO: 0x1484e7c (01/28/13 16:18:57) IN KEYFIND id 47000
INFO: 0x1484e7c (01/28/13 16:18:57) IN RECREAD_SQ id 47000
> 0x1484e7c Mon Jan 28 16:18:57 2013
dbm_ListLicenseKeysByProduct
> 0x1484e7c Mon Jan 28 16:18:57 2013
dbm_checkFolder
> 0x1484e7c Mon Jan 28 16:18:57 2013
dbm_ApplFolderExists
INFO: 0x1484e7c (01/28/13 16:18:57) IN KEYFIND id 9000
< 0x1484e7c Mon Jan 28 16:18:57 2013
dbm_ApplFolderExists ret: 0
< 0x1484e7c Mon Jan 28 16:18:57 2013
dbm_checkFolder ret: 0
INFO: 0x1484e7c (01/28/13 16:18:57) IN KEYFIND id 46001
< 0x1484e7c Mon Jan 28 16:18:57 2013
dbm_ListLicenseKeysByProduct ret: 1
< 0x1484e7c Mon Jan 28 16:18:57 2013
dbm_getProduct ret: 0
< 0x1484e7c Mon Jan 28 16:18:57 2013
svr_sec_GetProductDef ret: 0
< 0x1484e7c Mon Jan 28 16:18:57 2013
sec_dispatchMessage
> 0x1484e7c Mon Jan 28 16:18:57 2013
sec_dispatchMessage
> 0x1484e7c Mon Jan 28 16:18:57 2013
sec_CheckMsg
> 0x1484e7c Mon Jan 28 16:18:57 2013
sec_getAddrEntry
< 0x1484e7c Mon Jan 28 16:18:57 2013
sec_getAddrEntry ret: 21219856
< 0x1484e7c Mon Jan 28 16:18:57 2013
sec_CheckMsg ret: 0
EVENT: 0x1484e7c (01/28/13 16:18:57) Calling svr_sec_listLicenses for msgid: 61 from: (2/1:1804.0)
> 0x1484e7c Mon Jan 28 16:18:57 2013
svr_sec_listLicenses
> 0x1484e7c Mon Jan 28 16:18:57 2013
dbm_ListLicenses
> 0x1484e7c Mon Jan 28 16:18:57 2013
dbm_checkFolder
> 0x1484e7c Mon Jan 28 16:18:57 2013
dbm_ApplFolderExists
INFO: 0x1484e7c (01/28/13 16:18:57) IN KEYFIND id 9000
< 0x1484e7c Mon Jan 28 16:18:57 2013
dbm_ApplFolderExists ret: 0
< 0x1484e7c Mon Jan 28 16:18:57 2013
dbm_checkFolder ret: 0
INFO: 0x1484e7c (01/28/13 16:18:57) IN KEYFIND id 46001
< 0x1484e7c Mon Jan 28 16:18:57 2013
dbm_ListLicenses ret: 1
< 0x1484e7c Mon Jan 28 16:18:57 2013
svr_sec_listLicenses ret: 1
< 0x1484e7c Mon Jan 28 16:18:57 2013
sec_dispatchMessage
< 0x1450e1c Mon Jan 28 16:18:57 2013
sec_GetFeatures ret: 1
> 0x1450e1c Mon Jan 28 16:18:57 2013
sec_CheckLicense
> 0x1484e7c Mon Jan 28 16:18:57 2013
sec_dispatchMessage
> 0x1484e7c Mon Jan 28 16:18:57 2013
sec_CheckMsg
> 0x1484e7c Mon Jan 28 16:18:57 2013
sec_getAddrEntry
< 0x1484e7c Mon Jan 28 16:18:57 2013
sec_getAddrEntry ret: 21219856
< 0x1484e7c Mon Jan 28 16:18:57 2013
sec_CheckMsg ret: 0
EVENT: 0x1484e7c (01/28/13 16:18:57) Calling svr_sec_listLicenses for msgid: 63 from: (2/1:1804.0)
> 0x1484e7c Mon Jan 28 16:18:57 2013
svr_sec_listLicenses
> 0x1484e7c Mon Jan 28 16:18:57 2013
dbm_ListLicenses
> 0x1484e7c Mon Jan 28 16:18:57 2013
dbm_checkFolder
< 0x1484e7c Mon Jan 28 16:18:57 2013
dbm_checkFolder ret: 0
INFO: 0x1484e7c (01/28/13 16:18:57) IN KEYFIND id 10046
< 0x1484e7c Mon Jan 28 16:18:57 2013
dbm_ListLicenses ret: 1
< 0x1484e7c Mon Jan 28 16:18:57 2013
svr_sec_listLicenses ret: 1
< 0x1484e7c Mon Jan 28 16:18:57 2013
sec_dispatchMessage
FATAL: 0x1450e1c (01/28/13 16:18:57) ID00001495 Error getting license key: 10075 Please ensure that you are able to connect to any of the primary nodes, if so, restart all AutoStart Services.
yito1
262 Posts
0
January 28th, 2013 01:00
Hi,
Quote of the knowledge base
------------------------------------------------------
Cause
The AutoStart Agent on the secondary node is communicating over the verification Network, which causes latency with the FTCLI command to retrieve the licensing information.
Resolution
There is no resolution at this time.
------------------------------------------------------
My Workaround
My customer fell into the same symptom in the past.
I tried this method.
Change the Point to point from Multicast.
Pull out the cable of Verification Line.
Installation on the secondary host.