Solved!
Go to SolutionRegistering client for Ubuntu
I try to register a client for Ubuntu but I have a problem, the client doesn't register and the result is:
avagent.d Info: Could not stop client agent.
Can you help me?
laboratorio@test_server:/tmp$ sudo dpkg -i AvamarClient-debian4.0-x86_64-7.2.101-32.deb
[sudo] password for laboratorio:
Seleccionando el paquete avamarclient-debian previamente no seleccionado.
(Leyendo la base de datos ... 168978 ficheros o directorios instalados actualmente.)
Preparing to unpack AvamarClient-debian4.0-x86_64-7.2.101-32.deb ...
**********************************
**********************************
Unpacking avamarclient-debian (7.2.101-32) ...
Configurando avamarclient-debian (7.2.101-32) ...
Installation complete
You may run /usr/local/avamar/bin/avregister to register and activate this client with the Administrator server.
Adding system startup for /etc/init.d/avagent ...
/etc/rc0.d/K20avagent -> ../init.d/avagent
/etc/rc1.d/K20avagent -> ../init.d/avagent
/etc/rc6.d/K20avagent -> ../init.d/avagent
/etc/rc2.d/S20avagent -> ../init.d/avagent
/etc/rc3.d/S20avagent -> ../init.d/avagent
/etc/rc4.d/S20avagent -> ../init.d/avagent
/etc/rc5.d/S20avagent -> ../init.d/avagent
avagent Info <5008>: Logging to /usr/local/avamar/var/avagent.log
avagent Info <5417>: daemonized as process id 3060
avagent.d Info: Client Agent started.
laboratorio@test_server:/tmp$
laboratorio@test_server:/tmp$ /usr/local/avamar/bin/avregister
=== Client Registration and Activation
This script will register and activate the client with the Administrator server.
Enter the Administrator server address (DNS text name or numeric IP address, DNS name preferred): 200.75.56.117
Enter the Avamar server domain [clients]: Prueba_1
avagent.d Info: Stopping Avamar Client Agent (avagent)...
avagent.d Info: Could not stop client agent.
Enter the Administrator server address (DNS text name or numeric IP address, DNS name preferred):
umichklewis
4 Apprentice
•
1190 Posts
2131
0
Posted August 22nd, 2016 06:00
It looks like the user installs the tool as root with "sudo", but I don't see an explicit sudo when running avregister. It's not likely, but possible that the sudo session had released root privileges by the time it ran. As Gauam points out, you'll need to be root to run the command. Do you get the same result when you re-run avregister?
Karl
gautamgp
226 Posts
2131
0
Posted August 21st, 2016 08:00
try registering using the root account.