# Export Error Message

**URL:** <https://discuss.dgraph.io/t/export-error-message/9483>\
**Category:** Dgraph\
**Tags:** dgraph\
**Created:** [August 17, 2020, 8:50am UTC](https://discuss.dgraph.io/t/export-error-message/9483 "2020-08-17T08:50:03Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![M.Lau](https://avatars.discourse-cdn.com/v4/letter/m/db5fbb/32.png) [@M.Lau](https://discuss.dgraph.io/u/M.Lau)\
**Post date:** [August 17, 2020, 8:50am UTC](https://discuss.dgraph.io/t/export-error-message/9483/1 "2020-08-17T08:50:03Z")

</div>

Report a Dgraph Bug

I received the following Export Error message when running  
curl localhost:8080/admin/export?format=json

{“errors”:[{“message”:“Export failed.”,“extensions”:{“code”:“Export failed at readTs 3397396: cannot read posting list from this key”}}]}

when I check the export folder, I found the g01.json.gz file but the g01.schema.gz file is empty.

Is there a way to separately export the schema?

What version of Dgraph are you using?

Dgraph version : v1.2.1  
Dgraph SHA-256 : 3f18ff84570b2944f4d75f6f508d55d902715c7ca2310799cc2991064eb046f8  
Commit SHA-1 : ddcda9296  
Commit timestamp : 2020-02-06 15:31:05 -0800  
Branch : HEAD  
Go version : go1.13.5

Have you tried reproducing the issue with the latest release?  
I was planning to export first to try the latest release but if I cannot export, I am stucked.

What is the hardware spec (RAM, OS)?  
Ubuntu, not sure how to check the RAM but it should be the default 4096 allocated.

Steps to reproduce the issue (command/config used to run Dgraph).  
as above.

---

<div class="post-metadata">

**Author:** ![ibrahim](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/ibrahim/32/6387_2.png) [@ibrahim](https://discuss.dgraph.io/u/ibrahim)\
**Post date:** [August 17, 2020, 10:02am UTC](https://discuss.dgraph.io/t/export-error-message/9483/2 "2020-08-17T10:02:28Z")

</div>

@martinmr is this a known bug?

> [@M.Lau](#):
>
> Is there a way to separately export the schema?

Since the export isn’t working for you, how about querying for schema `curl "http://localhost:8080/query" -d 'schema {}' -s -H "Content-Type: application/graphql+-" `?

However, I don’t think all your data was exported since data and schema export happen at the same time.

---

<div class="post-metadata">

**Author:** ![M.Lau](https://avatars.discourse-cdn.com/v4/letter/m/db5fbb/32.png) [@M.Lau](https://discuss.dgraph.io/u/M.Lau)\
**Post date:** [August 18, 2020, 1:26am UTC](https://discuss.dgraph.io/t/export-error-message/9483/3 "2020-08-18T01:26:43Z")

</div>

Thanks.

Can I ask is there a way for me to debug this error code:  
Export failed at readTs 3397396:

so that I can export successfully?

---

<div class="post-metadata">

**Author:** ![ibrahim](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/ibrahim/32/6387_2.png) [@ibrahim](https://discuss.dgraph.io/u/ibrahim)\
**Post date:** [August 18, 2020, 5:38am UTC](https://discuss.dgraph.io/t/export-error-message/9483/4 "2020-08-18T05:38:39Z")

</div>

@martinmr any ideas on how to debug this?

---

<div class="post-metadata">

**Author:** ![martinmr](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/martinmr/32/1408_2.png) [@martinmr](https://discuss.dgraph.io/u/martinmr)\
**Post date:** [August 18, 2020, 7:59pm UTC](https://discuss.dgraph.io/t/export-error-message/9483/5 "2020-08-18T19:59:01Z")

</div>

I think this is a known bug that’s already been fixed in the latest 1.2 release.

@M.Lau I think you can try running Dgraph 1.2.6 with your data and doing the export. The two versions should be compatible in terms of the data so there’s no need to export/import your data first in order to switch versions. But backup your data before you do this just in case.

---

<div class="post-metadata">

**Author:** ![M.Lau](https://avatars.discourse-cdn.com/v4/letter/m/db5fbb/32.png) [@M.Lau](https://discuss.dgraph.io/u/M.Lau)\
**Post date:** [August 19, 2020, 8:56am UTC](https://discuss.dgraph.io/t/export-error-message/9483/6 "2020-08-19T08:56:02Z")

</div>

Ah yes, it worked!

Thanks very much.