This post is more than 5 years old
19 Posts
0
14767
October 10th, 2010 15:00
Backup schedular doesn,t start
Hello,
I have installed a single node avamar appliance and some how the backup schedular doesn't start. The following mesages appears when I run dpnctl start sched.
ERROR: error return from "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mccli mcs resume-scheduler --mc saddr='10.74.1.97' --mcsuserid=root --mcspasswd='*******'" - exit status 1
dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]
Does any one knows what the problem is?
Thanks in advance
Hans
0 events found
No Events found!
Charels
39 Posts
0
November 2nd, 2010 16:00
The problem may caused
1. MCS entry in one or all of the following files is missing or incomplete:
/root/.avamardata/var/mc/cli_data/prefs/mcclimcs.xml
/home/dpn/.avamardata/var/mc/cli_data/prefs/mcclimcs.xml
/home/admin/.avamardata/var/mc/cli_data/prefs/mcclimcs.xml
2. Garbled characters in above xml configuration files.
Resolution for this issue
1. Add/complete the MCS entry and start the scheduler.
example:
2. Check the garbled characters and fix them in those xml files and start the scheduler.
Hope this could resolve your problem.
Regards,
Charles
chrisvemc
50 Posts
0
October 10th, 2010 16:00
Is this a new install?
Has it ever started ok before?
Have you checked what is contained in the dpnctl.log file?
What user are you using to start sched?
Where there any changes made to ths system?
Whats the entire output for dpnctl status?
chrisvemc
50 Posts
0
October 10th, 2010 16:00
Please run dpnctl status and paste the output.
Please try re-running dpnctl start sched.
In another window please tail the dpnctl.log file by doing the following and paste the output:
dodo01
19 Posts
0
October 11th, 2010 01:00
Hello,
Hereby the output of the commands. I have migrate the node to an another subnet. Because that’s a pretty straight forward procedure I doubt that’s causing the problem. Despite that I am not sure the problem exist before the migration. Unfortunately I didn’t check that before the IP migration.
I hope this logs gives some understanding
admin@eurbackup1:/root/#: dpnctl status
Identity added: /home/admin/.ssh/dpnid (/home/admin/.ssh/dpnid)
dpnctl: INFO: gsan status: ready
dpnctl: INFO: MCS status: up.
dpnctl: INFO: EMS status: up.
dpnctl: INFO: Backup scheduler status: down.
dpnctl: INFO: dtlt status: down.
dpnctl: INFO: Maintenance windows scheduler status: enabled.
dpnctl: INFO: Maintenance cron jobs status: suspended.
dpnctl: INFO: Unattended startup status: enabled.
dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]
admin@eurbackup1:/root/#:
admin@eurbackup1:/root/#: dpnctl start sched
Identity added: /home/admin/.ssh/dpnid (/home/admin/.ssh/dpnid)
dpnctl: INFO: Resuming backup scheduler...
dpnctl: ERROR: error return from "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mccli mcs resume-scheduler --mcsaddr='10.74.1.97' --mcsuserid=root --mcspasswd='*******'" - exit status 1
dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]
tail -20 /usr/local/avamar/var/log/dpnctl.log
2010/10/11-07:55:04 rm -f /tmp/dpnctl-schedule-restart-status-19356 /tmp/dpnctl-schedule-restart- output-19356
2010/10/11-07:55:04 dpnctl: INFO: Scheduler status - - - - - - - - - - END
2010/10/11-07:55:04 dpnctl: INFO: Resuming backup scheduler...
2010/10/11-07:55:04 ( && . /etc/profile ; /usr/local/avamar/bin/mccli mcs resume-scheduler --mcsaddr='10.74.1.97' --mcsuserid=root --mcspasswd='*******' ; echo $? >/tmp/dpnctl -schedule-restart-status-19356) >/tmp/dpnctl-schedule-restart-output-19356 2>&1
2010/10/11-07:55:05 /bin/cat /tmp/dpnctl-schedule-restart-status-19356 2>&1
2010/10/11-07:55:05 [ "/bin/cat /tmp/dpnctl-schedule-restart-status-19356 2>&1" exit status = 0 ]
2010/10/11-07:55:05 output of "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mccli mcs resume-scheduler --mcsaddr='10.74.1.97' --mcsuserid=root --mcspasswd='*******'":
2010/10/11-07:55:05 - - - - - - - - - - - - - - - BEGIN
2010/10/11-07:55:05 :26:3: Element type "MCS" must be followed by either attribute specifications, ">" or "/>".
2010/10/11-07:55:05 exception: org.xml.sax.SAXParseException: Element type "MCS" must be followed by either attribute specifications, ">" or "/>".
2010/10/11-07:55:05 Failure to initialize the CLI ...exiting
2010/10/11-07:55:05 - - - - - - - - - - - - - - - END
2010/10/11-07:55:05 dpnctl: ERROR: error return from "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mccli mcs resume-scheduler --mcsaddr='10.74.1.97' --mcsuserid=root --mcspasswd ='*******'" - exit status 1
2010/10/11-07:55:05 rm -f /tmp/dpnctl-schedule-restart-status-19356 /tmp/dpnctl-schedule-restart-output-19356
2010/10/11-07:55:05 dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]
2010/10/11-07:55:05 rm -f /usr/local/avamar/var/dpnctl.lck
2010/10/11-07:55:05 ======= dpnctl 5.0.2-41 (1.112.2.2), running as admin, RETURNING at 2010-10-11 09:55:05 CEST =======
2010/10/11-07:55:05 [user "admin"] program (pid 19356) exit status = 2 (error)
2010/10/11-07:55:05 ======= dpnctl 5.0.2-41 (1.112.2.2), running as admin, ENDING at 2010-10-11 09:55:05 CEST =======
2010/10/11-07:55:05 [user "admin"] program (pid 19265) exit status = 2 (error)
admin@eurbackup1:~/>: tail -20 /usr/local/avamar/var/log/dpnctl.log
2010/10/11-07:55:04 rm -f /tmp/dpnctl-schedule-restart-status-19356 /tmp/dpnctl-schedule-restart-output-19356
2010/10/11-07:55:04 dpnctl: INFO: Scheduler status - - - - - - - - - - END
2010/10/11-07:55:04 dpnctl: INFO: Resuming backup scheduler...
2010/10/11-07:55:04 ( && . /etc/profile ; /usr/local/avamar/bin/mccli mcs resume-scheduler --mcsaddr='10.74.1.97 ' --mcsuserid=root --mcspasswd='*******' ; echo $? >/tmp/dpnctl-schedule-restart-status-19356) >/tmp/dpnctl-schedule-restart-output -19356 2>&1
2010/10/11-07:55:05 /bin/cat /tmp/dpnctl-schedule-restart-status-19356 2>&1
2010/10/11-07:55:05 [ "/bin/cat /tmp/dpnctl-schedule-restart-status-19356 2>&1" exit status = 0 ]
2010/10/11-07:55:05 output of "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mccli mcs resume-scheduler --mcsaddr='10.74.1.97' --mcsuserid=root --mcspasswd='*******'":
2010/10/11-07:55:05 - - - - - - - - - - - - - - - BEGIN
2010/10/11-07:55:05 :26:3: Element type "MCS" must be followed by either attribute specifications, ">" or "/>".
2010/10/11-07:55:05 exception: org.xml.sax.SAXParseException: Element type "MCS" must be followed by either attribute specifications, ">" or "/>".
2010/10/11-07:55:05 Failure to initialize the CLI ...exiting
2010/10/11-07:55:05 - - - - - - - - - - - - - - - END
2010/10/11-07:55:05 dpnctl: ERROR: error return from "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mccli mcs resume-scheduler --mcsaddr='10.74.1.97' --mcsuserid=root --mcspasswd='*******'" - exit status 1
2010/10/11-07:55:05 rm -f /tmp/dpnctl-schedule-restart-status-19356 /tmp/dpnctl-schedule-restart-output-19356
2010/10/11-07:55:05 dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]
2010/10/11-07:55:05 rm -f /usr/local/avamar/var/dpnctl.lck
2010/10/11-07:55:05 ======= dpnctl 5.0.2-41 (1.112.2.2), running as admin, RETURNING at 2010-10-11 09:55:05 CEST =======
2010/10/11-07:55:05 [user "admin"] program (pid 19356) exit status = 2 (error)
2010/10/11-07:55:05 ======= dpnctl 5.0.2-41 (1.112.2.2), running as admin, ENDING at 2010-10-11 09:55:05 CEST =======
2010/10/11-07:55:05 [user "admin"] program (pid 19265) exit status = 2 (error)
chrisvemc
50 Posts
0
October 11th, 2010 16:00
I dont understand a portion of the log, is this a copy paste error? or is this from the log itself?
2010/10/11-07:55:04 (https://community.emc.com/message/505912#505912/ -r /etc/profile && . /etc/profile ; /usr/local/avamar/bin/mccli mcs resume-scheduler --mcsaddr='10.74.1.97' --mcsuserid=root --mcspasswd='*******' ; echo $? >/tmp/dpnctl -schedule-restart-status-19356) >/tmp/dpnctl-schedule-restart-output-19356 2>&1
You migrated from another subnet to another. There is a proper and documented way of doing this, did you follow the documentation?
I also noticed that in your previous reply, you mentioned the following:
"...Despite that I am not sure the problem exist before the migration. Unfortunately I didn’t check that before the IP migration...."
Are you saying that you did not even know what the state of the Avamar server was, whether it was working and online? Even then you should have at least created and validated a checkpoint before making any changes to your system.
Is there any data on the Avamar system? Im guessing the answer "no" since there were no steps taken to ensure that the avamar system had a valid checkpoint. And if this is the case I am also assuming that it would be ok to rebuild the avamar server and if so, I suggest re-initializing the avamar installation i.e. clean the system and re-install avamar.
If it has come down to reinstalling Avamar for the nth time, I suggest that you consider contacting support or an implementation specialist to do the re-installation.