Update Connection Re-Registration
I have registered a system earlier w/subscription key (contract number) and for some unknown reason, it got a number of process queued in in progress status (for over 3 months!). I've updated the system via update manager and there should be no outstanding patches. In order for me to clear that off, I have to delete the system from update connection.
I've then tried to re-registered via the sconadm command, which reported successful. However, I cannot see the system when I log back into update connection. Any idea why? How can I make this work?
[565 byte] By [
btsanga] at [2007-11-27 0:36:34]
# 1
Did you include the following setting in your registration properties file?portalEnabled=True
# 2
Forgotten about that before, but I've set it back and re-registered (also have add the subscription via update manager with the same). The host is now showup on update connection for a day already, but it still do not have any required patch information (while update manager report I've got 7 patches). Am I missing something?
# 3
Is the host able to communicate with the portal -
# /usr/lib/cc-cfw/platform/transport/bin/cctrunner -p
When did it last checkin -
# /usr/lib/cc-ccr/bin/ccr -g cns.swup.lastCheckin
Are the correct entries in crontab and have they logged any errors during their run -
# crontab -l
and check the following log files (if they exist) for errors
/var/cron/log
/var/log/swupas/swupas.log
/var/log/swupas/swupas.error.log
Finally, is the cctransport process actually running -
# ps -ef | grep cctransport
# 4
Just checked, last check-in time was 2007/04/11 17:23:34 UTC, which is yestersday when I try to re-register again due to my issue above. Seems like after re-registration, it won't check-in.
And from the server side, the cron job is running and below is what I've got from swupas.log,
-bash-3.00$ cat swupas.log.1
Swup Agent run: Thu Apr 12 07:51:00 EDT 2007
** DEBUG ON **
Attempt to get exclusive lock: 1
We have the lock!
prepare to register with Transport
Error: unable to register with Transport
com.sun.cc.transport.client.TransportAdapterException: proxy communication failure
at com.sun.cc.transport.client.TransportAdapter.register(TransportAdapter.java:474 )
at com.sun.cc.transport.client.TransportAdapter.<init>(TransportAdapter.java :305)
at com.sun.swup.client.agent.SwupAgent.main(SwupAgent.java:337)
Swup Agent finish: Thu Apr 12 07:53:31 EDT 2007
# 5
Were you following the sconadm registration guide (infodoc: 82688 on sunsolve)?
In particular to you set the system to use a proxy prior to registration?
# /usr/sbin/sconadm proxy -r /tmp/registrationprofile.properties
Then:
# /usr/sbin/sconadm register -a -r /tmp/registrationprofile.properties
# 6
Tried all the option, but still got the same error ...seems like it still cannot connect to their update site. Out of idea for what to do.
--
bash-3.00# cat swupas.log
Swup Agent run: Fri Apr 13 21:51:00 EDT 2007
** DEBUG ON **
Attempt to get exclusive lock: 1
We have the lock!
prepare to register with Transport
Error: unable to register with Transport
com.sun.cc.transport.client.TransportAdapterException: proxy communication failure
at com.sun.cc.transport.client.TransportAdapter.register(TransportAdapter.java:474 )
at com.sun.cc.transport.client.TransportAdapter.<init>(TransportAdapter.java :305)
at com.sun.swup.client.agent.SwupAgent.main(SwupAgent.java:337)
Swup Agent finish: Fri Apr 13 21:53:31 EDT 2007
# 7
Run the following command and see if it gives an error similar to "Cannot establish communication with proxy"
# /usr/lib/cc-cfw/platform/transport/bin/cctstat
If it does, clear the cctransport queues and restart it before trying the ccstat vommand above again -
# /etc/init.d/cctransport stop
# rm -rf /var/tmp/cc-transport/*
# /etc/init.d/cctransport start
If all looks better and you dont get an error then try registering again. If it fails post the ouptut from running the above commands.
# 8
I run the command and result as follows,
bash-3.00# /usr/lib/cc-cfw/platform/transport/bin/cctstat
can't establish communication with proxy
and there is no cc-transport startup script as follows,
bash-3.00# /etc/init.d/cctransport stop
bash: /etc/init.d/cctransport: No such file or directory
Am I missing something? If so, how can I add it back? Also wondering why I don't have such problem until re-register?
# 9
I've found the init script in /usr/lib/cc-cfw/platform/transport directory, and make a copy to /etc/init.d. After starting it up, it now can connect and I can see from the update connection site that it did check in. So, this part is now working.
There is no update etc showup yet, does it take some time for it to show up? At least there should be a few outstanding patches.
# 10
HiIt is likely the cns-transport was not running as disabling the client on the portal prior to reregistration will have sent a command to the client from the portal to do this.You may also need to wait 24 hours for a checkin.Let us know how you get on.Mod.
