Hello Team,
We have encountered an issue where the application is creating a locked file associated with the runtime database, making the application unavailable until the locked file is cleared. This typically happens when the station performs something unexpected or detrimental to the application’s functionality.
Currently, we do not have access to the platform, so we would appreciate your guidance on how to identify and resolve this issue.
Can you please advise on the steps to locate and clear the locked file?
Are there any specific logs or diagnostics we should check to understand the root cause?
Do you recommend any preventive measures to avoid this issue in the future?
Your expertise and assistance in resolving this would be greatly appreciated
Are you trying to say you have a config.bog file that is locked?
The Niagara application was installed on a remote computer by the customer, who then created a station and shared the login details with us. We installed the Niagara application on our local PC and connected to the remote station from here. We are adding our field controllers (like JACE 8000 and Edge 534) to the Niagara network and creating graphics.
However, we’re experiencing a problem where the remote station frequently goes offline for 10 to 15 minutes or more, making it inaccessible. We reported this issue to the client, and they found that the problem is caused by the application creating a “locked file” linked to the runtime database. This locked file makes the application unavailable until it gets cleared. This usually happens when the station does something unexpected. The client advised us to fix this issue directly at the station level.
I needs to understand root cause
So you’re saying the supervisor is going offline?
How often is the supervisor saving its station? Typically config.bog.lock file is created when a backup is being made. But if something is causing a power outage, it can keep this file in a locked position.
We have kept the default time (24hr) for station auto save.
What I’m trying to ascertain is are you having the issue with the Supervisor or the JACE and edge controller?
The problem with the supervisor
In order to delete that. I believe you need to shut down the daemon, delete that file, then start the daemon again and then the station. If you are a Lynxspring partner, you can email their support team and they can get back to you on Monday.
Thank you, Charles. Please share any documentation you have for the process, so I can forward it to the client.
I don’t know if there’s any documentation per se on this particular subject. Again, if you’re a lynxspring partner, if you send an email to the support team, they might have documentation they’ve created internally for it. I wouldn’t be able to supply that here.
1 Like
Till the issue is not fixed. Attached here console dump please review when you get chance
dump.txt (259.7 KB)
Unfortunately without remote access, I cannot make a determination on how to fix this. I would contact Lynxspring’s Technical Support (support@lynxspring.com) and explain the situation.
If you are a lynxspring partner, we can assist you. However, I’m not sure where the config.bog.lock files are located. If you cannot move or delete them, I’m not sure how else to get rid of them. Maybe a rename of them would work?
1 Like