This article explains an issue where SRX1500 reboots constantly due to Linux "watchdogd" getting struck.
SSD failure detected, system is going to reboot!! 2025-01-08T10:50:56.831325+07:00 SRX rsyslogd: -- MARK -- 2025-01-08T11:03:01.150239+07:00 SRX rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="5276" x-info="http://www.rsyslog.com"] rsyslogd was HUPed 2025-01-08T11:30:57.031489+07:00 SRX rsyslogd: -- MARK -- 2025-01-08T11:50:57.132341+07:00 SRX rsyslogd: -- MARK -- 2025-01-08T12:10:57.233097+07:00 SRX rsyslogd: -- MARK -- 2025-01-08T12:12:01.338011+07:00 SRX rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="5276" x-info="http://www.rsyslog.com"] rsyslogd was HUPed 2025-01-08T12:30:57.332334+07:00 SRX rsyslogd: -- MARK -- 2025-01-08T12:50:57.433339+07:00 SRX rsyslogd: -- MARK -- 2025-01-08T13:10:57.533825+07:00 SRX rsyslogd: -- MARK -- 2025-01-08T13:18:01.114926+07:00 SRX rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="5276" x-info="http://www.rsyslog.com"] rsyslogd was HUPed 2025-01-08T13:30:57.633826+07:00 SRX rsyslogd: -- MARK -- SSD failure detected, system is going to reboot
This issue is reported in PR1845143 and has been fixed in the following junOS releases:
22.4R3-S6
23.2R2-S3
23.4R2-S4
24.2R2
24.4R1
24.4R2
25.1R1
Workaround:
srx@user:~ # vhclient -s srx@user-node:~# cd /usr/sbin srx@user-node:/usr/sbin# cp watchdogd watchdogd_copy srx@user-node:/usr/sbin# rm watchdogd srx@user-node:/usr/sbin# ps -x | grep watchdogd Warning: bad ps syntax, perhaps a bogus '-'? 13284 ? Ss 0:00 /usr/sbin/watchdogd 13547 pts/0 S+ 0:00 grep watchdogd srx@user-node:/usr/sbin# kill -15 13284
srx@user-node:/usr/sbin# ps -x | grep watchdogd Warning: bad ps syntax, perhaps a bogus '-'? 13557 pts/0 S+ 0:00 grep watchdogd
2025-01-17 : Article Created
2025-01-21 : Minor edits