-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't Upgrade from SELKS 5 to SELKS 6 -- Elasticsearch and Moloch errors #297
Comments
Did you use the upgrade script ?
… --
Regards,
Peter Manev
On 23 Feb 2021, at 20:45, P-Sandusky ***@***.***> wrote:
I have a SELKS installation here that I've successfully upgraded to SELKS 5, but now it's not making the transition to SELKS 6. Suricata and Scirius seem to have made the change, but Logstash hangs when I run the upgrade scripts, and Elasticsearch fails outright. Once Elastic fails, Moloch doesn't upgrade.
I've tried killing Logstash's processes directly, and that got the install script to run. Elastic promptly quit. At first, I noticed a number of what appeared to be Python dependencies missing, so I ran the dependency install script. At the most recent attempt, Logstash would not halt, so I did not see if installing the dependencies had an impact.
Here is my most recent health output:
***@***.***:~$ sudo selks-health-check_stamus
● suricata.service - LSB: Next Generation IDS/IPS
Loaded: loaded (/etc/init.d/suricata; generated)
Active: active (running) since Tue 2021-02-23 14:08:21 EST; 35min ago
Docs: man:systemd-sysv-generator(8)
Process: 846 ExecStart=/etc/init.d/suricata start (code=exited, status=0/SUCCESS)
Tasks: 14 (limit: 4915)
Memory: 1.4G
CGroup: /system.slice/suricata.service
└─909 /usr/bin/suricata -c /etc/suricata/suricata.yaml --pidfile /var/run/suricata.pid --af-packet -D -v --user=logstash
Feb 23 14:08:21 SELKS systemd[1]: Starting LSB: Next Generation IDS/IPS...
Feb 23 14:08:21 SELKS suricata[846]: Starting suricata in IDS (af-packet) mode... done.
Feb 23 14:08:21 SELKS systemd[1]: Started LSB: Next Generation IDS/IPS.
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-02-23 14:22:54 EST; 20min ago
Docs: https://www.elastic.co
Process: 3897 ExecStart=/usr/share/elasticsearch/bin/systemd-entrypoint -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE)
Main PID: 3897 (code=exited, status=1/FAILURE)
Feb 23 14:22:54 SELKS systemd-entrypoint[3897]: at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:150)
Feb 23 14:22:54 SELKS systemd-entrypoint[3897]: at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:75)
Feb 23 14:22:54 SELKS systemd-entrypoint[3897]: at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:116)
Feb 23 14:22:54 SELKS systemd-entrypoint[3897]: at org.elasticsearch.cli.Command.main(Command.java:79)
Feb 23 14:22:54 SELKS systemd-entrypoint[3897]: at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:115)
Feb 23 14:22:54 SELKS systemd-entrypoint[3897]: at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:81)
Feb 23 14:22:54 SELKS systemd-entrypoint[3897]: For complete error details, refer to the log at /var/log/elasticsearch/elasticsearch.log
Feb 23 14:22:54 SELKS systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
Feb 23 14:22:54 SELKS systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
Feb 23 14:22:54 SELKS systemd[1]: Failed to start Elasticsearch.
● logstash.service - logstash
Loaded: loaded (/etc/systemd/system/logstash.service; enabled; vendor preset: enabled)
Active: deactivating (stop-sigterm) since Tue 2021-02-23 14:12:36 EST; 31min ago
Main PID: 497 (java)
Tasks: 55 (limit: 4915)
Memory: 985.1M
CGroup: /system.slice/logstash.service
└─497 /usr/share/logstash/jdk/bin/java -Xms1g -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyO…
Feb 23 14:43:23 SELKS logstash[497]: [2021-02-23T14:43:23,532][WARN ][org.logstash.execution.ShutdownWatcherExt] {"inflight_count"=>0, "stalling_threads_info…
Feb 23 14:43:26 SELKS logstash[497]: [2021-02-23T14:43:26,752][WARN ][logstash.outputs.elasticsearch][main] Attempted to resurrect connection to dead ES inst…
Feb 23 14:43:26 SELKS logstash[497]: [2021-02-23T14:43:26,923][WARN ][logstash.outputs.elasticsearch][main] Attempted to resurrect connection to dead ES inst…
Feb 23 14:43:28 SELKS logstash[497]: [2021-02-23T14:43:28,605][WARN ][org.logstash.execution.ShutdownWatcherExt] {"inflight_count"=>0, "stalling_threads_info…
Feb 23 14:43:31 SELKS logstash[497]: [2021-02-23T14:43:31,759][WARN ][logstash.outputs.elasticsearch][main] Attempted to resurrect connection to dead ES inst…
Feb 23 14:43:31 SELKS logstash[497]: [2021-02-23T14:43:31,932][WARN ][logstash.outputs.elasticsearch][main] Attempted to resurrect connection to dead ES inst…
Feb 23 14:43:33 SELKS logstash[497]: [2021-02-23T14:43:33,698][WARN ][org.logstash.execution.ShutdownWatcherExt] {"inflight_count"=>0, "stalling_threads_info…
Feb 23 14:43:36 SELKS logstash[497]: [2021-02-23T14:43:36,766][WARN ][logstash.outputs.elasticsearch][main] Attempted to resurrect connection to dead ES inst…
Feb 23 14:43:36 SELKS logstash[497]: [2021-02-23T14:43:36,942][WARN ][logstash.outputs.elasticsearch][main] Attempted to resurrect connection to dead ES inst…
Feb 23 14:43:38 SELKS logstash[497]: [2021-02-23T14:43:38,777][WARN ][org.logstash.execution.ShutdownWatcherExt] {"inflight_count"=>0, "stalling_threads_info…
Hint: Some lines were ellipsized, use -l to show in full.
● kibana.service - Kibana
Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-02-23 14:22:54 EST; 20min ago
Docs: https://www.elastic.co
Main PID: 4121 (node)
Tasks: 11 (limit: 4915)
Memory: 159.4M
CGroup: /system.slice/kibana.service
└─4121 /usr/share/kibana/bin/../node/bin/node /usr/share/kibana/bin/../src/cli/dist --logging.dest=/var/log/kibana/kibana.log --pid.file=/run/kiba…
Feb 23 14:22:54 SELKS systemd[1]: Started Kibana.
● evebox.service - EveBox Server
Loaded: loaded (/lib/systemd/system/evebox.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-02-23 14:08:20 EST; 35min ago
Main PID: 491 (evebox)
Tasks: 9 (limit: 4915)
Memory: 19.2M
CGroup: /system.slice/evebox.service
└─491 /usr/bin/evebox server
Feb 23 14:08:20 SELKS systemd[1]: Started EveBox Server.
Feb 23 14:08:20 SELKS evebox[491]: 2021-02-23 14:08:20 INFO evebox::version: This is EveBox version 0.12.0 (rev: ba9d586); x86_64-unknown-linux-musl
Feb 23 14:08:20 SELKS evebox[491]: 2021-02-23 14:08:20 INFO evebox::server::main: Using temporary in-memory configuration database
Feb 23 14:08:20 SELKS evebox[491]: 2021-02-23 14:08:20 INFO evebox::sqlite::configrepo: Initializing SQLite database
Feb 23 14:08:20 SELKS evebox[491]: 2021-02-23 14:08:20 INFO evebox::sqlite::configrepo: Updating SQLite database to schema version 1
Feb 23 14:08:20 SELKS evebox[491]: 2021-02-23 14:08:20 ERROR evebox::server::main: Failed to get Elasticsearch version, things may not work righ…s error 111)
Feb 23 14:08:20 SELKS evebox[491]: 2021-02-23 14:08:20 INFO evebox::server::main: Starting server on 127.0.0.1:5636, tls=false
Hint: Some lines were ellipsized, use -l to show in full.
● molochviewer-selks.service - Moloch Viewer
Loaded: loaded (/etc/systemd/system/molochviewer-selks.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-02-23 14:14:39 EST; 29min ago
Process: 2085 ExecStart=/bin/sh -c /data/moloch/bin/node viewer.js -c /data/moloch/etc/config.ini >> /data/moloch/logs/viewer.log 2>&1 (code=exited, status=1/FAILURE)
Main PID: 2085 (code=exited, status=1/FAILURE)
Feb 23 14:14:39 SELKS systemd[1]: molochviewer-selks.service: Service RestartSec=1min 30s expired, scheduling restart.
Feb 23 14:14:39 SELKS systemd[1]: molochviewer-selks.service: Scheduled restart job, restart counter is at 4.
Feb 23 14:14:39 SELKS systemd[1]: Stopped Moloch Viewer.
Feb 23 14:14:39 SELKS systemd[1]: molochviewer-selks.service: Start request repeated too quickly.
Feb 23 14:14:39 SELKS systemd[1]: molochviewer-selks.service: Failed with result 'exit-code'.
Feb 23 14:14:39 SELKS systemd[1]: Failed to start Moloch Viewer.
● molochpcapread-selks.service - Moloch Pcap Read
Loaded: loaded (/etc/systemd/system/molochpcapread-selks.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-02-23 14:14:21 EST; 29min ago
Process: 2082 ExecStart=/bin/sh -c /data/moloch/bin/moloch-capture -c /data/moloch/etc/config.ini -m --copy --delete -R /data/nsm/ >> /data/moloch/logs/capture.log 2>&1 (code=exited, status=1/FAILURE)
Main PID: 2082 (code=exited, status=1/FAILURE)
Feb 23 14:14:21 SELKS systemd[1]: molochpcapread-selks.service: Service RestartSec=1min 30s expired, scheduling restart.
Feb 23 14:14:21 SELKS systemd[1]: molochpcapread-selks.service: Scheduled restart job, restart counter is at 4.
Feb 23 14:14:21 SELKS systemd[1]: Stopped Moloch Pcap Read.
Feb 23 14:14:21 SELKS systemd[1]: molochpcapread-selks.service: Start request repeated too quickly.
Feb 23 14:14:21 SELKS systemd[1]: molochpcapread-selks.service: Failed with result 'exit-code'.
Feb 23 14:14:21 SELKS systemd[1]: Failed to start Moloch Pcap Read.
scirius RUNNING pid 4135, uptime 0:20:46
ii elasticsearch 7.11.1 amd64 Distributed RESTful search engine built for the cloud
ii elasticsearch-curator 5.8.3 amd64 Have indices in Elasticsearch? This is the tool for you!\n\nLike a museum curator manages the exhibits and collections on display, \nElasticsearch Curator helps you curate, or manage your indices.
ii evebox 1:0.12.0 amd64 no description given
ii kibana 7.11.1 amd64 Explore and visualize your Elasticsearch data
ii kibana-dashboards-stamus 2020122001 amd64 Kibana 6 dashboard templates.
ii logstash 1:7.11.1-1 amd64 An extensible logging pipeline
hi moloch 2.2.3-1 amd64 Moloch Full Packet System
ii scirius 3.5.0-3 amd64 Django application to manage Suricata ruleset
ii suricata 1:2021012201-0stamus0 amd64 Suricata open source multi-thread IDS/IPS/NSM system.
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs tmpfs 798M 8.7M 790M 2% /run
/dev/sda1 ext4 484G 12G 448G 3% /
tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
tmpfs tmpfs 798M 0 798M 0% /run/user/1000
***@***.***:~$
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I used the one in /SELKS5-SELKS6/. No luck. |
Here's the most recent (two?) runs from Elasticsearch.log: [2021-02-23T14:08:40,776][INFO ][o.e.n.Node ] [SELKS] version[7.11.1], pid[849], build[default/deb/ff17057114c2199c9c1bbecc727003a907c0db7a/2021-02-15T13:44:09.394032Z], OS[Linux/4.19.0-14-amd64/amd64], JVM[AdoptOpenJDK/OpenJDK 64-Bit Server VM/15.0.1/15.0.1+9] |
Not to spam overmuch, but... Running updates directly from apt didn't set things to rights, either. Earlier, Elastic was giving some indexing errors. I found an earlier issue (#238) that I hoped would get around the problem, but there hasn't been much happiness to be found where Elastic is concerned. |
Here's what I'm getting when I run the install script (I killed Logstash before I ran this, else it would hang): selks-user@SELKS:
moloch_2.2.3-1_amd64.deb 100%[=============================================================================>] 78.86M 10.9MB/s in 7.4s 2021-02-23 15:14:50 (10.7 MB/s) - ‘moloch_2.2.3-1_amd64.deb’ saved [82686856/82686856]
Setting up sniffing interfacePlease supply a network interface(s) to set up SELKS Suricata IDPS thread detection on Configure threat detection for INTERFACE(S): The supplied network interface(s): ens33 DONE!
Starting Moloch DB set up% Total % Received % Xferd Average Speed Time Time Time Current Exited with ERRORFINISH of first time setup script - Tue 23 Feb 2021 03:17:58 PM EST Exited with FAILED selks-user@SELKS:~/SELKS/scripts/SELKS5-SELKS6$ |
It seems Elastic is not up? |
Still isn't. Now it's showing as "dead." I tried a fresh install from the 6.0 build, hoping to put back anything that might be missing and to start again as fresh as possible. Here's the latest health check report: selks-user@SELKS:~$ sudo selks-health-check_stamus -l Feb 23 20:49:01 SELKS systemd[1]: Starting LSB: Next Generation IDS/IPS... Feb 24 08:29:50 SELKS logstash[516]: [2021-02-24T08:29:50,891][WARN ][logstash.outputs.elasticsearch][main] Attempted to re… Feb 23 20:49:11 SELKS systemd[1]: kibana.service: Service RestartSec=3s expired, scheduling restart. Feb 23 20:55:02 SELKS systemd[1]: molochviewer-selks.service: Service RestartSec=1min 30s expired, scheduling restart. Feb 23 20:55:01 SELKS systemd[1]: molochpcapread-selks.service: Service RestartSec=1min 30s expired, scheduling restart. |
Ok - so if you tail the elasticsearch logs there should be some info > |
Elastic hasn't even built out a folder for itself in /var/log. Kibana and Logstash have folders, but Elastic has not generated one. |
I had to install an earlier version of Elastic and then upgrade it to the latest version to get it to behave itself semi-appropriately. Now it's failing again, but it has generated a log file. Here's what I got:
|
It seems incomplete - can you tail the last 200 lines please? |
Here's something a little more complete...
|
Does the Elasticsearch migration assistant run as part of the upgrade scripts? |
So that here is really the issue it seems - |
I have a SELKS installation here that I've successfully upgraded to SELKS 5, but now it's not making the transition to SELKS 6. Suricata and Scirius seem to have made the change, but Logstash hangs when I run the upgrade scripts, and Elasticsearch fails outright. Once Elastic fails, Moloch doesn't upgrade.
I've tried killing Logstash's processes directly, and that got the install script to run. Elastic promptly quit. At first, I noticed a number of what appeared to be Python dependencies missing, so I ran the dependency install script. At the most recent attempt, Logstash would not halt, so I did not see if installing the dependencies had an impact.
Here is my most recent health output:
selks-user@SELKS:~$ sudo selks-health-check_stamus
● suricata.service - LSB: Next Generation IDS/IPS
Loaded: loaded (/etc/init.d/suricata; generated)
Active: active (running) since Tue 2021-02-23 14:08:21 EST; 35min ago
Docs: man:systemd-sysv-generator(8)
Process: 846 ExecStart=/etc/init.d/suricata start (code=exited, status=0/SUCCESS)
Tasks: 14 (limit: 4915)
Memory: 1.4G
CGroup: /system.slice/suricata.service
└─909 /usr/bin/suricata -c /etc/suricata/suricata.yaml --pidfile /var/run/suricata.pid --af-packet -D -v --user=logstash
Feb 23 14:08:21 SELKS systemd[1]: Starting LSB: Next Generation IDS/IPS...
Feb 23 14:08:21 SELKS suricata[846]: Starting suricata in IDS (af-packet) mode... done.
Feb 23 14:08:21 SELKS systemd[1]: Started LSB: Next Generation IDS/IPS.
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-02-23 14:22:54 EST; 20min ago
Docs: https://www.elastic.co
Process: 3897 ExecStart=/usr/share/elasticsearch/bin/systemd-entrypoint -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE)
Main PID: 3897 (code=exited, status=1/FAILURE)
Feb 23 14:22:54 SELKS systemd-entrypoint[3897]: at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:150)
Feb 23 14:22:54 SELKS systemd-entrypoint[3897]: at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:75)
Feb 23 14:22:54 SELKS systemd-entrypoint[3897]: at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:116)
Feb 23 14:22:54 SELKS systemd-entrypoint[3897]: at org.elasticsearch.cli.Command.main(Command.java:79)
Feb 23 14:22:54 SELKS systemd-entrypoint[3897]: at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:115)
Feb 23 14:22:54 SELKS systemd-entrypoint[3897]: at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:81)
Feb 23 14:22:54 SELKS systemd-entrypoint[3897]: For complete error details, refer to the log at /var/log/elasticsearch/elasticsearch.log
Feb 23 14:22:54 SELKS systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
Feb 23 14:22:54 SELKS systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
Feb 23 14:22:54 SELKS systemd[1]: Failed to start Elasticsearch.
● logstash.service - logstash
Loaded: loaded (/etc/systemd/system/logstash.service; enabled; vendor preset: enabled)
Active: deactivating (stop-sigterm) since Tue 2021-02-23 14:12:36 EST; 31min ago
Main PID: 497 (java)
Tasks: 55 (limit: 4915)
Memory: 985.1M
CGroup: /system.slice/logstash.service
└─497 /usr/share/logstash/jdk/bin/java -Xms1g -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyO…
Feb 23 14:43:23 SELKS logstash[497]: [2021-02-23T14:43:23,532][WARN ][org.logstash.execution.ShutdownWatcherExt] {"inflight_count"=>0, "stalling_threads_info…
Feb 23 14:43:26 SELKS logstash[497]: [2021-02-23T14:43:26,752][WARN ][logstash.outputs.elasticsearch][main] Attempted to resurrect connection to dead ES inst…
Feb 23 14:43:26 SELKS logstash[497]: [2021-02-23T14:43:26,923][WARN ][logstash.outputs.elasticsearch][main] Attempted to resurrect connection to dead ES inst…
Feb 23 14:43:28 SELKS logstash[497]: [2021-02-23T14:43:28,605][WARN ][org.logstash.execution.ShutdownWatcherExt] {"inflight_count"=>0, "stalling_threads_info…
Feb 23 14:43:31 SELKS logstash[497]: [2021-02-23T14:43:31,759][WARN ][logstash.outputs.elasticsearch][main] Attempted to resurrect connection to dead ES inst…
Feb 23 14:43:31 SELKS logstash[497]: [2021-02-23T14:43:31,932][WARN ][logstash.outputs.elasticsearch][main] Attempted to resurrect connection to dead ES inst…
Feb 23 14:43:33 SELKS logstash[497]: [2021-02-23T14:43:33,698][WARN ][org.logstash.execution.ShutdownWatcherExt] {"inflight_count"=>0, "stalling_threads_info…
Feb 23 14:43:36 SELKS logstash[497]: [2021-02-23T14:43:36,766][WARN ][logstash.outputs.elasticsearch][main] Attempted to resurrect connection to dead ES inst…
Feb 23 14:43:36 SELKS logstash[497]: [2021-02-23T14:43:36,942][WARN ][logstash.outputs.elasticsearch][main] Attempted to resurrect connection to dead ES inst…
Feb 23 14:43:38 SELKS logstash[497]: [2021-02-23T14:43:38,777][WARN ][org.logstash.execution.ShutdownWatcherExt] {"inflight_count"=>0, "stalling_threads_info…
Hint: Some lines were ellipsized, use -l to show in full.
● kibana.service - Kibana
Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-02-23 14:22:54 EST; 20min ago
Docs: https://www.elastic.co
Main PID: 4121 (node)
Tasks: 11 (limit: 4915)
Memory: 159.4M
CGroup: /system.slice/kibana.service
└─4121 /usr/share/kibana/bin/../node/bin/node /usr/share/kibana/bin/../src/cli/dist --logging.dest=/var/log/kibana/kibana.log --pid.file=/run/kiba…
Feb 23 14:22:54 SELKS systemd[1]: Started Kibana.
● evebox.service - EveBox Server
Loaded: loaded (/lib/systemd/system/evebox.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-02-23 14:08:20 EST; 35min ago
Main PID: 491 (evebox)
Tasks: 9 (limit: 4915)
Memory: 19.2M
CGroup: /system.slice/evebox.service
└─491 /usr/bin/evebox server
Feb 23 14:08:20 SELKS systemd[1]: Started EveBox Server.
Feb 23 14:08:20 SELKS evebox[491]: 2021-02-23 14:08:20 INFO evebox::version: This is EveBox version 0.12.0 (rev: ba9d586); x86_64-unknown-linux-musl
Feb 23 14:08:20 SELKS evebox[491]: 2021-02-23 14:08:20 INFO evebox::server::main: Using temporary in-memory configuration database
Feb 23 14:08:20 SELKS evebox[491]: 2021-02-23 14:08:20 INFO evebox::sqlite::configrepo: Initializing SQLite database
Feb 23 14:08:20 SELKS evebox[491]: 2021-02-23 14:08:20 INFO evebox::sqlite::configrepo: Updating SQLite database to schema version 1
Feb 23 14:08:20 SELKS evebox[491]: 2021-02-23 14:08:20 ERROR evebox::server::main: Failed to get Elasticsearch version, things may not work righ…s error 111)
Feb 23 14:08:20 SELKS evebox[491]: 2021-02-23 14:08:20 INFO evebox::server::main: Starting server on 127.0.0.1:5636, tls=false
Hint: Some lines were ellipsized, use -l to show in full.
● molochviewer-selks.service - Moloch Viewer
Loaded: loaded (/etc/systemd/system/molochviewer-selks.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-02-23 14:14:39 EST; 29min ago
Process: 2085 ExecStart=/bin/sh -c /data/moloch/bin/node viewer.js -c /data/moloch/etc/config.ini >> /data/moloch/logs/viewer.log 2>&1 (code=exited, status=1/FAILURE)
Main PID: 2085 (code=exited, status=1/FAILURE)
Feb 23 14:14:39 SELKS systemd[1]: molochviewer-selks.service: Service RestartSec=1min 30s expired, scheduling restart.
Feb 23 14:14:39 SELKS systemd[1]: molochviewer-selks.service: Scheduled restart job, restart counter is at 4.
Feb 23 14:14:39 SELKS systemd[1]: Stopped Moloch Viewer.
Feb 23 14:14:39 SELKS systemd[1]: molochviewer-selks.service: Start request repeated too quickly.
Feb 23 14:14:39 SELKS systemd[1]: molochviewer-selks.service: Failed with result 'exit-code'.
Feb 23 14:14:39 SELKS systemd[1]: Failed to start Moloch Viewer.
● molochpcapread-selks.service - Moloch Pcap Read
Loaded: loaded (/etc/systemd/system/molochpcapread-selks.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-02-23 14:14:21 EST; 29min ago
Process: 2082 ExecStart=/bin/sh -c /data/moloch/bin/moloch-capture -c /data/moloch/etc/config.ini -m --copy --delete -R /data/nsm/ >> /data/moloch/logs/capture.log 2>&1 (code=exited, status=1/FAILURE)
Main PID: 2082 (code=exited, status=1/FAILURE)
Feb 23 14:14:21 SELKS systemd[1]: molochpcapread-selks.service: Service RestartSec=1min 30s expired, scheduling restart.
Feb 23 14:14:21 SELKS systemd[1]: molochpcapread-selks.service: Scheduled restart job, restart counter is at 4.
Feb 23 14:14:21 SELKS systemd[1]: Stopped Moloch Pcap Read.
Feb 23 14:14:21 SELKS systemd[1]: molochpcapread-selks.service: Start request repeated too quickly.
Feb 23 14:14:21 SELKS systemd[1]: molochpcapread-selks.service: Failed with result 'exit-code'.
Feb 23 14:14:21 SELKS systemd[1]: Failed to start Moloch Pcap Read.
scirius RUNNING pid 4135, uptime 0:20:46
ii elasticsearch 7.11.1 amd64 Distributed RESTful search engine built for the cloud
ii elasticsearch-curator 5.8.3 amd64 Have indices in Elasticsearch? This is the tool for you!\n\nLike a museum curator manages the exhibits and collections on display, \nElasticsearch Curator helps you curate, or manage your indices.
ii evebox 1:0.12.0 amd64 no description given
ii kibana 7.11.1 amd64 Explore and visualize your Elasticsearch data
ii kibana-dashboards-stamus 2020122001 amd64 Kibana 6 dashboard templates.
ii logstash 1:7.11.1-1 amd64 An extensible logging pipeline
hi moloch 2.2.3-1 amd64 Moloch Full Packet System
ii scirius 3.5.0-3 amd64 Django application to manage Suricata ruleset
ii suricata 1:2021012201-0stamus0 amd64 Suricata open source multi-thread IDS/IPS/NSM system.
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs tmpfs 798M 8.7M 790M 2% /run
/dev/sda1 ext4 484G 12G 448G 3% /
tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
tmpfs tmpfs 798M 0 798M 0% /run/user/1000
selks-user@SELKS:~$
The text was updated successfully, but these errors were encountered: