# Question on bootup messages **URL:** \ **Category:** Uncategorized\ **Created:** [December 3, 2023, 3:56pm UTC](https://forums.nanovms.com/t/question-on-bootup-messages/32 "2023-12-03T15:56:35Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![ernestomedina17](https://avatars.discourse-cdn.com/v4/letter/e/c89c15/32.png) [@ernestomedina17](https://forums.nanovms.com/u/ernestomedina17)\ **Post date:** [December 3, 2023, 3:56pm UTC](https://forums.nanovms.com/t/question-on-bootup-messages/32/1 "2023-12-03T15:56:35Z")
Hello When I launch my app in aws on a t4g.nano instance I see these msgs in the system log console: ```auto UEFI firmware (version built at 09:00:00 on Nov 1 2018) e[2Je[01;01He[=3he[2Je[01;01He[2Je[01;01He[=3he[2Je[01;01He[2Je[01;01He[=3he[2Je[01;01He[0me[35me[40men1: assigned 169.254.202.129 en1: assigned FE80::7C:9EFF:FED4:A459 en1: assigned 2A05:D014:11FB:6103:AD1C:DC7F:D2F5:7300 2023/12/03 14:43:30 DerBurritoAPI Initialization start... frame trace: loaded klibs: ntp@0xffffffff80200000/0x7000 tls@0xffffffff80300000/0xa5000 cloudwatch@0xffffffff80220000/0x11000 assertion t >= last_raw failed at /home/circleci/project/src/runtime/clock.h:78 (IP 0xffffffff8002b210) in now(); halt Keep alive watchdog timeout. Trigger reset is on free uncompleted tx mbuf qid 1 idx 0x18 Device reset completed successfully, Driver info: Elastic Network Adapter (ENA) ena v2.3.0 Potential MSIX issue on Rx side Queue = 0. Reset the device Trigger reset is on free uncompleted tx mbuf qid 1 idx 0x0 Device reset completed successfully, Driver info: Elastic Network Adapter (ENA) ena v2.3.0 Potential MSIX issue on Rx side Queue = 0. Reset the device Trigger reset is on ... ``` I notice that my app gets executed, because this msg is the first line of code in my app: ```auto 2023/12/03 14:43:30 DerBurritoAPI Initialization start... ``` Then the klibs get loaded, which I would expect to happen before the app gets executed, I thought that this happened because I set **“CPUs”: 2,** in the config.json, so I set it to 1, but the result was the same. And then a failed assertion, with a **halt** at the end: ```auto assertion t >= last_raw failed at /home/circleci/project/src/runtime/clock.h:78 (IP 0xffffffff8002b210) in now(); halt ``` After that, the same messages keep on repeating, and my application gets “halted” (I assume) as it does not respond. Any idea of what would be happening? I also added this config to see if it would change the order of the messages but it didn’t. ```auto "exec_wait_for_ip6_secs": "5", "exec_wait_for_ip4_secs": "5", ``` Note that my VPC contains IPv6-only subnets, so not sure if that might have something to do with this problem. I’ll try deploying my app in a traditional IPv4 subnet. Will keep you posted. Thanks and regards, Ernesto Medina. ---
**Author:** ![francescolavra](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.nanovms.com/francescolavra/32/33_2.png) [@francescolavra](https://forums.nanovms.com/u/francescolavra)\ **Post date:** [December 5, 2023, 9:37am UTC](https://forums.nanovms.com/t/question-on-bootup-messages/32/2 "2023-12-05T09:37:40Z")
You are right that the klibs are loaded before the app gets executed; in your log, the “loaded klibs” line is only there as part of the error messages printed as a result of the failed assertion (it’s an informative message listing the klibs that were loaded in the kernel at the time when the failure happened). The bug causing this failure has been identified and fixed in [AWS: add support for PTP hardware clock by francescolavra · Pull Request #1979 · nanovms/nanos · GitHub](https://github.com/nanovms/nanos/pull/1979). If you want, you can try the fixed Nanos kernel by specifying the `--nanos-version 46cf22d` option in your Ops command line when creating an image. ---
**Author:** ![ernestomedina17](https://avatars.discourse-cdn.com/v4/letter/e/c89c15/32.png) [@ernestomedina17](https://forums.nanovms.com/u/ernestomedina17)\ **Post date:** [December 5, 2023, 10:47am UTC](https://forums.nanovms.com/t/question-on-bootup-messages/32/3 "2023-12-05T10:47:14Z")
Would [this](https://docs.ops.city/ops/configuration#nanos_version) work also? ```auto { "NanosVersion": ["46cf22d"] } ``` ---
**Author:** ![francescolavra](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.nanovms.com/francescolavra/32/33_2.png) [@francescolavra](https://forums.nanovms.com/u/francescolavra)\ **Post date:** [December 5, 2023, 10:52am UTC](https://forums.nanovms.com/t/question-on-bootup-messages/32/4 "2023-12-05T10:52:28Z")
No, specifying the Nanos version via the configuration file is currently not supported (except for the `NightlyBuild` flag). ---
**Author:** ![ernestomedina17](https://avatars.discourse-cdn.com/v4/letter/e/c89c15/32.png) [@ernestomedina17](https://forums.nanovms.com/u/ernestomedina17)\ **Post date:** [December 5, 2023, 11:10am UTC](https://forums.nanovms.com/t/question-on-bootup-messages/32/5 "2023-12-05T11:10:47Z")
Should I exclude `-n` while using `--nanos-version 46cf22d` or there is no conflict? ---
**Author:** ![francescolavra](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.nanovms.com/francescolavra/32/33_2.png) [@francescolavra](https://forums.nanovms.com/u/francescolavra)\ **Post date:** [December 5, 2023, 11:14am UTC](https://forums.nanovms.com/t/question-on-bootup-messages/32/6 "2023-12-05T11:14:11Z")
`-n` and `--nanos-version` should never be specified in the same command line because they conflict with each other, so yes, you should exclude `-n` while using `--nanos-version 46cf22d` ---
**Author:** ![ernestomedina17](https://avatars.discourse-cdn.com/v4/letter/e/c89c15/32.png) [@ernestomedina17](https://forums.nanovms.com/u/ernestomedina17)\ **Post date:** [December 5, 2023, 10:59pm UTC](https://forums.nanovms.com/t/question-on-bootup-messages/32/7 "2023-12-05T22:59:06Z")
I was able to fix the problem, thanks. We can close this one. Regards, Ernesto. ---
**Author:** ![leroga1934](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.nanovms.com/leroga1934/32/24_2.png) [@leroga1934](https://forums.nanovms.com/u/leroga1934)\ **Post date:** [September 20, 2024, 7:17am UTC](https://forums.nanovms.com/t/question-on-bootup-messages/32/8 "2024-09-20T07:17:03Z")
I also faced the same issue. Thanks for the solution. @ernestomedina17