Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PostgreSQL: invalid length of startup packet #580

Open
WanderingAround187 opened this issue Jan 9, 2025 · 10 comments
Open

PostgreSQL: invalid length of startup packet #580

WanderingAround187 opened this issue Jan 9, 2025 · 10 comments

Comments

@WanderingAround187
Copy link

WanderingAround187 commented Jan 9, 2025

The server was running just fine for the last few months. however last time i restart docker after making sure that the containers all stopped the web server is no longer show a useful logs that can help me fix the issue. and you can find the database error below

Server Logs:
2025-01-09 20:29:43 usermod: no changes 2025-01-09 20:29:43 2025-01-09 20:29:43 ------------------------------------- 2025-01-09 20:29:43 User uid: 911 2025-01-09 20:29:43 User gid: 911 2025-01-09 20:29:43 ------------------------------------- 2025-01-09 20:29:43

DB Logs:
[100] LOG: invalid length of startup packet -- no longer shown/ fixed

i have tried to re-build the containers but no luck. the db however seems to work just fine. i can use queries inside the db docker just find.

i have tried the possible solutions on issue 246 and use the DEV version but the issue still occurs.

it seems it network issue but i will keep updating here if there is any, would love to see anyone thoughts on this.

update 1: after playing around a bit. the invalid length error is no longer shows it. but the website is not up and running. in docker the logs for the website did not changed.

and whenever i tried to access the web page i get "This web page is not working "ERR_EMPTY_RESPONSE" with the same logs above for the website.

@Zibbp
Copy link
Owner

Zibbp commented Jan 9, 2025

You're running the latest v4.0.1 image?
If you bring down all the containers then interactively bring up the containers (docker compose up) do you see any errors after a minute or two?

@WanderingAround187
Copy link
Author

WanderingAround187 commented Jan 9, 2025

Thank you for your replay @Zibbp,
yes, im running latest version.

running the docker again with docker compose show no error, however leaving the container up and running for a while shows new errors

I will attach the two errors as a text file since I can't seem to find a way to upload them here without losing their order.

error1.txt

and this one

error2.txt

It seems the issue is with the config file. The permissions for the config.json file are:

-rw-rw-rw- 1 abc abc 1586 Jan 3

Appreciate your help with the issue.

@Zibbp
Copy link
Owner

Zibbp commented Jan 9, 2025

Can you paste your docker-compose file, redacting any sensitive information?

@WanderingAround187
Copy link
Author

sure thing.
DockerCompose.txt

@Zibbp
Copy link
Owner

Zibbp commented Jan 9, 2025

Looks correct to me. You can try making a backup of the config file and deleting the config directory mount on your host (Z:\...) then let Docker re-create the directory.
Looks like you're using Windows, or Docker onWindows?

@WanderingAround187
Copy link
Author

I wasn't able to resolve the issue directly, so instead, I decided to create a new start with fresh files and a new database. I then transferred the data accordingly. The process took a bit longer than expected, as after moving the files, I had to insert the previous row records into the new table in the database, making some necessary modifications (such as updating the channel ID and other details). However, everything is working now.

another bug i have found is front-end wise. when i search for videos now after using the new clip function and download all the clips for one channel i got "Application error: a client-side exception has occurred (see the browser console for more information)."

and the error in the console is

8094-5023984a7e7b37e1.js:1 TypeError: Cannot read properties of undefined (reading 'toLowerCase') at page-3e625555b1d92379.js:1:7714 at Array.filter (<anonymous>) at page-3e625555b1d92379.js:1:7667 at oT (4bd1b696-a93e1545db647059.js:1:81814) at o9 (4bd1b696-a93e1545db647059.js:1:97506) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:97486) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:98601) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:98601) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:97486) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:98601) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:97486) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:97486) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:97486) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:97486) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:98601) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:97486) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:97486) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:98601) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:97486) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:98601) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:98601) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:97486) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:98601) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:97486) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:97486) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:97486) at o5 (4bd1b696-a93e1545db647059.js:1:97390) at o9 (4bd1b696-a93e1545db647059.js:1:97486) at o5 (4bd1b696-a93e1545db647059.js:1:97390)

when i click on it. it leads me to

x.useEffect)( () => { if (!er) return; let e = [...er]; B && (e = e.filter(e => e.id.toString().includes(B) || e.title.toLowerCase().includes(B.toLowerCase()) || e.ext_id.toString().includes(B.toLowerCase()) || e.streamed_at.toString().includes(B.toLowerCase()) || e.edges.channel.name.toLowerCase().includes(B.toLowerCase()) || e.edges.channel.id.toString().includes(B.toLowerCase()))); let a = b()(e, E.columnAccessor); e = "desc" === E.direction ? a.reverse() : a; let n = (t - 1) * _ , r = n + _; M(e.slice(n, r)), T || P(!0) }

with the mouse pointing to e.title.toLowerCase().includes(B.toLowerCase()) and e.filter.

any thoughts on the issue?

@Zibbp
Copy link
Owner

Zibbp commented Jan 13, 2025

What was the search term you used? Any logs in the docker container when searching?

@WanderingAround187
Copy link
Author

there is no logs on the frontend container. and the search input will result in error while typing anything. like any two characters will trigger the issue.

@Zibbp
Copy link
Owner

Zibbp commented Jan 16, 2025

It looks like some field is missing from a field in the database. I pushed a fix to the :dev image that you can try. I would either start with a clean database, fix the problematic records, or perform an actual database dump from your previous instance backup.

@WanderingAround187
Copy link
Author

WanderingAround187 commented Jan 16, 2025

yeah currently the database i have is new clean one. nothing has been modified and i got no issue running for few days.

will try the dev version and let you know. appreciate your help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants