Strange AZ Function logs - Linux different to windows logs - azure

I've swapped my AZ Functions to linux (Cheaper), and the logs I'm getting are vastly different from the Windows ones.
How can I get my windows style logs, in linux.
Host.json:
"logging": {
"logLevel": {
"default": "Information",
},
"applicationInsights": {
"samplingSettings": {
"isEnabled": true,
"excludedTypes": "Request"
}
}
}
(And is it normally it appears to be constantly restarting? Its running as expected.
EventHub Trigger and writing to a SQL Db fine)
Linux:
2022-05-26T12:32:25 Welcome, you are now connected to log-streaming service.
Starting Log Tail -n 10 of existing logs ----
/appsvctmp/volatile/logs/runtime/32d570889ada5fffd4821e889d028629adf71f5ff36ea7394911d6816e8e8aff.log
2022-05-26T12:08:53.855237110Z: [INFO] function-name : [00000000-0000-0000-0000-000000000000] [SystemAssigned] Added Identity with ClientId: <CLIENT-ID>
2022-05-26T12:08:53.856038609Z: [INFO] function-name : [00000000-0000-0000-0000-000000000000] Starting TokenService from /app with the following: IsLinuxDedicated: True, IsLinuxConsumption: False, IsWindows: False.
2022-05-26T12:08:53.970340540Z: [INFO] Hosting environment: Production
2022-05-26T12:08:53.970368740Z: [INFO] Content root path: /app
2022-05-26T12:08:53.970380340Z: [INFO] Now listening on: http://[::]:8081
2022-05-26T12:08:53.970385040Z: [INFO] Application started. Press Ctrl+C to shut down.
2022-05-26T12:08:54.993790139Z: [INFO] function-name : [5986fb39-9525-43c0-a14d-06bfdbe0fb9c] Incoming request on /healthcheck?api-version=2021-08-01
2022-05-26T12:08:59.151768328Z: [INFO] function-name : [bcc7a3ba-02b1-434c-bfd2-32f04990418f] Incoming request on /robots933456.txt
2022-05-26T12:09:25.450404632Z: [INFO] function-name : [00000000-0000-0000-0000-000000000000] Configuration update started. Site: function-name
2022-05-26T12:09:25.450426232Z: [INFO] function-name : [00000000-0000-0000-0000-000000000000] [SystemAssigned] Added Identity with ClientId: <CLIENT-ID>
/appsvctmp/volatile/logs/runtime/6acd2cf91b88dfaffb90c31b64b88a8ea919b18e2d1c9d75e97e6a27f39fb89f.log
2022-05-26T11:12:17.982676382Z: [INFO] Starting OpenBSD Secure Shell server: sshd.
2022-05-26T11:12:24.343773510Z: [INFO] Hosting environment: Production
2022-05-26T11:12:24.343798510Z: [INFO] Content root path: /azure-functions-host
2022-05-26T11:12:24.343812510Z: [INFO] Now listening on: http://[::]:80
2022-05-26T11:12:24.343816410Z: [INFO] Application started. Press Ctrl+C to shut down.
/appsvctmp/volatile/logs/runtime/321fcf9de2622c3c3dcc032a4cd3545b35e8797501f155b040b2397e2f7d31ea.log
2022-05-26T12:07:53.867902158Z: [INFO] function-name : [00000000-0000-0000-0000-000000000000] [SystemAssigned] Added Identity with ClientId: <CLIENT-ID>
2022-05-26T12:07:53.867933758Z: [INFO] function-name : [00000000-0000-0000-0000-000000000000] Starting TokenService from /app with the following: IsLinuxDedicated: True, IsLinuxConsumption: False, IsWindows: False.
2022-05-26T12:07:54.147981531Z: [INFO] Hosting environment: Production
2022-05-26T12:07:54.148010631Z: [INFO] Content root path: /app
2022-05-26T12:07:54.148262830Z: [INFO] Now listening on: http://[::]:8081
2022-05-26T12:07:54.148272330Z: [INFO] Application started. Press Ctrl+C to shut down.
2022-05-26T12:07:55.448095518Z: [INFO] function-name : [bcd344a8-ebd4-4b29-980c-7139da3f211d] Incoming request on /healthcheck?api-version=2021-08-01
2022-05-26T12:07:58.753565940Z: [INFO] function-name : [328b58ab-cfca-4cf8-876c-ae705493510d] Incoming request on /robots933456.txt
2022-05-26T12:08:50.957872214Z: [INFO] function-name : [00000000-0000-0000-0000-000000000000] Configuration update started. Site: function-name
2022-05-26T12:08:50.957900814Z: [INFO] function-name : [00000000-0000-0000-0000-000000000000] [SystemAssigned] Added Identity with ClientId: <CLIENT-ID>
Where as my windows logs:
Executing 'Functions.SourceReader' (Reason='(null)', Id=0b300c0f-ed5e-446e-a6ac-4ca6e049cdca)
[2022-05-26T12:37:00.624Z]
[2022-05-26T12:37:00.626Z] Trigger Details: PartionId: 4, Offset: 87823505798976-87823505806248, EnqueueTimeUtc: 2022-05-19T12:30:40.8030000+00:00-2022-05-19T12:30:40.8030000+00:00, SequenceNumber: 677125426-677125435, Count: 10
[2022-05-26T12:37:00.624Z] My Console Log

