Geoscada server

[Tyrone19]

Hi community

Ive had a complaint from a customer stating that their Geoscada server shuts down every week either on a Monday or Tuesday most of the time however I can seem to find any issues on the log.  

Does anyone know what could cause this or could inform me if I am looking at the correct log file. I am looking at the DB_xxx log files.

I have attached the last log file I got from the customer. This was the log they got while the server was still off so should of tracked the shutting down, however I do not see anything.

Any help would be highly appreciated.

[geoffpatton]

If it was doing a shutdown process you would have the last entry in the newest DB log file like this

27-AUG-2021 21:19:37.092 0628 [MAIN] Stopping logging
-------------------------------------------------------------------------------
Logging stopped at 27-AUG-2021 21:19:42.436 (UTC)

I suspect you've looked for anything odd in the Event log once its been restarted.

I would check for something outside of Geo SCADA killing the process. is there anything in the Windows logs at he same time? look at the timestamp on the DB log file since the log records are in UTC.

Virus scanner maybe getting to aggressive?

I have seen some Windows 10 machines arbitrarily kill programs. You do get a almost useless generic message that an application was blocked and to contact an administrator. I've never had it stop a service though.

I was told that that was related to something messed up with Microsoft Store.

Wish I could be of more help, maybe Adam, or Bevan will have an Idea they seem to have the most answers lately.

Of course contacting your local support is a good idea at this point.

[BevanWeiss]

Are you able to provide a startup log please? 🙂

[AdamWoodland]

I replied internally, but basically my thoughts I shared with Tyrone were:

1. I can see no evidence of DBServer knowing about any shutdown, so something external is killing/aborting it

2. ~160 logic programs running each second, probably not related to the problem more an observation of the system and something to be tuned if necessary

3. Disk performance is bad, possibly a cause, possibly an effect (e.g. something smashing the disks at the same time, for example disk image backups), and possibly irrelevant too depending on the size of the system and what its doing. Looks to be around a file flushed every 20mS when really should be multiple files per millisecond (we have some servers that reach 18 files per millisecond, ~360 times faster than what this system is doing), and to check AV exceptions