fpc,xme

fpc's People

Contributors

Stargazers

Watchers

fpc's Issues

socat issue

Thanks for the build!!

Wondering if you could help?

I have an indexer running per your build and the logs show these errors for moloch_socat.

7/19/2018 8:20:22 PM2018-07-19 16:20:22,491 INFO spawned: 'moloch_viewer' with pid 77
7/19/2018 8:20:22 PM2018-07-19 16:20:22,495 INFO spawned: 'moloch_capture' with pid 78
7/19/2018 8:20:22 PM2018-07-19 16:20:22,498 INFO spawned: 'moloch_socat' with pid 79
7/19/2018 8:20:22 PM2018-07-19 16:20:22,631 INFO exited: moloch_socat (exit status 1; not expected)

Should I just ignore? I cant find the call to the moloch_socat in the Dockerfile.. (?)

I tried running the startsocat script in the container shell and met with this:

root@fpc-moloch:/data# ./startsocat.sh
2018/07/19 17:16:16 socat[181] E SSL_CTX_use_certificate_file(): error:02001002:system library:fopen:No such file or directory

Also, on the Sensor last bit of logs...

7/19/2018 8:48:35 PMGenerating RSA private key, 1024 bit long modulus
7/19/2018 8:48:35 PM.................++++++
7/19/2018 8:48:35 PM........................++++++
7/19/2018 8:48:35 PMe is 65537 (0x10001)
7/19/2018 8:48:35 PMSniffing packets on eth1...
7/19/2018 8:48:35 PMdropped privs to nobody
7/19/2018 8:48:35 PMtcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 262144 bytes

There is no pcaps being sent to the indexer, the indexer sits idle.

Any ideas? Something I missed?

Thank you!

unprocessed pcaps cause moloch-capture start failures

Any ideas on why it is when pcaps are collected and sitting in the indexer host /data/pcap folder yet to be processed and a restart of container or host occurs, startup then fails with the moloch_capture in the fpc-moloch container?

To get all working again I must: