err_log.xml becoming too large

Where is this err_log.xml? On the server or on a client?

Alex

If you are getting errors in the err.XML file then there are some serious
problems with your installation. Xibo will only log to that file if all
else fails.

Could you paste the last few lines of that file here? You can delete that
file safely.

If the version number is not on the login page then you should definitely
upgrade as you have an old version.

On 12 Mar 2010 14:43, "aaron" <email address hidden> wrote:

New question #104097 on Xibo:
https://answers.launchpad.net/xibo/+question/104097

Hello

I have inherited a server running the xibo software.

The err_log.xml has become so large it is causing problems.

I've reviewed some similar items here in the forum and I haven't worked out
a solution.

can some one please give me a step by step on how to :

1 - check my version of xibo
2 - find the correct interface to truncate this err_log.xml file for it's
too late

--
You received this question notification because you are a member of Xibo
Developers, which is an answer contact for Xibo.

Thanks for responding.

The err_log.xml is located on my server in C:\xampp\xampplite\htdocs\xibo

it is currently 1.6Gb in size and growing.

I'm not sure how to view the log properly to relay it's message for you.

Have you got a client running on the same machine as the server?

http://tailforwin32.sourceforge.net/

You can use the "tail" app to view the last lines of that file.

Alex

Thanks Alex
How do I check to see if a client is running on the server ?

here is the last entry from the err_log.xml

this one was repeated over and over

The query [INSERT INTO log (logdate, type, page, function, message, RequestUri, RemoteAddr, UserAgent, UserID, displayID, scheduleID, layoutID, mediaID) VALUES ('2010-03-12 09:44:49','error', '', '', '<errormsg>Function eregi() is deprecated</errormsg>\n<errornum>8192</errornum>\n<errortype></errortype>\n<scriptname>C:\\xampp\\xampplite\\htdocs\\xibo\\3rdparty\\nuSoap\\nusoap.php</scriptname>\n<scriptlinenum>3728</scriptlinenum>\n', '/xibo/xmds.php', '10.10.2.30', 'Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 2.0.50727.3082)', 0, 0, 0, 0, 0)] failed to execute<br />MySQL error: Table '.\xibo\log' is marked as crashed and should be repaired

<errormsg>Function eregi() is deprecated</errormsg>
<errornum>8192</errornum>
<errortype></errortype>
<scriptname>C:\xampp\xampplite\htdocs\xibo\3rdparty\nuSoap\nusoap.php</scriptname>
<scriptlinenum>4217</scriptlinenum>

"MySQL error: Table '.\xibo\log' is marked as crashed and should be repaired"

There's your problem then. You need to get your log table in MySQL fixed, and then probably truncate it.

So, from mysql in your database, you need to run the following queries:

REPAIR TABLE log;
TRUNCATE log;

If your server is collecting alot of log output, make sure you've got debugging and auditing switched off in the Xibo server settings and auditing off on each of your display records on the server too.

If it's still generating too much log output, you need to periodically connect to mysql and do the TRUNCATE command as above to empty the log table.

Alex

excellent Alex.

Thank you so much for your help. This error log was cascading into other trouble on my network and it is now solved.

Thank you very much for the support.