Sun Update Connection error

Hi,

We are currently experiencing an error when trying to use the Update Connection portal to manage updates on systems. Scheduled jobs all fail with the following error message:

"Feature not available. We have experienced a system failure"

Running update manager locally on the system works correctly (ie: analysis, patch selection, download and installation)

When registering systems we selected the option to manage remotely via update connection.

Any ideas? Thanks.

Andrew

[519 byte] By [nastrond] at [2007-11-26 6:04:57]
# 1
Dear Nastrond,The problems you have experienced could be caused by a temporary outage. Could you please try to check if your Update Connection portal is working properly now?.Regards,SWUP team
ForumModerator at 2007-7-6 13:31:31 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 2

Dear SWUP team.

I have tried again and unfortunately it does not appear to be working. Intially, I was receiving the message "Host xxxxx not found. Check SWUP agent is running".

Both systems I am trying to control via the portal have the following in their crontab:

38 3 * * * /usr/lib/patch/swupAuto > /dev/null 2>&1

53 * * * * /usr/lib/patch/swupas > /dev/null 2>&1

Now, when I try again I am getting the first message which you mention is due to a temporary outage.

Any ideas? Thanks.

Regards,

Andrew

nastrond at 2007-7-6 13:31:31 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 3
Is the /usr/lib/cc-cfw/platform/invagent/bin/cc-invagent job also present in crontab?Is cron working OK? Are there any errors in /var/cron/log?Can you post the content of the /var/log/swupas/swupas.log and /var/log/swupas/swupas.error.log files?
ForumModerator at 2007-7-6 13:31:31 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 4

Hi,

Yes the invagent is present in crontab. We have had a successful update once (1 time only) from the portal, otherwise we consistently get the error message "encountered an error".

Cron is working and not generating any errors:

tail -50 /var/cron/log

> root 10236 c Wed Dec 21 03:30:00 2005

< root 10236 c Wed Dec 21 03:30:00 2005

> CMD: /usr/lib/patch/swupAuto > /dev/null 2>&1

> root 10384 c Wed Dec 21 03:38:00 2005

< root 10384 c Wed Dec 21 03:38:03 2005

> CMD: /usr/lib/patch/swupas > /dev/null 2>&1

> root 10646 c Wed Dec 21 03:53:00 2005

< root 10646 c Wed Dec 21 03:53:00 2005

> CMD: /usr/lib/patch/swupas > /dev/null 2>&1

> root 11669 c Wed Dec 21 04:53:00 2005

< root 11669 c Wed Dec 21 04:54:33 2005

> CMD: /usr/lib/patch/swupas > /dev/null 2>&1

> root 12668 c Wed Dec 21 05:53:00 2005

< root 12668 c Wed Dec 21 05:53:00 2005

> CMD: /usr/lib/patch/swupas > /dev/null 2>&1

> root 13683 c Wed Dec 21 06:53:00 2005

< root 13683 c Wed Dec 21 06:54:33 2005

> CMD: /usr/lib/patch/swupas > /dev/null 2>&1

> root 14731 c Wed Dec 21 07:53:00 2005

< root 14731 c Wed Dec 21 07:53:00 2005

> CMD: /usr/lib/patch/swupas > /dev/null 2>&1

> root 15834 c Wed Dec 21 08:53:00 2005

< root 15834 c Wed Dec 21 08:54:33 2005

> CMD: /usr/lib/patch/swupas > /dev/null 2>&1

> root 16958 c Wed Dec 21 09:53:00 2005

< root 16958 c Wed Dec 21 09:53:00 2005

> CMD: /usr/lib/patch/swupas > /dev/null 2>&1

> root 17954 c Wed Dec 21 10:53:00 2005

< root 17954 c Wed Dec 21 10:54:33 2005

> CMD: /usr/lib/patch/swupas > /dev/null 2>&1

> root 19001 c Wed Dec 21 11:53:00 2005

< root 19001 c Wed Dec 21 11:53:00 2005

> CMD: /usr/lib/patch/swupas > /dev/null 2>&1

> root 20028 c Wed Dec 21 12:53:01 2005

< root 20028 c Wed Dec 21 12:54:33 2005

> CMD: /usr/lib/patch/swupas > /dev/null 2>&1

> root 21013 c Wed Dec 21 13:53:00 2005

< root 21013 c Wed Dec 21 13:53:00 2005

> CMD: /usr/lib/patch/swupas > /dev/null 2>&1

> root 22090 c Wed Dec 21 14:53:00 2005

< root 22090 c Wed Dec 21 14:54:33 2005

> CMD: /usr/lib/cc-cfw/platform/invagent/bin/cc-invagent

> root 22803 c Wed Dec 21 15:35:00 2005

< root 22803 c Wed Dec 21 15:38:06 2005

> CMD: /usr/lib/patch/swupas > /dev/null 2>&1

> root 2374 c Wed Dec 21 15:53:00 2005

< root 2374 c Wed Dec 21 15:53:00 2005

> CMD: /usr/lib/patch/swupas > /dev/null 2>&1

> root 3875 c Wed Dec 21 16:53:00 2005

< root 3875 c Wed Dec 21 16:54:35 2005

cat /var/log/swupas/swupas.log

Swup Agent run: Wed Dec 21 16:53:00 EST 2005

** DEBUG ON **

Attempt to get exclusive lock: 1

We have the lock!

prepare to register with Transport

Registration complete

Sleeping 90 secs...

OK, WE'RE AWAKE AGAIN!...

Updated last checkin time in CCR: 18919059

Number of swup server cmds to be executed: 0

smpatch collection name:current

old cache age (min): 1319

need an analysis update: false

Exiting for now...

Swup Agent finish: Wed Dec 21 16:54:35 EST 2005

cat /var/log/swupas/swupas.log.1

Swup Agent run: Wed Dec 21 14:53:00 EST 2005

** DEBUG ON **

Attempt to get exclusive lock: 1

We have the lock!

prepare to register with Transport

Registration complete

Sleeping 90 secs...

OK, WE'RE AWAKE AGAIN!...

Updated last checkin time in CCR: 18918939

Number of swup server cmds to be executed: 0

smpatch collection name:current

old cache age (min): 1199

need an analysis update: false

Exiting for now...

Swup Agent finish: Wed Dec 21 14:54:33 EST 2005

No errors in the /var/log/swupas/swupas.error.log

Web based access to the internet is through a proxy (configured on the clients). Clients can successfully update via the GUI.

Thanks.

Andrew

nastrond at 2007-7-6 13:31:31 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 5
At what point does the error appear on the portal? Is it when trying to schedule the jobs or is it after/during the jobs scheduled run?
ForumModerator at 2007-7-6 13:31:31 > top of Java-index,Administration Tools,Sun Update Connection-System...