Partial page output (permissions ok)

[redbeardmcg]

I recently installed logzilla (from sources on a hand-built HLFS system) and upon verifying that logs are successfully being written to MySQL and also verifying sphinx indexing is functional I'm getting partial output. I verified all permissions in the webroot and monitored the apache error_log for permission errors [none found]. I also verified ioncube functionality.

If I visit the MPX Charts tab everything appears as it should, the sparkline shows my real-time MPS, and it shows data since it's been set up. Below is a link to the screenshot when I visit the home page:



By the way, there is not a single Microsoft device that will ever log here (or exist here) so if this error is somehow a gate to getting the home screen to function I'll need to figure out a workaround or at minimum a sample log entry to manually insert.

Thanks for your help!

-Ryan

[cdukes]

You can disable Windows events either during install or by setting SNARE=0 in the admin interface.
What is "redbeardcmg" in your screenshot?
Also, try logging out and back in to make sure your session is reset.

[redbeardmcg]

Thank for the quick response. I had previously set snare to 0 during my initial troubleshooting (and it is still 0) yet I still get the same output.

"Redbeardmcg" is my username.

-Ryan

[redbeardmcg]

I do have a number of years php development experience, yet am unfamiliar with ioncube. Does ioncube circumvent the standard php error / exception handling? If so are there any steps that I can take on my end to debug this issue?

Thanks,

-Ryan

[cdukes]

Thank for the quick response. I had previously set snare to 0 during my initial troubleshooting (and it is still 0) yet I still get the same output.
-Ryan

You have it set to 0 and it's still showing that?

"Redbeardmcg" is my username.

Oh, ha!

[cdukes]

I do have a number of years php development experience, yet am unfamiliar with ioncube. Does ioncube circumvent the standard php error / exception handling? If so are there any steps that I can take on my end to debug this issue?

Thanks,

-Ryan

IONCube doesn't circumvent anything.
You logged out and back in to clear any possible corrupt session vars, right?
I saw this happen once before during testing, but it was because I re-installed while I was still logged in.
After install, I clicked refresh and got this. Once I logged out and in, it fixed it.

If that doesn't do the trick, let me know and we can do a remote WebEx session to get you working

[redbeardmcg]

I did verify that my session was reset, also verified this from ff as well as chrome. Below is the current setting for SNARE:

Code: [Select]

--------------
select id,name,value,options,`default` FROM settings WHERE name LIKE 'SNARE'
--------------

id      name    value   options default
83      SNARE   0       0,1     0

-Ryan

[cdukes]

Ok, are you available for a WebEx?
It's probably something silly that I'm just not thinking of

Please email me with your availability.

[Lodarec92]

Whoa, this is really some fantastic guidance I have discovered at this website - pity that I missed this valuable thread before. Thank you every1 for putting such cool stuff.

[cdukes]

Whoa, this is really some fantastic guidance I have discovered at this website - pity that I missed this valuable thread before. Thank you every1 for putting such cool stuff.

Hey, thanks! That really means a lot to us!

[mh]

I have the same problem.
The system installed OK and collecting log messages to mysql.
It seems that no problems with permissions, apache, php, syslog-ng, sphinx, etc.
I can see Charts Window (with increased number of messages)
I can see Top 10's messages in any tab, but i don't see the main window.
Just empty screen like on first screenshot.
What may be the problem ?

[cdukes]

I have the same problem.
The system installed OK and collecting log messages to mysql.
It seems that no problems with permissions, apache, php, syslog-ng, sphinx, etc.
I can see Charts Window (with increased number of messages)
I can see Top 10's messages in any tab, but i don't see the main window.
Just empty screen like on first screenshot.
What may be the problem ?

Is this an upgrade?
If so, either click "logout" or point your browser to logout.php
Also, in some cases, clearing cookies after an upgrade (only from certain versions) does the trick.

[mh]

I have the same problem.
The system installed OK and collecting log messages to mysql.
It seems that no problems with permissions, apache, php, syslog-ng, sphinx, etc.
I can see Charts Window (with increased number of messages)
I can see Top 10's messages in any tab, but i don't see the main window.
Just empty screen like on first screenshot.
What may be the problem ?

Is this an upgrade?
If so, either click "logout" or point your browser to logout.php
Also, in some cases, clearing cookies after an upgrade (only from certain versions) does the trick.

No. It is not upgrade. But the second try over the unfinished first one. From the first install i missed some packets like sudo, ioncube and malfunction php. First time i install from /root/logzilla, but then decide to transfer all data to /usr/local/www/logzilla. It seems that install script not correctly setup all path, so i changed /root/logzilla/ to /usr/local/www/logzilla manually in all scripts & configs. It start collecting traffic but the main window don't appear. So i remove the /usr/local/www/logzilla, crontabs, corrected syslog-ng.conf and apache.conf and make reinstall to /root/logzilla. Nothing new happen (but it seems that all path was correct, except php path in sphinx.conf  (may be it affected only to FreeBSD). The messages collected, but main window not appearing.

I tested server from two different hosts and from different browsers (Opera, Chrome, FireFox and IE - the last two has a various ot problems with viewing the logzilla page). I clear all cache/cookie in all browsers and disable AdBlock and similar programs , reload apache/syslog-ng and even reboot syslog server). The problem persists.

P.S. Sorry for my english.

[cdukes]

No. It is not upgrade. But the second try over the unfinished first one.

That's the same as an upgrade. Logging out would make sure the session is cleared.

From the first install i missed some packets like sudo, ioncube and malfunction php. First time i install from /root/logzilla, but then decide to transfer all data to /usr/local/www/logzilla. It seems that install script not correctly setup all path, so i changed /root/logzilla/ to /usr/local/www/logzilla manually in all scripts & configs. It start collecting traffic but the main window don't appear. So i remove the /usr/local/www/logzilla, crontabs, corrected syslog-ng.conf and apache.conf and make reinstall to /root/logzilla. Nothing new happen (but it seems that all path was correct, except php path in sphinx.conf  (may be it affected only to FreeBSD). The messages collected, but main window not appearing.

Whew, that's a lot
Is this for BSD? If so, I know that other users have had trouble getting all the right programs and libs (for php, etc) like you have. Other users have volunteered to write an install guide, but unfortunately it hasn't happened yet.
Check here for a possible solution:
http://forum.logzilla.pro/index.php/topic,369.msg1925.html#msg1925

P.S. Sorry for my english.

No worries


Also, one final note. If you move LogZilla (as you did from root), it is better to delete the old one and install from scratch to ensure that the paths are updated properly in all files.

[mh]

Whew, that's a lot
Is this for BSD? If so, I know that other users have had trouble getting all the right programs and libs (for php, etc) like you have. Other users have volunteered to write an install guide, but unfortunately it hasn't happened yet.
Check here for a possible solution:
http://forum.logzilla.pro/index.php/topic,369.msg1925.html#msg1925

Yes, It's FreeBSD. (FreeBSD 7.0-RELEASE-p11)
logzilla_3.2.311.tgz
And i have already installed all necessary php extension, but i have php5, not php52.
I try install php52 and see whats changed. As i remember there was some problems with php52 installing..

Also, one final note. If you move LogZilla (as you did from root), it is better to delete the old one and install from scratch to ensure that the paths are updated properly in all files.

I installed from scratch - remove all previos files including database.