Linux agent ports

Backup agent for Linux servers and workstations on-premises or in the public cloud

Linux agent ports

Veeam Logoby mpiet » Tue Apr 25, 2017 2:28 pm

We're trying to evaluate if the linux agent will work with our current licensed windows veeam backup server, however I cannot successfully get any linux backup agent to complete a job. It appears to create both a job ID and backup ID, the job populates on the server, but never successfully runs anything. It complains about not being able to find a backup ID and not able to write to socket.

Are there more ports that should be opened apart from 10002?
mpiet
Novice
 
Posts: 3
Liked: never
Joined: Tue Apr 25, 2017 2:12 pm

Re: Linux agent ports

Veeam Logoby PTide » Tue Apr 25, 2017 3:19 pm

Hi,

Please provide the exact error message that you get, and briefly describe your setup (repo, host, backup server locations, networks etc). Please also check this list of required ports.

Thank you
PTide
Veeam Software
 
Posts: 2884
Liked: 236 times
Joined: Tue May 19, 2015 1:46 pm

Re: Linux agent ports

Veeam Logoby mpiet » Tue Apr 25, 2017 4:51 pm

Ports 2500-5000 have an IPTABLES rule to allow forward traffic between devices, as well as a rule for 10002 for the backup agent.

Setup:
Linux Agent: Centos 6 2.6.32-642.6.2.el6.x86_64
Code: Select all
yum list installed |grep veeam
veeam.x86_64                    1.0.0.944-1.el6         @veeam                 
veeam-release-el6.x86_64        1.0-1                   @/veeam-release-el6-1.0-1.x86_64
veeamsnap.noarch                1.0.0.944-1             @veeam


Backup Host: Windows 2016
Veeam Backup & Replication 9.5.0.853

Error messages consist of;
~ veeamsvc.log
Code: Select all
[25.04.2017 12:48:27] <139720008906496> cli    |   TCP/IP send cache is not empty and will be cleared in destructor.
[25.04.2017 12:48:27] <139720008906496>        | ERR |write: Broken pipe
[25.04.2017 12:48:27] <139720008906496>        | >>  |--tr:Cannot write data to the socket. Data size: [21168].
[25.04.2017 12:48:27] <139720008906496>        |   Closing socket device.
[25.04.2017 12:48:27] <139720008906496> lpbcore| Starting proxystub protocol dispatch loop. ok.
[25.04.2017 12:48:27] <139720008906496>        | Closing socket device.
[25.04.2017 12:48:27] <139720008906496>        | Thread finished. Role: 'peer 127.0.0.1:50526'.
[25.04.2017 12:48:27] <139719203600128> lpbcore| Manager process [77118] has been shutdown.
[25.04.2017 12:48:27] <139719203600128>        | Thread finished. Role: 'Manager process [77118] shutdown handler.'.
[25.04.2017 12:48:27] <139720040376064> lpbcore| Cleaning up resources for job process [77118].
[25.04.2017 12:48:27] <139719224579840> lpbcore| ERR |Backup job has failed.
[25.04.2017 12:48:27] <139719224579840> lpbcore| >>  |read: Connection reset by peer
[25.04.2017 12:48:27] <139719224579840> lpbcore| >>  |--tr:Cannot read data from the socket. Requested data size: [4].
[25.04.2017 12:48:27] <139719224579840> lpbcore| >>  |--tr:Unable send command to backup server [{e9649de5-b805-4ee4-8c56-3729a980f61f}]
[25.04.2017 12:48:27] <139719224579840> lpbcore| >>  |--tr:Failed to execute method [0] for class [N10lpbcorelib11interaction9proxystub14CVbrClientStubE].
[25.04.2017 12:48:27] <139719224579840> lpbcore| >>  |--tr:Failed to start agent process on target repository.
[25.04.2017 12:48:27] <139719224579840> lpbcore| >>  |Backup job has failed.
[25.04.2017 12:48:27] <139719224579840> lpbcore| >>  |An exception was thrown from thread [139720008906496].
[25.04.2017 12:48:27] <139719224579840> lpbcore| Retry is disabled. Attempts counter '3', isRetriable flag 'false'.
[25.04.2017 12:48:27] <139719224579840>        | Thread finished. Role: 'backup job retry handler'.
[25.04.2017 12:48:27] <139720029886208>        | Closing socket device.
[25.04.2017 12:48:33] <139719595165440> lpbcore| Starting proxystub protocol dispatch loop. ok.
[25.04.2017 12:48:33] <139719595165440>        | Closing socket device.
[25.04.2017 12:48:33] <139719595165440>        | Thread finished. Role: 'peer 127.0.0.1:50516'.
[25.04.2017 12:48:33] <139719214089984> lpbcore| LpbCfgSession: Tcp loop. Failed.
[25.04.2017 12:48:33] <139719214089984> lpbcore| ERR |LpbCfgSession failed.
[25.04.2017 12:48:33] <139719214089984> lpbcore| >>  |read: End of file
[25.04.2017 12:48:33] <139719214089984> lpbcore| >>  |--tr:Cannot read data from the socket. Requested data size: [4].
[25.04.2017 12:48:33] <139719214089984> lpbcore| >>  |An exception was thrown from thread [139719214089984].
[25.04.2017 12:48:33] <139719214089984>        | Closing socket device.
[25.04.2017 12:48:33] <139719214089984>        | Thread finished. Role: '(async) LPBConfig session (127.0.0.1:50518)'.


