sawhat

CloudServer 1.15.2.32 Auto-Maintenance Reboot failure

Discussion created by sawhat on Jul 23, 2018

Database fails to re-open after CloudServer 1.15.2.32 Auto-Maintenance Reboot

7/23/18 - 7:38am est

I just got a call from a customer that the database was down and when they tried to login they got a message saying the database is encrypted. I was able to manually open the database from the console.

 

 

Tail of Journal log:

2018-07-23T04:30:00.986Z - info: Auto maintenance schedule restart in 20 minutes.

2018-07-23T04:50:00.987Z - info: Auto maintenance triggered, no connected users.

2018-07-23T04:52:13.731Z - info: Auto Maintenance scheduled:0 34 0 * * *, using timezone:America/Kentucky/Louisville

2018-07-23T04:52:13.754Z - info: HeartBeat cron schedule:24 31 0-23 * * *

 

Excerpt from Event Log: (with ip address obscured)

2018-07-23 04:54:02.280 +0000 Information 606 ip-xxx-xx-x-xx.ec2.internal Default database location: filelinux:/opt/FileMaker/FileMaker Server/Data/Databases/

2018-07-23 04:54:02.280 +0000 Error 759 ip-xxx-xx-x-xx.ec2.internal Additional database folder [1] is invalid or could not be set: filelinux:/media/Data/Databases/

2018-07-23 04:54:02.281 +0000 Information 622 ip-xxx-xx-x-xx.ec2.internal Additional database folder [2] disabled.

Outcomes