Expand my Community achievements bar.

Announcing the launch of new sub-community for Campaign Web UI to cater specifically to the needs of Campaign Web UI users!
SOLVED

Workflow server (wfserver) stopped - How to read logs

Avatar

Level 2

Hi,

 

We have observed that Workflow server (wfserver) stopped and the logs are read as below:

stop requested (pid=xxxxx)

stopping workflow server (pid=xxxxx, tid=xxxxx)

 

We are not aware why this happened? Did someone ran the command to stop the workflow server?

How to read those logs?

 

Please help understand these.

 

Regards, Hari Krishna D

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @harikrishnadevanabowina ,

 

Could you Please go to the below directory and read the system logs by filtering the logs based on the pid in the error generated.

 

<installation directory>/var/<instance>/log/<module>.log.

 

By default, the Adobe Campaign platform has the syslogd module installed on it, but it is possible to use another syslog daemon. This module creates the log files in the log directory.

The logs of multi-instance modules are stored in the following directory: <installation directory>/var/default/log/. The same log file is shared by all instances (e.g. web.log).

 

You can check the file logins.log Logs all login attempts to Adobe Campaign (success or not) for any failure logins and trace out by comparing the Timestamps in this file VS Timestamps when the error was generated from web.log.

 

PFA the adobe documentation link for reference.

 

https://experienceleague.adobe.com/docs/campaign-classic/using/monitoring-campaign-classic/productio...

 

Regards,

Pravallika.

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Hi @harikrishnadevanabowina ,

 

Could you Please go to the below directory and read the system logs by filtering the logs based on the pid in the error generated.

 

<installation directory>/var/<instance>/log/<module>.log.

 

By default, the Adobe Campaign platform has the syslogd module installed on it, but it is possible to use another syslog daemon. This module creates the log files in the log directory.

The logs of multi-instance modules are stored in the following directory: <installation directory>/var/default/log/. The same log file is shared by all instances (e.g. web.log).

 

You can check the file logins.log Logs all login attempts to Adobe Campaign (success or not) for any failure logins and trace out by comparing the Timestamps in this file VS Timestamps when the error was generated from web.log.

 

PFA the adobe documentation link for reference.

 

https://experienceleague.adobe.com/docs/campaign-classic/using/monitoring-campaign-classic/productio...

 

Regards,

Pravallika.