Jan 4 10:38:30 gateway exec-stop-post.sh: Job for rvice failed because start of the service was attempted too often. ![]() Jan 4 10:38:30 gateway systemd: rvice failed. Jan 4 10:38:30 gateway systemd: Failed to start ClearOS Firewall Engine. Jan 4 10:38:30 gateway systemd: start request repeated too quickly for rvice Jan 4 10:38:30 gateway netifyd: void ndSocketThread::ClientHangup(std::map::iterator& It can't harm and may help, so please post them but not the whole thing, just a relevant section. Jan 4 18:17:45 server netifyd: enp2s0: capture started on CPU: 1Īnd I've just checked and those two files do not exist. Jan 4 18:17:45 server netifyd: enp5s0: capture started on CPU: 0 Jan 4 18:17:45 server netifyd: Unable to hash file: /var/lib/netifyd/app-host-match.csv: No such file or directory Jan 4 18:17:45 server netifyd: Unable to hash file: /var/lib/netifyd/app-content-match.csv: No such file or directory Jan 4 18:17:45 server netifyd: Netify Agent v2.3 Jan 4 18:17:44 server systemd: rvice failed. Jan 4 18:17:44 server systemd: Unit rvice entered failed state. Jan 4 18:17:44 server systemd: rvice: main process exited, code=killed, status=11/SEGV ![]() ![]() Jan 4 18:17:44 server netify-fwa: Error connecting to Netify node: Connection refused Jan 4 18:17:44 server netify-fwa: Netify socket hung-up, reconnecting. It segfaulted on me earlier today and I was not in the house: Jan 4 18:17:44 server kernel: enp2s0: segfault at ffffffffffffffe8 ip 000000000041805b sp 00007f4727a147e0 error 5 in netifyd
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |