I reaized I had this same problem on several different DNN installations, which started when I upgraded to 4.9.1, as far as I can tell. I had changed nothing related to site log settings, yet the database table mysteriously stopped having new entries after the upgrade date.
Today I found the solution was to set the site log buffer to the value "1". I originally had it set to "2". I also tried setting it to "3" as a test to see if that would also work, but it did not. I have not tried any other values, but setting the buffer to "1" fixed the problem on the 3 sites in question.
For the record, the following settings under Host Settings:
- Site log storage: Database
- Site log buffer: 1
- Site log history: (some are 180, some are 365)
Under the Portal Admin Site Settings, Host Settings:
- Site log history: -1 (from my experience, this tells DNN to use the main Host settings value for this site)
Also, before changing the site log buffer to 1, I first tried manually deleting the site log records via SQL. I left 30 days of data, but still did not help. As an aside to this, I have read other user comments about the size of the site log table and that it should be kept very small for performance, or it might get "full". Since I am using a full SQL SQL Server 2005 dB as the back end, I'm not sure I understand these comments. I know it can take a long time to pull a large history report, but adding a log record to a large table shouldn't be a problem.
I am more concerned that I now have to have a buffer of only "1" which will cause a lot more SQL activity.
If others can confirm this or have similar experiences, I will be happy to report this as a bug in Gemini.
Rob Ralston