Highlighted

Appserver shuts down

Avatar

Avatar

SteveKCampaign

Avatar

SteveKCampaign

SteveKCampaign

10-08-2017

Hello Community,

I'm happy that I found you! I have a problem with the adobe campaign applicationserver 6.1.1

On Server Manager -> Configuration -> services is the serves listed. The problem is when I start it it shuts down again after about 1 minute.

After some research I went into the console directed to the directory of the nlserver. exe and executed some commands.

I found out that the is missing. After that I tried to start the watchdog. But he shuts down.

It's trying to start a childtask.. and waiting becaus childtask is already running.... I got the PID of the task and killed it. But still the same. It looked like the task got reinitated instantly. Howeder I cannot name the task because I cannot found it. Guess because it's a childtask.

After that I found out that in the service options of the server Manager-Configuration-services that behind the serves is also the starting of this command:
nlserver watchdog -svc -noconsole

Watchdog again.So my conclusion is that I cannot start it because the watchdog isnt starting.

By the way the the childproces is "syslogd@default"

Thanks for help

Steven

Replies

Highlighted

Avatar

Avatar

Amit_Kumar

MVP

Avatar

Amit_Kumar

MVP

Amit_Kumar
MVP

10-08-2017

Hi Steven,

Thanks for reaching out the community.

Can you start watchdog with -verbose argument and share Catalina logs(will be there if you are not using Apache server) from var\logs?https://marketingcloudblog.com/managing-adobe-campaign-via-command-line/

If you are not sure how to execute the command you can take look at this blog post:

Command line: Tricks to Improve Your Productivity with Adobe Campaign

Hope this will give you more info to debug the problem.

Regards,

Amit

Avatar

Avatar

SteveKCampaign

Avatar

SteveKCampaign

SteveKCampaign

11-08-2017

Sorry some logs are in german...
but here the most important I guess

Catalina

Aug 08, 2017 6:13:39 PM org.apache.coyote.AbstractProtocol init

INFORMATION: Initializing ProtocolHandler ["http-bio-8080"]

Aug 08, 2017 6:13:39 PM org.apache.catalina.startup.Catalina load

INFORMATION: Initialization processed in 1693 ms

Aug 08, 2017 6:13:39 PM org.apache.catalina.core.StandardService startInternal

INFORMATION: Starting service Tomcat-Standalone

Aug 08, 2017 6:13:39 PM org.apache.catalina.core.StandardEngine startInternal

INFORMATION: Starting Servlet Engine: Apache Tomcat/7.0.52

Aug 08, 2017 6:13:42 PM org.apache.catalina.util.SessionIdGenerator createSecureRandom

INFORMATION: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [1,061] milliseconds.

Aug 08, 2017 6:13:45 PM org.apache.catalina.startup.HostConfig deployDirectory

INFORMATION: Deploying web application directory C:\Program Files (x86)\Adobe\Adobe Campaign v6\tomcat-7\bin

Aug 08, 2017 6:13:45 PM org.apache.catalina.startup.HostConfig deployDirectory

INFORMATION: Deploying web application directory C:\Program Files (x86)\Adobe\Adobe Campaign v6\tomcat-7\conf

Aug 08, 2017 6:13:45 PM org.apache.catalina.startup.HostConfig deployDirectory

INFORMATION: Deploying web application directory C:\Program Files (x86)\Adobe\Adobe Campaign v6\tomcat-7\lib

Aug 08, 2017 6:13:45 PM org.apache.catalina.startup.HostConfig deployDirectory

INFORMATION: Deploying web application directory C:\Program Files (x86)\Adobe\Adobe Campaign v6\tomcat-7\work

Aug 08, 2017 6:13:45 PM org.apache.coyote.AbstractProtocol start

INFORMATION: Starting ProtocolHandler ["http-bio-8080"]

Aug 08, 2017 6:13:45 PM org.apache.catalina.startup.Catalina start

