well it's simple really the ssh-copy-id routine does not copy [in my case] the client /root/.ssh/id_rsa.pub to the server man says thats the default but that's not what is happening. whatever it copies allows me to run a shell script from a console without passwords but not from cron hmmm cute! When I copied the contents of client ~/.ssh/id_rsa.pub to server ~/.ssh/authorized_keys network transfers in scripts run from cron are all working now What I can't understand is how some were working and some were not *ssh-add -L* produces a key which appears to be out of date something I am missing here but I do now have an operating network. Thanks Joseph, I just started again and did it the 'old' way. R On 17/01/17 15:05, Joseph L. Casale wrote: >> has something changed in cron? >> has there been an update? >> Have looked in all the usual places. >> >> any help/suggestions? > The environment maybe, enable debug output on the job and redirect > or make sure the output is logged or picked up and mailed to you. > > More than likely the ssh config that used to work no longer does. > For example you had a custom section for a host in ~/.ssh/config > that is no longer valid or that file is not even being read etc... > > jlc > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos -- *Communication Consultants* 64 Warner Park Avenue Laingholm Auckland 0604 09 8176358 0221693124 06 650 6087