Problems with Bulk Uploading.

[Michael Robellard]

I am having a terrible time getting my bulk upload to work.
It is working fine on my dev enviornment. When I try and upload to my
app I get:

[INFO 2009-11-21 23:49:48,233 bulkloader.py] Logging to bulkloader-
log-20091121.234948
[INFO 2009-11-21 23:49:48,250 bulkloader.py] Throttling transfers:
[INFO 2009-11-21 23:49:48,250 bulkloader.py] Bandwidth: 250000
bytes/second
[INFO 2009-11-21 23:49:48,250 bulkloader.py] HTTP connections: 8/
second
[INFO 2009-11-21 23:49:48,250 bulkloader.py] Entities inserted/
fetched/modified: 20/second
[INFO 2009-11-21 23:49:48,250 bulkloader.py] Opening database:
bulkloader-progress-20091121.234948.sql3
[DEBUG 2009-11-21 23:49:48,608 adaptive_thread_pool.py] [Thread-1]
WorkerThread: started
[DEBUG 2009-11-21 23:49:48,608 adaptive_thread_pool.py] [Thread-2]
WorkerThread: started
[DEBUG 2009-11-21 23:49:48,608 adaptive_thread_pool.py] [Thread-3]
WorkerThread: started
[DEBUG 2009-11-21 23:49:48,608 adaptive_thread_pool.py] [Thread-4]
WorkerThread: started
[DEBUG 2009-11-21 23:49:48,608 adaptive_thread_pool.py] [Thread-5]
WorkerThread: started
[DEBUG 2009-11-21 23:49:48,608 adaptive_thread_pool.py] [Thread-6]
WorkerThread: started
[DEBUG 2009-11-21 23:49:48,608 adaptive_thread_pool.py] [Thread-7]
WorkerThread: started
[DEBUG 2009-11-21 23:49:48,608 adaptive_thread_pool.py] [Thread-9]
WorkerThread: started
[DEBUG 2009-11-21 23:49:48,608 adaptive_thread_pool.py] [Thread-8]
WorkerThread: started
[DEBUG 2009-11-21 23:49:48,608 adaptive_thread_pool.py] [Thread-10]
WorkerThread: started
[DEBUG 2009-11-21 23:49:48,608 bulkloader.py] Configuring
remote_api. url_path = /remote_api, servername =
railroadempire.appspot.com
[DEBUG 2009-11-21 23:49:48,608 bulkloader.py] Bulkloader using
app_id: railroadempire
[INFO 2009-11-21 23:49:48,608 bulkloader.py] Connecting to
railroadempire.appspot.com/remote_api
[INFO 2009-11-21 23:49:59,578 bulkloader.py] Authentication Failed

Here is my app.yaml file:
application: railroadempire
version: 1
runtime: python
api_version: 1

handlers:
- url: /remote_api
script: $PYTHON_LIB/google/appengine/ext/remote_api/handler.py
login: admin

- url: /.*
script: environment.py

I know I am just doing something stupid, but I have been trying to get
this working for 2 hours now.

[Michael Robellard]

I added an --auth_domain=therailroadempire.com

so my entire command is:
appcfg.py upload_data --has_header --config_file=models/loaders.py --
filename=docs/cities.csv --kind=City --
auth_domain=therailroadempire.com .

I am using the same username/password that I use to connect to the
admin console.

I am sure I am missing something simple, but I still can't figure it
out.

Anyone have any ideas?

[Matthew Blain]

Typically this problem can arise when the application is set up to use
one authentication option (e.g. Google Accounts) and you are using a
user with a different configuration (e.g. Google Apps account with the
domain 'therailroadempire.com'). The simplest solution is to add
another admin to your application which matches the authentication
options of the application.

--Matthew

[Michael Robellard]

So I tried what you suggested and now I am getting a 403 forbidden,
when logging on with my mrobe...@gmail.xxx which I have set up as an
application developer

Authentication Options:
When this application was created it was configured to allow anyone
with a valid Google Account to sign in if the Google Accounts API is
used for authentication. A Google Account includes all Gmail Accounts,
but does not include accounts on Google Apps domains. Learn more
Note: pages that don't use authentication are visible to anyone.

[Michael Robellard]

Finally Got it.

So from what I understand, if anyone else has this issue, and kind
figure it out.
The problem I had was that my authentication setting for my
application was set to allow anyone with a Google Account to access
the application, however my application is a Google Apps application.
When you try to authenticate within the application it will only
authenticate regular Google Accounts, creating a regular non-google
apps account gets around this limitation, however you have to watch
and make sure you have completely logged out of your Google Apps
account before you accept the invite for your non-google apps account,
otherwise it will just login with your Google Apps account.

Is there a bug report open for the Google Account vs. Google Apps
issue?

On Nov 23, 10:09 pm, Michael Robellard <m...@robellard.com> wrote:
> So I tried what you suggested and now I am getting a 403 forbidden,

> when logging on with my mrobell...@gmail.xxx which I have set up as an