# MQTT Explorer v0.2.0 - MQTT swiss-army-knife

**URL:** <https://discourse.nodered.org/t/mqtt-explorer-v0-2-0-mqtt-swiss-army-knife/7308>\
**Category:** General\
**Created:** [27 January 2019 13:30 UTC](https://discourse.nodered.org/t/mqtt-explorer-v0-2-0-mqtt-swiss-army-knife/7308 "2019-01-27T13:30:14Z")\
**Posts on this page:** 14\
**Page:** 3

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [8 June 2019 21:15 UTC](https://discourse.nodered.org/t/mqtt-explorer-v0-2-0-mqtt-swiss-army-knife/7308/42 "2019-06-08T21:15:15Z")

</div>

> [@Colin](#):
>
> Is there a reason you are concerned about this or are you just trying to understand what is going on?

I'm not experiencing any problems, just doing some housekeeping, and if there are some retained messages bouncing about ad infinitum, it would probably be better to delete them.  
But not a big issue for me.

It's MQTT Explorer's fault!!! - ignorance is bliss 🤔

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [9 June 2019 07:31 UTC](https://discourse.nodered.org/t/mqtt-explorer-v0-2-0-mqtt-swiss-army-knife/7308/43 "2019-06-09T07:31:01Z")

</div>

> [@Paul-Reed](#):
>
> retained messages bouncing about ad infinitum

If they are not being published and not being subscribed to then they are just sitting there doing nothing.

---

<div class="post-metadata">

**Author:** ![jtmoderate876](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jtmoderate876/32/6423_2.png) [@jtmoderate876](https://discourse.nodered.org/u/jtmoderate876)\
**Post date:** [9 June 2019 13:56 UTC](https://discourse.nodered.org/t/mqtt-explorer-v0-2-0-mqtt-swiss-army-knife/7308/44 "2019-06-09T13:56:21Z")

</div>

Thanks for this @thomasnordquist - handy!

---

<div class="post-metadata">

**Author:** ![habach](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/habach/32/9518_2.png) [@habach](https://discourse.nodered.org/u/habach)\
**Post date:** [20 June 2019 06:28 UTC](https://discourse.nodered.org/t/mqtt-explorer-v0-2-0-mqtt-swiss-army-knife/7308/45 "2019-06-20T06:28:30Z")

</div>

Hi Thomas,

I'm using Ubuntu 16.04, 64-bit laptop. I have been using your app for a couple of months. It's been working just fine untill today. Since this morning I can't launch the app any more. When I clicked on the MQTT Explorer icon, it ran for few seconds then stopped for unknown reason. No Connect screen appeared as usual. Yesterday morning, it worked just well. I uninstalled and then re-installed the newest version 0.3 . Phenomena is still. Nothing happens when I click on the app. Please advise. Thank you a lot!

---

<div class="post-metadata">

**Author:** ![thomasnordquist](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/thomasnordquist/32/5446_2.png) [@thomasnordquist](https://discourse.nodered.org/u/thomasnordquist)\
**Post date:** [20 June 2019 11:43 UTC](https://discourse.nodered.org/t/mqtt-explorer-v0-2-0-mqtt-swiss-army-knife/7308/46 "2019-06-20T11:43:08Z")

</div>

Can you please launch mqtt-explorer from the shell/terminal and post the result. Did you use the snap or AppImage?

I installed a Ubuntu 16.04 machine and the application did not launch, a ubuntu update fixed the issue. `sudo apt-get update && sudo apt-get upgrade`

---

<div class="post-metadata">

**Author:** ![habach](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/habach/32/9518_2.png) [@habach](https://discourse.nodered.org/u/habach)\
**Post date:** [21 June 2019 02:12 UTC](https://discourse.nodered.org/t/mqtt-explorer-v0-2-0-mqtt-swiss-army-knife/7308/47 "2019-06-21T02:12:53Z")

</div>

I have tried your guide above and still failed, nothing happened and no any response from mqtt-explorer command. Here is all I tried.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/d/d814b92e4561c866e12a87619ae93e1deaaa0c52.png)

---

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [21 June 2019 08:17 UTC](https://discourse.nodered.org/t/mqtt-explorer-v0-2-0-mqtt-swiss-army-knife/7308/48 "2019-06-21T08:17:55Z")

</div>

Fantastic tool, thank you!!! Very useful  
Best regards, Walter

---

<div class="post-metadata">

**Author:** ![thomasnordquist](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/thomasnordquist/32/5446_2.png) [@thomasnordquist](https://discourse.nodered.org/u/thomasnordquist)\
**Post date:** [21 June 2019 09:39 UTC](https://discourse.nodered.org/t/mqtt-explorer-v0-2-0-mqtt-swiss-army-knife/7308/49 "2019-06-21T09:39:19Z")

</div>

That is indeed weird, there should be at least an error.  
There are two things that can be done to get more info:

1. Use snappy-debug to get info if libraries are missing  
(run snappy debug and then mqtt-explorer)

```auto
sudo snap install snappy-debug --devmode
snappy-debug.security scanlog

```

1. Allow electron to dump its stacktraces

```auto
export ELECTRON_ENABLE_STACK_DUMPING=true
mqtt-explorer

```

I believe the AppImage build should also work.

---

<div class="post-metadata">

**Author:** ![thomasnordquist](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/thomasnordquist/32/5446_2.png) [@thomasnordquist](https://discourse.nodered.org/u/thomasnordquist)\
**Post date:** [21 June 2019 09:40 UTC](https://discourse.nodered.org/t/mqtt-explorer-v0-2-0-mqtt-swiss-army-knife/7308/50 "2019-06-21T09:40:14Z")

</div>

Always glad to hear it 😊

---

<div class="post-metadata">

**Author:** ![habach](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/habach/32/9518_2.png) [@habach](https://discourse.nodered.org/u/habach)\
**Post date:** [21 June 2019 12:13 UTC](https://discourse.nodered.org/t/mqtt-explorer-v0-2-0-mqtt-swiss-army-knife/7308/51 "2019-06-21T12:13:54Z")

</div>

Followed your guide, I opened 2 terminal windows, one for debugging log, one for launching mqtt-explorer then got these log upon fail of mqtt-explorer. Please take a view and advise me, Thomas. Thanks a lot.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/d/d3ee62ab239cda0edb4581c195df92b48d6b32a8.png)

---

<div class="post-metadata">

**Author:** ![thomasnordquist](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/thomasnordquist/32/5446_2.png) [@thomasnordquist](https://discourse.nodered.org/u/thomasnordquist)\
**Post date:** [21 June 2019 14:04 UTC](https://discourse.nodered.org/t/mqtt-explorer-v0-2-0-mqtt-swiss-army-knife/7308/52 "2019-06-21T14:04:59Z")

</div>

This needs to happen in the same shell with the same user, no root required.

```auto
export ELECTRON_ENABLE_STACK_DUMPING=true
mqtt-explorer

```

I think it would probably be best if we discuss it here:

> <https://github.com/thomasnordquist/MQTT-Explorer/issues/135>

Thanks for your help so far, I really appreciate it 😊

---

<div class="post-metadata">

**Author:** ![thomasnordquist](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/thomasnordquist/32/5446_2.png) [@thomasnordquist](https://discourse.nodered.org/u/thomasnordquist)\
**Post date:** [21 June 2019 14:08 UTC](https://discourse.nodered.org/t/mqtt-explorer-v0-2-0-mqtt-swiss-army-knife/7308/53 "2019-06-21T14:08:35Z")

</div>

I may have found the problem (with app-armor), need to do some research.

---

<div class="post-metadata">

**Author:** ![thomasnordquist](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/thomasnordquist/32/5446_2.png) [@thomasnordquist](https://discourse.nodered.org/u/thomasnordquist)\
**Post date:** [21 June 2019 14:39 UTC](https://discourse.nodered.org/t/mqtt-explorer-v0-2-0-mqtt-swiss-army-knife/7308/54 "2019-06-21T14:39:34Z")

</div>

The application tries to access `/media/SSD-XP/MyDocuments/` but is not allowed. I have no idea why.  
Is it possible that you got some symlinks/mount from your home directory to the `MyDocuments` directory?

---

<div class="post-metadata">

**Author:** ![habach](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/habach/32/9518_2.png) [@habach](https://discourse.nodered.org/u/habach)\
**Post date:** [21 June 2019 18:02 UTC](https://discourse.nodered.org/t/mqtt-explorer-v0-2-0-mqtt-swiss-army-knife/7308/55 "2019-06-21T18:02:04Z")

</div>

Nice thing! AppImage version works just fine. Of course I don't know why 😃 Just one thing I lost all saved brokers before, but this is not a big problem. 😊

For /media/SSD-XP/MyDocuments I have no idea too. I even don't know where your app's data stored 😃 As I described above, the app has been working fine for long time before suddenly broken down yesterday. I suppose that my laptop recently goes freeze for low memory issue and I had to force power it down sometime.

So good that now I can run the app by click on AppImage. I will try to reinstall your app later. Many thanks for your kindly and promptly support. 👍

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/e/e8afec0a7f7c628bcd031357aa664a55ea2d1c73.png)

[Previous page](https://discourse.nodered.org/t/mqtt-explorer-v0-2-0-mqtt-swiss-army-knife/7308.md?page=2)