[8599863] at com.webMethods.sc.auditing.queue.AuditQueueWorker.run(AuditQueueWorker.java:88) [wm-scg-audit.jar:10.15.0.0001-0343]
[8599862] at com.webMethods.sc.auditing.queue.AuditQueueWorker.processEvent(AuditQueueWorker.java:184) [wm-scg-audit.jar:10.15.0.0001-0343]
[8599861] at com.webMethods.sc.auditing.destination.WmDirectoryDestination.logEvent(WmDirectoryDestination.java:245) ~[wm-scg-audit.jar:10.15.0.0001-0343]
[8599860]2023-10-08 21:59:04 PDT [WmAuditingSC.queue.2406E] (tid=253) [2406] AuditQueueWorker for queue âSecurityQueueâ failed to log event to destination âAuditFSDestâ; reason âDestination âAuditFSDestâ is not openâ; stack trace follows com.webMethods.sc.auditing.API.destination.WmAuditDestinationException: Destination âAuditFSDestâ is not open
looks like Audit logging is configured to file system.
Did you check your FileSystem where IS is installed for proper read/write permissions and capacity, please?
There should be a more detailed error message why the destination could not be opened.
We have the proper read / write permissions as well good storage around 200GB is free.
drwxr-xr-x. 14 kmv kmv 233 Oct 9 10:48 wm1015_kmv_com
Whenever i click on the error logs this is the error message we are capturing from the server log
2023-10-12 07:10:17 PDT [WmAuditingSC.queue.2406E] (tid=250) [2406] AuditQueueWorker for queue âSecurityQueueâ failed to log event to destination âAuditFSDestâ; reason âDestination âAuditFSDestâ is not openâ; stack trace follows com.webMethods.sc.auditing.API.destination.WmAuditDestinationException: Destination âAuditFSDestâ is not open
at com.webMethods.sc.auditing.destination.WmDirectoryDestination.logEvent(WmDirectoryDestination.java:245) ~[wm-scg-audit.jar:10.15.0.0001-0343]
at com.webMethods.sc.auditing.queue.AuditQueueWorker.processEvent(AuditQueueWorker.java:184) [wm-scg-audit.jar:10.15.0.0001-0343]
at com.webMethods.sc.auditing.queue.AuditQueueWorker.run(AuditQueueWorker.java:88) [wm-scg-audit.jar:10.15.0.0001-0343]
Eventually you will get a more detailed error message there.
Another place to look at will be the wrapper.log in the profiles directory for the affected IS instance.
Addendum:
When using a database for the IS most of the logging options will be configured to use the database pools assigned to the proper JDBC functions in IS Admin under Settings. Usually, only server.log will be redirected to a log file in this case.
Can you share a screenshot of your JDBC Pools and Logging Destinations pages (both available under Settings in IS Admin)?
I am not able to check the error logs, the actual problem persists here, whenever i click on the error logs or security logs i am getting the below 400 error
UPDATE - I just noticed in your latest reply that youâre using the Embedded Database. Try mapping the âISCoreAuditâ Function to the âEmbedded Database Poolâ and restart the IS.
Iâve checked a few things and cannot narrow down the cause for âDestination âAuditFSDestâ is not openâ. You can try the following - 1. Shutdown the IS, take a backup of your DB schema, re-execute the DB scripts via DB Configurator and ensure that you have the right DB components installed, startup the IS
2. Create a support ticket
as error logger is configured to use a file you should have a WMERROR log file in the same directory as the server log.
Same applies to the security logger with WMSECURITY log file.
Additionally:
As you are already using an Oracle DB for your TN database, you might want to consider to reconfigure your JDBC functions to another schema on the same database equipped with the products âBPMâ and âIntergrationServerâ from DB Configurator.
You can then reconfigure most of the file based loggers to use the new JDBC Pool then.
Remember to create an extra schema for archiving operations.
See Monitor Users Guide for how to set up this schema correctly.
Most likely this will require a MWS instance with its own schema equipped with DB product âMyWebmethodsServerâ, which then should be configured for Central Users function.
Can you check the reason for SSL handshake issue shown in the wrapper.log:
To be more precise, Actually we have migrated our hosts from lapp300 to new host i.e kmv.
I have created a tar for working directory from lapp300 and placed in new server and generated the IS certs and placed, started the new server.
The same approach we followed for UAT servers, there we didnt faced this issue. But in this environment we are getting 400 Bad Request while accessing Error and Security logs in Admin page.
please check if the old database can be reached from the new server.
If not, prepare a new database and update the jdbc pool config under config/jdbc directory for your IS instance to point to the new database. Restart IS afterwards.
This needs a closer investigation, Varun - I recommend that you create a support ticket.
This seems something to do with the WmAdmin package, as opposed to your database.
There is an problem with the AuditConfig.xml
In that xml AuditFSDest parameter destination is pointing to our old directory.
After updating the correct details.
Restarted the server, it worked
