# Query preview works but don't run

**URL:** <https://community.dremio.com/t/query-preview-works-but-dont-run/9922>\
**Category:** Uncategorized\
**Created:** [November 10, 2022, 3:00pm UTC](https://community.dremio.com/t/query-preview-works-but-dont-run/9922 "2022-11-10T15:00:21Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Diego](https://avatars.discourse-cdn.com/v4/letter/d/f04885/32.png) [@Diego](https://community.dremio.com/u/Diego)\
**Post date:** [November 10, 2022, 3:00pm UTC](https://community.dremio.com/t/query-preview-works-but-dont-run/9922/1 "2022-11-10T15:00:21Z")

</div>

Hello, everyone!

In Dremio AWS Edition, we’re using an version of Asterisk’s database with Postgres.

When we try to run the _‘select \* from queue\_log’_ statement with _Run_ button show up this error message:

> The source [asterisk] is currently unavailable. Info: []

When we click on _Preview_ button rows are shown. When we send the command **ctrl + enter** all rows are shown too.

If it is saved as _virtual data set_ the error remains. Were it could be? Do you have any ideas?

_ **Versions below:** _

**Dremio**  
Build  
22.1.1-202208230402290397-a7010f28  
Edition  
AWS Edition  
Build Time  
23/08/2022 04:11:32  
Change Hash  
a7010f284dfb7bf28a29fb72846572e6991972d7  
Change Time  
23/08/2022 03:53:28

**Database server**  
PostgreSQL 9.2.24 on x86\_64-redhat-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39), 64-bit

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [November 27, 2022, 6:30pm UTC](https://community.dremio.com/t/query-preview-works-but-dont-run/9922/2 "2022-11-27T18:30:54Z")

</div>

@Diego Can we have the profile of the job that was successful and the one that failed?

---

<div class="post-metadata">

**Author:** ![Diego](https://avatars.discourse-cdn.com/v4/letter/d/f04885/32.png) [@Diego](https://community.dremio.com/u/Diego)\
**Post date:** [December 7, 2022, 6:35pm UTC](https://community.dremio.com/t/query-preview-works-but-dont-run/9922/3 "2022-12-07T18:35:54Z")

</div>

> [@balaji.ramaswamy](#):
>
> profile of

@balaji.ramaswamy I upload the files here:

[profile\_dremio\_success.zip](https://community.dremio.com/uploads/short-url/4AYRbYcqEqJEtNtWiJWG8UKbql6.zip) (9,7,KB)  
[profile\_dremio\_error.zip](https://community.dremio.com/uploads/short-url/6TpBNj6KKcqTnTwjkzKckJuVA6.zip) (10,7,KB)

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [December 9, 2022, 3:54am UTC](https://community.dremio.com/t/query-preview-works-but-dont-run/9922/4 "2022-12-09T03:54:23Z")

</div>

@Diego Seems to complain from node `10.0.0.120` which is an executor. Can you restart this executor and when it is coming up, tail the server.log and make sure the plugin status is marked healthy and if not see why?

Maybe you have not added this IP in pg\_hba.conf to allow access to PG?

---

<div class="post-metadata">

**Author:** ![Diego](https://avatars.discourse-cdn.com/v4/letter/d/f04885/32.png) [@Diego](https://community.dremio.com/u/Diego)\
**Post date:** [December 10, 2022, 12:58pm UTC](https://community.dremio.com/t/query-preview-works-but-dont-run/9922/5 "2022-12-10T12:58:41Z")

</div>

@balaji.ramaswamy I will to try enable IP list in pg\_hba.conf. Thanks!

---

<div class="post-metadata">

**Author:** ![Diego](https://avatars.discourse-cdn.com/v4/letter/d/f04885/32.png) [@Diego](https://community.dremio.com/u/Diego)\
**Post date:** [January 12, 2023, 3:25pm UTC](https://community.dremio.com/t/query-preview-works-but-dont-run/9922/6 "2023-01-12T15:25:38Z")

</div>

@balaji.ramaswamy I had enable IP’s from firewall and make all configurations but same problem persists

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [January 12, 2023, 4:34pm UTC](https://community.dremio.com/t/query-preview-works-but-dont-run/9922/7 "2023-01-12T16:34:25Z")

</div>

@Diego Check the error tab and see if it is the same executor again `10.0.0.120`, if not maybe all the executors where not added to `pg_hba.conf`? Also review the server.log on the executor it is complaining on and look at the startup section to see if the plugin reports healthy

---

<div class="post-metadata">

**Author:** ![Diego](https://avatars.discourse-cdn.com/v4/letter/d/f04885/32.png) [@Diego](https://community.dremio.com/u/Diego)\
**Post date:** [January 12, 2023, 4:53pm UTC](https://community.dremio.com/t/query-preview-works-but-dont-run/9922/8 "2023-01-12T16:53:08Z")

</div>

> [@balaji.ramaswamy](#):
>
> error tab and see if it is the s

It’s not the same. I’ve already destroy and create new executors since last chat

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [January 12, 2023, 5:25pm UTC](https://community.dremio.com/t/query-preview-works-but-dont-run/9922/9 "2023-01-12T17:25:42Z")

</div>

@Diego Can we check two things

- What is the error reported on the executor server.log?
- What is the error on the server side? Postgres log

---

<div class="post-metadata">

**Author:** ![Diego](https://avatars.discourse-cdn.com/v4/letter/d/f04885/32.png) [@Diego](https://community.dremio.com/u/Diego)\
**Post date:** [January 12, 2023, 8:56pm UTC](https://community.dremio.com/t/query-preview-works-but-dont-run/9922/10 "2023-01-12T20:56:01Z")

</div>

@balaji.ramaswamy  
See the execution:  
First I click on _ **Run** _ button, the result is error; Second, I clicked on _ **Preview** _, returned success. Third, I click on _ **Run** _ and I receive error again

 ![dremio asterisk error](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/2X/7/79d320a89474934fabe29f30c4fcba9aa3ae72d4.png)

Here the server.log from executor node  
[server.zip](https://community.dremio.com/uploads/short-url/cvvizILkgknpe3cPj7u4l7oagl5.zip) (45,0,KB)

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [January 15, 2023, 6:49am UTC](https://community.dremio.com/t/query-preview-works-but-dont-run/9922/11 "2023-01-15T06:49:00Z")

</div>

@Diego Is this part of the server.log as the last line in the server.log just has the start fragment

```auto
023-01-12 20:43:49,136 [FABRIC-rpc-event-queue] INFO c.d.sabot.exec.FragmentExecutors - Received remote fragment start instruction for 1c3f8efb-0643-edc9-d8d2-9a29a5b54f00:0:0 with assigned weight 1 and scheduling weight 1
2023-01-12 20:43:49,140 [FABRIC-rpc-event-queue] INFO c.d.s.e.f.FragmentExecutorBuilder - Setting outStandingRPCsPerTunnel:3

```

---

<div class="post-metadata">

**Author:** ![Diego](https://avatars.discourse-cdn.com/v4/letter/d/f04885/32.png) [@Diego](https://community.dremio.com/u/Diego)\
**Post date:** [January 16, 2023, 12:37pm UTC](https://community.dremio.com/t/query-preview-works-but-dont-run/9922/12 "2023-01-16T12:37:52Z")

</div>

@balaji.ramaswamy I think I didn’t understand very well. Do you need a more complete log?

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [January 20, 2023, 7:46am UTC](https://community.dremio.com/t/query-preview-works-but-dont-run/9922/13 "2023-01-20T07:46:55Z")

</div>

@Diego Go to the `log/archive` folder of this executor `10.0.0.120` and send the tar of all server logs

```auto
tar -cvf serverlog.tar.gz server*

```
