Facebook
TwitterIssue could not create //run/named/session.key
- Thread starter nMLxTMJTZ
- Start date
Have you checked that the path named in named.conf for "session-keyfile" is writeable?
1) Look into /etc/named.conf and find the line "session-keyfile".
2) Check the file permissions of that path, e.g. "ll <path>".
2) Check the file permissions of that path, e.g. "ll <path>".
This looks correct. Could you please check whether the situation described in https://support.plesk.com/hc/en-us/...based-OS-couldn-t-mkdir-run-Permission-denied is yours and maybe try the suggested solution?
We discussed it here and think it is necessary to check directly on your server. It's most likely not a Plesk issue in the first place, but we're still willing to assist to the best of our knowledge. Please open a support ticket so that a Plesk engineer can check and solve the issue directly on your server.
To sign-in to support please go to https://support.plesk.com
If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work
If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-
To sign-in to support please go to https://support.plesk.com
If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work
If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-
Johnny9977
Basic Pleskian
Hi. Any out coming here? I have the same issue!!!
asolopovas
New Pleskian
I am struggling from the same issue it constantly flooding my logs since I clean installed my plesk panel.
These 2 following me every couple minutes.
If you check the folder the folder owned by root:bind
ls -ld /run/named
drwxrwxr-x 2 root bind 40 Mar 24 11:37 /run/named
if I chown it with bind:bind, problem disappears until reboot, when the folder reverts to root:bind, how can this behaviour be adjusted is there any solution to this problem?
These 2 following me every couple minutes.
| 2025-03-23 18:20:12 | err | named [766] System daemons [3] | failed to generate session key for dynamic DNS: permission denied |
| 2025-03-23 18:20:12 | err | named [766] System daemons [3] | could not create //run/named/session.key |
If you check the folder the folder owned by root:bind
ls -ld /run/named
drwxrwxr-x 2 root bind 40 Mar 24 11:37 /run/named
if I chown it with bind:bind, problem disappears until reboot, when the folder reverts to root:bind, how can this behaviour be adjusted is there any solution to this problem?
