You are great :) i commented the "# Use syslog for logging." which was uncommented by default ! and now the keystone.log is working.
Tha 2013/6/26 Miller, Mark M (EB SW Cloud - R&D - Corvallis) < mark.m.mil...@hp.com> > Here are some logging options we use in keystone.conf:**** > > ** ** > > # === Logging Options ===**** > > # Print debugging output**** > > # (includes plaintext request logging, potentially including passwords)*** > * > > debug = True**** > > ** ** > > # Print more verbose output**** > > verbose = True**** > > ** ** > > # Name of log file to output to. If not set, logging will go to stdout.*** > * > > log_file = keystone.log**** > > ** ** > > # The directory to keep log files in (will be prepended to --logfile)**** > > log_dir = /var/log/keystone**** > > ** ** > > # Use syslog for logging.**** > > # use_syslog = False**** > > ** ** > > # syslog facility to receive log lines**** > > # syslog_log_facility = LOG_USER**** > > ** ** > > # If this option is specified, the logging configuration file specified is > **** > > # used and overrides any other logging options specified. Please see the** > ** > > # Python logging module documentation for details on logging configuration > **** > > # files.**** > > # log_config = /etc/keystone/logging.conf**** > > ** ** > > # A logging.Formatter log message format string which may use any of the** > ** > > # available logging.LogRecord attributes.**** > > # log_format = %(asctime)s %(levelname)8s [%(name)s] %(message)s**** > > ** ** > > # Format string for %(asctime)s in log records.**** > > log_date_format = %Y-%m-%d %H:%M:%S**** > > ** ** > > # onready allows you to send a notification when the process is ready to > serve**** > > # For example, to have it notify using systemd, one could set shell > command:**** > > # onready = systemd-notify --ready**** > > # or a module with notify() method:**** > > # onready = keystone.common.systemd**** > > ** ** > > ** ** > > *From:* CHABANI Mohamed El Hadi [mailto:chabani.mohamed.h...@gmail.com] > *Sent:* Wednesday, June 26, 2013 6:25 AM > *To:* Jamie Lennox > *Cc:* Miller, Mark M (EB SW Cloud - R&D - Corvallis); > openstack@lists.launchpad.net; tu...@tudorholton.com > > *Subject:* Re: [Openstack] Swift / Keystone authentication**** > > ** ** > > *Mark Miller : *Until yesterday the container.recon didn't exist at all, > this morning when rectifying a mistake in the keystone.conf, the keystone > service started and these files (account.recon, container and object.recon) > were created and the problem is solved.**** > > Now the problem is that there is no logs in Keystone.log, only in syslog > (i set the permissions as mentioned )**** > > *Tudor : *Thank you for the advice :) i will keep it in mind.**** > > *Jamie Lennox :* - How can i put Swift into debug mode ? i've changed the > "debug" and "verbose" variables in Keystone.conf to"*True*" but nothing > happened !**** > > - For the bug, i don't think that is my case, i > don't have the same exceptions, this one is much more complicated than mine > :)**** > > ** ** > > Thanks to all of you !**** > > ** ** > > 2013/6/26 Jamie Lennox <jlen...@redhat.com>**** > > On Tue, 2013-06-25 at 18:05 +0200, CHABANI Mohamed El Hadi wrote: > > my logs looks like that : http://pastebin.ubuntu.com/5798930/....i > > didn't really understand a lot of things ! any suggestions please ?**** > > So the logs are not really informative, they just show that swift is > crashing. Generally you should put swift into debug mode via the config > files so there is some information there. > > However given that this has happened today i would suggest that this is > being caused by the same bug that is being discussed in > http://lists.openstack.org/pipermail/openstack-dev/2013-June/010861.html > which is this bug: https://bugs.launchpad.net/keystone/+bug/1193112**** > > > > > > 2013/6/25 Miller, Mark M (EB SW Cloud - R&D - Corvallis) > > <mark.m.mil...@hp.com> > > Bottom line the keystone service attempting to start but is > > running into a problem and cannot start. Check > > the /var/log/syslog file. > > > > > > > > From: CHABANI Mohamed El Hadi > > [mailto:chabani.mohamed.h...@gmail.com] > > Sent: Tuesday, June 25, 2013 8:46 AM > > To: Miller, Mark M (EB SW Cloud - R&D - Corvallis) > > Cc: Виль Суркин; openstack@lists.launchpad.net > > > > > > Subject: Re: [Openstack] Swift / Keystone authentication > > > > > > Yes you are right :) ! > > > > When trying 'service keystone status' i get : keystone > > stop/waiting......however when i do service keystone start, it > > shows 'keystone start/running, process 32462' i'm missing > > something here ? because i've installed keystone without > > changing his database (no need). > > > > > > > > > > 2013/6/25 Miller, Mark M (EB SW Cloud - R&D - Corvallis) > > <mark.m.mil...@hp.com> > > > > The keystone service will open these 2 ports. They are defined > > in file /etc/keystone/keystone.conf > > > > > > > > From: Openstack [mailto:openstack-bounces > > +mark.m.miller=hp....@lists.launchpad.net] On Behalf Of > > CHABANI Mohamed El Hadi > > Sent: Tuesday, June 25, 2013 7:48 AM > > To: Виль Суркин > > > > > > Cc: openstack@lists.launchpad.net > > Subject: Re: [Openstack] Swift / Keystone authentication > > > > > > > > > > When i tried with port : 5000 and even 35357 i got : > > Authorization Failed: [Errno 111] Connection refused > > > > > > These 2 ports are not open i guess, should i open them > > manually ? (the keystone service is start/running) > > > > > > > > > > > > > > 2013/6/25 Виль Суркин <vill....@gmail.com> > > > > You should authenticate in keystone service, not in > > swift-proxy. > > > > > > Keystone's Public API usually binds to TCP port 5000. > > > > > > > > > > > > -- > > > > > > Виль Суркин > > > > > > > > > > > > вторник, 25 июня 2013 г. в 18:38, CHABANI Mohamed El Hadi > > написал: > > > > Hi, > > > > > > I'm trying to install Swift from this Guide, and for > > the authentication service (Keystone) i'm a bit lost, > > should i install Keystone as a full-fledged service > > with the MySql database ? i want just to use Swift for > > test purpose (but not SAIO version), so idon't need a > > lot of bandwidth or storage space, i finished the > > nodes configuration and when verifying the > > installation with : swift -V 2.0 -A > > http://127.0.0.1:8888/v2.0 -U swift:swift -K swift > > stat > > i get : Unauthorised. Check username, password and > > tenant name/id > > > > > > Or with : keystone --os-username=swift > > --os-password=swift > > --os-auth-url=http://127.0.0.1:8888/v2.0 token-get > > i get : > > > > This server could not verify that you are authorized > > to access the document you requested. Either you > > supplied the wrong credentials (e.g., bad password), > > or your browser does not understand how to supply the > > credentials required. > > > > Any sugestions ? here my proxy-server.conf. > > > > > > > > Thank you > > > > > > > > > > > > > > _______________________________________________ > > > > > > Mailing list: https://launchpad.net/~openstack > > > > > > Post to : openstack@lists.launchpad.net > > > > > > Unsubscribe : https://launchpad.net/~openstack > > > > > > More help : https://help.launchpad.net/ListHelp > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~openstack > > Post to : openstack@lists.launchpad.net > > Unsubscribe : https://launchpad.net/~openstack > > More help : https://help.launchpad.net/ListHelp > > > **** > > ** ** >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp