OPNsense Forum
Archive => 21.7 Legacy Series => Topic started by: Dobi on September 03, 2021, 10:10:17 am
-
Hello,
After reboot there are some services which don't start:
- cicap (C-ICAP Server)
- clamd (ClamAV Daemon)
- freshclam (freshclam daemon)
- squid (Web Proxy)
Apart from this also the Sensei-Services don't start:
- Sensei Packet Engine
- Elasticsearch
After a manual "Start" of those services they work.
I tried do search for solutions online but I did not find anything helpful.
Maybe someone has an idea over here?
Greetings,
Dobi
-
How long did you wait? It can take a little time after a startup for all services to come online and show green on the dashboard. I'd suggested rebooting, and waiting 10 min or so then checking. When I first started using opnsense I thought I had an issue but turns out I was impatient, just curious if maybe that's what's happening for you. 8)
-
How long did you wait? It can take a little time after a startup for all services to come online and show green on the dashboard. I'd suggested rebooting, and waiting 10 min or so then checking. When I first started using opnsense I thought I had an issue but turns out I was impatient, just curious if maybe that's what's happening for you. 8)
Thank you for the reply.
Even after about +- 6 hours it did not start.
-
How long did you wait? It can take a little time after a startup for all services to come online and show green on the dashboard. I'd suggested rebooting, and waiting 10 min or so then checking. When I first started using opnsense I thought I had an issue but turns out I was impatient, just curious if maybe that's what's happening for you. 8)
Thank you for the reply.
Even after about +- 6 hours it did not start.
Ah yea 6 hrs should have been plenty lol. Anything useful when you run dmesg in terminal? If needed filter with dmesg | grep error
Sent from my IN2025 using Tapatalk
-
How long did you wait? It can take a little time after a startup for all services to come online and show green on the dashboard. I'd suggested rebooting, and waiting 10 min or so then checking. When I first started using opnsense I thought I had an issue but turns out I was impatient, just curious if maybe that's what's happening for you. 8)
Thank you for the reply.
Even after about +- 6 hours it did not start.
Ah yea 6 hrs should have been plenty lol. Anything useful when you run dmesg in terminal? If needed filter with dmesg | grep error
During the WE I had access to the OPNsense server itself.
When doing a "reboot", it actually did not do a full reboot. So I took if from current, and booted afterwards.
One of my disks was corrupted. After a rebuild of the RAID nearly every service behaved normally again.
The only thing which I do not get to start is the Elasticsearch.
(Using "dmesg | grep error", I only get a VESA error, but I can not imagine that it has sth. to do with Elasticsearch.)
Elasticsearch shows the Information : "Disk usage:0 B".
-
I now backuped Sensei, removed Elasticsearch:
pkg remove elasticsearch5
cd /usr/local/etc
rm -rf elasticsearch
removed Sensei, reinstalled Sensei and restored the config.
Maybe not the most beautiful solution, but now everything works again as it should.
Thank you very much for you help.
-
Glad you got it figured out.
Sent from my IN2025 using Tapatalk