Strange Database Error on Dial Server
Posted: Mon Oct 10, 2016 10:58 amSo, we have a set up with 7 dial servers, 2 web servers and a data base server. We're in the process of moving the operation offsite to a managed data center. We're doing it in two stages so last friday we shipped 3 of our dial servers and 1 web server leaving us with a still functioning stack of 4 dial servers 1 web server and our core db server.
Anyway, shortly after we took the other servers offline one of our dial servers started behaving badly and throwing this error
WARNING[3830]: db.c:332 ast_db_put: Couldn't execute statement: SQL logic error or missing database
I can still connect to the database from that server but I can't figure out where this error is coming from, seems like something may have been corrupted.
UPDATE: it looks like something is rapidly eating up the disk space on the server; still don't know the source.
UPDATE2 (PROBLEM SOLVED): df -i shows the inode usage maxed... the culprit was the /tmp/ directory with over 6.5 million little files... they appear to be asterisk creations. Once purged the problem went away. Could anyone explain to me what these files are (they look like this: ASUBtmpD_22628235_1470156868) and if they are necessary (can I write a shell script to programatically delete them) and lastly, why there isn't already built in clean up for these?
Anyway, shortly after we took the other servers offline one of our dial servers started behaving badly and throwing this error
WARNING[3830]: db.c:332 ast_db_put: Couldn't execute statement: SQL logic error or missing database
I can still connect to the database from that server but I can't figure out where this error is coming from, seems like something may have been corrupted.
UPDATE: it looks like something is rapidly eating up the disk space on the server; still don't know the source.
UPDATE2 (PROBLEM SOLVED): df -i shows the inode usage maxed... the culprit was the /tmp/ directory with over 6.5 million little files... they appear to be asterisk creations. Once purged the problem went away. Could anyone explain to me what these files are (they look like this: ASUBtmpD_22628235_1470156868) and if they are necessary (can I write a shell script to programatically delete them) and lastly, why there isn't already built in clean up for these?