# Ubuntu installation: network.host failure

**URL:** <https://community.cratedb.com/t/ubuntu-installation-network-host-failure/1703>\
**Category:** Installation\
**Tags:** fundamentals\
**Created:** [January 24, 2024, 4:48pm UTC](https://community.cratedb.com/t/ubuntu-installation-network-host-failure/1703 "2024-01-24T16:48:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![fhasanabadi](https://sea2.discourse-cdn.com/flex020/user_avatar/community.cratedb.com/fhasanabadi/32/1170_2.png) [@fhasanabadi](https://community.cratedb.com/u/fhasanabadi)\
**Post date:** [January 24, 2024, 4:48pm UTC](https://community.cratedb.com/t/ubuntu-installation-network-host-failure/1703/1 "2024-01-24T16:48:52Z")

</div>

Hi,

I’m heading to run CrateDB on a Ubuntu machine, aiming at make it accessible via a virtual network.  
When I add the network interface name in the crate.yaml file, crate fails with the following logs:  
How should I approach the network values for binding and make it accessible externally? Cheers!

```auto
× crate.service - CrateDB Server
     Loaded: loaded (/lib/systemd/system/crate.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Wed 2024-01-24 17:38:32 CET; 1s ago
       Docs: https://crate.io/docs/
    Process: 45404 ExecStart=/usr/share/crate/bin/crate -Cpath.conf=${CRATE_PATH_CONF} -Cpath.l>
   Main PID: 45404 (code=exited, status=78)
        CPU: 6.612s

Jan 24 17:38:32 cratedn001 crate[45404]: [2024-01-24T17:38:32,935][INFO][o.e.b.BootstrapChecks>
Jan 24 17:38:32 cratedn001 crate[45404]: ERROR: [1] bootstrap checks failed
Jan 24 17:38:32 cratedn001 crate[45404]: [1]: initial heap size [268435456] not equal to maximu>
Jan 24 17:38:32 cratedn001 crate[45404]: [2024-01-24T17:38:32,943][INFO][o.e.n.Node >
Jan 24 17:38:32 cratedn001 crate[45404]: [2024-01-24T17:38:32,953][INFO][o.e.n.Node >
Jan 24 17:38:32 cratedn001 crate[45404]: [2024-01-24T17:38:32,954][INFO][o.e.n.Node >
Jan 24 17:38:32 cratedn001 crate[45404]: [2024-01-24T17:38:32,968][INFO][o.e.n.Node >
Jan 24 17:38:32 cratedn001 systemd[1]: crate.service: Main process exited, code=exited, status=>
Jan 24 17:38:32 cratedn001 systemd[1]: crate.service: Failed with result 'exit-code'.
Jan 24 17:38:32 cratedn001 systemd[1]: crate.service: Consumed 6.612s CPU time.

```

---

<div class="post-metadata">

**Author:** ![proddata](https://sea2.discourse-cdn.com/flex020/user_avatar/community.cratedb.com/proddata/32/1379_2.png) [@proddata](https://community.cratedb.com/u/proddata)\
**Post date:** [January 24, 2024, 4:54pm UTC](https://community.cratedb.com/t/ubuntu-installation-network-host-failure/1703/2 "2024-01-24T16:54:41Z")

</div>

If you bind to a network reachable address, CrateDB performs bootstrap checks during startup  
see here:

> **[Bootstrap checks](https://cratedb.com/docs/crate/howtos/en/latest/admin/bootstrap-checks.html)**
>
> If you are binding to a network reachable IP address, CrateDB performs a number of bootstrap checks during startup. These checks examine your setup and will prevent startup if a problem is detected. This best practices guide is intended to help you...

One of the bootstrap checks that fails is the one concerning heap size, which on Ubuntu should be configurable in `/etc/default/crate`

also see here: [Debian GNU/Linux — CrateDB: Tutorials](https://cratedb.com/docs/crate/tutorials/en/latest/self-hosted/debian.html#id7)