By ano.nimmus on

I see this error all over the place in my logs, as an error box in my admin interface, etc.

with,

drush pm-info syslog

	Extension        :  syslog                                    
	Project          :  drupal                                    
	Type             :  module                                    
	Title            :  Syslog                                    
	Description      :  Logs and records system events to syslog. 
	Version          :  7.26                                      
	Date             :  2014-01-15                                
	Package          :  Core                                      
	Core             :  7.x                                       
	PHP              :  5.2.4                                     
	Status           :  enabled                                   
	Path             :  modules/syslog                            
	Schema version   :  module has no schema                      
	Files            :  syslog.test                               
	Requires         :  none                                      
	Required by      :  none                                      
	Permissions      :  none                                      
	Configure        :  admin/config/development/logging

drush en syslog

	The following extensions will be enabled: syslog
	Do you really want to continue? (y/n): y
		openlog() expects parameter 3 to be long, string given syslog.module:103                                  [warning]
		syslog was enabled successfully.

cat syslog.module

	  if (!$log_init) {
	    $log_init = TRUE;
	    $default_facility = defined('LOG_LOCAL0') ? LOG_LOCAL0 : LOG_USER;
103	    openlog(variable_get('syslog_identity', 'drupal'), LOG_NDELAY, variable_get('syslog_facility', $default_facility));
	  }

Since this is a core module bug, I filed a bug @ core, https://drupal.org/node/2188797 a few weeks ago, and tried to ask about it in #irc -- no response in either place.

⋅ Categories: Drupal 7.x

Comments

vm’s picture

vm commented

Is this issue occurring on a new install and no contributed modules added? if not; what I'd do is check a new test install. If the issue isn't present, I'd take a move the prod site to a test site and disable contrib modules to see if there is some more clues.

The above advice is suggested based on researching the error with google and finding it reporting in multiple contrib module issue queues.

ano.nimmus’s picture

ano.nimmus commented

---------------------------------------