Trivial Description
Since updating to 21.11.11755 rancid is unable to carry out config fetching on routers. I have clarified there are no connection issues:
rancid@ixllvmva190:~$ bin/clogin hgrsjufw01
hgrsjufw01
spawn ssh -i /var/lib/rancid/.ssh/id_rsa -c aes256-ctr -x -l rancid hgrsjufw01
Last login: Wed Nov 24 05:12:58 2021 from 10.252.32.196
— JUNOS 19.4R3-S1.3 Kernel 64-bit JNPR-11.0-20201028.e1cef1d_buil
{primary:node0}rancid@HGRSJUFW01>
However config backups now seem to be failing. I have noticed the devices have changed from "juniper" to "juniper-srx" I'm not sure if this holds any bearing.
Attachments
Activity
Disabled SRX variant of rancid map in r11765 (rolling updates).
As written in Rancid comments "juniper-srx type is for SRX with ThreatSTOP"
While you not show device overview page we will not be able to resolve this issue in any way.
Errors in rancid log will not help.
Thanks for the response Adam, Rancid is on version 3.3.0. It seems when the rancid script runs on the cron job it reverts back to junos-srx hardware string. Looking at the rancid log it shows the following error when junos-srx is the hardware string - "ERROR: hostname configuration appears truncated"
Please show/attach screenshot of device overview page.
(There should be hardware info too).
About a year ago we improved the juniper to rancid mapping :
$config['os'][$os]['rancid'][] = [ 'name' => 'juniper-srx', 'rancid_min' => '3', 'hardware' => '/SRX/i' ];
$config['os'][$os]['rancid'][] = [ 'name' => 'junos', 'rancid_min' => '3.11' ]; // Rancid generator os map
$config['os'][$os]['rancid'][] = [ 'name' => 'juniper' ]; // Rancid generator os map
Things should only get mapped as juniper if the rancid version is >3 and it has SRX in the hardware string.
It seems that rancid 3.11+ wants "junos" and the default if neither of these are true is "juniper"
What version of rancid are you using and what's the hardware string of the devices?
I've not used rancid for a decade though 
Yes we are using the observium script to generate rancid and populate the router.db file, I’m not sure why the devices switched to -srx after running the observium update.
are you using the observium script to generate rancid configurations?
This was fixed by changing the device type in the router.db file from "juniper-srx" to "juniper"
Thanks!