AnsweredAssumed Answered

Why the agent is getting disconnected automatically when it goes into idle state

Question asked by Srujan_Pathuri_9871 on Feb 21, 2018
Latest reply on Feb 22, 2018 by MatthiasSchelp

Like • Show 0 Likes0
Comment • 9

Hi All,

Could anyone please tell me why the agents are automatically getting disconnected when it goes into idle state. I have gone through the agent logs and understand that it's because of "License Class=1" that is defined in Agent's INI file. However, I set it to License Class 2 and restarted the agent. Now I don't see any connectivity issues on that particular node after tweaking this value.But some nodes are expecting License Class value must be set to 5. I am getting confused regarding this and please tell me on what basis this License Class value should be set.

Many Regards,
Srujan.

Michael_Pirson Feb 21, 2018 7:11 PM

Correct Answer

What type of agents are these? Generally speaking OS agents use class V these days with a possible legacy class 9.

From what I've noticed the ones that use 1 and 5 are java agents and those INI's do not have a place to define the license class.

Last exception is if the OS agent runs on the same server as the AE. In this case a class S can be used.

I would look in the License tab of the System Overview in the UI and look to see what is available for the type of agent you are starting.

See the reply in context

No one else had this question

Outcomes

Michael_Pirson Feb 21, 2018 7:11 PM

Actions

Hoai_Truong-Thi-Thu_5649 Feb 22, 2018 7:37 AM

Srujan_Pathuri_9871

Just FYI, there is a Known issue related to this U00034018 message:
Unix agent crashes during shutdown

Problems have been fixed where
- error message 34018 is corrupted
- agent crashes during shutdown when some backend variables are still active
- agent ignores the license_class parameter in the ini file

Fixed versions:
Agent Unix, Automation Engine
Automation Engine 12.2.0 – Planned release date: 2018-06-19
Automation Engine 12.1.1 - available

Detail:
https://automic.force.com/support/apex/CommunityArticleDetail?id=ka30N000000H4GE

Best,
Hoai

Actions

Srujan_Pathuri_9871 Feb 22, 2018 9:53 AM

Michael_Pirson

Thanks for the information. I have looked into License tab and it did help me to understand that. But I see there are two rows related to OS.UNX and the license class is different for both of them. So can we assign either 9 or V to License class or is there any specific reason b/w them?

Regards,
Srujan.

Actions

Srujan_Pathuri_9871 Feb 22, 2018 9:57 AM

Hoai_Truong-Thi-Thu_5649

Thanks but we are on V12.1.1, seems like the issue is still persists.

Regards,
Srujan.

Actions

Antoine_Sauteron_1266 Feb 22, 2018 10:36 AM

Hi Srujan_Pathuri_9871

Maybe this post will help you understand how licenses work:
https://community.automic.com/discussion/comment/30905#Comment_30905

Best regards,
Antoine

1 person found this helpful

Actions

Carsten_Schmitz Feb 22, 2018 10:37 AM

Srujan Pathuri said:
Hoai_Truong-Thi-Thu_5649

Thanks but we are on V12.1.1, seems like the issue is still persists.

Regards,
Srujan.

If you can be reasonably sure that issues persist or that there is a regression, and have possibly exhausted other ressources, please don't hesitate to open an incident at support.automic.com.

It is important that potential issues be identified and subsequently be fixed.

Thanks!
Carsten

Actions

Carsten_Schmitz Feb 22, 2018 10:47 AM

Btw, here's one more hunch:

There was an issue with the spelling of the ini parameter "license_class". They spelled it "licence_class" at some point (letter "c" in place of the letter "s"), and then changed how UC4 behaves. This is what Hoai_Truong-Thi-Thu_5649 hinted at.

I can not find the details on the fly (or which one is "correct" and which one is "wrong"), but you might want to change the spelling from the one variant to the other for a test and see if that helps. Especially if you are using an old .ini file that you took over from an older version of the agent.

Edit: of course please ensure to restart the agent after each .ini change.

Hth,
Carsten

Actions

Hoai_Truong-Thi-Thu_5649 Feb 22, 2018 10:45 AM

Yes Srujan_Pathuri_9871 , I strongly agree with Mr.Carsten_Schmitz_7883 , if you can be sure the same issue persist on v12.1.1,
please open a ticket with Support at support.automic.com.

Thanks!
Hoai

Actions

MatthiasSchelp Feb 22, 2018 10:53 AM

Hi Srujan_Pathuri_9871 ,

The bug Hoai_Truong-Thi-Thu_5649 describes is most likely not related to the error message you receive. Just change the license class to V and you should be fine.

Pay attention to the spelling like Carsten_Schmitz_7883 described and check out Antoine_Sauteron post for further information.

