Hi Guys
I have a few questions as I must be missing something.
I struggled with this in my test deployment but eventually got it to work after a load of fiddling where I increased the timeout and tried different hostnames for the device in the router.db file and on the gui.
However since I have redeployed the system to a production variant, I am once again getting the timeouts. I understand this is due to the size of the fortigates configs but I am not sure what to try as all the fiddling I have done to try get it to work hasn’t helped.
Nov 23 11:00:17 oxidized oxidized[1919200]: W, [2023-11-23T11:00:17.304632 #1919200] WARN – : /FORTIGATE status no_connection, retry attempt 1
Nov 23 11:00:17 oxidized oxidized[1919200]: W, [2023-11-23T11:00:17.304787 #1919200] WARN – : /FORTIGATE status no_connection, retry attempt 1
Nov 23 11:10:20 oxidized oxidized[1919200]: W, [2023-11-23T11:10:20.359146 #1919200] WARN – : FORTIGATE raised Timeout::Error with msg “execution expired”
Nov 23 11:10:20 oxidized oxidized[1919200]: W, [2023-11-23T11:10:20.359361 #1919200] WARN – : FORTIGATE raised Timeout::Error with msg “execution expired”
Nov 23 11:10:20 oxidized oxidized[1919200]: W, [2023-11-23T11:10:20.656281 #1919200] WARN – : /FORTIGATE status no_connection, retries exhausted, giving up
Nov 23 11:10:20 oxidized oxidized[1919200]: W, [2023-11-23T11:10:20.656635 #1919200] WARN – : /FORTIGATE status no_connection, retries exhausted, giving up
oxidized@dc1-oxidized:~$ cat .config/oxidized/config
username: username
password: password
resolve_dns: true
interval: 3600
use_syslog: false
debug: false
threads: 30
use_max_threads: true
timeout: 600
retries: 1
prompt: !ruby/regexp /^([\w.@-]+[#>]\s?)$/
rest: 0.0.0.0:8888
next_adds_job: false
The above is the top part of the config file. I know the fortigate backups work as I have smaller fortigates that backup just fine with no issues at all.
Any help would be great.
Regards,
Josh