Skip to main content

Linux Agent Problem

Thread needs solution

Hi there...

New to Acronis solution and trying to get Linux agent working.

The agent installed just fine and was able to register with the backup server itself (Windows). When I schedule a backup though I get errors that it wasn't able to communicate. Port 9876/TCP is open on the linux agent - Windows server has no firewall at the moment.

Logs show below from the email report. Not sure how to resolve this?

1 Information 12/31/13 12:00:01 AM Command 'Running backup plan 'Daily Backup'' is running.
2 Information 12/31/13 12:00:01 AM Found GRUB stage 2.
3 Information 12/31/13 12:00:01 AM Searching for stage 2 file 'stage2'.
4 Information 12/31/13 12:00:01 AM Detected GRUB stage 2 loader on disk '\local\hd_sign(000A079F)'. Activated on volume '\local\hd_sign(000A079F)\part_sn(A296F475EB458BE4BE5BF1A98D3A0087)start(2048)'.
5 Information 12/31/13 12:00:02 AM Command 'Backing up' is running.
6 Information 12/31/13 12:00:02 AM Found GRUB stage 2.
7 Information 12/31/13 12:00:02 AM Searching for stage 2 file 'stage2'.
8 Information 12/31/13 12:00:02 AM Detected GRUB stage 2 loader on disk '\local\hd_sign(000A079F)'. Activated on volume '\local\hd_sign(000A079F)\part_sn(A296F475EB458BE4BE5BF1A98D3A0087)start(2048)'.
9 Information 12/31/13 12:00:02 AM Found GRUB stage 2.
10 Information 12/31/13 12:00:02 AM Searching for stage 2 file 'stage2'.
11 Information 12/31/13 12:00:02 AM Detected GRUB stage 2 loader on disk '\local\hd_sign(000A079F)'. Activated on volume '\local\hd_sign(000A079F)\part_sn(A296F475EB458BE4BE5BF1A98D3A0087)start(2048)'.
12 Information 12/31/13 12:00:04 AM Failed to connect to the storage node.
Additional info:
--------------------
Error code: 17
Module: 161
LineInfo: cbaf98c283a3b136
Fields: host : acronis, $module : disk_bundle_lxa64_pic_38350
Message: Failed to connect to the storage node.
--------------------
Error code: 3
Module: 173
LineInfo: 67e2725e54112c8e
Fields: $module : disk_bundle_lxa64_pic_38350
Message:
--------------------
Error code: 17
Module: 173
LineInfo: 1c13eceb383289b2
Fields: ServiceID : 34, $module : service_process_lxa64_38350
Message: Failed to connect to service 'ASN'. Destination host 'acronis' is unreachable or a firewall may be blocking the connection.
--------------------
13 Error 12/31/13 12:00:04 AM Command 'Backing up' has failed.
Additional info:
--------------------
Error code: 61
Module: 309
LineInfo: 4a8728dc8a1c950f
Fields: $module : service_process_lxa64_38350
Message: Command 'Backing up' has failed.
--------------------
Error code: 200
Module: 161
LineInfo: b320396adfe3b55
Fields: IsReturnCode : 1, $module : disk_bundle_lxa64_pic_38350
Message: Failed to get archive URIs from location 'arl:/A01259EA-2FE6-44FB-94D5-CC1F2AA65DAA/CCB04930-BEF8-42A2-9926-EAECAD678499'.
--------------------
Error code: 17
Module: 161
LineInfo: cbaf98c283a3b136
Fields: host : acronis, $module : disk_bundle_lxa64_pic_38350
Message: Failed to connect to the storage node.
--------------------
Error code: 3
Module: 173
LineInfo: 67e2725e54112c8e
Fields: $module : disk_bundle_lxa64_pic_38350
Message:
--------------------
Error code: 17
Module: 173
LineInfo: 1c13eceb383289b2
Fields: ServiceID : 34, $module : service_process_lxa64_38350
Message: Failed to connect to service 'ASN'. Destination host 'acronis' is unreachable or a firewall may be blocking the connection.
--------------------
Task 'Level 6 backup' has failed on machine 'xxxxxxxxxxxxxxxxxxx'.

0 Users found this helpful

According to this log, agent tries to connect to the storage node (to store backup there) by hostname and fails. Does it ping by its name from the this linux machine?

Fedor Larin wrote:

According to this log, agent tries to connect to the storage node (to store backup there) by hostname and fails. Does it ping by its name from the this linux machine?

Thank you - no, it won't ping by that hostname. When I installed the agent I used an IP address specifically to avoid DNS problems. Is there a conf file in the agent I can modify this information with to avoid this problem?

If this 'acronis' machine with Storage Node has static IP you can just add it to hosts file on the linux machine. I'm not sure if it's possible to force the storage node to appear by its IP on Management Server (so that it deploy Storage Node address to agents as IP too)

Fedor Larin wrote:

If this 'acronis' machine with Storage Node has static IP you can just add it to hosts file on the linux machine. I'm not sure if it's possible to force the storage node to appear by its IP on Management Server (so that it deploy Storage Node address to agents as IP too)

Thanks - I realized we were going to run into a number of issues here so did some more digging and found this:

http://kb.acronis.com/content/42047

This was the solution to our problem - works great now :)

Paul