• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • 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.

Getting a "Lock" Error on Decommissioned Nodes

buster99

ADSM.ORG Member
#1
Hello, Running into a very odd issue. Our TSM server us getting flooded with the following errors:
02/12/20 12:55:05 ANR0430W Session 628894 for node RDRE1-XXXXX (WinNT)
refused - node name is locked.

The nodes that are getting it exist but are decommissioned and they are not associated with a backup schedule. Why would they be trying to start sessions in TSM ? Thank you
 

marclant

ADSM.ORG Moderator
#2
Did you disable/uninstall the client scheduler? If not, the client scheduler will try to connect a few times a day to check if there are any schedules to run.
 

buster99

ADSM.ORG Member
#3
I doubt they were done on the client side. Would this cause a slowdown of live session processing for legit backups ? That is how we stumbled across these messages, We have nodes sitting at RecW and IdleW much longer than usual. There are quite a few nodes trying to connect. Thanks
 

marclant

ADSM.ORG Moderator
#4
I don’t think it would cause a slow down, the session is rejected right away. It’s certainly less stress than when they were doing backups.

RecvWait means the client was in the middle of a transaction, but stopped sending data temporarily. Slow disks on the client or networking issue. The session will get cancelled if it stays in RecvW longer than the commtimeout.

IdleWait is that the client has an opened session, but not doing any work. That’s common. Each client usually has 2 sessions by default. A producer that does determines what needs to be backed up and a consumer that does the actual data transfer. At some point during the backup, the producer gets idle and sometimes the session is cancelled when hitting the idletimeout.
 

hogmaster

ADSM.ORG Senior Member
#5
setup the SP server OS firewall to deny connections from those clients, if this solves your issue you know where the request originate.
You can see the IP adress of the nodes in the actlog.
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 18 18.4%
  • Keep using TSM for Spectrum Protect.

    Votes: 60 61.2%
  • Let's be formal and just say Spectrum Protect

    Votes: 12 12.2%
  • Other (please comement)

    Votes: 8 8.2%

Forum statistics

Threads
31,686
Messages
135,067
Members
21,703
Latest member
agent0810
Top