I had to make changes to my client node and restart the scheduler on my client node. I kieed the scheduler process via kill -9 process number on the node. when I attempt to restart the scheduler if fails with a "ANS1018E Port 1501 is already in use". How do I restart the scheduler without rebooting the node? Is there a reset command I can run? Is there a graceful way to stop the scheduler?
-
-
Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.
Port 1501 in use after scheduler stopped
- Thread starter daveisme
- Start date
sandeepkontham
ADSM.ORG Senior Member
try changing the tcpclientport from 1501 to say 1502 and try
gimlet
ADSM.ORG Member
- Joined
- Apr 25, 2008
- Messages
- 154
- Reaction score
- 4
- Points
- 0
- Location
- St. Louis, Missouri
- Website
- www.lanigera.com
Are you sure nothing else is listening on the port? Using "lsof -i :1501 -n" should work, if you have lsof on your system.
Is there a command to reset the connect for the TSM server? It appears that whenever we stop and start the scheduler it fails to stay started? The scheduler is running in prompted mode. Do we have to unassociated the node from the schedule on the TSM server and reassociate it to get the scheduler to restart without having to reboot?
