Search the Community
Showing results for tags 'linux centos'.
Found 1 result
I installed version 220.127.116.11 of the 64 bit client on on CentOS V7 recently. Each time I do a successful backup (using proactive from a Windows Pro V11.5 install) - the client stays reserved and the client status shows 1 connection still. This prevents the proactive backup from being able to run the next scheduled backup as the client remains "in use". The backup in each case ends normally and is successful. I can work around the problem by manually stopping and then starting the Linux client. That will allow the next backup to run to completion - but again the client will remain in use - so obviously this is not a viable workaround. I could put a cron in place to do the stop/start on a daily basis - but that seems like a total kludge and should be unnecessary. Any ideas on what might be preventing the connection from being properly closed with this client? This is my only Linux client - all other clients are Win clients - and do not exhibit this same issue. So I am sure it must be something peculiar to the Linux environment on this machine... Do I need to adjust/tune some TCP options on the Linux side perhaps?