# Python Pipeline **URL:** \ **Category:** Installation\ **Created:** [July 15, 2024, 5:26pm UTC](https://forum.seatable.com/t/python-pipeline/4899 "2024-07-15T17:26:28Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![goran.kuga](https://forum.seatable.com/letter_avatar_proxy/v4/letter/g/258eb7/32.png) [@goran.kuga](https://forum.seatable.com/u/goran.kuga)\ **Post date:** [July 15, 2024, 5:26pm UTC](https://forum.seatable.com/t/python-pipeline/4899/1 "2024-07-15T17:26:28Z")
## Your Setup: - Virtualized environment VMware - SeaTable Edition Enterprise - SeaTable Version 5.0.7 ## Describe the Problem/Error/Question: Please describe your issue as precise as possible. If helpful, you can also provide: - Manual pages you used [SeaTable Server - SeaTable Admin Manual](https://admin.seatable.io/installation/basic-setup/) and [Separate Python Pipeline - SeaTable Admin Manual](https://admin.seatable.io/installation/advanced/python-pipeline-dedicated-server/) Dear Support, I’ve started with building new SeaTable environment including separate SeaTable server and Python Pipeline. I followed instructions for both of those precisely but when attempting to execute script from SeaTable it does not work showing: error: Error: Internal Server Error. Could you please point me to correct direction at least to get some logs ? For Python Pipeline I adjusted .env to COMPOSE\_FILE=‘caddy.yml,python-pipeline.yml’ I did have to adjust python-pipeline.yml file in order for it to start working. I adjusted (removed this part): networks: - backend-seatable-net ![removed part](https://forum.seatable.com/uploads/default/original/2X/3/35829f9d9bcd9e590de067003a782a6cfb90ad6d.png) If I don’t remove it, container will not start, showing an error. Could you please assist me further to get this working ? I did update with URL and AUTH key on SeaTable side in dtable\_web\_server. ---
**Author:** ![goran.kuga](https://forum.seatable.com/letter_avatar_proxy/v4/letter/g/258eb7/32.png) [@goran.kuga](https://forum.seatable.com/u/goran.kuga)\ **Post date:** [July 15, 2024, 5:27pm UTC](https://forum.seatable.com/t/python-pipeline/4899/2 "2024-07-15T17:27:02Z")
SeaTable Server Docker: ![image](https://forum.seatable.io/uploads/default/original/2X/3/35f5b812f98f8e3aabfef7dc60961128eb8de7b6.png) ---
**Author:** ![goran.kuga](https://forum.seatable.com/letter_avatar_proxy/v4/letter/g/258eb7/32.png) [@goran.kuga](https://forum.seatable.com/u/goran.kuga)\ **Post date:** [July 15, 2024, 5:28pm UTC](https://forum.seatable.com/t/python-pipeline/4899/3 "2024-07-15T17:28:05Z")
SeaTable Python Pipeline: ![image](https://forum.seatable.io/uploads/default/original/2X/e/eafbeb345a500b6ab011aac9a7b8a07b6518e40f.png) ---
**Author:** ![goran.kuga](https://forum.seatable.com/letter_avatar_proxy/v4/letter/g/258eb7/32.png) [@goran.kuga](https://forum.seatable.com/u/goran.kuga)\ **Post date:** [July 15, 2024, 5:28pm UTC](https://forum.seatable.com/t/python-pipeline/4899/4 "2024-07-15T17:28:38Z")
Message I get when executing a script from SeaTable: ![Error SeaTable](https://forum.seatable.io/uploads/default/original/2X/c/c28aaa0c86801dc42606aa073701a65463f1d2ae.png) ---
**Author:** ![goran.kuga](https://forum.seatable.com/letter_avatar_proxy/v4/letter/g/258eb7/32.png) [@goran.kuga](https://forum.seatable.com/u/goran.kuga)\ **Post date:** [July 15, 2024, 5:29pm UTC](https://forum.seatable.com/t/python-pipeline/4899/5 "2024-07-15T17:29:58Z")
As I mentioned that I had to remove network from .yml file. If I don’t remove it this is what happens: ![image](https://forum.seatable.io/uploads/default/original/2X/4/45668249f0fdc7ba213d623fd2ce2b0de924ddda.png) Or if anyone can provide precise instructions on how to build separate Python Pipeline. ---
**Author:** ![cdb](https://forum.seatable.com/user_avatar/forum.seatable.com/cdb/32/7_2.png) [@cdb](https://forum.seatable.com/u/cdb)\ **Post date:** [July 15, 2024, 8:21pm UTC](https://forum.seatable.com/t/python-pipeline/4899/6 "2024-07-15T20:21:54Z")
Hey Goran, can you please post the output of these commands? ```auto docker logs python-starter docker logs python-scheduler ``` Does SeaTable and Python-Pipeline have separate but public available domains? I assume that the problem is, that python-scheduler does not find the database for initialization. Did you define DB\_HOST in the .env? Is the MariaDB reachable over the network? ---
**Author:** ![goran.kuga](https://forum.seatable.com/letter_avatar_proxy/v4/letter/g/258eb7/32.png) [@goran.kuga](https://forum.seatable.com/u/goran.kuga)\ **Post date:** [July 16, 2024, 11:42am UTC](https://forum.seatable.com/t/python-pipeline/4899/7 "2024-07-16T11:42:18Z")
Hey, Thank you so much for your reply. They both have same domain but different DNS, example: [seatable.company.com](http://seatable.company.com) and [python.company.com](http://python.company.com). DNS is resolvable between them and they can communicate without any restrictions. As I looked at the logs I would say that is correct, it is showing issues with DB. I did not place DB\_HOST in the .env as I did not see it in documentation anywhere. I presume that this has to be setup on Python Pipeline to point to SeaTable server were DB is ? PS: Logs from docker: ![image](https://forum.seatable.io/uploads/default/original/2X/3/3b66f54bf3d6feb3d1878884bdd6aa54329abf3e.png) Thanks ! Kind regards, Goran ---
**Author:** ![goran.kuga](https://forum.seatable.com/letter_avatar_proxy/v4/letter/g/258eb7/32.png) [@goran.kuga](https://forum.seatable.com/u/goran.kuga)\ **Post date:** [July 16, 2024, 11:42am UTC](https://forum.seatable.com/t/python-pipeline/4899/8 "2024-07-16T11:42:49Z")
![image](https://forum.seatable.io/uploads/default/original/2X/5/54ba91f66ac88434bdb6d14ea48fd0383f8267db.png) ---
**Author:** ![goran.kuga](https://forum.seatable.com/letter_avatar_proxy/v4/letter/g/258eb7/32.png) [@goran.kuga](https://forum.seatable.com/u/goran.kuga)\ **Post date:** [July 16, 2024, 11:46am UTC](https://forum.seatable.com/t/python-pipeline/4899/9 "2024-07-16T11:46:43Z")
What would be a good example of how DB\_HOST is configured in .env ? ---
**Author:** ![goran.kuga](https://forum.seatable.com/letter_avatar_proxy/v4/letter/g/258eb7/32.png) [@goran.kuga](https://forum.seatable.com/u/goran.kuga)\ **Post date:** [July 16, 2024, 12:00pm UTC](https://forum.seatable.com/t/python-pipeline/4899/10 "2024-07-16T12:00:04Z")
I did adjustments on seatable-server.yml and exposed MariaDB. ![image](https://forum.seatable.io/uploads/default/original/2X/c/c8392f48c8ef751d16667e3dbf920d9d00256b1b.png) Tested from Python Pipeline server and through telnet its reachable on port 3306. How do I configure now Python Pipeline to connect to it? Should I place DNS of my SeaTable server in DB\_HOST that I place in .env file or ? How does this work ? Thanks ! ---
**Author:** ![goran.kuga](https://forum.seatable.com/letter_avatar_proxy/v4/letter/g/258eb7/32.png) [@goran.kuga](https://forum.seatable.com/u/goran.kuga)\ **Post date:** [July 16, 2024, 12:11pm UTC](https://forum.seatable.com/t/python-pipeline/4899/11 "2024-07-16T12:11:37Z")
Hey, I figured it out. So in .env on Python Pipeline server, variable named SEATABLE\_MYSQL\_HOST= should be placed not DB\_HOST. After that its running, at least logs are showing it from Python Pipeline server: ![image](https://forum.seatable.io/uploads/default/original/2X/6/617b5b82c2f444d0ac50bf0a7193458976870a62.png) I tried again executing script from SeaTable but again getting error: Error: Internal Server Error. ---
**Author:** ![goran.kuga](https://forum.seatable.com/letter_avatar_proxy/v4/letter/g/258eb7/32.png) [@goran.kuga](https://forum.seatable.com/u/goran.kuga)\ **Post date:** [July 16, 2024, 12:39pm UTC](https://forum.seatable.com/t/python-pipeline/4899/12 "2024-07-16T12:39:13Z")
On my SeaTable server I adjust .env with following, placed for scheduler URL on http as per seatable-server.yml file that is in example. AUTH is generated and placed on both servers same in .env. PYTHON\_SCHEDULER\_URL= PYTHON\_SCHEDULER\_AUTH\_TOKEN= ---
**Author:** ![cdb](https://forum.seatable.com/user_avatar/forum.seatable.com/cdb/32/7_2.png) [@cdb](https://forum.seatable.com/u/cdb)\ **Post date:** [July 16, 2024, 1:48pm UTC](https://forum.seatable.com/t/python-pipeline/4899/13 "2024-07-16T13:48:09Z")
I am sorry, it seems that my description how to deploy python pipeline on a separate server is not covering all necessary requirements. Unfortunately, I don’t have time today to have a look at this. Give me some time and I will have a look. Probably this description of the python pipeline workflow helps you to check the different components part of python pipeline: > **[Python Pipeline Workflow - SeaTable Admin Manual](https://admin.seatable.io/installation/advanced/python-pipeline-workflow/)** > > Official SeaTable Admin Manual. ---
**Author:** ![goran.kuga](https://forum.seatable.com/letter_avatar_proxy/v4/letter/g/258eb7/32.png) [@goran.kuga](https://forum.seatable.com/u/goran.kuga)\ **Post date:** [July 17, 2024, 1:20pm UTC](https://forum.seatable.com/t/python-pipeline/4899/14 "2024-07-17T13:20:10Z")
Dear, Any feedback ? Thanks Kind regards, Goran ---
**Author:** ![goran.kuga](https://forum.seatable.com/letter_avatar_proxy/v4/letter/g/258eb7/32.png) [@goran.kuga](https://forum.seatable.com/u/goran.kuga)\ **Post date:** [July 22, 2024, 7:09am UTC](https://forum.seatable.com/t/python-pipeline/4899/15 "2024-07-22T07:09:29Z")
Dear, I tried standalone version and its also not working, though the error is different. Could you please review your documentation on how to build this? With previous version documentation was great, this is really… Thanks ! Kind regards, Goran ---
**Author:** ![goran.kuga](https://forum.seatable.com/letter_avatar_proxy/v4/letter/g/258eb7/32.png) [@goran.kuga](https://forum.seatable.com/u/goran.kuga)\ **Post date:** [July 31, 2024, 11:45am UTC](https://forum.seatable.com/t/python-pipeline/4899/16 "2024-07-31T11:45:20Z")
Dear, Any feedback ? Thanks Kind regards, Goran ---
**Author:** ![cdb](https://forum.seatable.com/user_avatar/forum.seatable.com/cdb/32/7_2.png) [@cdb](https://forum.seatable.com/u/cdb)\ **Post date:** [July 31, 2024, 2:24pm UTC](https://forum.seatable.com/t/python-pipeline/4899/17 "2024-07-31T14:24:20Z")
I updated the documentation to install a standalone python-pipeline on a separate host: [Separate Python Pipeline - SeaTable Admin Manual](https://admin.seatable.io/installation/advanced/python-pipeline-dedicated-server/). ---
**Author:** ![goran.kuga](https://forum.seatable.com/letter_avatar_proxy/v4/letter/g/258eb7/32.png) [@goran.kuga](https://forum.seatable.com/u/goran.kuga)\ **Post date:** [July 31, 2024, 3:08pm UTC](https://forum.seatable.com/t/python-pipeline/4899/18 "2024-07-31T15:08:07Z")
Dear, I looked at documentation but cannot find anything over there that was not already mentioned here in a ticket. Is this proven to be working, you tested it out on your own? As it still does not work for me, and its completely the same. I’m still getting this issue: I tried again executing script from SeaTable but again getting error: Error: Internal Server Error. Thanks ! Kind regards, Goran ---
**Author:** ![cdb](https://forum.seatable.com/user_avatar/forum.seatable.com/cdb/32/7_2.png) [@cdb](https://forum.seatable.com/u/cdb)\ **Post date:** [July 31, 2024, 7:24pm UTC](https://forum.seatable.com/t/python-pipeline/4899/19 "2024-07-31T19:24:28Z")
Dear @goran.kuga, I can confirm that the new documentation is working. I updated and tested the documentation by myself today. Did you really take the necessary time to understand what I changed? - new `python-pipeline-standalone.yml` file with MariaDB container included - new env variable to expose the python-scheduler to a public URL via caddy Here are the concrete changes from Github: - [Commits · seatable/seatable-admin-docs · GitHub](https://github.com/seatable/seatable-admin-docs/commits/main/) - [Commits · seatable/seatable-release · GitHub](https://github.com/seatable/seatable-release/commits/main/) My recommendation: delete all containers and `.yml` files from your python-pipeline host and follow the documentation. Then it will work. ---
**Author:** ![goran.kuga](https://forum.seatable.com/letter_avatar_proxy/v4/letter/g/258eb7/32.png) [@goran.kuga](https://forum.seatable.com/u/goran.kuga)\ **Post date:** [August 1, 2024, 10:36am UTC](https://forum.seatable.com/t/python-pipeline/4899/20 "2024-08-01T10:36:34Z")
Dear, I did everything from scratch with new files pulled from repository, adjusted them properly. And everything is indeed healthy under docker, no issues when looking docker logs for each container, but still it does not work. Whenever I try Python script from SeaTable it shows error: Error: Internal Server Error. If I do inspect on the page to see errors it shows following: (I hidden start of URL). Failed to load resource: the server responded with a status of 500 () https://MY\_SEA\_TABLE\_URL/api/v2.1/dtable/dd0c1599-34b5-44f8-8d89-2b33ef169e3f/run-script/TiGw.py/ Could you please let me know where I can find the log of what happens when I execute Python script from SeaTable, where I can see that it actually tries or connect to Python Pipeline? I’m using simple script: print(“Hello World”) PS: Servers are reachable between, I did curl to confirm. When I do a curl toward Python Pipeline URL or open that URL in browser of my jump server I see following, not sure if I should see anything different. 404 Not Found # Not Found The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again. Thanks ! Kind regards, Goran [Next page](https://forum.seatable.com/t/python-pipeline/4899.md?page=2)