INFORMATION: Server startup in 5693 ms

Aug 08, 2017 6:14:31 PM org.apache.coyote.AbstractProtocol pause

INFORMATION: Pausing ProtocolHandler ["http-bio-8080"]

Aug 08, 2017 6:14:31 PM org.apache.catalina.core.StandardService stopInternal

INFORMATION: Stopping service Tomcat-Standalone

Aug 08, 2017 6:14:32 PM org.apache.coyote.AbstractProtocol stop

INFORMATION: Stopping ProtocolHandler ["http-bio-8080"]

Aug 08, 2017 6:33:53 PM org.apache.coyote.AbstractProtocol init

INFORMATION: Initializing ProtocolHandler ["http-bio-8080"]

Aug 08, 2017 6:33:53 PM org.apache.catalina.startup.Catalina load

INFORMATION: Initialization processed in 980 ms

Aug 08, 2017 6:33:53 PM org.apache.catalina.core.StandardService startInternal

INFORMATION: Starting service Tomcat-Standalone

Aug 08, 2017 6:33:53 PM org.apache.catalina.core.StandardEngine startInternal

INFORMATION: Starting Servlet Engine: Apache Tomcat/7.0.52

Aug 08, 2017 6:33:57 PM org.apache.catalina.startup.HostConfig deployDirectory

INFORMATION: Deploying web application directory C:\Program Files (x86)\Adobe\Adobe Campaign v6\tomcat-7\bin

Aug 08, 2017 6:33:57 PM org.apache.catalina.startup.HostConfig deployDirectory

INFORMATION: Deploying web application directory C:\Program Files (x86)\Adobe\Adobe Campaign v6\tomcat-7\conf

Aug 08, 2017 6:33:57 PM org.apache.catalina.startup.HostConfig deployDirectory

INFORMATION: Deploying web application directory C:\Program Files (x86)\Adobe\Adobe Campaign v6\tomcat-7\lib

Aug 08, 2017 6:33:57 PM org.apache.catalina.startup.HostConfig deployDirectory

INFORMATION: Deploying web application directory C:\Program Files (x86)\Adobe\Adobe Campaign v6\tomcat-7\work

Aug 08, 2017 6:33:57 PM org.apache.coyote.AbstractProtocol start

INFORMATION: Starting ProtocolHandler ["http-bio-8080"]

Aug 08, 2017 6:33:57 PM org.apache.catalina.startup.Catalina start

INFORMATION: Server startup in 4300 ms


NLSERVER LOG

2017-08-08 18:13:33.757+02    0000096C    00000970      1    error    log    Syntaxfehler: Option 'tracefile' kann nur einmal genutzt werden (iRc=16384)

2017-08-08 18:13:33.757+02    0000096C    00000970      1    info    log    Anwendungsserver für Adobe Campaign Version 6.1.1 (build 8667) vom 04.08.2015

2017-08-08 18:13:33.773+02    0000093C    00000940      1    error    log    Syntaxfehler: Option 'tracefile' kann nur einmal genutzt werden (iRc=16384)

2017-08-08 18:13:33.773+02    0000093C    00000940      1    info    log    Anwendungsserver für Adobe Campaign Version 6.1.1 (build 8667) vom 04.08.2015

2017-08-08 18:13:33.773+02    00000964    00000968      1    error    log    Syntaxfehler: Option 'tracefile' kann nur einmal genutzt werden (iRc=16384)

2017-08-08 18:13:33.773+02    00000964    00000968      1    info    log    Anwendungsserver für Adobe Campaign Version 6.1.1 (build 8667) vom 04.08.2015

2017-08-08 18:13:33.773+02    0000095C    00000960      1    error    log    Syntaxfehler: Option 'tracefile' kann nur einmal genutzt werden (iRc=16384)

2017-08-08 18:13:33.773+02    0000095C    00000960      1    info    log    Anwendungsserver für Adobe Campaign Version 6.1.1 (build 8667) vom 04.08.2015

