While pushing/deploying config from CSO, the CSO reports Error:
###### The response of Config Server is {"status": "SUCCESS", "deviceid": "48e44c4b-9713-4bdd-8dd5-ffe858baca2e", "connectionid": "48e44c4b-9713-4bdd-8dd5-ffe858baca2e:JUNOS", "cmdstatus": "SENT", "detail": [{"status": "SUCCESS", "result": "<nc:rpc-reply xmlns:nc=\"urn:ietf:params:xml:ns:netconf:base:1.0\" xmlns:junos=\"http://xml.juniper.net/junos/20.4R0/junos\" message-id=\"101\">\n<output>\nls: */: No such file or directory\nmkdir: configbackup: No space left on device\ncould not open file 'configbackup/version.cfg' Wrote 0 lines of output to 'configbackup/version.cfg'\n/tmp/fetch_cfg.sh: cannot create configbackup/time.cfg: No such file or directory\ncat: configbackup/version.cfg: No such file or directory\ncould not open file 'configbackup/raw.cfg' Wrote 0 lines of output to 'configbackup/raw.cfg'\ncould not open file 'configbackup/set.cfg' Wrote 0 lines of output to 'configbackup/set.cfg'\ncould not open file 'configbackup/xml.cfg' Wrote 0 lines of output to 'configbackup/xml.cfg'\ncould not open file 'configbackup/commit.cfg' Wrote 0 lines of output to 'configbackup/commit.cfg'\nsed: configbackup/xml.cfg: No such file or directory\nsed: configbackup/xml.cfg: No such file or directory\nsed: configbackup/xml.cfg: No such file or directory\ncould not open file 'configbackup/xml.inheritance.cfg' Wrote 0 lines of output to 'configbackup/xml.inheritance.cfg'\nsed: configbackup/xml.inheritance.cfg: No such file or directory\nsed: configbackup/xml.inheritance.cfg: No such file or directory\nsed: configbackup/xml.inheritance.cfg: No such file or directory\ncd: configbackup: No such file or directory\ntar: *.cfg: Cannot stat: No such file or directory\ntar: Write error\ntar: Error exit delayed from previous errors.\nAll config saved to ====configbackup/all_config.tgz====\n</output>\n</nc:rpc-reply>\n]]>]]>\n"}], "queue": "cs_to_cms_notification_queue.SyncConfig_d48c22f4-871c-45ab-98a7-b3410502cca7", "serviceid": null, "details": "", "requestid": "UI_0f5d1825-0fae-c93a-f172-75469beab794,kCqm,MYkt,vAeV.2c881184-8b16-11ef-a0db-d2633cbfd931"}, retry 1, task d48c22f4-871c-45ab-98a7-b3410502cca7 ######
"show system storage" shows -ve value for Available space for /dev/gpt/var which is mounted as /.mount/var
[email protected]> show system storage
Filesystem Size Used Avail Capacity Mounted on
/dev/gpt/junos 4.0G 891M 2.8G 24% /.mount
/dev/gpt/config 290M 1.2M 266M 0% /.mount/config
/dev/gpt/var 3.1G 3.1G -243.1M 108% /.mount/var <<<<<<
tmpfs 1.7G 256K 1.7G 0% /.mount/tmp
tmpfs 318M 1.1M 316M 0% /.mount/mfs
host_corefiles 4.5G 219M 4.1G 5% /.mount/var/crash/corefiles
host_volatile 5.9G 4.0K 5.9G 0% /.mount/var/log/host
host_log 4.5G 219M 4.1G 5% /.mount/var/log/hostlogs
host_traffic_log 4.5G 219M 4.1G 5% /.mount/var/traffic-log
Review the "show system storage" output and look for any -ve value for any Partitions.
If we find any:
go to SRX shell prompt (start shell user root) and CD to the directory.
Do "ls -lStrh" for sorting the files by file size
Verify and clear the content of the largest file consuming space. (cat /dev/null > file.log)
cat /dev/null > file.log
Example:
{primary:node1}root@srx1500> start shell root@srx1500:~ # cd /.mount/varroot@srx1500:/.mount/var # pwd/var
root@srx1500:/.mount/var # ls -lStrhtotal 176
drwxr-xr-x 1 root wheel 2.1G Jan 1 1980 jet.log <<<
drwxr-xr-x 1 root wheel 16K Jan 1 1980 host-rw-r--r-- 1 root wheel 3.3K Jun 16 2023 BSD.var.distdrwxr-xr-x 3 root wheel 4.0K Apr 22 2024 install_diskdrwxr-xr-x 2 root wheel 512B Jun 28 22:43 accountdrwxr-xr-x 4 root wheel 512B Jun 28 22:43 atdrwxr-x--- 2 root wheel 512B Jun 28 22:43 backupsdrwxr-x--- 3 root wheel 512B Jun 28 22:43 cron
root@jsrx1500:/.mount/var # cat /dev/null > jet.log
NOTE : The error is related to disk space available on the SRX. It could be with any partition or any file consuming the disk space. Review the "show system storage" output and take required action. If the issue still persists, raise a ticket with JTAC.