Over the past weekend, we had transitioned myLPFM.com and Internal Application N01.
At this time, we have shut down lpfm.ws (Voluntary Public File) as we determine what will be the future of this service. We want to bring this back and it may come back after we are able to integrate the station interface into myLPFM.
We have been dealing with some very serious database performance issues and therefore a lot of time has been spent on trying to adjust the mySQL settings and taking other actions to improve the database performance.
We believe that a significant contributor to the database performance is the Drupal 10 cacheing. This was handled very differently in Drupal 7 (which Legacy used). The cache routines are ran at times when Drupal pages are accessed.
To address this issue as well as to address various issues that may impact other REC sites outside of Drupal, we have enhanced our IP Blocker routine to also include specific user agents such as Bytespider and GPTbot. IP Blocker is a brute force block where we can block specific query terms, IP addresses and now user agents. Attempts that get stopped by the IP Blocker will receive a HTTP 403 error (it used to receive a 401 error).
We have placed IP Blocker on the front end of our Drupal 10 operation and will cover all sites on System40 that are served using Drupal. We are still monitoring the efficacy of this change. So far, we are seeing the targeted bots being directed to 403 error codes and not reaching Drupal cache routines.
Recoding on FCCdata is continuing. We are now expecting a November cutover for FCCdata due to the delays caused by these database issues, which are still not considered resolved. We are looking also at other options to deal with the database performance.
