-
Notifications
You must be signed in to change notification settings - Fork 55
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
IRMA in maintenance mode #75
Comments
It usually means no probe available (it may take several seconds for probes to show up). If it fails after a minute check the status of celery daemons: $ vagrant ssh <vm_name if multiple vms>
$ sudo journalclt -fu irma.probe_app
# If no errors look at others
$ sudo journalclt -fu irma.frontend_app
$ sudo journalclt -fu irma.result_app |
Hereby attached with logfile, it does looked suspicious.. Before this happened I tested the installation twice resulting in the same problem. |
could you do the same command with scan_app: $ sudo journalclt -fu irma.scan_app |
Hereby attached with the second logfile. |
Could you try to restart scan_app.
|
Tested, but still producing the same output as both logs shown with: |
probe default config for rabbitmq server is "brain.irma" (config in file /opt/irma/irma-probe/current/config/probe.ini) |
Sorry, where should i start from here? |
try to ssh inside the vm and test various command like
|
Hi there, After some further testing I think I messed up some of the network interfaces in my VM. However, should I open a new issue because I have a further problem to ask.. |
Good to hear. For your new problem it is better to go in a new issue. |
Hi, would like to ask for help again.
My installation was a success after referring to my post #74. I am able to see the web interface on 172.16.1.30 for the first time.
However, the next time I reboot the machine and also manually turn on ansible_brainirma in VM, I am getting a message whereas it shows "Irma is currently in maintenance mode".
Help is greatly appreciated..
The text was updated successfully, but these errors were encountered: