I was tryting to install Proxylizer, but its not working. I get a blank page with only a Mikrotik Logo at the bottom. I followed all the steps as per the Wiki, but no progress.
Please let me know how will i be able to set it up properly.
I have made database.
when i try to open the web-page this is what i get besides getting a config page.
Somehow i have come around the problem that i described in my last.
My last problem was resolved by using “/usr/bin/php” to execute .php files.
Now i am facing a new problem.
i am getting " Not valid web proxy log!!! " message in /var/log/proxylizer/webproxytodb_debug.log , how i ever i am able to see all the logs in my “mysql.pipe” file, going smoothly.
in my mikrotik i have selected “web-proxy” + " debug" both for the logs, becasue when i select only “web-proxy” without “debug” i see no logs at all, not in Winbox Logs and also not in mysql.pipe.
please tell me what to do with this proxylizer. Its creating a lot of troubles for me.
And i need this software to work urgently.
I resolved this issue also by editing he PHP file. There are allot of mistakes in PHP files, believe me.
Now when i do cat /root/mysql.pipe , i see the logs going.
And aslo in my proxylizer page it is showing that i have logs. But how to use this Dumb thing. Unable to do any thing.
For me Proxylizer is the Dumbest Software, becasue it is not at all user-friendly. (My opinion).
Lines starting with “//” are default lines, followed by the lines that i made. After making changes Proxylizer started recieving Logs, and was also showing logs on the proxylizer web.
But i was unable to anything from there. I am unable to understand how to use/operate this proxylizer.
When you are logging debug packets, they may contain completely different information, which comes in different format. Therefore you have to modify PHP to understand these other logs. But you MUST NOT to that, because data you are receiving this way, contains different info.
Looks like there are platform dependencies causing problems. Because we are deploying proxylizer for half a year without problems - logs are inserted, reports generated and sent over email.
What platform are you using on the Proxylizer side? Ubuntu? Which web server? Apache2? Which version of PHP and MySQL? Which SysLog client - Syslog-NG?
Check your firewall - maybe it is blocking syslog messages or somehow modifying them. Are you using Layer-7 filtering?
When following the Getting started guide, at which step are you stuck now? Is the web page working? Have you configured reports? Are they sent over email?
Dear let me requote, when i use “topics=web-proxy, !debug” i get no logs at all. And i really mean no logs, so what will be transfered if i have no logs. The only way i see any sort of web-proxy logs is “topics=web-proxy,debug” .
I am using Red-Hat Enterprise 5, with Apache2 and PHP 5.xx and MySQL 5.xx . And using SYSLOG-NG.
I am saying again, i can see the logs in mysql.pipi, but it always say “Not Valid Web-Proxy Logs”, so for this i edited the file, which some how started working.
It is showing me that logs are being generated on the main page of Proxylizer, but how to use this App. Mails are not being generated, no logs are being mailed at all.
Dear when i make a rule “topics=web-proxy” still the logs that i see have the “debug” option in it. So its no use.
I am using 2.9 as well as 3.23.
I have 3 machine on 2.9 and 2 machine on 3.23. And i want to make a centralized loggin server, for which i have re-installed my server with CentOS 5.3, with all the required dependencies.
Even if you leave debug messages on, it should work - the debug messages are not in the required format, so they are simply discarded. The question is - why do you receive logs in different format?
Could you, please, send web-proxy logs to memory for a while (/system logging set … action=memory), watch the logs (/log print follow) and paste one of the entries, containing accounting info (the whole line) here, in this topic.
And, it could really help, if you could give us (Mikrotik) access to your RedHat box - provide us with IP address, username and password - send it to support at mikrotik dot com!
We would like to help, but it is hard to identify the problem.