...
- During "normal" login to the GUI of a Standby FMC there are stacktraces in the logs due to `DBD::SQLAnywhere::st execute failed: Modifications not permitted for read-only database (DBD: execute failed)`. However, this is expected as the database must be in read-only mode to be the standby FMC. - The state of the FMC's database is known and this stacktrace should not occur under "normal" conditions. MOJO: 09-20 14:39:55 [.68227] [40767] [info] DBD::SQLAnywhere::db do failed: Modifications not permitted for read-only database (DBD: execute failed) at /usr/local/sf/lib/perl/5.24.4/SF/EOHandler.pm line 4786. MOJO: 09-20 14:39:55 [.68407] [40767] [info] storeContainer failed with exception: $VAR1 = bless( { MOJO: 09-20 14:39:55 '-file' => '/usr/local/sf/lib/perl/5.24.4/SF/EOHandler.pm', MOJO: 09-20 14:39:55 '-line' => 4786, MOJO: 09-20 14:39:55 '-stacktrace' => '_storePerms: Unable to store perms
FMC in HA
There is no workaround for this problem but this bug does not have any functional impact. Stack traces are present but not influencing the functionality - just showing up because DB on the standby FMC is in read-only mode. This is an expected transitory behaviour.
If the correct password is provided stacktraces occur resulting in access and: MOJO: 09-20 14:39:55 [.72003] [40767] [info] Session timeout set at /usr/local/sf/lib/perl/5.24.4/SF/Auth.pm line 380. MOJO: 09-20 14:39:55 [.78171] [40767] [info] Use of uninitialized value in string eq at /usr/local/sf/lib/perl/5.24.4/SF/PageData.pm line 196. MOJO: 09-20 14:39:55 [.78276] [40767] [debug] 200 OK (0.310409s, 3.222/s) If the wrong password is provided stacktraces occur resulting in no access and: MOJO: 09-20 16:31:07 [.97433] [40763] [info] Error storing user admin at /usr/local/sf/lib/perl/5.24.4/SF/Auth.pm line 4363. MOJO: 09-20 16:31:08 [.04456] [40763] [debug] 401 Unauthorized (0.193416s, 5.170/s) MOJO: 09-20 16:31:08 [.04467] [40763] [debug] after dispatch worker inspection