Bugzilla – Bug 3843
Undefined subroutine &Slim::Networking::Async::Socket::UDP::msg
Last modified: 2011-03-16 04:34:06 UTC
Solaris SPARC 9 12/03 (update 5) MySQL 5.0.22 community edition libmysqlclient 3.23.56 Working with SlimServer 6.5 beta of 2006-07-30. Wanted to report some errors arising in the log file which lead to the server exiting at startup. If you want/need further debugging, just let me know. If you want me to hold off and use a later build, let me know. Anyhow, here's the log file. 060730 22:42:19 InnoDB: Started; log sequence number 0 131981 060730 22:42:19 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.22-standard' socket: '/Cache/slimserver-mysql.sock' port: 9092 MySQL Community Edition - Standard (GPL) File '/usr/local/share/libmysqlclient/charsets/?.conf' not found (Errcode: 2) Character set '#33' is not a compiled character set and is not specified in the '/usr/local/share/libmysqlclient/charsets/Index' file File '/usr/local/share/libmysqlclient/charsets/?.conf' not found (Errcode: 2) Character set '#33' is not a compiled character set and is not specified in the '/usr/local/share/libmysqlclient/charsets/Index' file File '/usr/local/share/libmysqlclient/charsets/?.conf' not found (Errcode: 2) Character set '#33' is not a compiled character set and is not specified in the '/usr/local/share/libmysqlclient/charsets/Index' file Undefined subroutine &Slim::Networking::Async::Socket::UDP::msg called at /usr/local/src/SlimServer_v2006-07-30/Slim/Networking/Async/Socket/UDP.pm line 53. File '/usr/local/share/libmysqlclient/charsets/?.conf' not found (Errcode: 2) Character set '#33' is not a compiled character set and is not specified in the '/usr/local/share/libmysqlclient/charsets/Index' file 060730 22:42:29 [Note] /usr/sbin/mysqld: Normal shutdown 060730 22:42:29 InnoDB: Starting shutdown... 060730 22:42:31 InnoDB: Shutdown completed; log sequence number 0 131991 060730 22:42:31 [Note] /usr/sbin/mysqld: Shutdown complete
fixed at change 8741
FWIW, I fixed UDP.pm myself and the message which was being reported is 2006-07-30 23:39:03.1012 UPnP: Error adding multicast membership, UPnP may not work properly: Option not supported by protocol 2006-07-30 23:39:03.1029 UPnP: Error setting multicast TTL: Option not supported by protocol i