topic Re: swagentd log in Operating System - HP-UX

swagentd log

Macho_2 — Thu, 21 Aug 2008 05:49:23 GMT

I had received the following error from the swagentd log file during swinstall. Please advice how to solve this issue :-

======= 08/21/08 15:37:03 JST END swagentd (pid = 24203).

======= 08/21/08 15:37:15 JST BEGIN swagentd (pid = 25134).

* Registered RPC protocol "ncacn_ip_tcp" with endpoint "2121".
* Registered RPC protocol "ncadg_ip_udp" with endpoint "2121".
* Checking job queue at 1 minute intervals.
* Started install agent on "/" for root@malvin.ea.com,
pid=25150, 08/21/08 15:37:33 JST
ERROR: Cannot lock "/" because another command holds a conflicting
lock. The process id of that command is 351.
ERROR: The target "/" could not be opened. pid=25150 08/21/08
15:37:33 JST
* Agent pid=25150 completed. 08/21/08 15:37:33 JST
* Started install agent on "/" for root@malvin.ea.com,
pid=26084, 08/21/08 15:40:35 JST
ERROR: Cannot lock "/" because another command holds a conflicting
lock. The process id of that command is 351.
ERROR: The target "/" could not be opened. pid=26084 08/21/08
15:40:35 JST
* Agent pid=26084 completed. 08/21/08 15:40:35 JST

Re: swagentd log

Torsten. — Thu, 21 Aug 2008 05:54:00 GMT

Looks like another install session is already running - check this.

Re: swagentd log

Deepak Kr — Thu, 21 Aug 2008 07:23:37 GMT

>>>ERROR: Cannot lock "/" because another command holds a conflicting
lock. The process id of that command is 351

answer is there in output:

check if another instance is active when you tried
check process id 351..if your session is still active..

regds...Deepak

Re: swagentd log

Macho_2 — Thu, 21 Aug 2008 08:01:49 GMT

Hi;

Please refer to my attachment. Why my swinstall screeen is not readable properly.
Please advice.

Re: swagentd log

Torsten. — Thu, 21 Aug 2008 08:09:38 GMT

You have a problem with the terminal emulation - what client are you using?

Try putty!

Re: swagentd log

Macho_2 — Thu, 21 Aug 2008 08:22:24 GMT

I am using HyperTerminal with vt100 Emulation and even using telnet and putty, I have the same problem.

Re: swagentd log

Torsten. — Thu, 21 Aug 2008 08:30:07 GMT

check your TERM variable:

# echo $TERM
and set accordingly
# export TERM=vt100
or
# export TERM=xterm
(for putty).

You can also try

# eval `ttytype -s -a`

Re: swagentd log

Macho_2 — Thu, 21 Aug 2008 08:53:44 GMT

Hi;

I had change the term to vt100 and the problem still like that and even the putty have the same problem. Please advice.

Re: swagentd log

Deepak Kr — Thu, 21 Aug 2008 12:00:20 GMT

Macho,

Please run following

#/bin/X11/resize

Recycle swagent daemon

/sbin/init.d/swagentd -r

See the results.

Re: swagentd log

Macho_2 — Thu, 21 Aug 2008 12:12:35 GMT

Dear;

I am still having the same issue. Cannot read the swinstall menu properly. What else can do ?

Re: swagentd log

Torsten. — Thu, 21 Aug 2008 13:18:44 GMT

Even if I think you can make this working with putty, you can also try the GUI for swinstall.

Re: swagentd log

Bob E Campbell — Tue, 26 Aug 2008 18:10:16 GMT

I personally use Putty as others have mentioned (http://www.putty.org) but in either case your terminal and TERM settings must match.

In Hyperterminal under "File|Properties|Settings" set Emulation to VT100. Next, after logging in run the command "export TERM=vt100" before starting SD.