Regards, Matthias

Actions

9 Replies

Michael_Pirson Feb 21, 2018 7:11 PM
Unmark Correct
Correct Answer
What type of agents are these? Generally speaking OS agents use class V these days with a possible legacy class 9.

From what I've noticed the ones that use 1 and 5 are java agents and those INI's do not have a place to define the license class.

Last exception is if the OS agent runs on the same server as the AE. In this case a class S can be used.

I would look in the License tab of the System Overview in the UI and look to see what is available for the type of agent you are starting.
Like • Show 0 Likes0
Actions
Hoai_Truong-Thi-Thu_5649 Feb 22, 2018 7:37 AM
Mark Correct
Correct Answer
Srujan_Pathuri_9871

Just FYI, there is a Known issue related to this U00034018 message:
Unix agent crashes during shutdown

Problems have been fixed where
- error message 34018 is corrupted
- agent crashes during shutdown when some backend variables are still active
- agent ignores the license_class parameter in the ini file

Fixed versions:
Agent Unix, Automation Engine
Automation Engine 12.2.0 – Planned release date: 2018-06-19
Automation Engine 12.1.1 - available

Detail:
https://automic.force.com/support/apex/CommunityArticleDetail?id=ka30N000000H4GE

Best,
Hoai
Like • Show 1 Like1
Actions
Srujan_Pathuri_9871 Feb 22, 2018 9:53 AM
Mark Correct
Correct Answer
Michael_Pirson

Thanks for the information. I have looked into License tab and it did help me to understand that. But I see there are two rows related to OS.UNX and the license class is different for both of them. So can we assign either 9 or V to License class or is there any specific reason b/w them?

Regards,
Srujan.
Like • Show 0 Likes0
Actions
Srujan_Pathuri_9871 Feb 22, 2018 9:57 AM
Mark Correct
Correct Answer
Hoai_Truong-Thi-Thu_5649

Thanks but we are on V12.1.1, seems like the issue is still persists.

Regards,
Srujan.
Like • Show 0 Likes0
Actions
Antoine_Sauteron_1266 Feb 22, 2018 10:36 AM
Mark Correct
Correct Answer
Hi Srujan_Pathuri_9871

Maybe this post will help you understand how licenses work:
https://community.automic.com/discussion/comment/30905#Comment_30905

Best regards,
Antoine

1 person found this helpful
Like • Show 0 Likes0
Actions
Carsten_Schmitz Feb 22, 2018 10:37 AM
Mark Correct
Correct Answer
Srujan Pathuri said:
Hoai_Truong-Thi-Thu_5649

Thanks but we are on V12.1.1, seems like the issue is still persists.

Regards,
Srujan.

If you can be reasonably sure that issues persist or that there is a regression, and have possibly exhausted other ressources, please don't hesitate to open an incident at support.automic.com.

It is important that potential issues be identified and subsequently be fixed.

Thanks!
Carsten
Like • Show 1 Like1
Actions
Carsten_Schmitz Feb 22, 2018 10:47 AM
Mark Correct
Correct Answer
Btw, here's one more hunch:

There was an issue with the spelling of the ini parameter "license_class". They spelled it "licence_class" at some point (letter "c" in place of the letter "s"), and then changed how UC4 behaves. This is what Hoai_Truong-Thi-Thu_5649 hinted at.

I can not find the details on the fly (or which one is "correct" and which one is "wrong"), but you might want to change the spelling from the one variant to the other for a test and see if that helps. Especially if you are using an old .ini file that you took over from an older version of the agent.

Edit: of course please ensure to restart the agent after each .ini change.

Hth,
Carsten
Like • Show 1 Like1
Actions
Hoai_Truong-Thi-Thu_5649 Feb 22, 2018 10:45 AM
Mark Correct
Correct Answer
Yes Srujan_Pathuri_9871 , I strongly agree with Mr.Carsten_Schmitz_7883 , if you can be sure the same issue persist on v12.1.1,
please open a ticket with Support at support.automic.com.

Thanks!
Hoai
Like • Show 1 Like1
Actions
MatthiasSchelp Feb 22, 2018 10:53 AM
Mark Correct
Correct Answer
Hi Srujan_Pathuri_9871 ,

The bug Hoai_Truong-Thi-Thu_5649 describes is most likely not related to the error message you receive. Just change the license class to V and you should be fine.

Pay attention to the spelling like Carsten_Schmitz_7883 described and check out Antoine_Sauteron post for further information.

Regards, Matthias
Like • Show 1 Like1
Actions

Why the agent is getting disconnected automatically when it goes into idle state

Outcomes

Related Content

Recommended Content