Cannot start MCS + EMS - exit status 1

Question

Suddenly I can't start the service. I'm trying to start these services as user admin with ssh keys loaded without success. I just configured a notification profile by email and modified the mcserver.xml part of smtp server and email address. Then I tried to restart the mcs server but now it doesn't start up. Licenses are installed correctly if I run the avamaint license --avamaronly I get the license printed. The log from dpnctl.log is here. Please help. 2010/07/27-14:29:48 - - - - - - - - - - - - - - - BEGIN2010/07/27-14:29:48 server up: idle2010/07/27-14:29:48 - - - - - - - - - - - - - - - END2010/07/27-14:29:48 rm -f /tmp/dpnctl-opstatus-dpn-status-1918 /tmp/dpnctl-opstatus-dpn-output-19182010/07/27-14:29:48 dpnctl: INFO: gsan status - - - - - - - - - - BEGIN2010/07/27-14:29:48 dpnctl: INFO: gsan status - - - - - - - - - - END2010/07/27-14:29:48 dpnctl: INFO: gsan status: ready2010/07/27-14:29:48 dpnctl: INFO: MCS status - - - - - - - - - - BEGIN2010/07/27-14:29:48 ([ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --test ; echo $? >/tmp/dpnctl-get-mcs-status-status-1918) >/tmp/dpnctl-get-mcs-status-output-1918 2>&12010/07/27-14:29:49 /bin/cat /tmp/dpnctl-get-mcs-status-output-19182010/07/27-14:29:49 [ '/bin/cat /tmp/dpnctl-get-mcs-status-output-1918' exit status = 0 ]2010/07/27-14:29:49 /bin/cat /tmp/dpnctl-get-mcs-status-status-1918 2>&12010/07/27-14:29:49 [ '/bin/cat /tmp/dpnctl-get-mcs-status-status-1918 2>&1' exit status = 0 ]2010/07/27-14:29:49 output of '[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --test':2010/07/27-14:29:49 - - - - - - - - - - - - - - - BEGIN2010/07/27-14:29:49 INFO: Administrator Server status: down2010/07/27-14:29:49 - - - - - - - - - - - - - - - END2010/07/27-14:29:49 error return from '[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --test' - exit status 22010/07/27-14:29:49 rm -f /tmp/dpnctl-get-mcs-status-status-1918 /tmp/dpnctl-get-mcs-status-output-19182010/07/27-14:29:49 dpnctl: INFO: MCS status - - - - - - - - - - END2010/07/27-14:29:49 dpnctl: INFO: MCS status: down.2010/07/27-14:29:49 (/usr/local/avamar/bin/../lib/dpnutils/connectemcctl status; echo $? >/tmp/dpnctl-connectemc_ctl_status-status-1918) >/tmp/dpnctl-connectemc_ctl_status-output-1918 2>&12010/07/27-14:29:49 /bin/cat /tmp/dpnctl-connectemc_ctl_status-status-1918 2>&12010/07/27-14:29:49 [ '/bin/cat /tmp/dpnctl-connectemc_ctl_status-status-1918 2>&1' exit status = 0 ]2010/07/27-14:29:49 output of '/usr/local/avamar/bin/../lib/dpnutils/connectemcctl status':2010/07/27-14:29:49 - - - - - - - - - - - - - - - BEGIN2010/07/27-14:29:49 connectemc dead but subsys locked2010/07/27-14:29:49 connectemcctl: INFO: ConnectEMC status: down.2010/07/27-14:29:49 - - - - - - - - - - - - - - - END2010/07/27-14:29:49 error return from '/usr/local/avamar/bin/../lib/dpnutils/connectemcctl status' - exit status 22010/07/27-14:29:49 rm -f /tmp/dpnctl-connectemc_ctl_status-status-1918 /tmp/dpnctl-connectemc_ctl_status-output-19182010/07/27-14:29:49 dpnctl: INFO: ConnectEMC is down2010/07/27-14:29:49 dpnctl: INFO: EMS status - - - - - - - - - - BEGIN2010/07/27-14:29:49 ([ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/emserver.sh --test ; echo $? >/tmp/dpnctl-get-ems-status-status-1918) >/tmp/dpnctl-get-ems-status-output-1918 2>&12010/07/27-14:29:51 /bin/cat /tmp/dpnctl-get-ems-status-output-19182010/07/27-14:29:51 [ '/bin/cat /tmp/dpnctl-get-ems-status-output-1918' exit status = 0 ]2010/07/27-14:29:51 /bin/cat /tmp/dpnctl-get-ems-status-status-1918 2>&12010/07/27-14:29:51 [ '/bin/cat /tmp/dpnctl-get-ems-status-status-1918 2>&1' exit status = 0 ]2010/07/27-14:29:51 output of '[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/emserver.sh --test':2010/07/27-14:29:51 - - - - - - - - - - - - - - - BEGIN2010/07/27-14:29:51 INFO: Enterprise Manager Server status: down2010/07/27-14:29:51 - - - - - - - - - - - - - - - END2010/07/27-14:29:51 error return from '[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/emserver.sh --test' - exit status 22010/07/27-14:29:51 rm -f /tmp/dpnctl-get-ems-status-status-1918 /tmp/dpnctl-get-ems-status-output-19182010/07/27-14:29:51 dpnctl: INFO: EMS status - - - - - - - - - - END2010/07/27-14:29:51 dpnctl: INFO: EMS Tomcat component status - - - - - - - - -- BEGIN2010/07/27-14:29:51 (/usr/local/avamar/bin/tomcatctl status ; echo $? >/tmp/dpnctl-tomcatctl-status-status-1918) >/tmp/dpnctl-tomcatctl-status-output-1918 2>&12010/07/27-14:29:51 /bin/cat /tmp/dpnctl-tomcatctl-status-status-1918 2>&12010/07/27-14:29:51 [ '/bin/cat /tmp/dpnctl-tomcatctl-status-status-1918 2>&1' exit status = 0 ]2010/07/27-14:29:51 output of '/usr/local/avamar/bin/tomcatctl status':2010/07/27-14:29:51 - - - - - - - - - - - - - - - BEGIN2010/07/27-14:29:51 tomcatctl: INFO: Tomcat status: up.2010/07/27-14:29:51 - - - - - - - - - - - - - - - END2010/07/27-14:29:51 rm -f /tmp/dpnctl-tomcatctl-status-status-1918 /tmp/dpnctl-tomcatctl-status-output-19182010/07/27-14:29:51 dpnctl: INFO: EMS Tomcat component status - - - - - - - - -- END2010/07/27-14:29:51 dpnctl: INFO: EMS status: down.2010/07/27-14:29:51 dpnctl: INFO: [MCS is not up, so backup scheduler is not up.]2010/07/27-14:29:51 dpnctl: INFO: Backup scheduler status: down.2010/07/27-14:29:51 dpnctl: INFO: dtlt status - - - - - - - - - - BEGIN2010/07/27-14:29:51 ([ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/../lib/dpnutils/dtltctl status ; echo $? >/tmp/dpnctl-dtlt-status-status-1918) >/tmp/dpnctl-dtlt-status-output-1918 2>&12010/07/27-14:29:52 /bin/cat /tmp/dpnctl-dtlt-status-status-1918 2>&12010/07/27-14:29:52 [ '/bin/cat /tmp/dpnctl-dtlt-status-status-1918 2>&1' exit status = 0 ]2010/07/27-14:29:52 output of '[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/../lib/dpnutils/dtltctl status':2010/07/27-14:29:52 - - - - - - - - - - - - - - - BEGIN2010/07/27-14:29:52 INFO: DTLT web application status: up2010/07/27-14:29:52 dtltctl: INFO: Desktop/laptop services status: up.2010/07/27-14:29:52 - - - - - - - - - - - - - - - END2010/07/27-14:29:52 rm -f /tmp/dpnctl-dtlt-status-status-1918 /tmp/dpnctl-dtlt-status-output-19182010/07/27-14:29:52 dpnctl: INFO: dtlt status - - - - - - - - - - END2010/07/27-14:29:52 dpnctl: INFO: dtlt status: up.2010/07/27-14:29:52 dpnctl: INFO: axionfs subsystem does not appear to have been installed - no status available2010/07/27-14:29:52 avmaint sched status --avamaronly >/tmp/dpnctl-avmaint-sched-status-1918.stdout 2>/tmp/dpnctl-avmaint-sched-status-1918.stderr2010/07/27-14:29:52 [ 'avmaint sched status --avamaronly >/tmp/dpnctl-avmaint-sched-status-1918.stdout 2>/tmp/dpnctl-avmaint-sched-status-1918.stderr' exit status = 0 ]2010/07/27-14:29:52 dpnctl: INFO: standard output of preceding 'avmaint sched status' command:

Charels · Accepted Answer

As for smtp configuration, please double check if you modify correctly in mcserver.xml.

                smtpserver" />
                sender email address" />

You may try to restart mcs + ems following the command:

1. login as user admin and loaded keys with

ssh-agent bash
ssh-add ~admin/.ssh/dpnid

2. following the command to stop mcs + ems service.

emserver.sh --stop

mcserver.sh --stop

3. make sure there is no mcs and ems process running, kill the process if still exist

ps -ef | grep mcserver

ps -ef | grep emserver

4. restart the mcs and ems service, use --ignore_lock only after you have looked around and you have determined that it is safe to break the lock

emserver.sh --start (--ignore_lock)

mcserver.sh --start (--ignore_lock)

Hope above information could resolve your problem.

alfredo_SnT · Answer

Thanks Charels, I tried your command and after a second try it worked! Now everything is up and running:

/>: dpnctl status
dpnctl: INFO: gsan status: ready
dpnctl: INFO: MCS status: up.
dpnctl: INFO: EMS status: up.
dpnctl: INFO: Backup scheduler status: up.
dpnctl: INFO: dtlt status: up.
dpnctl: INFO: Maintenance windows scheduler status: enabled.
dpnctl: INFO: Maintenance cron jobs status: enabled.
dpnctl: INFO: Unattended startup status: enabled.

Cheers

Maquiavello · Answer

In some cases de Tomcat maybe its not responding, I stopped de dtlt first (just in case) then I kill all the tomcat process and then i started again the EMS and the dtlt without problems. Cya Diego.

Avamar

Was this post helpful?