2017-08-08 18:33:51.778+02    00000694    00000828      1    error    log    Syntaxfehler: Option 'tracefile' kann nur einmal genutzt werden (iRc=16384)

2017-08-08 18:33:51.778+02    00000694    00000828      1    info    log    Anwendungsserver für Adobe Campaign Version 6.1.1 (build 8667) vom 04.08.2015

2017-08-08 18:33:51.809+02    0000000C    00000140      1    error    log    Syntaxfehler: Option 'tracefile' kann nur einmal genutzt werden (iRc=16384)

2017-08-08 18:33:51.809+02    0000000C    00000140      1    info    log    Anwendungsserver für Adobe Campaign Version 6.1.1 (build 8667) vom 04.08.2015

2017-08-08 18:33:51.825+02    00000D6C    00000510      1    error    log    Syntaxfehler: Option 'tracefile' kann nur einmal genutzt werden (iRc=16384)

2017-08-08 18:33:51.825+02    00000D6C    00000510      1    info    log    Anwendungsserver für Adobe Campaign Version 6.1.1 (build 8667) vom 04.08.2015

2017-08-08 18:33:51.934+02    00000B58    00000594      1    error    log    Syntaxfehler: Option 'tracefile' kann nur einmal genutzt werden (iRc=16384)

2017-08-08 18:33:51.934+02    00000B58    00000594      1    info    log    Anwendungsserver für Adobe Campaign Version 6.1.1 (build 8667) vom 04.08.2015


-------------------------
Watchdog

2017-08-11 09:08:04.323+02    00001E6C    00001B34      1    info    log    Anwendungsserver für Adobe Campaign Version 6.1.1 (build 8667) vom 04.08.2015

2017-08-11 09:08:04.323+02    00001E6C    00001B34      1    info    log    Start des Watchdog-Prozesses (PID=7788, TID=6964)...

2017-08-11 09:08:04.339+02    00001E6C    00001B34      1    info    log    Aufgabe 'syslogd@default' ('nlserver syslogd -verbose -tracefile:syslogd@default -instance:default -detach') wird in einem neuen Prozess gestartet

2017-08-11 09:08:04.355+02    00001E6C    00001B34      1    warning    log    Der Kindprozess 'syslogd@default' existiert bereits (PID=2892, TID=3348). Er wurde nicht gestartet.

2017-08-11 09:08:10.439+02    00001E6C    00001B34      1    info    log    Warten auf den Start der Kindaufgaben...

2017-08-11 09:08:15.509+02    00001E6C    00001B34      1    info    log    Warten auf den Start der Kindaufgaben...

2017-08-11 09:08:20.579+02    00001E6C    00001B34      1    info    log    Warten auf den Start der Kindaufgaben...

2017-08-11 09:08:25.649+02    00001E6C    00001B34      1    info    log    Warten auf den Start der Kindaufgaben...

2017-08-11 09:08:30.720+02    00001E6C    00001B34      1    info    log    Warten auf den Start der Kindaufgaben...

2017-08-11 09:08:35.790+02    00001E6C    00001B34      1    info    log    Warten auf den Start der Kindaufgaben...

2017-08-11 09:08:40.860+02    00001E6C    00001B34      1    info    log    Warten auf den Start der Kindaufgaben...

2017-08-11 09:08:45.930+02    00001E6C    00001B34      1    info    log    Warten auf den Start der Kindaufgaben...

2017-08-11 09:08:51.000+02    00001E6C    00001B34      1    info    log    Warten auf den Start der Kindaufgaben...

2017-08-11 09:08:56.071+02    00001E6C    00001B34      1    info    log    Warten auf den Start der Kindaufgaben...

2017-08-11 09:09:01.141+02    00001E6C    00001B34      1    info    log    Warten auf den Start der Kindaufgaben...

