Back to where I started with logging into Elastix

rs232c

Joined
Sep 5, 2009
Messages
47
Likes
0
Points
0
#1
It's been awhile but now the system works fine but I cannot properly log into Elastix. I get to the Systems Resources page after login but have no graphic for the Hard Drive. Clicking on anything will return me to the login page to sign in again and I cannot view anything other than the top of the first login page up to and including where it says Hard Drives.

Viewing the source (or the php output) I discover I am missing a table. The code snippet is:

<table width="99%" border="0" cellspacing="0" cellpadding="0" align="center">
<tr class="moduleTitle">
<td class="moduleTitle" valign="middle">&nbsp;&nbsp;<img src="images/hd.png" border="0" align="absmiddle">&nbsp;&nbsp;Hard Drives</td>
</tr>
<tr>
<td>
<table width="100%" border="0" cellspacing="0" cellpadding="0" class="tabForm">
<====== NOTICE MISSING TABLE INFO
</table>
</td>
</tr>
</table>
</td>
</tr>
</table>

<div align="center" class="copyright">Elastix is licensed under GPL by PaloSanto Solutions. 2006 - 2009.</div>
<br>
</td>
</tr>
</table>
</body>
</html>
Notice the missing blank table entry. This is what is missing on the page.

My question is: Is it possible to repair the php output or source file to correct this, or am I back to reinstalling and configuring a clean system again?

Thank You.
 

rs232c

Joined
Sep 5, 2009
Messages
47
Likes
0
Points
0
#2
ISSUE RESOLVED

I traced the solution backwards by rolling up my sleeves. Considering how little I really understand about Linux, Asterisk, Elastix, PHP, MYSQL and even worse telephones sometimes the impossible does happen I guess.

Q: Why was the Elastix page missing a table and not displaying correctly?
A: Because the PHP preprocessor was unable to connect to MYSQL.

Q: Why was PHP unable to connect to MYSQL?
A: Because the MYSQL service was not running and would not start.

Q: Why wouldn't the MYSQL service start?
A: MYSQL wouldn't start because the partion was full and had no space to run.

Q: Why was the partition full?
A: Because the monitored calls filled up the partition.

The solution was to clear out the .wav files from the monitor directory which brought everything back to life. The long term solution is going to be to figure out how to create a cron job to delete .wav files older than some number of days that seems appropriate for the user environment.

I know I need formal training for this stuff and this is exactly how I had to think it through. It was a grim reminder just how stuck I am in a WinTel world.

Thank you and perhaps this may help someone else - resolve the same issue much faster of course.

Status: RESOLVED.
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#3
Welcome to a real OS :)

Code:
if  [ " `/bin/df -h|/bin/grep -r "/$"|/bin/sed 's/%//'|/bin/awk '$5 > 90 {print "The " $2 , " Root partition mounted on",$1, "is",$5 ,"% full, I will delete files older than 30 days" }'`" ];then /usr/bin/find /var/spool/asterisk/monitor/*.wav -mtime +30 -delete;fi



I offer a "one-liner" that will conditionally delete all monitor files older than 30 days, but only if the root partition gets fuller than 90%, it is a just a sample of the power of many of the basic shell functions and a reminder that cron scripts run in a restricted shell, which is why they are called with a full path.

maybe

/usr/bin/find /var/spool/asterisk/monitor/*.wav -mtime +30 -delete

is sufficient for your purposes, a properly set up cron system will email you the results, the first example is silent until used, the second one will annoy you every day :)
 

Members online

Latest posts

Forum statistics

Threads
30,902
Messages
130,886
Members
17,563
Latest member
dineshr
Top