On Sat, Nov 26, 2011 at 1:54 AM, Me Myself and I <[email protected]> wrote: > Still having problems getting drizzled to start. > > [root@localhost sbin]# ./drizzled --user=drizzle > InnoDB: Doublewrite buffer not found: creating new > InnoDB: Doublewrite buffer created > InnoDB: 127 rollback segment(s) active. > InnoDB: Creating foreign key constraint system tables > InnoDB: Foreign key constraint system tables created > Could not load auth file: Could not open users file: /etc/drizzle.users > > Plugin 'auth_file' init function returned error. > > Aborting:"plugin_finalize() failed". Abort was called from > drizzled/drizzled.cc:1478 in init_server_components() > [root@localhost sbin]# > > I have removed the auth_file plugin package, and get this: > > [root@localhost sbin]# ./drizzled --user=drizzle > InnoDB: Log scan progressed past the checkpoint lsn 48941 > 111126 10:20:04 InnoDB: Database was not shut down normally! > InnoDB: Starting crash recovery. > InnoDB: Reading tablespace information from the .ibd files... > InnoDB: Restoring possible half-written data pages from the doublewrite > InnoDB: buffer... > 111126 10:20:04 InnoDB: Starting an apply batch of log records to the > database... > InnoDB: Progress in percents: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 > 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 > 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 > 93 94 95 96 97 98 99 > InnoDB: Apply batch completed > auth_http plugin loaded but required option url not specified. Against which > URL are you intending on authenticating? > > Plugin 'auth-http' init function returned error. > > Aborting:"plugin_finalize() failed". Abort was called from > drizzled/drizzled.cc:1478 in init_server_components() > [root@localhost sbin]#
Ah yeah, so this is where you went ahead and installed all the auth plugins available. Now Drizzle expects you to configure them too and fails when you don't. (That's perhaps a poor choice, otoh silently disabling auth plugins could have security implications too...) So why don't you just continue with the same strategy: remove the auth_http plugin as you won't be using it, then auth_ldap and probably auth_pam as well... It's probably easiest if you just start with auth_all (no authentication) to start drizzle, then you can pick another auth plugin later. henrik -- [email protected] +358-40-8211286 skype: henrik.ingo irc: hingo www.openlife.cc My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
