/build/static/layout/Breadcrumb_cap_w.png

Agent provisioning failed on Ubuntu 12.04

Hi guys, I tried to put agent to Ubuntu 12.04 and agent is infact installed, but provisioning fails. I've copied the output so maybe someone can explain why is this happening...

[06/12/14 02:30:48 PM] Begin provisioning...

  [06/12/14 02:30:48 PM] Executing Unix platform provisioning. 

  [06/12/14 02:30:48 PM] Probing tcp ports for accessibility. 

  [06/12/14 02:30:48 PM] Port 22 [ssh] open. 


  STEP 1: CONNECT TCP/SSH - SUCCESSFUL



  STEP 2: AUTHENTICATION - SUCCESSFUL


  [06/12/14 02:30:53 PM] Target is ubuntu-x86_64. 

  [06/12/14 02:31:04 PM] K1000 agent NOT detected via ssh query. 

  [06/12/14 02:31:04 PM] Attempting remote agent installation. 

  [06/12/14 02:31:04 PM] Copying K1000 agent installer./kbox/samba/client/agent_provisioning/linux_platform/ampagent-6.0.1079.ubuntu.64.deb 

  [06/12/14 02:31:10 PM] Running K1000 agent installer. 

  [06/12/14 02:31:10 PM] Setting K1000 server to k1000novi.ipkomunikacije.local. 


    Selecting previously unselected package ampagent.

    (Reading database ...

    dpkg: warning: files list file for package `ttf-mscorefonts-installer' missing, assuming package has no files currently installed.

    174099 files and directories currently installed.)

    Unpacking ampagent (from /tmp/kboxagent.deb) ...

    Setting up ampagent (6.0.1079-1) ...

     Adding system startup for /etc/init.d/AMPctl ...

     /etc/rc0.d/K02AMPctl -> ../init.d/AMPctl

     /etc/rc1.d/K02AMPctl -> ../init.d/AMPctl

     /etc/rc6.d/K02AMPctl -> ../init.d/AMPctl

     /etc/rc2.d/S98AMPctl -> ../init.d/AMPctl

     /etc/rc3.d/S98AMPctl -> ../init.d/AMPctl

     /etc/rc4.d/S98AMPctl -> ../init.d/AMPctl

     /etc/rc5.d/S98AMPctl -> ../init.d/AMPctl


  [06/12/14 02:31:16 PM] Verifying installation. 


  STEP 3: PUSH SCRIPT\PROVISIONING - FAILED


  [06/12/14 02:31:21 PM] K1000 agent detected via ssh query. 

  [06/12/14 02:31:27 PM] Version is 6.0.1079. 

  [06/12/14 02:31:32 PM] K1000 agent KUID: ad2ec4de63c04f758c87eec27704b818 

  [06/12/14 02:31:37 PM] K1000 agent NOT connected via AMP. 

  [06/12/14 02:31:37 PM] End provisioning run.

0 Comments   [ + ] Show comments

Answers (3)

Answer Summary:
Posted by: dlistar 6 years ago
Second Degree Blue Belt
1
Thank you everyone for helping me, you're the best. I've found solution and want to share it with you. I don't know if this is the best fix but it helped me so...

I wasn't able to ping my FQDN of my DNS server so I changed a line in /etc/nsswitch.conf like in this article here:

http://longerthan5.blogspot.com/2008/05/help-i-cant-ping-fqdns-in-ubuntu.html

and the the provisioning succeeded. Hope it helps
Posted by: AbhayR 6 years ago
Red Belt
0
Agent provisioning failed as there was a warning of a missing font package during the agent installation step. Since, this was a warning and not an error, agent got installed. Also, agent is not dependent on this package, this package files seems to be missing from the OS which is causing this warning. Please check this http://ubuntuforums.org/showthread.php?t=1989709

Are you able to see the inventory record of this ubuntu machine on your K1 ? If yes, then everything should be fine.

Comments:
  • I've reinstalled that package files but still agent provisioning failed...My Ubuntu OS is a virtual machine...
    I don't see inventory record in Devices Inventory tab... any other recommendations?
    Provisioning output is below:

    STEP 1: CONNECT TCP/SSH - SUCCESSFUL

    STEP 2: AUTHENTICATION - SUCCESSFUL

    [06/16/14 12:08:50 PM] Target is ubuntu-x86_64.

    [06/16/14 12:09:01 PM] K1000 agent NOT detected via ssh query.

    [06/16/14 12:09:01 PM] Attempting remote agent installation.

    [06/16/14 12:09:01 PM] Copying K1000 agent installer./kbox/samba/client/agent_provisioning/linux_platform/ampagent-6.0.1079.ubuntu.64.deb

    [06/16/14 12:09:07 PM] Running K1000 agent installer.

    [06/16/14 12:09:07 PM] Setting K1000 server to k1000novi.ipkomunikacije.local.


    Selecting previously unselected package ampagent.

    (Reading database ... 202236 files and directories currently installed.)

    Unpacking ampagent (from /tmp/kboxagent.deb) ...

    Setting up ampagent (6.0.1079-1) ...

    Adding system startup for /etc/init.d/AMPctl ...

    /etc/rc0.d/K02AMPctl -> ../init.d/AMPctl

    /etc/rc1.d/K02AMPctl -> ../init.d/AMPctl

    /etc/rc6.d/K02AMPctl -> ../init.d/AMPctl

    /etc/rc2.d/S98AMPctl -> ../init.d/AMPctl

    /etc/rc3.d/S98AMPctl -> ../init.d/AMPctl

    /etc/rc4.d/S98AMPctl -> ../init.d/AMPctl

    /etc/rc5.d/S98AMPctl -> ../init.d/AMPctl


    [06/16/14 12:09:13 PM] Verifying installation.


    STEP 3: PUSH SCRIPT\PROVISIONING - FAILED


    [06/16/14 12:09:19 PM] K1000 agent detected via ssh query.

    [06/16/14 12:09:24 PM] Version is 6.0.1079.

    [06/16/14 12:09:30 PM] K1000 agent KUID: ad2ec4de63c04f758c87eec27704b818

    [06/16/14 12:09:35 PM] K1000 agent NOT connected via AMP.

    [06/16/14 12:09:35 PM] End provisioning run. - dlistar 6 years ago
  • I cannot ping k1000 hostname from Ubuntu VM...also, it's not joined to the domain... is that a problem? - dlistar 6 years ago
    • Did you verify the virtual network setting are set to bridge and not NAT or HOST only? - dedenker 6 years ago
      • I don't have that option enabled in my VMWare...i think its only test environment so its not fully licensed...also, some guy before me has set up that environment...
        I've joined that VM to my domain and tried with k1000 5.5 ver and same issuse happend... - dlistar 6 years ago
Posted by: dedenker 6 years ago
3rd Degree Black Belt
0
Reading the last comment(s) from dlistar.
The problem is with network settings.
Please first make sure you can ping the server.
With VMware (workstation or Player) you can double click the network icon to change this virtual machine connection settings.
Set that to bridged.


Comments:
  • I'm using ESXi 5.1.0 hypervisor and vSphere client... so there isn't any option for bridging...or I simply can't find it...probably there is a different way of making bridged connection... I agree that the problem is because I can't ping k1000 hostname... :/ hmmm,I'll try to find some tutorial about bridging esxi... - dlistar 6 years ago
    • aha :) you do not have the right I guest. Ask you ESXi admin - dedenker 6 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