Start a Conversation

Unsolved

48 Posts

3370

December 10th, 2018 10:00

NetWorker v18.1 won't start with systemctl

Hello guys,

I just installed NetWorker Server v18.2 on a freshly installed SLES 12 SP3. But after the installation the startup crashes with the message:

0 12/10/18 13:26:41  1 5 0 370726720 17146 0 nsrexecd NSR notice @(#) Product:      NetWorker

0 12/10/18 13:26:41  1 5 0 370726720 17146 0 nsrexecd NSR notice @(#) Release:      18.2.0.0.Build.28

0 12/10/18 13:26:41  1 5 0 370726720 17146 0 nsrexecd NSR notice @(#) Build number: 28

0 12/10/18 13:26:41  1 5 0 370726720 17146 0 nsrexecd NSR notice @(#) Build date:   Thu Nov 29 09:59:39 PST 2018

0 12/10/18 13:26:41  1 5 0 370726720 17146 0 nsrexecd NSR notice @(#) Build arch.:  linux86w

0 12/10/18 13:26:41  1 5 0 370726720 17146 0 nsrexecd NSR notice @(#) Build info:   DBG=0,OPT=-O2 -fno-strict-aliasing

0 12/10/18 13:27:49  1 5 0 2687940416 17174 0 nsrctld NSR notice @(#) Product:      NetWorker

0 12/10/18 13:27:49  1 5 0 2687940416 17174 0 nsrctld NSR notice @(#) Release:      18.2.0.0.Build.28

0 12/10/18 13:27:49  1 5 0 2687940416 17174 0 nsrctld NSR notice @(#) Build number: 28

0 12/10/18 13:27:49  1 5 0 2687940416 17174 0 nsrctld NSR notice @(#) Build date:   Thu Nov 29 09:59:39 PST 2018

0 12/10/18 13:27:49  1 5 0 2687940416 17174 0 nsrctld NSR notice @(#) Build arch.:  linux86w

0 12/10/18 13:27:49  1 5 0 2687940416 17174 0 nsrctld NSR notice @(#) Build info:   DBG=0,OPT=-O2 -fno-strict-aliasing

127106 12/10/18 13:27:49  1 5 0 2687940416 17174 0 nsrctld NSR notice Startup in progress; starting all daemons...

144355 12/10/18 13:27:49  1 5 0 2687940416 17174 0 nsrctld NSR notice Daemon rmq-epmd is running.

144355 12/10/18 13:27:51  1 5 0 2687940416 17174 0 nsrctld NSR notice Daemon rmq is running.

  12/10/18 13:27:52  1 5 0 2639673088 17174 0 nsrctld NSR notice rmq: Failed to create thread: Resource temporarily unavailable (11)

0 12/10/18 13:27:53  1 5 0 2639673088 17174 0 nsrctld NSR notice rmq: /opt/nsr/rabbitmq-server-3.6.14/sbin/rabbitmq-server: line 271: 17418 Aborted                 (core dumped) start_rabbitmq_server "$@"

144354 12/10/18 13:27:53  1 5 0 2687940416 17174 0 nsrctld NSR notice Daemon rmq terminated.

144359 12/10/18 13:27:53  3 5 0 2687940416 17174 0 nsrctld NSR error Scheduling restart of daemon /opt/nsr/rabbitmq-server-3.6.14/bin/rabbitmq-server in 5 seconds

137911 12/10/18 13:27:53  5 5 0 2687940416 17174 0 nsrctld NSR critical Aborting startup sequence: Process /opt/nsr/rabbitmq-server-3.6.14/bin/rabbitmq-server exited in less than 10 seconds at startup: exit code 0

127108 12/10/18 13:27:53  5 5 0 2687940416 17174 0 nsrctld NSR critical Failed to start all daemons; shutting down...

  12/10/18 13:27:54  1 5 0 2639673088 17174 0 nsrctld NSR notice rmq-epmd: epmd: Mon Dec 10 13:27:54 2018: got KILL_REQ - terminates normal

137914 12/10/18 13:27:54  5 5 0 2687940416 17174 0 nsrctld NSR critical Shutdown due to error: Process /opt/nsr/rabbitmq-server-3.6.14/bin/rabbitmq-server exited in less than 10 seconds at startup: exit code 0

I also tried installing v18.1 and v9.2.2 which result in the same behaviour.

When I start the NetWorker daemons from /opt/nsr/admin/networker.sh start, all daemons come up and work properly.

It must have something to do mit the RabbitMQ. In the logs of it is nothing what pointed to a failure.

Can someone help?

Thanks

Beacon

48 Posts

December 11th, 2018 06:00

I needed to adjust two settings in /etc/systemd/system.conf:

#DefaultTasksMax=512

to

DefaultTasksMax=infinity

and


#DefaultLimitNOFILE=

to

DefaultLimitNOFILE=65536


Now the daemons are starting correctly.

No Events found!

Top