Re: prelude-admin / prelude-manager setup insanity

Nevermind, I tracked it down to a filesystem permissions issue. 
Prelude-manager seems to be up and running now.

I stand by my previous comments about the online wiki documentation being 
very obtuse, incomplete, and disorganized. I'd be happy to volunteer to help 
clean things up if only I had a clue what I was doing. I'm documenting my 
own setup on an internal departmental wiki and would be happy to share with 
others if I am successful getting everything going properly. I think that a 
document along the lines of "HOWTO Configure a Basic Prelude Setup from 
Start to Finish" is sorely lacking from the official Prelude wiki...

In case anyone else feels the same and might be looking for a more 
comprehensive guide, I found this link to be very helpful:

http://dismf5ve.wordpress.com/2009/09/27/setting-up-prelude/

-- 
[ Robert Vineyard | RHCE, Security+ ]    [ [email protected]  ]
[ Information Security Engineer III ]    [ 404.385.6900 | FAX 404.894.4690 ]
[Finding a needle in a haystack isn't hard when every straw is computerized]


Robert Vineyard wrote:
> I have been pulling my hair out for several days now trying to figure out 
> how to mate the prelude-manager with prelude-admin. I can't find 
> documentation on this critical process anywhere (the prelude online docs on 
> the wiki are *terrible*, disorganized, and very hard to follow).
> 
> Can anyone walk me through this? I've got all of the core prelude stuff 
> setup to run on the same machine, but I can't get prelude-manager to startup 
> without errors like this:
> 
> $ /opt/prelude/bin/prelude-manager
> 13 Nov 22:09:25 (process:2817) INFO: Subscribing Normalize to active 
> decoding plugins.
> 13 Nov 22:09:25 (process:2817) WARNING: prelude-client: error initializing 
> prelude-client: could not open profile 'prelude-manager': insufficient 
> permission
> 
> root@protonpack:~# /opt/prelude/bin/prelude-manager
> 13 Nov 22:09:36 (process:2818) INFO: Subscribing Normalize to active 
> decoding plugins.
> 13 Nov 22:09:36 (process:2818) INFO: server started (listening on 
> xxx.xxx.xxx.xxx port 4690).
> 13 Nov 22:09:36 (process:2818) INFO: Subscribing db[default] to active 
> reporting plugins.
> 13 Nov 22:09:36 (process:2818) ERROR: could not open 
> /opt/prelude/etc/prelude/profile/prelude-manager/server.keycrt for reading. 
> (manager-auth.c:640 manager_auth_init)
> 13 Nov 22:09:36 (process:2818) WARNING:
> Profile 'prelude-manager' does not exist. In order to create it, please run:
> prelude-admin add "prelude-manager" --uid 0 --gid 0
> 
> I've run the prelude-admin add command over and over again, in every 
> combination of user accounts and command line settings that I can come up 
> with. I've registered it under the "prelude" account and as root with no 
> success. I even tried registering with the uid/gid of the prelude user while 
> logged in as root and vice versa.
> 
> Does anyone have a complete, easy-to-follow guide for getting this mess 
> started up? I think I'll be good for the rest of the process if I could only 
> get prelude-manager working...
> 
> Thanks!
> 



_______________________________________________
Prelude-user site list
[email protected]
http://lists.prelude-ids.org/mailman/listinfo/prelude-user