On Mar 11, 2011, at 1:53 AM, Michael Friedrich wrote: > Brian Timares wrote: >> Looking at the latest (1.3) instructions, on the quickstart-idoutils.html, I >> see >> PostgreSQL: >> >> Create database and User: >> >> #> su - postgres >> $psql >> postgres=# CREATE USER icinga; >> postgres=# ALTER USER icinga WITH PASSWORD 'icinga'; >> postgres=# CREATE DATABASE icinga; >> >> >> When I type psql at the $ prompt I get: >> psql: FATAL: Ident authentication failed for user "postgres" > > then you'd have to edit/setup your pg_hba.conf correctly in order to > allow the postgres on the local machine without password. but that's
Well, that is what I thought at first. Sorry, perhaps I wasn't clear enough since 2 people misunderstood me. See this: >> OK, maybe the instructions don't include a prompt, although they do in the >> section above and below. Sloppy. So I try: >> $psql >> or if you prefer >> -bash-3.2$ $psql >> and that does work, or at least it doesn't complain. So the instructions should change. The section before and after the one I quote, have a prompt listed in the examples, but this section doesn't *after the su - postgres*. The $ needs to be typed, or at least, that works and doesn't give an error. Since the sections before and after have "#> " as the example prompt, I suggest matching that and using "$> " or such. Or better "# " and "$ " throughout. Or even better, "#@hostname> " and "postgres@hostname> ". But be consistent, as "Quia ursus pusilli ingenii sum verba difficilia fastidio." :) More apropos to my problem, after having success with typing $psql, I tried the next bit: >> Then I type at the -bash-3.2$ prompt >> postgres=# CREATE USER icinga; >> and I get >> -bash: CREATE: command not found >> >> Am I missing something (e.g. correct instructions)? >> >> CentOS 5.5 and a load of frustration. postgres is a command, but postgres=# is not the right way to call it. If I'm supposed to be in postgres somehow, the instructions aren't clear about that. I was up late so I gave up on postgres and used MySQL where the instructions are more clear, but long-term I'd like to use Postgres. I suggest that someone take a fresh installation, use standard prompts, and copy/paste into a document _every_ step necessary. I'm willing to convert it to HTML to match the current instructions (if that doesn't step on anyone's toes) but I don't have the right steps. And passwords. If there is a password for it, I don't know what it is. I don't believe one is necessary for local users per my pg_hba.conf but I'm no DBA. And if someone gives an example without a password, but that isn't the default, then they would need to show changing the default first. Otherwise, show giving a password (unless no password _is_ the default). I hope this is more clear. Try a fresh install and type exactly what is there, and at least for RHEL/CentOS, I do believe it'll fail just like it did for me. Brian <-= less sleep deprived ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ icinga-users mailing list icinga-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/icinga-users
