1833792 Members
2651 Online
110063 Solutions
New Discussion

signal 11 swagentd.log

 
Gerrit_1
Advisor

signal 11 swagentd.log

Hi,
does anybody know what this messages means in
the swagentd.log?
"
WARNING: The ACL stored in file "//var/adm/sw/products/ifiles/_OWNER"
contains hostname(s) which could not be resolved.
* Agent pid=3643 died from signal 11. See signal(5) for more
information about this signal. 03/26/04 11:23:09 MET
"

When trying to swinstall :
wroot/sv00138#swinstall -s /softdist/SD_TEST_DEPOT SYS_EMERG_FVS @ ds39911
outout:
ERROR: RPC exception: "Connection closed (dce / rpc)" 03/26/04
11:23:09 MET
ERROR: Could not perform the requested operation for "ds39911:/",
possibly due to a network communications failure or the agent
timing out. Check that the host is still accessible from the
network, and the agent_timeout_minutes option is not set too
low.
* The execution phase failed for "ds39911:/".
* Execution had errors.

Any ideas?
Tx
I have a vision...... a television
8 REPLIES 8
Fabio Ettore
Honored Contributor

Re: signal 11 swagentd.log

Hi again Gerrit,

what about hostname resolutions?

# nslookup
# nslookup
# ifconfig lan0 (or what it is in netconf)
# cat /etc/hosts

and check that all is ok.
If there is some problems with resolutions then definitely it could be a possible reason of your problem.

Best regards,
Ettore
WISH? IMPROVEMENT!
Sanjay Kumar Suri
Honored Contributor

Re: signal 11 swagentd.log

1. Check if host is defined in /etc/hosts.
2. swagentd is running on both the hosts.
3. Are you able to connect to networked depot?

sks
A rigid mind is very sure, but often wrong. A flexible mind is generally unsure, but often right.
Gerrit_1
Advisor

Re: signal 11 swagentd.log

I'm having this problem only with this
specific product.

All the checks mentioned above are ok.

Gerrit
I have a vision...... a television
Robert Binkhorst
Trusted Contributor

Re: signal 11 swagentd.log

Hi Gerrit,

I've seen this happen when I changed ip's or hostnames of machines. A restart of the swagentd on the host this happened would set this straight. swagentd can cache these names though, so you might want to restart the client side as well if your depot server changed names/ips.

Robert-Jan: Your link doesn't work for me, is that me or is something wrong with it?

HTH,

Robert
linux: the choice of a GNU generation
Robert-Jan Goossens
Honored Contributor

Re: signal 11 swagentd.log

------

Your system will respond to the old host name until you change
two files under /var/adm/sw/products/ifiles: _OWNER and _ACL.

_OWNER looks like this:

# default_realm=
num_entries=2
user:root:00
group:sys:00

_ACL looks like this:

# default_realm=
user_obj:rwict
group:swadm:rwict
any_other:r---t

These files reflect your old hostname. Once you change the names
in these files

-----

Robert-Jan

Ps Hein don't know why it is not responding to the link. Thanks
Robert-Jan Goossens
Honored Contributor

Re: signal 11 swagentd.log

Now why do I say Hein, when I mean Robert ! :-)
Gerrit_1
Advisor

Re: signal 11 swagentd.log

_ACL en _OWNER files are ok, but the problems
remain.

Any other suggetions?


I have a vision...... a television