Issues with a new PCS not allowing the pcscopy command to run<\/p>\n
The issue was with a new PCS which when I did the initial pcscopy just kept failing. The error was as follows<\/p>\n
14\/02\/13 15:19:17 001010M|—\/–\/-\/—|=3:0433=PCS 10.106.124.1: Database update: error 5 info 0. (which when you look it up say the copy failed and there is no more info, which is really useful!)<\/p>\n
After some digging I found that the .rhosts file in \/<\/span>usr2\/soft_install\/bin\/<\/span><\/i> did not contain the IP address of the main OxE so the connection was being rejected by the PCS<\/p>\n [root@pcs mtcl]# more \/<\/span>usr2\/soft_install\/bin\/<\/span><\/i>.rhosts If you look in \/var\/log\/auth.log you will see something like the following which shows the main OxE 10.103.163.21 in this case trying to access the PCS and being rejected.<\/p>\n Mar 24 02:49:14 pcs_perth_tem xinetd[558]: START: shell pid=1234 from=10.103.163.21 After the address was added to the .rhosts file the problem went away.<\/p>\n Don\u2019t know why it did it but this fixed it.<\/p>\n","protected":false},"excerpt":{"rendered":" Issues with a new PCS not allowing the pcscopy command to run The issue was…<\/p>\n
\n10.253.253.1 +@wild
\n10.253.253.2 +@wild
\n10.253.253.3 +@wild
\n10.253.253.4 +@wild
\n10.253.253.10 +@wild
\n10.253.253.11 +@wild
\n10.253.253.20 +@wild
\n10.253.253.21 +@wild
\n10.106.124.1 +@wild
\n10.106.124.254 +@wild
\n127.0.0.1 +@wild
\n10.103.163.21 +@wild \uf0df———— This was missing<\/p>\n
\nMar 24 02:49:14 pcs_perth_tem pam_rhosts_auth[1234]: denied to mtcl@oxe as swinst: access not allowed<\/p>\n