[Bug 1437846] Re: akonadi mysql 5.6 crash with signal 11
I solved this issue. This is what I did. - I deleted from folder .local/share/akonadi/ - socket-(computername) - mysql.conf - Start Akonadi server. = problem solved. Akonadi server started normal Maybe this helps solving the problem. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1437846 Title: akonadi mysql 5.6 crash with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1437846/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1015819] Re: sb_sasl_generic_pkt_length: received illegal packet length when using ldapsearch and sasl with ssl or tls
This has to do with Active Directory not supporting nested security or privacy layers. To make it work you need to set sasl_secprops minssf=0,maxssf=0 in /etc/openldap/ldap.conf /J -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1015819 Title: sb_sasl_generic_pkt_length: received illegal packet length when using ldapsearch and sasl with ssl or tls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1015819/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1176178] Re: Setting pid in memcached.conf causes strange behavior
Is there anything that can be done about this? Bug still affects me. ** Changed in: memcached (Ubuntu) Status: Expired = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to memcached in Ubuntu. https://bugs.launchpad.net/bugs/1176178 Title: Setting pid in memcached.conf causes strange behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1176178/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1176178] Re: Setting pid in memcached.conf causes strange behavior
How can we move forward on this? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to memcached in Ubuntu. https://bugs.launchpad.net/bugs/1176178 Title: Setting pid in memcached.conf causes strange behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1176178/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1176178] Re: Setting pid in memcached.conf causes strange behavior
$ ls -l /var/run lrwxrwxrwx 1 root root 4 May 3 20:20 /var/run - /run $ less /etc/memcached.conf # memcached default config file # 2003 - Jay Bonci jaybo...@debian.org # This configuration file is read by the start-memcached script provided as # part of the Debian GNU/Linux distribution. # Run memcached as a daemon. This command is implied, and is not needed for the # daemon to run. See the README.Debian that comes with this package for more # information. -d # Log memcached's output to /var/log/memcached logfile /var/log/memcached/memcached.log # pid file -P /var/run/memcached.pid # Be verbose (shows errors, warnings, and socket connections) -v # Be even more verbose (print client commands as well) # -vv # Start with a cap of 64 megs of memory. It's reasonable, and the daemon default # Note that the daemon will grow to this size, but does not start out holding this much # memory -m 768 # Override the size of each slab page in bytes, i.e. the maximum item size that # memcached will accept. Recommended not to set above 1 MB for performance reasons. # The default value is 1 MB. -I 1048576 # Default connection port is 11211 -p 11211 # Run the daemon as root. The start-memcached will default to running as root if no # -u command is present in this config file -u memcache # Specify which IP address to listen on. The default is to listen on all IP addresses # This parameter is one of the only security measures that memcached has, so make sure # it's listening on a firewalled interface. # -l 127.0.0.1 # Limit the number of simultaneous incoming connections. The daemon default is 1024 # -c 1024 # Lock down all paged memory. Consult with the README and homepage before you do this # -k # Return error when memory is exhausted (rather than removing items) # -M # Maximize core file limit # -r -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to memcached in Ubuntu. https://bugs.launchpad.net/bugs/1176178 Title: Setting pid in memcached.conf causes strange behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1176178/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1176178] [NEW] Setting pid in memcached.conf causes strange behavior
Public bug reported: In memcached.conf, if I set this line: # pid file -P /var/run/memcached.pid Then when I run sudo service memcached start I observe two strange behaviors: 1) The following log lines appears: WARNING: The pid file contained the following (running) pid: 19 Could not open the pid file /var/run/memcached.pid for writing: permission denied (the second line only appears when I set the user to -u memcache, rather than -u root) 2) The sudo service memcached start command does not daemonize until I press enter I'm running Ubuntu precise (12.04.2 LTS), with the most recent memcached package installed. ** Affects: memcached (Ubuntu) Importance: Undecided Status: New ** Description changed: In memcached.conf, if I set this line: # pid file -P /var/run/memcached.pid Then when I run sudo service memcached start I observe two strange behaviors: 1) The following log lines appears: WARNING: The pid file contained the following (running) pid: 19 Could not open the pid file /var/run/memcached.pid for writing: permission denied - (the second line only appears when I have -u memcache set as well) + (the second line only appears when I set the user to -u memcache, + rather than -u root) 2) The sudo service memcached start command does not daemonize until I press enter ** Description changed: In memcached.conf, if I set this line: # pid file -P /var/run/memcached.pid Then when I run sudo service memcached start I observe two strange behaviors: 1) The following log lines appears: WARNING: The pid file contained the following (running) pid: 19 Could not open the pid file /var/run/memcached.pid for writing: permission denied (the second line only appears when I set the user to -u memcache, rather than -u root) 2) The sudo service memcached start command does not daemonize until I press enter + + + I'm running Ubuntu precise (12.04.2 LTS), with the most recent memcached package installed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to memcached in Ubuntu. https://bugs.launchpad.net/bugs/1176178 Title: Setting pid in memcached.conf causes strange behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1176178/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1073510] Re: Upstart init script executes before network bridge is available
This is on Ubuntu 12.04 with Folsom installed using ubuntu- cloud.archive.canonical.com -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1073510 Title: Upstart init script executes before network bridge is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1073510/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
