1832087 Members
3047 Online
110037 Solutions
New Discussion

Re: swagentd problem

 
Dario_4
Frequent Advisor

swagentd problem

Hello,
I have a problem with swagentd daemon.
When the machine comings up, I see in boot messages:

Initialize software distributor agent daemon ...
(and after 12 minutes, I see) FAIL*

What does it means?
This machine is a clone, created with ignite-ux. Alls works fine, but at each boot, I must wait 12 minutes for this thing. How to solve it?

Thanks in advance
9 REPLIES 9

Re: swagentd problem

Take a look at these log files:

/etc/rc.log

/var/adm/swagentd.log

HTH

Duncan

I am an HPE Employee
Accept or Kudo
Helen French
Honored Contributor

Re: swagentd problem

Hi Dario:

You need to check two log files to find out more information about the error and post any further information, if required:

/var/adm/sw/swagentd.log
/etc/rc.log

HTH,
Shiju
Life is a promise, fulfill it!
David Burgess
Esteemed Contributor

Re: swagentd problem

Hi,

Look for an error in the following files :-

/etc/rc.log
/var/adm/swagentd.log

Regards,

Dave.
Dario_4
Frequent Advisor

Re: swagentd problem

Sorry,
i forget the log files.

The output of rc.log is:

Initialize Software Distributor agent daemon
Output from "/sbin/rc2.d/S870swagentd start":
----------------------------
Running /usr/lib/sw/mx/configure to reset hostname.
ERROR: Failed to package AgentConfig into /var/opt/mx/depot11.
cat: Cannot open /var/tmp/swpackage11.log.1327: No such file or directory
ERROR: Failed to package AgentConfig into /var/opt/mx/depot10.
cat: Cannot open /var/tmp/swpackage10.log.1327: No such file or directory
WARNING: Could not properly configure SD into ServiceControl.
You may try again later by running /usr/lib/sw/mx/configure.
"/sbin/rc2.d/S870swagentd start" FAILED

Set/update sched.models
Output from "/sbin/rc2.d/S888schedmodel start":
-----------------------------
James R. Ferguson
Acclaimed Contributor

Re: swagentd problem

Hi Dario:

You indicated that this was a cloned (via Ignite) server. Have a look at '/var/adm/sw/security/_OWNER'. If the hostname represented by the entry 'default_realm=' isn't correct, try changing it and restarting the 'swagentd' daemon:

# swagentd -r

Regards!

...JRF...
Dario_4
Frequent Advisor

Re: swagentd problem

Well,
# default_realm=CLN01
num_entries=2
user:root:0
group:sys:0

This is my _OWNER file.
Can i try uncomment #default and restart the machine?
Helen French
Honored Contributor

Re: swagentd problem

Hi Dario:

1) If you are using 11.11, then try applying the patch - PHCO_25887 (s700_800 11.11 Software Distributor Cumulative Patch)

2) If you are using the Service Control Manager, then you may need to reconfigre it. If you are not using that product, then remove it from the system using 'swremove'

HTH,
Shiju
Life is a promise, fulfill it!
MANOJ SRIVASTAVA
Honored Contributor

Re: swagentd problem

Hi Dario


Can you run SAM properly ?


Manoj Srivastava
S.K. Chan
Honored Contributor

Re: swagentd problem

The problem lies in your SCM package. There are alot of dependencies on how the hostname is resolved in SCM and the OS itself, both must match. For example ../var/opt/mx/agent/agent.properties which has all the SCM nodes hostname must be able to be resolved by your system. Check if these entries can be resolved and other files that might have similar entries need to be checked as well. The swagentd startup will hang and eventually timeout if it could resolve any hosts defined in SCM.