Hi everyone.
I have gotten Drupal up and running, and am enjoying playing around with the CSS of a template I downloaded. I had tried one from another source but it was way too complex for me and their support was pants - I had paid for it thinking it would save me time and money.
However I am getting the following errors:
Warning: openlog() has been disabled for security reasons in syslog_watchdog() (line 103 of
[... url ]/modules/syslog/syslog.module).
Warning: syslog() has been disabled for security reasons in syslog_watchdog() (line 118 of
[ ...url ] /modules/syslog/syslog.module)
I have unchecked the box running the syslog function in the modules area of administration - yet it returns the same error.
Can anybody tell me why this is?
I have also posted this question as an answer to this problem that remains unsolved from 2009.
Comments
=-=
The issue is the environment in which you are running has the function disabled that syslog.module depends on. If you've no control over the environment, you will need to speak with your host with regard to enabling openlog() which is commonly dealt with in php.ini
Thanks VMI am the
Thanks VM
I am the administrator of this site. When I had the function enabled, I got the error message. Switching this off gave me the message.
Either that or I am editing the wrong Syslog Module.
Where do I go from here???
Puzzled by Drupal's attitude.
=-=
you shouldn't edit core files. Either disable the syslog.module or allow the openlog() function to be run in your PHP environment. A google search for how to enable openlog() in php should be fruitful.
Poor Wording, Apols.
Sorry, I meant checking and unchecking boxes in the administrator section.
Any tweaks in the code I have done was to add my ID to a Statcounter module. I haven't tried it yet (bites fingernails).
Your answer sounds a daunting one - just to deal with an error message on a freshly installed template.
Another thought: enabling Syslog by enabling/disabling another module sounds confusing. Is there no way to have an error message that does more than just tell you what is wrong?
Puzzled by Drupal's attitude.
=-=
what module is enabling syslog? if the module being enabled is dependent on syslog, then yes that is normal behavior.
The issue has nothing to do with the template. The issue is the syslog module uses a function of php that it can't find in your environment. you can switch themes, the error will be there regardless. The only way to have access to the function that syslog needs is to enable it in your environment. Not sure how daunting it is really, based on my quick research you do it in the php.ini file. If you aren't the server administrator you need to contact them.
an error message that does more than tell you what is wrong? What else would you have it do? it's an error message. IN this case it's not even an error but a warning. letting you know that the module is not going to work as expected because it doesn't have access to a php function that it requires.
Okay, got most of that. I'll
Okay, got most of that. I'll bear all that in mind.
Bear in mind that as a marketer, I don't just give my audience an "error message" because they tend to give up and go somewhere else. I make sure that they are told exactly what they can do instead. That way they get more of a choice and can make up their minds what to do. It means that if I made an unwitting error, I don't lose as much traffic.
I only use such tactics when winnowing clients when I only want the very best ones.
Puzzled by Drupal's attitude.
=-=
the error has nothing to do with traffic. The error has nothing to do with users. The error has to do with what has already been explained. you've two options: disable and uninstall the syslog.module, or adjust your PHP environment on the server so that the syslog.module can work properly. The warning is from PHP and the way to correct it can be researched with google. I've taken the liberty of performing the search for you see: here which produces the following: http://2by2host.com/articles/php-errors-faq/disabled_openlog/
and includes the following instructions:
* Remove the openlog string from the disable_functions at php.ini* file* Ask your hosting provider to remove the string above if you don't have an access to the php.ini* file
* Change hosting provider which allows the running of the openlog function.
php.ini is not a drupal file. It is a php configuration file. The warning is from PHP, displayed through drupal because the drupal module you've enabled requires a function of PHP which is disabled.
As far as the warning continuing to show after the syslog module has been disabled. use the uninstall tab and uninstall the module and test. If the warning continues to display after uninstalling the module, clear the cache tables of the database in administer -> performance and test.