syslogd@elprod (missing process) | Community
Skip to main content
S
Shruti1
Level 4
August 6, 2022
Solved

syslogd@elprod (missing process)

  • August 6, 2022
  • 2 replies
  • 1113 views

Hi All

Mine Adobe on premise instance and I am facing this issue

 

 

 

Please please help me all--how can i make this up IN Adobe

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Shubham_Goyal__

Hi Shruti,

syslogd module helps to save system logs for processes (modules) like web, webmdl, watchdog logs save in the directory (<installation directory>/var/<instance>/log/<module>.log). Now, if this module was not running then the log files for these processes would not have been generated in that directory for those days. Check the configuration of the syslogd in the serverConf.xml file also make sure syslogd process is running (nlserver start syslogd@default) on your campaign server at port 666 (default).

Some docs you can refer: 
Log files - syslogd
syslogd serverConf
syslogd listening port

Cheers,

Shubham

2 replies

S
Shruti1Author
Level 4
August 6, 2022

please help

S
SurabattulaSr
Level 6
August 6, 2022

Hi,

You might have to verify the Server Configuration for your instance. Also, refer this thread where a similar issue was reported. Ideally this module should be running on Port 6666. Verify that as well.

If in case you are not able to fix it, you do also have an option of reaching out to Adobe via Support Ticket to get their assistance if it is hosted Instance. If on-prem, reach out to your support admin

Thanks,

SSB

 

    Shubham_Goyal__
    Shubham_Goyal__Accepted solution
    Level 6
    August 8, 2022

    Hi Shruti,

    syslogd module helps to save system logs for processes (modules) like web, webmdl, watchdog logs save in the directory (<installation directory>/var/<instance>/log/<module>.log). Now, if this module was not running then the log files for these processes would not have been generated in that directory for those days. Check the configuration of the syslogd in the serverConf.xml file also make sure syslogd process is running (nlserver start syslogd@default) on your campaign server at port 666 (default).

    Some docs you can refer: 
    Log files - syslogd
    syslogd serverConf
    syslogd listening port

    Cheers,

    Shubham

      Terms & ConditionsAccessibility statement

      Loading footer...