ice
ice copied to clipboard
Running on non-8080 port and non-localhost
Im trying to get ice to run on port 80 so my URL would be more presentable like http://ice.example.com instead of http://ice.example.com:8080/ice/dashboard/summary..
How do I change it so that ":port/ice/dashboard/summary" does not show up?
I changed all references to localhost:8080 to the correct domain name on port 80 in the files listed below
grails-app/conf/Config.groovy work/plugins/tomcat-2.2.1/scripts/Tomcat.groovy
i dont see a reference to localhost:8080 on conf/system/server.xml .. Is there somewhere else i am missing. Please let me know.. thanks
How are you running the application, @mcorral6? If you're running it in development with the run-app
command then you need to supply the -Dserver.port
argument: http://grails.org/doc/2.3.1/ref/Command%20Line/run-app.html
@grahamlyons Im running the app with a different user. I have ran into issue when using the -Dserver.port argument stating the user im using does not have the rights to run it in port 80
@mcorral6 you can use "sudo -E" to execute grails as root using your current environment.
Check your Config.groovy for environment variables.
// set per-environment serverURL stem for creating absolute links environments { production { } development { grails.serverURL = "http://localhost:8080/${appName}" } test { grails.serverURL = "http://localhost:8080/${appName}" }
}
I use "grails prod run-app" to avoid the serverURL setting above.
On Thu, Mar 12, 2015 at 1:53 PM, galindro [email protected] wrote:
When I pass the -Dserver.port=80 to start it, the application redirects my browser to http://localhost:8080/ice/dashboard/summary . How can I fix that? I've tried to setup -Dserver.host host to my domain name but not works.
— Reply to this email directly or view it on GitHub https://github.com/Netflix/ice/issues/82#issuecomment-78546812.
And then: 2015-05-22 23:46:14,957 [com.netflix.ice.processor.BillingFileProcessor] WARN s3.AmazonS3Client - No content length specified for stream data. Stream contents will be buffered in memory and could result in out of memory errors. | Error 2015-05-22 23:46:15,048 [com.netflix.ice.processor.BillingFileProcessor] ERROR processor.BillingFileProcessor - Error reading from file lastProcessMillis_2015-03 Message: The specified key does not exist. (Service: Amazon S3; Status Code: 404; Error Code: NoSuchKey; Request ID: 7826BC1D56EBFBAF) Line | Method ->> 1077 | handleErrorResponse in com.amazonaws.http.AmazonHttpClient
| 725 | executeOneRequest in '' | 460 | executeHelper . . . in '' | 295 | execute in '' | 3710 | invoke . . . . . . in com.amazonaws.services.s3.AmazonS3Client | 1146 | getObject in '' | 1018 | getObject . . . . . in '' | 658 | getLastMillis in com.netflix.ice.processor.BillingFileProcessor | 672 | lastProcessTime . . in '' | 151 | poll in '' | 50 | doWork . . . . . . in com.netflix.ice.common.Poller | 28 | access$000 in '' | 88 | run . . . . . . . . in com.netflix.ice.common.Poller$1 ^ 745 | run in java.lang.Thread
Thanks for the suggestions here, guys. I got mine working by specifying the 'prod' environment and the 'Dserver.port=XX'.
So, if using the grails wrapper, my sample command-line is: './grailsw prod -Dserver.port=XX -Dice.s3AccessKeyId=XXXXX -Dice.s3SecretKey=XXXXX run-app'
Can I suggest that we close this issue? It's not a problem with the code it's just a usage question, and a Grails one at heart.
There's a Google Group for Ice, right?