Issue
Imunify360 hook events are not being logged to /var/log/imunify360/hook.log. The log file is empty or not populated, making it difficult to verify whether hooks are being executed during troubleshooting. Logging appears to have stopped across multiple servers within the same timeframe.
Environment
- Imunify360
Solution
To see possible errors related to the Notifications feature, check the system journal for the notification service.
- For example, simulated an issue script and set it in the Notifications Settings.
- The culprit has been caught in its events:
[root@imunifytestnew scripts]# journalctl -u imunify-notifier.service -f
..
Jan 30 06:47:01 imunifytestnew.srv.local imunify-notifier[439462]: new connection accepted
Jan 30 06:47:01 imunifytestnew.srv.local imunify-notifier[439462]: waiting for a connection/timeout
Jan 30 06:47:01 imunifytestnew.srv.local imunify-notifier[439462]: error handling connection: could not handle message: error during custom script execution: /var/imunify360/scripts/hook1.sh: line 16: hookoutput.txt: Permission denied
ls: cannot access 'hookoutput.txt': No such file or directory
, exit status 2
Jan 30 06:48:01 imunifytestnew.srv.local systemd[1]: imunify-notifier.service: Deactivated successfully.
Jan 30 06:48:01 imunifytestnew.srv.local systemd[1]: Started Imunify360 notifications service.
Jan- In addition, this service does not have its own log file:
[root@imunifytestnew scripts]# systemctl status imunify-notifier.service
● imunify-notifier.service - Imunify360 notifications service
Loaded: loaded (/usr/lib/systemd/system/imunify-notifier.service; enabled; preset: disabled)
Active: active (running) since Fri 2026-01-30 06:52:01 UTC; 48s ago
TriggeredBy: ● imunify-notifier.socket
Main PID: 440831 (imunify-notifie)
Tasks: 7 (limit: 22816)
Memory: 2.1M
CPU: 19ms
CGroup: /Imunify.slice/Imunify-notifier.slice/imunify-notifier.service
└─440831 /usr/sbin/imunify-notifier
Jan 30 06:52:01 imunifytestnew.srv.local systemd[1]: Started Imunify360 notifications service.
Jan 30 06:52:01 imunifytestnew.srv.local imunify-notifier[440831]: starting, version 2.1.12-1
Jan 30 06:52:01 imunifytestnew.srv.local imunify-notifier[440831]: waiting for a connection/timeout
Jan 30 06:52:01 imunifytestnew.srv.local imunify-notifier[440831]: new connection accepted
Jan 30 06:52:01 imunifytestnew.srv.local imunify-notifier[440831]: waiting for a connection/timeout
Jan 30 06:52:01 imunifytestnew.srv.local imunify-notifier[440831]: new connection accepted
Jan 30 06:52:01 imunifytestnew.srv.local imunify-notifier[440831]: waiting for a connection/timeout
[root@imunifytestnew scripts]# lsof -p 440831
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
imunify-n 440831 root cwd DIR 8,2 4096 2 /
imunify-n 440831 root rtd DIR 8,2 4096 2 /
imunify-n 440831 root txt REG 8,2 10335760 34237 /usr/sbin/imunify-notifier
imunify-n 440831 root mem REG 8,2 2549264 19687 /usr/lib64/libc.so.6
imunify-n 440831 root mem REG 8,2 70528 19698 /usr/lib64/libresolv.so.2
imunify-n 440831 root mem REG 8,2 932688 19683 /usr/lib64/ld-linux-x86-64.so.2
imunify-n 440831 root 0r CHR 1,3 0t0 4 /dev/null
imunify-n 440831 root 1u unix 0xffff8eb969609900 0t0 64343977 type=STREAM (CONNECTED)
imunify-n 440831 root 2u unix 0xffff8eb969609900 0t0 64343977 type=STREAM (CONNECTED)
imunify-n 440831 root 4u unix 0xffff8eba48d47200 0t0 64343981 type=DGRAM (CONNECTED)
imunify-n 440831 root 5u a_inode 0,14 0 11943 [eventpoll:4,6,7]
imunify-n 440831 root 6u a_inode 0,14 0 11943 [eventfd:24]
imunify-n 440831 root 7u unix 0xffff8eba4a3d6d00 0t0 20532 /opt/imunify360/lib/event.sock type=STREAM (LISTEN)
[root@imunifytestnew scripts]#Cause
The Hooks feature is deprecated; "Notifications" serves the same purpose instead.
Comments
0 comments
Please sign in to leave a comment.