# Update stuck in 'rebooting' state on hosted mender

**URL:** https://hub.mender.io/t/update-stuck-in-rebooting-state-on-hosted-mender/4915
**Category:** General Discussions
**Tags:** state-scripts, update
**Created:** [May 2, 2022, 8:08am UTC](https://hub.mender.io/t/update-stuck-in-rebooting-state-on-hosted-mender/4915 "2022-05-02T08:08:28Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![perceval](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/perceval/32/1557_2.png) [@perceval](https://hub.mender.io/u/perceval)
#### Post date: [May 2, 2022, 8:08am UTC](https://hub.mender.io/t/update-stuck-in-rebooting-state-on-hosted-mender/4915/1 "2022-05-02T08:08:28Z")

</div>

Hello all 😃

I tryed to add a state script to my Jetson TX2. Once I updated my device through hosted.mender the device reboot correctly and the update is installed but the device state on hosted mender is stuck at “rebooting”. What could cause such behaviour?

To add a state script I crated a dedicated recipe that `inherit mender-state-scripts`. The purpose of the script is to cleanup `mender.conf` files and correctly split up the confs between `/etc/` and `/data` partition. The script works well and give the expected result.

What did I miss?

 ![Screenshot from 2022-05-02 10-03-05](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/2X/9/9f276d570901ec8a701d04362be92ae72c4ebe87.png)

---

<div class="post-metadata">

### Author: ![perceval](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/perceval/32/1557_2.png) [@perceval](https://hub.mender.io/u/perceval)
#### Post date: [May 2, 2022, 5:01pm UTC](https://hub.mender.io/t/update-stuck-in-rebooting-state-on-hosted-mender/4915/2 "2022-05-02T17:01:25Z")

</div>

I Finally found out that my device couldn’t connect to the internet after reboot that is why. My DNS configuration was not properly done therefore the device couldn’t tell hosted.mender that it has correctly rebooted.

---

<div class="post-metadata">

### Author: ![oleorhagen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/oleorhagen/32/297_2.png) [@oleorhagen](https://hub.mender.io/u/oleorhagen)
#### Post date: [May 3, 2022, 6:10am UTC](https://hub.mender.io/t/update-stuck-in-rebooting-state-on-hosted-mender/4915/3 "2022-05-03T06:10:10Z")

</div>

Hi @perceval 👋

I am curious, how did you figure it out? Logs, troubleshoot? SSH ?

---

<div class="post-metadata">

### Author: ![perceval](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/perceval/32/1557_2.png) [@perceval](https://hub.mender.io/u/perceval)
#### Post date: [May 3, 2022, 10:33am UTC](https://hub.mender.io/t/update-stuck-in-rebooting-state-on-hosted-mender/4915/4 "2022-05-03T10:33:39Z")

</div>

Hey @oleorhagen,

I had still an ssh connexion on the device so I could run commands on it and investigate.  
first I noticed that I had network routing by pinging an internet IP (like 1.1.1.1 or 8.8.8.8) but no name resolution because ping [mender.io](http://mender.io) failed.  
The process responsible of name resolution when running a systemd based distribution is `systemd-resolved`. But the service was stopped in a failed state.

By looking at the `journald` errors and trying to restart `systemd-resolved` service, I understood that the folders `/var/volatile/log` and `/var/volatile/tmp` where missing. I created them and restarted the service. Et voilà I could ping [mender.io](http://mender.io). and the device came back on hosted.mender.