Richard G
Verified User
I can understand no logs are shown if you don't use Evo skin and thus custombuild via CLI.
But if I switch to Evo as admin on any server, and to some update like today the Direct admin update, there is an error that log can not be loaded.
And if I view the log section of Custombuild they are all 0 bytes.
The upper one from today, is for sure made via CB in Evo, most others just via CLI.
Maybe it's a permission issue.
The logfile custombuild.1720713268.3569774.aW5zdGFsbAA.log from today is non existing in /var/log/directadmin.
Older custombuild logs look like this:
This is the permission/owner of the /var/log/directadmin directory:
How can we fix this
But if I switch to Evo as admin on any server, and to some update like today the Direct admin update, there is an error that log can not be loaded.
And if I view the log section of Custombuild they are all 0 bytes.
The upper one from today, is for sure made via CB in Evo, most others just via CLI.
Maybe it's a permission issue.
The logfile custombuild.1720713268.3569774.aW5zdGFsbAA.log from today is non existing in /var/log/directadmin.
Older custombuild logs look like this:
Code:
-rw-r--r-- 1 root root 0 2024-06-16 06:00 custombuild.1718510400.224024.Y3Jvbl9leGVjdXRlAA.log
-rw-r--r-- 1 root root 0 2024-06-17 06:00 custombuild.1718596800.1864984.Y3Jvbl9leGVjdXRlAA.log
This is the permission/owner of the /var/log/directadmin directory:
drwx------. 2 diradmin diradmin 12K 2024-07-11 17:54 directadmin
How can we fix this
Last edited: