• Replies 2 replies
  • Subscribers 586 subscribers
  • Views 118 views
  • Users 0 members are here
Options
Related

LogDevice Functioning in Citect 2018 R2 redundant Architechure

Hemant

Hi,

I have some special operational logs to records in a seperate file, for which i create a seperate alarm category and logdevices OperLog and specify seperate folder location other than DATA

folder to store the file

.

When i put project in runtime on primary server, Opelog.txt file is correctly generating, in midnight as per set time, old file were renamed as operlog.001, operlog.002 and etc correctly, 

however on standby server this is not functioning. All the time in destination folder specify only a  Opelog.txt file of current date is showing and its off 0 KB, no logs recorded at all. Also operlog.001, operlog.002 no such files are created. 

Kindly help to understand the functioning of logdevices in redundant configuration and posible reasons which may causes the issue.

Warm regards

Hemant

Parents

  • Sorry for such a delayed response.

    The behavior as you described is by design. If the primary server is offline, it is believed that the standby server would kick in and operlog.txt would be created. If you want both servers to be able to perform the log, you need to configure the log operation on Report_Server process and set [Report]RunStandby = 1. Give a go and see your requirement could be satisfied.

    Regards,

    Jacky

Reply

  • Sorry for such a delayed response.

    The behavior as you described is by design. If the primary server is offline, it is believed that the standby server would kick in and operlog.txt would be created. If you want both servers to be able to perform the log, you need to configure the log operation on Report_Server process and set [Report]RunStandby = 1. Give a go and see your requirement could be satisfied.

    Regards,

    Jacky

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