Azure linux logs gives Detailed Information about each and every detail because of which logs are more, Syslog is a widely used Linux event logging mechanism. Messages are sent by applications and may be saved locally or forwarded to a Syslog collector. The Log Analytics agent for Linux configures the local Syslog daemon to forward messages to the agent when it is installed. After that, the agent delivers the message to Azure Monitor, which creates a record for it because of which logs are more.
For more information you can go through the Microsoft Documentation.

Related

EB CLI create failed with error: TypeError - expected str, bytes or os.PathLike object, not NoneType

I'm first time I deploy an nodejs expresss application to AWS using EB CLI follow by aws guide
First step, I run eb init success.
Next step, I run eb create my-env to create an environment. And I get a error message:
ERROR: TypeError - expected str, bytes or os.PathLike object, not NoneType
Update: This's log when I run eb logs
/var/log/eb-engine.log
----------------------------------------
2021/02/24 02:37:43.600169 [INFO] Executing instruction: RunAppDeployPreDeployHooks
2021/02/24 02:37:43.600179 [INFO] The dir .platform/hooks/predeploy/ does not exist in the application. Skipping this step...
2021/02/24 02:37:43.600191 [INFO] Executing instruction: stop X-Ray
2021/02/24 02:37:43.600196 [INFO] stop X-Ray ...
2021/02/24 02:37:43.600212 [INFO] Running command /bin/sh -c systemctl show -p PartOf xray.service
2021/02/24 02:37:43.607595 [WARN] stopProcess Warning: process xray is not registered
2021/02/24 02:37:43.607611 [INFO] Running command /bin/sh -c systemctl stop xray.service
2021/02/24 02:37:43.615106 [INFO] Executing instruction: stop proxy
2021/02/24 02:37:43.615123 [INFO] Running command /bin/sh -c systemctl show -p PartOf httpd.service
2021/02/24 02:37:43.623248 [WARN] deregisterProcess Warning: process httpd is not registered, skipping...
2021/02/24 02:37:43.623266 [INFO] Running command /bin/sh -c systemctl show -p PartOf nginx.service
2021/02/24 02:37:43.628431 [WARN] deregisterProcess Warning: process nginx is not registered, skipping...
2021/02/24 02:37:43.628457 [INFO] Executing instruction: FlipApplication
2021/02/24 02:37:43.628462 [INFO] Fetching environment variables...
2021/02/24 02:37:43.628470 [INFO] setting default port 8080 to application
2021/02/24 02:37:43.628559 [INFO] Purge old process...
2021/02/24 02:37:43.628593 [INFO] Register application processes...
2021/02/24 02:37:43.628598 [INFO] Registering the proc: web
Update 2: Now, I deployed my application to AWS EB by manual (upload source zip). I still find and fix above problem.
I search many time but I not found solution to fix it. If you understand my problem, please help me. Thank you so much.
FINAL UPDATE: I resolved problem by this comment. problem involve to git config.

