Messages

Ignore my previous message - my bad as I had not enabled query logging under Advanced.

I am facing the same issue where Unbound is NOT logging via syslog-ng. I am on 20.7.3 on a PCEngine kit. On a similar system with 20.7.3 i5 Qotom, that is working correctly. I have checked the settings and they are near identical. Any insights would be most helpful please...

I am facing the same issue where Unbound is NOT logging via syslog-ng. I am on 20.7.3 on a PCEngine kit. On a similar system with 20.7.3 i5 Qotom, that is working correctly. I have checked the settings and they are near identical. Any insights would be most helpful please...

Just donated to a great project and the great support we are getting! THANK YOU!

Hi 172pilot,

It would be useful to provide some details e.g. 20.1.7, installation CF or IDE/SATA HDD etc.

I have had issues when the IDE/SATA HDD was not properly secured in place and it caused a corruption to the bootloader and hence was not able to bootstrap the kernel etc.

May I know if there is any progress on the high CPU usage front? Am on 20.1.6 and am observing the same with load hovering between 2.0 - 2.5

So how do I go about enabling accounting then for FR?

When SQLite is  enabled, FreeRadius cannot start or at least that is what the UI shows - as stopped.

Moving to 19.7 where I observed this.

Enabling SQLite, FreeRadius does not appear to start.

With physical interface I get the same error - any ideas?

[-Xms2g -Xmx2g]

No it was a fresh install!

Running "ps awxu | grep elastic | grep -v grep" shows the following output:-

elasticsearch 18938  30.9 61.1 3897508 2528480  -  I    04:09       6:49.91 /usr/local/openjdk8/bin/java -Xms2g -Xmx2g -XX:+UseConc

"cat /usr/local/libexec/elasticsearch/config/jvm.options | grep 512" gives me

-Xms512m
-Xmx512m

I restarted ElasticSearch via the UI.

Is there a default setting it is picking up instead of from usr/local/libexec/elasticsearch/config/jvm.options?

For fresh installs we adjust this setting. Any chances you had a prior Sensei installation in this device?

No it was a fresh install!

@patcsy88, what does the following tell?

Code Select Expand

cat /usr/local/libexec/elasticsearch/config/jvm.options  | grep "^\-Xm"
-Xms2g
-Xmx2g

ps awxu | grep elastic | grep -v grep
elasticsearch  4875   2.2 46.6 3878304 1927928  -  I    08:22     74:00.13 /usr/local/openjdk8/bin/java -Xms2g -Xmx2g -XX:+UseConcM

ps awxu | grep eastpect | grep -v grep
root           7417   0.5  4.5 3094852  185100  -  S<   08:35      8:29.81 eastpect: Eastpect Instance 0 (eastpect)
root          66470   0.0  0.0 1270428       0  -  IW<  -          0:00.00 eastpect: Eastpect Streamer Instance (eastpect)
root          80093   0.0  2.2 1270428   92760  -  S<   08:35      0:04.70 /usr/local/sensei//bin/eastpect -D


One question: I guess you have like 4 GB of memory. For how many devices are you running Sensei for?

@MB only 4 devices with normal web browsing

Just reinstalled OPNsense and the RC1 on APU2C4 with 2GB Swap - so far so good!

So Sensei detected high Swap usage over the last 10+ hours and shut itself down. On prompt, I restarted ES. I have now also disabled the Health Check and on the Configuration page started Sensei Packet Engine and the overlay on the page says it is waiting for the service to startup. After 10 or so minutes, nothing happens on the page but vmstat in a shell suggest it is back up. Refreshing the OPNsense page and then going to the Configuration page again shows Sensei is up and running. Not sure if it is the OPNsense framework or Sensei page that is not polling for refresh of content/data...