This post talks about the issue of failing to export the Radius log. Please find the way to tackle it below.
Physical Network Topology
The customer has three servers, one with SM + SC installed and the other two with SC server. Configure the database mirroring environment, with the SM server as the witness database, and the principal database and the mirror database are located on two side-hung SC's respectively.
Figure 1-1 Controller network
Fault Description
The customer filters the log information under a certain static ID, with a total of about 40,000 entries. When exporting, the browser page is always displayed and loaded, and there is still no response after waiting for half an hour.
Troubleshooting Procedure
Step 1 Customer told us that the hard disk was full before, and then he shrinkaged the log to solve the problem. Check the disk now, we find the disks has resumed normally.
Step 2 All three databases logged in with sa account can be accessed normally, but the status of the principal database is displayed as Pending.
Step 3 Viewing RADIUS Log shows that the controller connected to the database was abnormal because the database was suspended.
Step 4 Restore the database status manually.
1. Open the database management software, and login to the database with sa account.
2. Click New Query, enter alter database AgileControllerDB set partner resume, and click Execute.
----End
Root Cause
Insufficient disk space leads to abnormal database status, database can not read and write normally, resulting in the normal export of logs.
