Yes, of courrse.
Output of service directadmin status
service directadmin status
Redirecting to /bin/systemctl status directadmin.service
● directadmin.service - DirectAdmin Web Control Panel
Loaded: loaded (/etc/systemd/system/directadmin.service; enabled; vendor pre>
Active: active (running) since Wed 2021-09-08 10:20:22 UTC; 3h 24min ago
Docs:
http://www.directadmin.com
Process: 1746110 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SU>
Main PID: 1748389 (directadmin)
Tasks: 32 (limit: 202276)
Memory: 71.0M
CGroup: /system.slice/directadmin.service
├─1748389 /usr/local/directadmin/directadmin
├─1748395 /usr/local/directadmin/directadmin
├─1748409 /usr/local/directadmin/directadmin
├─1748410 /usr/local/directadmin/directadmin
├─1748411 /usr/local/directadmin/directadmin
├─1748412 /usr/local/directadmin/directadmin
├─1748413 /usr/local/directadmin/directadmin
├─1748414 /usr/local/directadmin/directadmin
├─1748415 /usr/local/directadmin/directadmin
├─1748416 /usr/local/directadmin/directadmin
├─1756926 /usr/local/directadmin/directadmin
└─1756927 /usr/local/directadmin/directadmin
error.log file output
2021:09:07-15:03:30: Socket write error: fd is connected to a pipe or socket whose reading end is closed. When this happens the writing process will also receive a SIG_PIPE signal. (Thus, the write return value is seen only if the program catches, blocks or ignores this signal.)
2021:09:07-15:03:30: Send:sendData(/admin/modsecurity): attempted to send 1688 bytes, but only 0 were delivered
2021:09:07-15:04:58: Socket write error: fd is connected to a pipe or socket whose reading end is closed. When this happens the writing process will also receive a SIG_PIPE signal. (Thus, the write return value is seen only if the program catches, blocks or ignores this signal.)