{"id":1864,"date":"2012-04-08T11:19:35","date_gmt":"2012-04-08T15:19:35","guid":{"rendered":"http:\/\/linuxhostingsupport.net\/blog\/?p=1864"},"modified":"2013-03-20T08:38:23","modified_gmt":"2013-03-20T12:38:23","slug":"plesk-error-swkeyexfatalerror-cannot-open-file","status":"publish","type":"post","link":"https:\/\/linuxhostingsupport.net\/blog\/plesk-error-swkeyexfatalerror-cannot-open-file","title":{"rendered":"Plesk error: SWKeyExFatalError Cannot open file"},"content":{"rendered":"

 
\nSometimes a Plesk upgrade may result in an “SWKeyExFatalError: Cannot open file” error while accessing the Plesk panel. The error message looks like<\/p>\n

\n
ERROR: SWKeyExFatalError\r\nerror: Cannot open file\r\n----------------------------\r\n0: common_func.php3:4537\r\nof_get_key_by_product(string \u2018plesk-unix\u2019)\r\n1: common_func.php3:4537\r\ngetPleskKey()\r\n2: common_func.php3:4616\r\ngetKeyProp(string \u2018demo\u2019)\r\n3: auth.php3:48<\/pre>\n<\/blockquote>\n
 
\nThe SWKeyExFatalError error occurs when ownership of files\/directories in \/etc\/sw\/keys are incorrect.
\nThe files and directories in \/etc\/sw\/keys\/ should be owned by psaadm:swkey-data except registry.xml.<\/strong><\/p>\n
\n
# ls -la \/etc\/sw\/keys<\/span>\r\n drwxrws--- 2 psaadm swkey-data 4096 Mar 25 04:02 backup\r\n -rw-r--r-- 1 psaadm swkey-data 22 May 18 2010 info\r\n drwxrws--- 2 psaadm swkey-data 4096 Sep 15 2011 instances\r\n drwxrws--- 2 psaadm swkey-data 4096 Mar 25 04:02 keys\r\n drwxrws--- 2 psaadm swkey-data 4096 Sep 15 2011 lock\r\n -rw-rw---- 1 root swkey-data 7431 Apr 8 04:02 registry.xml\r\n drwxrws--- 2 psaadm swkey-data 4096 Sep 15 2011 restart<\/pre>\n<\/blockquote>\n
 
\nIf the ownership of the files is not what you see above, correct them as follows:<\/p>\n
\n
# chown psaadm:swkey-data \/etc\/sw\/keys -R<\/span>\r\n# chown root:swkey-data registry.xml<\/span><\/pre>\n<\/blockquote>\n
 
\nNext, restart the Plesk service and Plesk control panel should work.<\/p>\n
\n
# service psa restart<\/span><\/pre>\n<\/blockquote>\n
 
\nHowever, if the user ‘psaadm’ is not in the ‘swkey-data’ group, <\/strong>it is possible that the ownership of the files get reverted on restarting the Plesk service<\/strong>.<\/p>\n
\n
# id psaadm<\/span>\r\n uid=501(psaadm) gid=501(psaadm) groups=501(psaadm),2522(psaserv)<\/pre>\n<\/blockquote>\n
 
\nAs you can see above, the user psaadm is not in the group of swkey-data. You can also verify it as follows:<\/p>\n
\n
# grep swkey-data \/etc\/group<\/span>\r\n swkey-data:x:502:<\/pre>\n<\/blockquote>\n
 
\nIn such a case, edit the \/etc\/group file and add the psaadm user in swkey-data group. The line should look like follows:<\/p>\n
\n
swkey-data:x:502:psaadm<\/span><\/pre>\n<\/blockquote>\n
 
\nSave the file and verify the new settings<\/p>\n
\n
# id psaadm<\/span>\r\nuid=501(psaadm) gid=501(psaadm) groups=501(psaadm),502(swkey-data),\r\n2522(psaserv)<\/pre>\n<\/blockquote>\n
 
\nRestart the Plesk service and the Plesk panel will work without problems.<\/p>\n","protected":false},"excerpt":{"rendered":"
 
\nSometimes a Plesk upgrade may result in an “SWKeyExFatalError: Cannot open file” error while accessing the Plesk panel. The error message looks like<\/p>\n
ERROR: SWKeyExFatalError
\nerror: Cannot open file
\n—————————-
\n0: common_func.php3:4537
\nof_get_key_by_product(string \u2018plesk-unix\u2019)
\n1: common_func.php3:4537
\ngetPleskKey()
\n2: common_func.php3:4616
\ngetKeyProp(string \u2018demo\u2019)
\n3: auth.php3:48<\/p>\n
 
\nThe SWKeyExFatalError error occurs when ownership of files\/directories in \/etc\/sw\/keys are incorrect.
\nThe files and directories in \/etc\/sw\/keys\/ should be owned by psaadm:swkey-data except registry.xml.<\/p>\n
# ls -la \/etc\/sw\/keys
\n drwxrws— 2 psaadm swkey-data 4096 Mar 25 04:02 backup
\n -rw-r–r– 1 psaadm swkey-data 22 May 18 2010 info
\n drwxrws— 2 psaadm swkey-data 4096 Sep 15 2011 instances
\n drwxrws— 2 […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[1384,1385,1383],"_links":{"self":[{"href":"https:\/\/linuxhostingsupport.net\/blog\/wp-json\/wp\/v2\/posts\/1864"}],"collection":[{"href":"https:\/\/linuxhostingsupport.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/linuxhostingsupport.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/linuxhostingsupport.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/linuxhostingsupport.net\/blog\/wp-json\/wp\/v2\/comments?post=1864"}],"version-history":[{"count":13,"href":"https:\/\/linuxhostingsupport.net\/blog\/wp-json\/wp\/v2\/posts\/1864\/revisions"}],"predecessor-version":[{"id":2080,"href":"https:\/\/linuxhostingsupport.net\/blog\/wp-json\/wp\/v2\/posts\/1864\/revisions\/2080"}],"wp:attachment":[{"href":"https:\/\/linuxhostingsupport.net\/blog\/wp-json\/wp\/v2\/media?parent=1864"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/linuxhostingsupport.net\/blog\/wp-json\/wp\/v2\/categories?post=1864"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/linuxhostingsupport.net\/blog\/wp-json\/wp\/v2\/tags?post=1864"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}