Data storage issues
If FortiWeb cannot locally store
any data such as logs, reports, and web site backups for anti-defacement, it might have a damaged or corrupted hard disk. For fixes, see
“Hard disk corruption or failure”.
If FortiWeb has been storing data but has suddenly stopped, first verify that FortiWeb has not used all of its local storage capacity by entering this CLI command:
diagnose system mount list
to display disk usage for all mounted file systems, such as:
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/ram0 61973 31207 30766 50% /
none 262144 736 261408 0% /tmp
none 262144 0 262144 0% /dev/shm
/dev/sdb2 38733 25119 11614 68% /data
/dev/sda1 153785572 187068 145783964 0% /var/log
/dev/sdb3 836612 16584 777528 2% /home
| You can use alerts to notify you when FortiWeb has almost consumed its hard disk space. See “SNMP traps & queries”. You can also configure FortiWeb to overwrite old logs rather than stopping logging when the disk is full. See “When log disk is full”. (Keep in mind, however, that this may not prevent full disk problems for other features. To free disk space, delete files such as auto-learning data and old reports that you no longer need.) |
If a full disk is not the problem, examine the configuration to determine if an administrator has disabled those features that store data.
If neither of those indicate the cause of the problem, verify that the disk’s file system has not been mounted in read-only mode, which can occur if the hard disk is experiencing problems with its write capabilities (see
“Hard disk corruption or failure”).