Hi,
this happens after we upgrading epo from 5.9 to 5.10 CU 10 and in cluster environment , from there every time we have situation that needs or happened restart the system the apache services won't start automatically like it used to be, it still automatically move/failover the application to the secondary node or vice versa but we have to start the apache services manually and then we too also have to manually "bring online" the services role in cluster manager,
is this on McAfee side or i have to check to the Microsoft team ?
NOTE: we already tried change apache services to start automatic (in services.msc) but still it will goes back to manually when failover occurs again,
Solved! Go to Solution.
after the support send this kb : docs.trellix.com/bundle/epolicy-orchestrator-5.10.0-installation-guide/page/GUID-D3B2313F-0DC9-4CC4-...
i tried to followed that kb and i think its fixed using this lines:
ill monitor until a few days and also tried to do some failover clustering /reset services etc, to test it,
Do event logs show it trying to start and can't? Do the cluster logs show any issues?
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
And is it specifically the epo server service or the application server service? How exactly did you run update 10 on the secondary node? See if this helps: https://kc.mcafee.com/corporate/index?page=content&id=KB94883
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
yes it's only specifically the epo server service,
well the one that helped me in the upgrade process was the support team, I remember that the two of them (the current one called help from more expert person in upgrading on cluster at that time) did some editing in the registry section (because the tomcat version on secondary node still error using version 7 than 9 so she edited the registry for that) and lastly reminded me that for this issue, try discussing it with the team servers or OS,
and after those upgrade stage now we have issue like this, and also the node doesn't have status "primary or secondary" on each nodes like before epo upgraded,
and also this is happened not only when failover to secondary node but vice versa too/to primary
You will probably need to get back with support, as without logs or seeing what is going on, it is difficult to guess at the problem.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
okay i'll tried rise a ticket support, but just want some confirmation, if my cluster epo runs failover process normal is it true that all application including the apache/server services will start running automatically and "online" it self ??
or maybe this is normal? (when failover i have to manually start the services and the cluster role)?
It should indeed as soon as the cluster is set correctly and all share drives are moved to the active node
after the support send this kb : docs.trellix.com/bundle/epolicy-orchestrator-5.10.0-installation-guide/page/GUID-D3B2313F-0DC9-4CC4-...
i tried to followed that kb and i think its fixed using this lines:
ill monitor until a few days and also tried to do some failover clustering /reset services etc, to test it,
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: