Unable to see probes in frontend about irma-probe HOT 11 CLOSED

@andrewjones216, does the celery logs on the probes and the frontend show that they are connected to the brain ?

a thing I may think of for your issue is collision on hostnames, but I assume that you have different hostnames for your different virtual machines ?

If it is still not solved, come on IRC and leave me a message. We can discuss more about your issue and try to find a solution quickly.

from irma-probe.

Hi kamino,

The celery logs showed a discrepancy in time between the brain and one of the probes. Once I'd fixed that the probes are showing in the frontend.

Part2:
I have two different hosts for Probes connected at the moment:
IRMA-Windows: Kaspersky/ Sophos/ Avira and GDATA
IRMA-Linux: ClamAV

What I see in the interface is "ClamAV/ GDATA/ Kaspersky/ Sophos and brain".
When pressing 'scan for malwares' I get a red bar at the top of the page that says "API error". Could this error be to do with the mystery probe 'brain'?

Cheers

from irma-probe.

@andrewjones216 : the brain should not appear in the probe list. Can you double check the rabbitmq vhosts you configured ? In the expected configuration, the brain should not be there.

from irma-probe.

No brain listed as a vhost in rabbitmq.
Cheers
Andrew

from irma-probe.

brain is a queue on "mqbrain" vhost, available probes list is the queues list on "mqprobe" vhost. Check your brain and frontend config files to see if the "brain" queue is correctly set on the "mqbrain" vhost (check here https://github.com/quarkslab/irma-brain/blob/master/config/brain.ini#L4 and here https://github.com/quarkslab/irma-frontend/blob/master/config/frontend.ini#L22 /opt/irma/irma-frontend/config/frontend.ini and /opt/irma/irma-brain/config/brain.ini).

from irma-probe.

That's worked well thank you, for some reason I had "brain" as the username for mqprobe in the brain.ini file.
New territory for me having never used celery, rabbitmq or even Debian! IRMA looks like a good fit for what we need.

I do still get the "API error" red bar after clicking "Scan for malwares"?

Cheers
Andrew

from irma-probe.

Hi @andrewjones216,
Can you give us logs from your server? They should be located at /var/log/supervisor/frontend_api.log.

Regards,

from irma-probe.

Hi @guillaumededrie,
I've checked on my server and I do not have a folder "supervisor" located in /var/log/...

Cheers
Andrew

from irma-probe.

Hum, your are using the new Debian 8.1 version, is that right?

from irma-probe.

I'm using Debian 8.0 on all the VM's

from irma-probe.

feel free to re-open an issue if you are still stuck with this problem.

from irma-probe.