~ Job.log
Code: Select all
[25.04.2017 12:48:27] <140620618688352> lpbcore| ERR |write: Broken pipe
[25.04.2017 12:48:27] <140620618688352> lpbcore| >>  |--tr:Cannot write data to the socket. Data size: [19609].
[25.04.2017 12:48:27] <140620618688352> lpbcore| >>  |--tr:Unable send command to backup server [{e9649de5-b805-4ee4-8c56-3729a980f61f}]
[25.04.2017 12:48:27] <140620618688352> lpbcore| >>  |--tr:Failed to execute method [0] for class [N10lpbcorelib11interaction9proxystub14CVbrClientStubE].
[25.04.2017 12:48:27] <140620618688352> lpbcore| >>  |--tr:Failed to notify VBR resource scheduler about job finish.
[25.04.2017 12:48:27] <140620618688352> lpbcore| >>  |An exception was thrown from thread [140620618688352].
[25.04.2017 12:48:27] <140620568073984>        | Thread finished. Role: 'lease keeper'.
[25.04.2017 12:48:27] <140620618688352> lpbcore| WARN|Method invocation was not finalized. Method id [0]. Class: [N10lpbcorelib11interaction10IVbrClientE]
[25.04.2017 12:48:27] <140620618688352> lpbcore| ERR |write: Broken pipe
[25.04.2017 12:48:27] <140620618688352> lpbcore| >>  |--tr:Cannot write data to the socket. Data size: [20309].
[25.04.2017 12:48:27] <140620618688352> lpbcore| >>  |--tr:Unable send command to backup server [{e9649de5-b805-4ee4-8c56-3729a980f61f}]
[25.04.2017 12:48:27] <140620618688352> lpbcore| >>  |--tr:Failed to execute method [0] for class [N10lpbcorelib11interaction9proxystub14CVbrClientStubE].
[25.04.2017 12:48:27] <140620618688352> lpbcore| >>  |--tr:Failed to invoke method [0] in class [N10lpbcorelib11interaction10IVbrClientE].
[25.04.2017 12:48:27] <140620618688352> lpbcore| >>  |An exception was thrown from thread [140620618688352].
[25.04.2017 12:48:27] <140620618688352> lpbcore| ERR |Failed to destroy lease keeper for lease {f2c50c07-6ee5-41b4-9bfd-c747398b9513}.
[25.04.2017 12:48:27] <140620618688352> lpbcore| >>  |write: Broken pipe
[25.04.2017 12:48:27] <140620618688352> lpbcore| >>  |--tr:Cannot write data to the socket. Data size: [20309].
[25.04.2017 12:48:27] <140620618688352> lpbcore| >>  |--tr:Unable send command to backup server [{e9649de5-b805-4ee4-8c56-3729a980f61f}]
[25.04.2017 12:48:27] <140620618688352> lpbcore| >>  |--tr:Failed to execute method [0] for class [N10lpbcorelib11interaction9proxystub14CVbrClientStubE].
[25.04.2017 12:48:27] <140620618688352> lpbcore| >>  |--tr:Unable to destroy lease on VBR server.
[25.04.2017 12:48:27] <140620618688352> lpbcore| >>  |An exception was thrown from thread [140620618688352].
[25.04.2017 12:48:27] <140620618688352> lpbcore| [DEV] Destroyed [0x3357f40]
[25.04.2017 12:48:27] <140620618688352> lpbman | ERR |Main thread has failed.
[25.04.2017 12:48:27] <140620618688352> lpbman | >>  |write: Broken pipe
[25.04.2017 12:48:27] <140620618688352> lpbman | >>  |--tr:Cannot write data to the socket. Data size: [18777].
[25.04.2017 12:48:27] <140620618688352> lpbman | >>  |--tr:Unable send command to backup server [{e9649de5-b805-4ee4-8c56-3729a980f61f}]
[25.04.2017 12:48:27] <140620618688352> lpbman | >>  |--tr:Failed to execute method [0] for class [N10lpbcorelib11interaction9proxystub14CVbrClientStubE].
[25.04.2017 12:48:27] <140620618688352> lpbman | >>  |--tr:Failed to notify VBR server (task finished).
[25.04.2017 12:48:27] <140620618688352> lpbman | >>  |An exception was thrown from thread [140620618688352].
[25.04.2017 12:48:27] <140620618688352> lpbman | Application session has been finished.



Initially i had some issues getting the install to work correctly due to some of the intricacies for the package dependencies, however I was able to configure a job in my test lab pointing to a simple CIFS share. It appears to be authenticating properly as shown in the logs and from the Backup client on the Windows server, however that is as far as I have been able to get.
mpiet
Novice
 
Posts: 3
Liked: never
Joined: Tue Apr 25, 2017 2:12 pm

Re: Linux agent ports

Veeam Logoby PTide » Tue Apr 25, 2017 5:29 pm

Please contact our support team directly and post your case ID.
PTide
Veeam Software
 
Posts: 2884
Liked: 236 times
Joined: Tue May 19, 2015 1:46 pm

Re: Linux agent ports

Veeam Logoby mpiet » Tue Apr 25, 2017 6:36 pm

Case created; ID#02137950
mpiet
Novice
 
Posts: 3
Liked: never
Joined: Tue Apr 25, 2017 2:12 pm


Return to Veeam Agent for Linux



Who is online

Users browsing this forum: Google [Bot] and 2 guests