MonitorWare Knowledge Base

jumping right in the middle... do you have selinux enabled? Smells like a problem with it... If not: please disregard my uninformed comment

• Custom phpLogCon configuration?
• Maintenance Contract?
• Installation support?

It has to be something like selinux, reinstallation will not help you as this is not a phplogcon problem, but a permission problem.

best regards,
Andre Lorbach

I am stuck at step 7.
My data source is various folders in /var/log/rsyslog.
The system is not accepting this path; it gives permission error.
Does it mean phpcon will not accept data in folders? We have to create a single log file?
Pl. help
Thanks,
Murali

It doesn't work like that, you have to specify the logfilename you want to see in phpLogCon.
You can use dynamic filenames, for more see the dynamic logfiles part in the documentation:
http://www.phplogcon.org/module-Static_ ... html.phtml

best regards,
Andre Lorbach

hello again!

version 2.6.4 has been released since I last posted here about the issues I found

The problem is still the same: phpLogCon isn't able to read the "messages" file and it yields in the same error as before...

But... if the source logfile is called something different like /var/log/current/myhostname.yyyymmdd.log it works just fine!
This is weird. File permissions and ownerships are the same on all files. It just fails if the filename = "messages"...

On the other hand, using /var/log/current/myhostname.yyyymmdd.log as input (i.e. 20090907) is not very reliable as phpLogCon will fail once the day changes (i.e.: 20090908)... so can DynFiles be used with phpLogCon at all?

Any ideas now on the problem? If you need some information from my end please let me know.


Thanks!

Jsut FYI: Andre is currently on vacation, and everyone else probably too busy to look at this. I think dynafiles shold now work. But probably it is a good idea to bump this post early next week

I just saw this http://www.phplogcon.org/module-Static_ ... html.phtml

It would be very convenient to keep the same variables as in rsyslog so we don't need to learn how things are done on every product...

rsyslog's dynamic template %HOSTNAME%.%$YEAR%%$MONTH%%$DAY%.log would be something like %HOSTNAME.%Y%m%d.log in phpLogCon, provided that phpLogCon can cope or provides a similar approach for using %HOSTNAME%...

my 2 cents...

Hi again,

is Andre back from holidays? can someone please do a follow up with this?


Thanks

Hi,

I am not sure what you expect from me now
From your last answer I thought the problem was already solved by using the correct replacement characters?

If it is regarding the rsyslog variable names, I will add this to my todo list, some aliases for those replacement strings won't hurt .

best regards,
Andre Lorbach

Hi Andre,

please re-read the thread as there are some new questions unanswered which in the end mean that phpLogCon hasn't been installed...

Thanks!

Well it wasn't so clear what you meant by "messages" to me, but now I guess you mean the /var/log/messages file.
If phpLogCon cannot read it, it is most likely a premission problem. We have had threads about this before, have you checked if there is something running that could block access to import syslogfiles in general? And have you seen this wiki article before?
http://wiki.rsyslog.com/index.php/How_t ... _debian%3F

best regards,
Andre Lorbach

Hi,

my first thought was also a permissions problem and therefore changed the whole path to 777 apache.rsyslog ... but stil it didn't work.
rsyslog.conf contains the following directives too:
--
22 $umask 0000
23 $FileCreateMode 0640
24 $FileGroup rsyslog
--

...which should take care of chgrp'ing te dynamically created files to rsyslog... (I just noticed that this is not working properly :-/ )

I added a "create 0640 root rsyslog" to logrotate.conf as suggested in the link you posted. Anyway, logrotate runs once a day (well, at night) so it shouldn't be blocking the files.

Finally, with messages I also mean the logfiles created dynamically by
--
$template DynaFile,"/var/log/current/%HOSTNAME%.%$YEAR%%$MONTH%%$DAY%.log"
*.* -?DynaFile
--


Thanks!

Some Linuxversion contain some extra security software like selinux which prevent apache for example from accessing any systemfiles like the messages file. If permissions are fine on the files, it is most likely that something like selinux is preventing phpLogCon from accessing system logfiles. This would explain why other uncommon logfiles names are not blocked.

But I already wrote this in this thread before

best regards,
Andre Lorbach

...and I also wrote that SELinux is disabled in our logserver...

what now?


Thanks

Then it is something else, however it is very unlike to be a phpLogCon problem as you see that other logfiles are readable.

best regards,
Andre Lorbach