# Issue with mender client 2.4.0 on standalone update **URL:** \ **Category:** General Discussions\ **Created:** [October 9, 2020, 5:57am UTC](https://hub.mender.io/t/issue-with-mender-client-2-4-0-on-standalone-update/2642 "2020-10-09T05:57:40Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [October 9, 2020, 5:57am UTC](https://hub.mender.io/t/issue-with-mender-client-2-4-0-on-standalone-update/2642/1 "2020-10-09T05:57:40Z")
Hi, I’m facing an issue on meta-mender dunfell that on some sunxi board where I used standalone update successfully on v2.3 in mender v2.4 when I run mender commit I got: ```auto build/src/github.com/mendersoftware/mender/main.go:28 main.doMain() There is nothing to commit ``` When checked source seems env variable `upgrade_available` is not set. When before commit I set it to 1 commit will pass. Am I missing something or something was changed between v2.3 and v2.4? Thanks ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [October 9, 2020, 11:02am UTC](https://hub.mender.io/t/issue-with-mender-client-2-4-0-on-standalone-update/2642/2 "2020-10-09T11:02:06Z")
Nothing that I am aware of. What is the U-Boot version? Can you maybe share output of: ```auto mender -install fw_printenv reboot fw_printenv ``` ---
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [October 9, 2020, 11:26am UTC](https://hub.mender.io/t/issue-with-mender-client-2-4-0-on-standalone-update/2642/3 "2020-10-09T11:26:51Z")
u-boot version is 2020.01 -\> comes from meta-mender dunfell andI verify that env handling working fine. I’ll get more logs and get back. Thanks. ---
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [October 9, 2020, 7:20pm UTC](https://hub.mender.io/t/issue-with-mender-client-2-4-0-on-standalone-update/2642/4 "2020-10-09T19:20:46Z")
Logs can be found here: [https://drive.google.com/file/d/1AzasjIjAcT7kB5-m2DYEvY9Vb-6Gmm-f/view?usp=sharing](https://drive.google.com/file/d/1AzasjIjAcT7kB5-m2DYEvY9Vb-6Gmm-f/view?usp=sharing) Basically upgrade\_available + mender\_boot\_part after `mender install` are not set. I verity and can set u-boot env variable, reboot and after reboot read it back. Really strange 🤫 🤔 ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [October 9, 2020, 7:22pm UTC](https://hub.mender.io/t/issue-with-mender-client-2-4-0-on-standalone-update/2642/5 "2020-10-09T19:22:20Z")
> [@MarekBelisko](#): > > Logs can be found here: [logs.zip - Google Drive](https://drive.google.com/file/d/1AzasjIjAcT7kB5-m2DYEvY9Vb-6Gmm-f/view?usp=sharing) Restricted access. ---
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [October 9, 2020, 7:23pm UTC](https://hub.mender.io/t/issue-with-mender-client-2-4-0-on-standalone-update/2642/6 "2020-10-09T19:23:17Z")
Pls try again ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [October 12, 2020, 6:51am UTC](https://hub.mender.io/t/issue-with-mender-client-2-4-0-on-standalone-update/2642/7 "2020-10-12T06:51:40Z")
Unfortunately the logs do no say much. Everything looks ok from the Mender client side. But to confirm, does the Mender client 2.3 work in the same environment? I would otherwise point towards the [integration checklist](https://docs.mender.io/system-updates-yocto-project/board-integration/bootloader-support/u-boot/integration-checklist), as this seems to be a problem with the U-Boot enviornment. Can you also share content of `/etc/fw_env.confg` ? ---
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [October 12, 2020, 9:17am UTC](https://hub.mender.io/t/issue-with-mender-client-2-4-0-on-standalone-update/2642/8 "2020-10-12T09:17:08Z")
I verify integration list and everything seems fine. I debug a mender code a bit and seems I have an issue with setting any u-boot env from code. I saw that for setting it’s used fw\_setenv -s - to read from stdin and I verify using shell script fw\_setenv -s - \<\<\< echo “mender\_boot\_part=2” but when read back it’s not updated still. Ideas? Thanks Marek ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [October 12, 2020, 9:27am UTC](https://hub.mender.io/t/issue-with-mender-client-2-4-0-on-standalone-update/2642/9 "2020-10-12T09:27:04Z")
Can you try: ```auto echo test_variable=1 | fw_setenv -s - fw_printenv test_variable ``` and ```auto echo test_variable 2 | fw_setenv -s - fw_printenv test_variable ``` ---
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [October 12, 2020, 9:52am UTC](https://hub.mender.io/t/issue-with-mender-client-2-4-0-on-standalone-update/2642/10 "2020-10-12T09:52:00Z")
Both runs return test\_variable= Marek ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [October 12, 2020, 11:29am UTC](https://hub.mender.io/t/issue-with-mender-client-2-4-0-on-standalone-update/2642/11 "2020-10-12T11:29:51Z")
Can you check what packages provides `fw_setenv` ? On dunfell I believe it should come from `libubootenv`, e.g: ```auto oe-pkgdata-util find-path /usr/bin/fw_setenv libubootenv-bin: /usr/bin/fw_setenv ``` This is expected to work (verified a new dunfell build today): > ```auto > root@raspberrypi4:~# echo test_variable=1 | fw_setenv -s - > root@raspberrypi4:~# fw_printenv test_variable > test_variable=1 > > ``` ---
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [October 12, 2020, 11:44am UTC](https://hub.mender.io/t/issue-with-mender-client-2-4-0-on-standalone-update/2642/12 "2020-10-12T11:44:15Z")
Yes got the same result but it’s strange it’s not working on my end when in mender code replace WriteEnv by calling fw\_setenv individually for all variables it start working. I have libubootenv v0.2 Thanks BR, Marek