Hello Stefan,
The api mode specifies how the director will talk to the other side. Api mode 2 is basically json. You can try it out yourself in the bconsole:
$ bconsole
...
Enter a period (.) to cancel a command.
*.api 2
{
"jsonrpc": "2.0",
"id": null,
"result": {
"api": 2
}
}*list jobs
{
"jsonrpc": "2.0",
"id": null,
"result": {
"jobs": []
}
}*
Does this work for you as well ? Could you enable debug tracing
on the director before trying to connect with the webui ?
You can do so with `bconsole <<< "setdebug level=500
trace=1 director"`. Please post the trace file once you have
tried connecting.
You can turn it off afterwards like so: `bconsole <<<
"setdebug level=20 trace=0 director"`.
Kind Regards
Sebastian Sura
--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bareos-users/d8372aed-0db0-498e-b989-2615998116aen%40googlegroups.com.
-- Sebastian Sura sebasti...@bareos.com Bareos GmbH & Co. KG Phone: +49 221 630693-0 https://www.bareos.com Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz
Hi Stefan,
the director probably refuses to restart because of the systemd restart limit. Try executing
systemctl reset-failed bareos-dir.service
systemctl start bareos-dir.service
as can be seen here: 'Feb 07 16:42:21 dsme01 systemd[1]:
bareos-director.service: Start request repeated too quickly'
Could you send us a debug log of the director ? I.e. do
$ bconsole
*setdebug level=500 trace=1 dir
*.api 2
This should show us why the director keeps crashing for you!
Kind Regards
Sebastian Sura