2017-08-11 09:09:05.197+02    00001E6C    00001B34      1    error    log    Kindaufgaben werden nach 60 Sekunden immer noch gestartet. (iRc=-60)

2017-08-11 09:09:05.197+02    00001E6C    00001B34      1    info    log    Monitoring-Modus wird angehalten (PID=7788, TID=6964)...

Highlighted

Avatar

Avatar

florentlb

Total Posts

1.1K

Likes

234

Correct Answer

239

Avatar

florentlb

Total Posts

1.1K

Likes

234

Correct Answer

239
florentlb

18-08-2017

Hi Steve,

Were you able to find the cause by checking your logs? Have you raised a support ticket to have it investigated?

Let me know,

Florent

Highlighted

Avatar

Avatar

Amit_Kumar

MVP

Avatar

Amit_Kumar

MVP

Amit_Kumar
MVP

20-08-2017

Hi Steven,

I can't read German so unable to help you there. The App server usually crashes because of two reasons, incorrect configuration for instance/server conf file or Unstable build/missing files.

Take a backup of this server and Install a new server and connect that server to existing database, you will not loose anything.

Regards,

Amit

Highlighted

Avatar

Avatar

SteveKCampaign

Avatar

SteveKCampaign

SteveKCampaign

22-08-2017

Hello, not yet. We are propably going to rais a ticket soon.

Highlighted

Avatar

Avatar

SteveKCampaign

Avatar

SteveKCampaign

SteveKCampaign

22-08-2017

Hi Amit,

the  nl server log says in the error lines:

Syntaxerror: The option tracefile can only used once..

The watchdog says:

1. start of watchdog process

2. syslogd@default is started in a new process
3. syslogd@default already exists and will not get started.

4. wait for start of childprocess....

4. wait for start of childprocess....

4. wait for start of childprocess....

5. the child process hasnt started after 60 seconds.

6. Monitoring modus is stopped.

Highlighted

Avatar

Avatar

david_garcia1

MVP

Avatar

david_garcia1

MVP

david_garcia1
MVP

22-08-2017

Here are some good documentation links relating to your issue.

https://docs.campaign.adobe.com/doc/AC6.1/en/PRO_Production_procedures_Log_files.html

https://docs.campaign.adobe.com/doc/AC6.1/en/PRO_Production_procedures_Administration.html

https://docs.campaign.adobe.com/doc/AC6.1/en/PRO_Troubleshooting_Modules_and_frequent_issues.html

https://docs.campaign.adobe.com/doc/AC6.1/en/PRO_General_architecture_List_of_open_ports.html

https://docs.campaign.adobe.com/doc/AC6.1/en/PRO_Production_procedures_Operating_principle.html

In the config-default.xml

Check that syslogd autostart is set to true as well as trackinglogd

  <syslogd autoStart="true" processRestartTime="05:50:00" runLevel="0"/>

  <!-- Avoid restarting at 6:00 AM since some recurring workflows can try to contact the server at exactly this time -->

  <web args="-tomcat -autorepair" autoStart="true" processRestartTime="06:01:00"/>

  <!-- to start if the machine is also a redirection server -->

  <trackinglogd autoStart="true"/>

</serverconf>

Also in the serverConf.xml file share the following with us.

    <!-- Log management module.

       args :  Start-up parameters

       autoStart :  Automatic start Default: false

       initScript :  ID of JavaScript to execute when starting the process

       maxFileSizeMb :  Maximum size in Mb for a log file Default: 10

       maxProcessMemoryAlertMb :  Alert concerning the amount of RAM consumed (in Mb) by a given process Default: 1800

       maxProcessMemoryWarningMb :  Warning concerning the amount of RAM consumed (in Mb) by a given process Default: 1600

       processRestartTime :  Time of the day when the process is automatically restarted Default: '06:00:00'

       runLevel :  Priority at start Default: 10 -->

  <syslogd args="" autoStart="false" initScript="" maxFileSizeMb="100" maxProcessMemoryAlertMb="1800"

           maxProcessMemoryWarningMb="1600" processRestartTime="06:00:00" runLevel="10"/>

    <!-- Configuration of the tracking server

       args :  Start-up parameters

       autoStart :  Automatic start Default: false

       consolidationPeriodSec :  Consolidation period Default: 300

       dedupOpenPeriodMin :  Remove duplicate open tracking logs to limit the effects of mail previews in mail readers like Outlook. Default: 1

       errorIgnorePercent :  Do not update tracking indicators as long as the ratio of journals not already taken into account does not reach this value. Default: 1

       errorIgnorePeriod :  Maximum duration before error indicators are recomputed. Default: 86400

       indicatorsDuration :  Duration after the validity date of a delivery after which consolidated indicators are no longer computed Default: 2592000

       initScript :  ID of JavaScript to execute when starting the process

       logCountPerRequest :  Number of logs requested by call to the remote tracking server Default: 1000

       maxProcessMemoryAlertMb :  Alert concerning the amount of RAM consumed (in Mb) by a given process Default: 1800

       maxProcessMemoryWarningMb :  Warning concerning the amount of RAM consumed (in Mb) by a given process Default: 1600

       processRestartTime :  Time of the day when the process is automatically restarted Default: '06:00:00'

       runLevel :  Priority at start Default: 10

       trackingIgnorePercent :  Do not update tracking indicators as long as the ratio of journals not already taken into account does not reach this value. Default: 1

       trackingIgnorePeriod :  Maximum duration before tracking indicators are recomputed. Default: 86400

       userAgentCacheSize :  Size of browser identifier cache. Default: 500 -->

  <tracking args="" autoStart="false" consolidationPeriodSec="300" dedupOpenPeriodMin="1"

            errorIgnorePercent="1" errorIgnorePeriod="86400" indicatorsDuration="2592000"

            initScript="" logCountPerRequest="1000" maxProcessMemoryAlertMb="1800"

            maxProcessMemoryWarningMb="1600" processRestartTime="06:00:00" runLevel="10"

            trackingIgnorePercent="1" trackingIgnorePeriod="86400" userAgentCacheSize="500"/>

    <!-- Configuration of the tracking log writing daemon

       args :  Start-up parameters

       autoStart :  Automatic start Default: false

       initScript :  ID of JavaScript to execute when starting the process

       maxCreateFileRetry :  Maximum number of files that can be created in case of writing failure in log files. Default: 5

       maxLogsSizeOnDiskMb :  Maximum space used by logs on disk (in MB). May not be less than 100 MB. Default: 500

       maxProcessMemoryAlertMb :  Alert concerning the amount of RAM consumed (in Mb) by a given process Default: 1800

       maxProcessMemoryWarningMb :  Warning concerning the amount of RAM consumed (in Mb) by a given process Default: 1600

       maxSharedLogs :  Maximum number of logs stored in shared memory. Cannot be less than 10000. Default: 25000

       processRestartTime :  Time of the day when the process is automatically restarted Default: '06:00:00'

       purgeLogsPeriod :  Number of logs inserted before starting the purge of log files. May not be lower than 50000. Default: 50000

       runLevel :  Priority at start Default: 10

       webTrackingParamSize :  Maximum number of characters saved in shared memory for extra web tracking parameters Default: 64 -->

  <trackinglogd args="" autoStart="false" initScript="" maxCreateFileRetry="5" maxLogsSizeOnDiskMb="500"

                maxProcessMemoryAlertMb="1800" maxProcessMemoryWarningMb="1600" maxSharedLogs="25000"

                processRestartTime="06:00:00" purgeLogsPeriod="50000" runLevel="10"

                webTrackingParamSize="64"/>

  • Can you perform an nlserver config -reload and paste the console output.
  • Share the serverConf.xml.diff and obscure any domains/IPs/passwords.