error while accessing Hyperldger explorer "Cannot GET /"

I have configured our Fabric network (v1.4) with Explorer (latest version).
node --version v8.16.0
No errors in db log
No application level errors
Explorer syncing process is going on continuously for the network
Able to view the updated data in DB
http://localhost:8080/api-docs/ (Explorer Swagger) works fine.
However while accessing http://localhost:8080/ i am getting
Cannot GET / error.
Chrome inspect logs -
Failed to load resource: the server responded with a status of http://localhost:8080/ 404 (Not Found)
console logs -
[2020-01-28T22:30:53.167] [INFO] PgService - SSL to Postgresql disabled
[2020-01-28T22:30:53.167] [INFO] PgService - connecting to Postgresql postgres://hppoc:******#127.0.0.1:5432/fabricexplorer
[2020-01-28T22:30:54.285] [INFO] Platform - client_configs.name first-network client_configs.profile ./connection-profile/first-network.json
[2020-01-28T22:30:54.285] [INFO] Platform - FabricUtils.createFabricClient
[2020-01-28T22:30:54.286] [INFO] FabricConfig - config.client.tlsEnable true
[2020-01-28T22:30:54.287] [INFO] FabricGateway - peer0.org1.example.com
[2020-01-28T22:30:54.287] [INFO] FabricGateway - /path/fabric-samples/first-network/crypto-config/peerOrganizations/org1.example.com/users/Admin#org1.example.com/msp/signcerts/Admin#org1.example.com-cert.pem
adminPrivateKeyPath /path/fabric-samples/first-network/crypto-config/peerOrganizations/org1.example.com/users/Admin#org1.example.com/msp/keystore/e65fa2dd29a69b2b28f9e439d1a8d555d411e9906e5a20d0a7341207a3a46424_sk
[2020-01-28T22:30:54.287] [INFO] FabricConfig - FabricConfig, this.config.channels mychannel
[2020-01-28T22:30:54.607] [INFO] FabricClient - FabricClient.discover_results endpoint { host: 'orderer.example.com', port: 7050 }
[2020-01-28T22:30:54.638] [INFO] Platform - FabricUtils.createDetachClient
[2020-01-28T22:30:54.640] [INFO] Platform - initializeListener, client_name, client first-network { name: 'first-network',
profile: './connection-profile/first-network.json' }
[2020-01-28T22:30:54.646] [INFO] main - Please open web browser to access :http://localhost:8080/
[2020-01-28T22:30:54.646] [INFO] main - pid is 18213
[2020-01-28T22:30:54.782] [INFO] PgService - SSL to Postgresql disabled
[2020-01-28T22:30:54.782] [INFO] PgService - connecting to Postgresql postgres://hppoc:******#127.0.0.1:5432/fabricexplorer
[2020-01-28T22:30:55.397] [INFO] SyncPlatform - Updating the client network and other details to DB
[2020-01-28T22:30:55.404] [INFO] SyncServices - SyncServices.synchNetworkConfigToDB client first-network channel_name mychannel
[2020-01-28T22:30:55.427] [INFO] FabricClient - FabricClient.discover_results endpoint { host: 'orderer.example.com', port: 7050 }
[2020-01-28T22:30:55.528] [INFO] SyncPlatform - Sync process is started for the network : [first-network] and client : [first-network]
[2020-01-28T22:30:55.530] [INFO] FabricConfig - config.client.tlsEnable true
[2020-01-28T22:30:55.530] [INFO] FabricGateway - peer0.org1.example.com
[2020-01-28T22:30:55.530] [INFO] FabricGateway - /path/fabric-samples/first-network/crypto-config/peerOrganizations/org1.example.com/users/Admin#org1.example.com/msp/signcerts/Admin#org1.example.com-cert.pem
adminPrivateKeyPath /path/fabric-samples/first-network/crypto-config/peerOrganizations/org1.example.com/users/Admin#org1.example.com/msp/keystore/e65fa2dd29a69b2b28f9e439d1a8d555d411e9906e5a20d0a7341207a3a46424_sk
[2020-01-28T22:30:55.530] [INFO] FabricConfig - FabricConfig, this.config.channels mychannel
[2020-01-28T22:30:55.798] [INFO] FabricClient - FabricClient.discover_results endpoint { host: 'orderer.example.com', port: 7050 }
[2020-01-28T22:30:55.833] [INFO] SyncServices - SyncServices.synchNetworkConfigToDB client first-network channel_name mychannel
[2020-01-28T22:30:55.865] [INFO] FabricClient - FabricClient.discover_results endpoint { host: 'orderer.example.com', port: 7050 }
[2020-01-28T22:30:55.883] [INFO] Sync - Synchronizer pid is 18220
[2020-01-28T22:30:55.901] [INFO] SyncServices - block_row.blocknum 4
[2020-01-28T22:30:58.200] [INFO] SyncPlatform - Updating the client network and other details to DB
[2020-01-28T22:30:58.209] [INFO] SyncServices - SyncServices.synchNetworkConfigToDB client first-network channel_name mychannel
[2020-01-28T22:30:58.241] [INFO] FabricClient - FabricClient.discover_results endpoint { host: 'orderer.example.com', port: 7050 }
So, I found the answer to the problem -
Weirdly the problem was it shows everywhere that it serves on localhost:8080 but after a lot of research found out that node js cannot serve static pages which hyperledger explorer is on port 8080.
So, needs to use "serve" to build and serve that page. I had did that 2 days back, it starts on port 5000 and it`s own IP address, but I was getting error on web browser for violation of "control security policy".
Solution :
$ cd ~/Hyperledger/blockchain-explorer/client
$ npm install
$ npm test -- -u --coverage
$ npm run build
$ npm install -g serve
$ serve -s build
Now it will show you the output something like :
┌────────────────────────────────────────────────────┐
│ │
│ Serving! │
│ │
│ - Local: http://localhost:5000 │
│ - On Your Network: http://160.33.244.178:5000 │
│ │
│ Copied local address to clipboard! │
│ │
└────────────────────────────────────────────────────┘
If you open up : http://localhost:5000 it will not show anything and in the network logs on inspect window will show you - "control security policy violation".
so use port 8080 instead like this :
- Local: http://localhost:8080 │
- On Your Network: http://160.33.244.178:8080
Also, you would need to start the hyperldger explorer server :
$ cd ~/<YourPath>/blockchain-explorer
$ ./start.sh
You will see login page with first network selected.
Use :
"adminUser" is the the admin user of the network, in this case it's fabric CA or an identity user.
"adminPassword" is the password for the admin user.
and you are in !
If you start explorer using docker compose, that is in root of repo, then check your 8090 port, cause docker map 8080 port of container to 8090 port of your machine.
See github:hyperledger/blockain-explorer/docker-compose.yaml

Fabric-Ca server setup issue

I am using the given link for exploring the fabric-ca
http://fabric-ca.readthedocs.io/en/latest/users-guide.html
Following the content in the link, I am trying to setup fabric-ca-server with mysql as DB and I am specifying the below config for the same in the fabric-ca-server-config.yaml
db:
type: mysql
datasource: root:**123##tcp(localhost:3306)/fabric_ca?parseTime=true
tls:
enabled: false
certfiles:
- db-server-cert.pem
client:
certfile: db-client-cert.pem
keyfile: db-client-key.pem
I do not pass the argument tls=custom in 'datasource' above as I am not using the TLS
Upon server startup I get
root#Openwhisk-Node2-172:~/fabric-ca/fabric-ca-server# fabric-ca-server start -b admin:adminpw
2017/09/05 15:25:17 [INFO] Configuration file location: /root/fabric-ca/fabric-ca-server/fabric-ca-server-config.yaml
2017/09/05 15:25:17 [INFO] Starting server in home directory: /root/fabric-ca/fabric-ca-server
2017/09/05 15:25:17 [INFO] The CA key and certificate already exist
2017/09/05 15:25:17 [INFO] The key is stored by BCCSP provider 'SW'
2017/09/05 15:25:17 [INFO] The certificate is at: /root/fabric-ca/fabric-ca-server/ca-cert.pem
2017/09/05 15:25:17 [INFO] Initialized mysql database at root:Nokia123##tcp(localhost:3306)/fabric_ca?parseTime=true
2017/09/05 15:25:17 [INFO] Home directory for default CA: /root/fabric-ca/fabric-ca-server
2017/09/05 15:25:17 [INFO] Listening on %!s(int=7054)%!(EXTRA string=http://0.0.0.0:7054)
but when I try to use the client for enroll bootstrap identity, I get
fabric-ca-client enroll -u http://admin:adminpw#localhost:7054
2017/09/05 15:27:40 [INFO] User provided config file: /root/fabric-ca/fabric-ca-client1/admin/fabric-ca-client-config.yaml
2017/09/05 15:27:40 [INFO] Created a default configuration file at /root/fabric-ca/fabric-ca-client1/admin/fabric-ca-client-config.yaml
2017/09/05 15:27:40 [INFO] generating key: &{A:ecdsa S:256}
2017/09/05 15:27:40 [INFO] encoded CSR
Error: Error response from server was: Authorization failure
The database is up.
I have also created a database with name fabric_ca
NO_ZERO_DATE related changes are also done
Kindly help. let me know if some steps I have missed or if I have done something wrong
If you actually created the database prior to running the fabric-ca-server that's likely the issue. The code currently just checks to see if the database exists. If it exists, then it does not run any of the SQL setup scripts. So the best best is to just start with a clean MYSQL which does not have any database instance created.

cassandra and vault error logs

after upgrading a node in cassandra, these error in log occured:
I want to investigate but dont have a direction, any clue will help
thanks
2016/09/19 06:24:49 [INFO] core: post-unseal setup starting
2016/09/19 06:24:49 [INFO] core: mounted backend of type generic at secret/
2016/09/19 06:24:49 [INFO] core: mounted backend of type cubbyhole at cubbyhole/
2016/09/19 06:24:49 [INFO] core: mounted backend of type system at sys/
2016/09/19 06:24:49 [INFO] core: mounted backend of type cassandra at cassandra/
2016/09/19 06:24:49 [INFO] rollback: starting rollback manager
2016/09/19 06:24:50 [INFO] expire: restored 2 leases
2016/09/19 06:24:50 [INFO] core: post-unseal setup complete
2016/09/19 06:24:55 gocql: unable to dial control conn node-0.cassandra-app.mesos:9042: dial tcp 10.0.2.42:9042: getsockopt: connection refused
2016/09/19 06:25:12 error: failed to connect to 10.0.2.42:9042 due to error: gocql: no response to connection startup within timeout
Cassandra cluster is not cross-version compatible, you can not upgrade a node only, you have to upgrade the cluster. This is a common mistake people tend to do, please see this video here it mentiones this problem, also it is very very useful with lots of good info.

Spring-boot slow to start

When I launch my jhipster app using "mvn spring-boot:run", it takes up to 60 seconds to start...
First part of my log is :
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building jhipster 0.0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> spring-boot-maven-plugin:1.1.9.RELEASE:run (default-cli) # jhipster >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-versions) # jhipster ---
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) # jhipster ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 4 resources
[INFO] Copying 22 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) # jhipster ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) # jhipster ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) # jhipster ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] <<< spring-boot-maven-plugin:1.1.9.RELEASE:run (default-cli) # jhipster <<<
[INFO]
[INFO] --- spring-boot-maven-plugin:1.1.9.RELEASE:run (default-cli) # jhipster ---
[INFO] Attaching agents: []
Listening for transport dt_socket at address: 5005
--> Then it hangs for around 30 seconds before continuing :
[INFO] com.mycompany.myapp.Application - Starting Application on MacBook-Pro.local with PID 5130 (/Users/othomas/Developpement/jhipster-1.9.0/target/classes started by othomas in /Users/othomas/Developpement/jhipster-1.9.0)
[DEBUG] com.mycompany.myapp.Application - Running with Spring Boot v1.1.9.RELEASE, Spring v4.0.8.RELEASE
[DEBUG] org.jboss.logging - Logging Provider: org.jboss.logging.Log4jLoggerProvider
...
I remember having used older versions of jhipster generator (0.17 etc) et it started in 15-20 seconds.
Is it normal or is there a problem on my side ? Where to look for ?
Thanks,
O.
I've been suffering slow startup times myself and wondering what the cause was. I get all the console messages saying various things have started and then it hangs just before the final message to say the app has loaded.
Eventually I found I could use Java VisualVM as part of the JDK to see what was going on. If you have the jdk installed its jvisualvm.exe in the bin folder. Then when I select to debug as Application.java the tomcat process pops up and you can track what's going on.
I took a couple of thread dumps where it hangs and it always seemed to be where the swagger API docs are being generated. A bit more digging and this is configured in a class called MetricsConfiguration which is excluded if you run with a profile called "fast".
In eclipse I edited my debug configuration to include a program argument of:
--spring.profiles.active=dev,fast
This cuts down the startup time from 230 seconds to just 25!
I had a quick scan and fast seems to disable all sorts of things. It mainly looks like the stuff under the admin menu which you'll probably not need during development anyway. Personally I would prefer a fast bootup to being able to see the rest docs during development.
Swagger being such a hog made me wonder if it's such a good idea after all. Is it worth the cost? i then read this http://java.dzone.com/articles/swagger-great and I'm considering just removing it altogether. It's a nice idea but seems to add 33mb to the build + for me was causing really slow startup times.
For info I have around 16 entities. So not small but not excessively large either.
Make sure you aren't running the server in debug mode and have a breakpoint set. This reduced the startup time of one of my applications from 3 min to 22 sec.
This is weird.
Indeed, it should start in 5-15 seconds depending on your machine and specific setup.
But it should not hang for 30 seconds: the line you show is a bit new, it's because we launch the application in debug mode when you use the dev profile -> you can attach a debugger on it.
It looks like it's waiting for you to connect a debugger: I've never seen it myself, so maybe you have some specific JVM option for attaching a debugger at start up, with a timeout of 30 seconds?
Thanks for your feedback. I investigated and put more logs in the app (Application.java).
Actually the problem does not come from the debug mode, the application does not hang here.
The first big "pause" comes from the scanning of liquibase packages (addLiquibaseScanPackages(); in Application.java ) : 26 seconds !
My second pause is still related to Liquibase (log "Configuring Liquibase" ) : 20 seconds. During that time, if I put Liquibase log level to DEBUG, I see that a lock is set and then released but it happens very quickly.
I really don't understand. I am using h2 in-memory database, jdk 1.7.0_25 and Maven 3.0.5, running on MacBook Pro with SSD.
Here is my full log when I run with "mvn spring-boot:run".
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building jhipster 0.0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> spring-boot-maven-plugin:1.1.9.RELEASE:run (default-cli) # jhipster >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-versions) # jhipster ---
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) # jhipster ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 4 resources
[INFO] Copying 22 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) # jhipster ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) # jhipster ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) # jhipster ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] <<< spring-boot-maven-plugin:1.1.9.RELEASE:run (default-cli) # jhipster <<<
[INFO]
[INFO] --- spring-boot-maven-plugin:1.1.9.RELEASE:run (default-cli) # jhipster ---
[INFO] Attaching agents: []
Listening for transport dt_socket at address: 5005
Wed Nov 26 16:32:23 CET 2014 Added log : Application is about to start
Wed Nov 26 16:32:28 CET 2014Added log : Application started, now we set banner to false
Wed Nov 26 16:32:28 CET 2014Added log : About to add Default profile
Wed Nov 26 16:32:28 CET 2014Added log : Default Profile added. Now we scan liquibase packages
Wed Nov 26 16:32:28 CET 2014Added log : Liquibase pakages scanned. Now we run the app
2014-11-26 16:32:54,564 [INFO] com.mycompany.myapp.Application - Starting Application on MacBook-Pro.local with PID 25452 (/Users/othomas/Developpement/jhipster-1.9.0/target/classes started by othomas in /Users/othomas/Developpement/jhipster-1.9.0)
2014-11-26 16:32:54,567 [DEBUG] com.mycompany.myapp.Application - Running with Spring Boot v1.1.9.RELEASE, Spring v4.0.8.RELEASE
2014-11-26 16:32:57,429 [DEBUG] org.jboss.logging - Logging Provider: org.jboss.logging.Log4jLoggerProvider
2014-11-26 16:32:57,559 [DEBUG] com.mycompany.myapp.config.AsyncConfiguration - Creating Async Task Executor
2014-11-26 16:32:58,305 [DEBUG] com.mycompany.myapp.config.MetricsConfiguration - Registering JVM gauges
2014-11-26 16:32:58,379 [INFO] com.mycompany.myapp.config.MetricsConfiguration - Initializing Metrics JMX reporting
2014-11-26 16:32:58,445 [DEBUG] com.mycompany.myapp.config.DatabaseConfiguration - Configuring Datasource
2014-11-26 16:32:59,353 [DEBUG] com.mycompany.myapp.config.DatabaseConfiguration - Configuring Liquibase
2014-11-26 16:33:19,489 [DEBUG] com.mycompany.myapp.config.CacheConfiguration - Starting Ehcache
2014-11-26 16:33:19,491 [DEBUG] com.mycompany.myapp.config.CacheConfiguration - Registering Ehcache Metrics gauges
2014-11-26 16:33:23,419 [DEBUG] com.mycompany.myapp.config.MailConfiguration - Configuring mail server
2014-11-26 16:33:24,559 [INFO] com.mycompany.myapp.config.WebConfigurer - Web application configuration, using profiles: [dev]
2014-11-26 16:33:24,560 [DEBUG] com.mycompany.myapp.config.WebConfigurer - Initializing Metrics registries
2014-11-26 16:33:24,564 [DEBUG] com.mycompany.myapp.config.WebConfigurer - Registering Metrics Filter
2014-11-26 16:33:24,565 [DEBUG] com.mycompany.myapp.config.WebConfigurer - Registering Metrics Servlet
2014-11-26 16:33:24,567 [DEBUG] com.mycompany.myapp.config.WebConfigurer - Registering GZip Filter
2014-11-26 16:33:24,569 [DEBUG] com.mycompany.myapp.config.WebConfigurer - Initialize H2 console
2014-11-26 16:33:24,570 [INFO] com.mycompany.myapp.config.WebConfigurer - Web application fully configured
2014-11-26 16:33:29,753 [INFO] com.mycompany.myapp.Application - Running with Spring profile(s) : [dev]
2014-11-26 16:33:30,012 [INFO] com.mycompany.myapp.config.ThymeleafConfiguration - loading non-reloadable mail messages resources
2014-11-26 16:33:30,896 [DEBUG] com.mycompany.myapp.aop.logging.LoggingAspect - Enter: com.mycompany.myapp.repository.CustomAuditEventRepository.auditEventRepository() with argument[s] = []
2014-11-26 16:33:30,905 [DEBUG] com.mycompany.myapp.aop.logging.LoggingAspect - Exit: com.mycompany.myapp.repository.CustomAuditEventRepository.auditEventRepository() with result = com.mycompany.myapp.repository.CustomAuditEventRepository$1#1edce963
2014-11-26 16:33:37,229 [INFO] com.mycompany.myapp.Application - Started Application in 68.311 seconds (JVM running for 73.972)
Wed Nov 26 16:33:37 CET 2014Added log : App is running
Thanks,
Olivier
It is advised to start the application with the debug points disabled unless you want to debug while starting up
you can just modify xmx like java -jar -Xmx1024m.
Because when Spring boot started, it loads lots of spring bean. You can add heap memory to improve it's performance.

Resources