- Joined
- May 1, 2019
- Messages
- 7
- Reaction score
- 1
The last few weeks I've noticed days later, that the Database Server service has stopped. It does not impact call routing but I have noticed that CPU is at 50% currently with only 5 users logged in and no active calls taking place.
I've tried looking at the logs, but it also seems that when the service fails, the logs cease to be written to. Is there a way to turn up verbosity on the logs? Right now it seems that the logs are only capturing 'INFO' messages.
I believe I have enough resources allocated to this VM:
6 GB RAM
2 CPU
Has anyone else run into this issue where the Database Service service stops? It seems that this started to occur when I upgraded to version 16.
I've tried looking at the logs, but it also seems that when the service fails, the logs cease to be written to. Is there a way to turn up verbosity on the logs? Right now it seems that the logs are only capturing 'INFO' messages.
I believe I have enough resources allocated to this VM:
6 GB RAM
2 CPU
Has anyone else run into this issue where the Database Service service stops? It seems that this started to occur when I upgraded to version 16.