Teevity / ice

AWS Usage Tool
2.86k stars 436 forks source link

Cannot get property 'companyName' on null object #216

Open chicagobuss opened 8 years ago

chicagobuss commented 8 years ago

Hey all, can't figure this out. I'm trying to run the processor and reader in the same app (first of all, is this allowed?), and I had a successful processor run... see the data under my ice_work folder and all.

Now, I'm getting the same companyName on null object error when I try to use the reader.

What else can I try to resolve this error?

Here's my ice.properties:

ice.processor=true
ice.processor.localDir=/mnt/ice_processor
ice.work_s3bucketname=ourcompany-billing
ice.work_s3bucketprefix=ice_work/
ice.startmillis=1464739200000

ice.reader=true
ice.reader.localDir=/mnt/ice_reader
ice.companyName=ourcompany

# s3 bucket name where the billing files are. multiple bucket names are delimited by ",". Ice must have read access to billing s3 bucket.
ice.billing_s3bucketname=ourcompany-billing

# prefix of the billing files. multiple prefixes are delimited by ","
ice.billing_s3bucketprefix=
levitanmichael commented 8 years ago

Having the exactly the same problem, tried to pass the company name directly ./grailsw -Dice.companyName=ourcompany run-app and getting the same error.

Also, running the processor and the reader together on the same server.

chicagobuss commented 8 years ago

FWIW I tried running the reader on its own and I'm still getting the issue.

On Jul 25, 2016 8:40 AM, "levitanmichael" notifications@github.com wrote:

Having the exactly the same problem, tried to pass the company name directly ./grailsw -Dice.companyName=ourcompany run-app and getting the same error.

Also, running the processor and the reader together on the same server.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Netflix/ice/issues/216#issuecomment-234955753, or mute the thread https://github.com/notifications/unsubscribe-auth/AGylHtiZ5ZrH1HWLs0SW9M6vTaCgzIZkks5qZLzYgaJpZM4JTCNv .

levitanmichael commented 8 years ago

i found the solution for this one. Using sample.properties and rename to ice.properties instead 0f creating my own ice.properties

chicagobuss commented 8 years ago

Uh.. that's not much of a solution, haha. Can you tell us the differences between your ice.properties and the sample one so I can track down what might be wrong with mine?

vady112 commented 6 years ago

For anyone who face this issue just make sure that following option are true in ice.properties file

ice.processor=true

# whether or not to start reader/UI
ice.reader=true