Written By: |
Jim Reinhardt |
---|---|
Manufacturer: |
Avaya |
Product: |
Session Border Controller Enterprise |
Version: |
R8, R10 |
Patch Information: |
|
Ticket Number(s): |
Description:
Full disk alerts have been received by the customers NMS coming from their Avaya Aura Session Border Controller.
Related Articles:
Problem Clarification:
Avaya Aura SBC is showing alerts in the console as well having issues writing other log files.
Cause:
Logging into the SBC as root we can see that the filesystem is full and the /var/ partition is the source of it
sbc302 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda6 9.1G 1.5G 7.2G 17% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
/dev/sda13 56G 34G 20G 64% /archive
/dev/sda1 923M 50M 826M 6% /boot
/dev/sda11 30G 713M 28G 3% /usr/local
/dev/sda8 4.5G 4.3G 0 100% /var
Solution:
We will need to find out what files in the /var directory are filing up the disk.
[root@asbc302 var]# pwd
/var
[root@asbc302 var]# du -sh *
4.0K account
880K cache
4.0G crash
8.0K db
8.0K empty
4.0K games
35M lib
4.0K local
16K lock
300M log
16K lost+found
0 mail
4.0K nis
4.0K opt
4.0K preserve
120K run
112K spool
4.0K tmp
4.0K yp
[root@asbc302 var]#
We can see that the /var/crash/ directory has 4.0 GB of data in it and is our likely source of the issue. Usually, the files on any /var/ partition can be deleted with the exception of database directories.
In the /var/crash partition we can see a whole bunch of files.
root@asbc302 crash]# ls
127.0.0.1-2020-07-11-09:11:37 127.0.0.1-2020-09-03-16:31:27
127.0.0.1-2020-07-13-03:25:24 127.0.0.1-2020-09-05-02:45:31
127.0.0.1-2020-07-15-08:33:42 127.0.0.1-2020-09-06-21:09:28
127.0.0.1-2020-07-17-10:09:04 127.0.0.1-2020-09-08-10:19:13
[root@asbc302 crash]# ls -lh '127.0.0.1-2020-07-15-08:33:42'
total 255M
-rw------- 1 root root 255M Jul 15 08:34 vmcore
-rw-r--r-- 1 root root 214K Jul 15 08:33 vmcore-dmesg.txt
We need to delete these files to resolve the issue, repeat this by calling out the file names as arguments to the Linux rm command to ensure only the correct files are removed.
root@asbc302 127.0.0.1-2020-07-13-03:25:24]# rm vmcore vmcore-dmesg.txt
rm: remove regular file `vmcore'? y
rm: remove regular file `vmcore-dmesg.txt'? y
[root@asbc302 127.0.0.1-2020-07-13-03:25:24]#
Disclaimer: intlx Solutions Knowledge Base
The information contained in this knowledge base ("Content") is provided for informational purposes only and is intended to be a general resource. intlx Solutions does not guarantee the accuracy, completeness, or timeliness of the Content.
Use at Your Own Risk: By accessing and using the Content, you agree that you do so at your own risk. intlx Solutions assumes no responsibility for any errors or omissions in the Content, nor for any damages or losses you may suffer arising out of or related to the use of the Content.
Current Customers: If you are a current intlx Solutions customer and have questions or require further clarification on any information presented here, please do not hesitate to contact our support team directly. They are available to assist you and ensure you have the most up-to-date information specific to your needs.
Not a Customer? If you are not currently an intlx Solutions customer but are interested in learning more about our solutions and how we can help your business, please click here. We look forward to the opportunity to discuss your needs and explore how a partnership with intlx Solutions can benefit you.
Thank you for your understanding.