Audit log stopped in 3.4b

[mathgallant]

Hello,

I'm having another issue, this time with the Audit log. I know there was a change in the audit functionalities between 3.3g and 3.4b, but I can't imagine that my problems are related to those changes.

My problem is that the audit logs are always empty. If I try to start the audit log in the RM module, it says "Audit log stopped". If I perform a search in the Audit log, it says Audit log stopped. I enabled auditing in global properties, but this has no effect (I restarted).

This is a default install of 3.4b on Windows XP.

Thanks.

[rwetherall]

Hi,

Yes, this was an issue introduced when audit was turned off by default in the main product.

It has since been fixed for RM, but in the mean time try adding the following to your global.properties …

audit.enabled=true
audit.dod5015.enabled=true
‍‍‍‍

Cheers,
Roy

[dk1]

Hi,

Yes, this was an issue introduced when audit was turned off by default in the main product.

It has since been fixed for RM, but in the mean time try adding the following to your global.properties …

audit.enabled=true
audit.dod5015.enabled=true
‍‍‍‍

Cheers,
Roy

I have the same problem as the OP and this didn't work for me… do you have any more solutions?? thanks

[eholt]

DK1,

I was having similar problems with a fresh 3.4c installation as well but I was able to correct it.  I'll list out the steps I took to get there.  This is with a basic install of community edition with the mysql server running off the same computer as I am accessing from with share.

I copied in rwetherall's code to alfresco-global.properties located in the tomcat\shared\classes directory (opened with notepad).  I'm not sure if it makes a difference in terms of location of the where you enter the code, but I placed my entry at the end of the "External Executable Locations" list.

At this point, I had to stop the server and reboot it so it could have the new code running in the background.  I went through my programs list from the start button and clicking on 'Stop Alfresco Community Service'.  Give it a few moments to finish closing the database.  Once the dos windows close, click on 'Start Alfresco Community Service'.  Give it a few more moments until the dos windows close again.  Open share and login as normal and you should have a working audit trail in your records management site.

In my opinion, audit trails really need to be active by default and not require adding in a couple lines of code as I believe this is a crucial component that makes up DoD5015.2

[mathgallant]

Well this project bubbled back to the top of my list and it seems time heals. Or at least it allows time for newer versions to be released. I tried with 3.4d and indeed the two lines (audit.enabled=true, audit.dod5015.enabled=true) do the trick. Possible other variables worth mentioning for my success story are that I used Ubuntu Desktop 10.04 32 bits and completely default install of the community release.