• Replies 6 replies
  • Subscribers 585 subscribers
  • Views 339 views
  • Users 0 members are here
Options
Related

Citect Running as Service - Number of sessions limit

Mike

All,

I have a client who has a (CitectSCADA 2016 with the latest update) Citect Standby server for a number of clusters (6 of).  The machine has really be spec'ed up and can handle the workload.

It runs well with Citect in runtime in User Session, but we want to secure it by running it as a service so that it can be logged out.  All the primary server cluster machines are running separately as services with no problems.

The standby server is trying to run 37 services to support the standby servers for the 6 clusters. 

When running the runtime manager as a service will only run up 31 sessions and the rest won't start (they are listed).  It is actually possible to stop one and start another one, but only a total 31 can run at one time when citect runtime manager is running as a service.

When runtime manager is running in a user session and then this limit doesn't apply and all 37 sessions run fine.

Is there anyway to increase this limit with Citect Runtime Manager as a service?  Yes it seems like a lot but its not a problem to with the power of this machine.  

Yes Citect2016 needs attention too, but that's for another day, let's get this system performing as well as it can first.

Cheers,

Mike

Parents

  • Hi  ,

    Just confirming the customer is running March 2020 Update?

    Is it random which process doesn't startup or is it always the same ones? E.g. does it only impact IO Servers or other types?

    There was a fix in a patch which related to number of CPUs on the host. Which was ringing a bell when you mention the machine resources are spec'd up.

    This was the bug:

    IO Server / 64999 - Setting Processor Affinity could throw an exception if more than 64 cores: On systems with more than 64 cores, setting processor affinity could throw an exception which would cause problems in the Runtime Manager backend. This exception is now captured and ignored.

    Another thing to consider is when running as a Windows Service, anything that would normally block UI, would also block the service. E.g. like modal popup windows.

    We have another customer with 2016 that has over 60 processes running on the same machine (in Windows Service mode). They hit some port limits, so looked at reducing the cluster to cluster connections. You can do this by running the computer setup wizard and deselecting the cluster connections for each process. They most likely only need to connect to their own cluster (Client process does need to connect to all clusters!). Unless you have cross cluster data sharing, like IO on Cluster 1, but Trend or Alarm tag on Cluster2 for example.

  • in reply to Olivier

    Oliver, Thanks for your interest.

    1. Yes the customer is running the Citect2016 March 2020 update - Update 38 (Mar 10, 2020)

    2. The hardware tells me it has 56 CPU's x  Intel(R) Xeon(R) CPU E5-2600 v4 W 2.00GHz,  Windows reports Node 0, CPU's  0 -27 and Node 1, CPU's 0-27, which also looks like 56 CPU's to me. 

    3. Yes got caught with the UI where i turned on the AutoLoginMode=1 and hence it was trying to popup a login window, that caused it to throw errors.  None of that happening now.

    4.  It impacts any server function, using CitectRunTime manager i can stop one that is running and start one that isn't running. But i cannot go over the 31 services runnning. I can run any combination i like less than 32.

    If i stop RunTime Manager in services and just run it in the user session i can run all 36 services.  

    I am begining to think this is operating system related, not runtime manager.

    Mike

  • in reply to Mike

    Hi Mike;

    You should raise it with Support.

    Best Regards

  • in reply to Mike

    Can you share details of your Operating System that Citect is running on? Is this physical hardware or virtualized machine?

    I've replicated your issue using Citect SCADA 2018 R2 + May 2021 Update, on Windows 2016 machine.

    I think it is a defect in 2016-2018 R2 versions. I also tested it in 2020 R2 (not officially released yet) and it work as expected. Like Antonio mentioned, best to raise this with support.

Reply
  • in reply to Mike

    Can you share details of your Operating System that Citect is running on? Is this physical hardware or virtualized machine?

    I've replicated your issue using Citect SCADA 2018 R2 + May 2021 Update, on Windows 2016 machine.

    I think it is a defect in 2016-2018 R2 versions. I also tested it in 2020 R2 (not officially released yet) and it work as expected. Like Antonio mentioned, best to raise this with support.

Children
  • in reply to Olivier

    Oliver, Many thanks for your help in confirming the issue.  It's was beneficial to know that it was a Windows Server 2016 and Citect 2016 together had the issue that could be replicated.  We are restructuring the project which will tidy up some lazy configuration issues.

    Cheers,

    Mike

© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.