TOS webpage always shows "Loading..."?

[Nekle]

Looks like it definitly a TOSdeamon issue due to postgres database as @gremlin said.

I attached the output of the `TOSdaemon.log` file and the ouput of the postgres `pgsql.long`

Code: Select all

2024-06-26 03:30:32.808 CST [1772] LOG:  starting PostgreSQL 13.2 on x86_64-buildroot-linux-gnu, compiled by x86_64-tnas-linux-gnu-gcc.br_real (Buildroot 2017.11.2) 7.2.0, 64-bit
2024-06-26 03:30:32.808 CST [1772] LOG:  listening on IPv4 address "127.0.0.1", port 5032
2024-06-26 03:30:32.841 CST [1772] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5032"
2024-06-26 03:30:32.882 CST [1772] LOG:  could not resolve "localhost": Name or service not known
2024-06-26 03:30:32.882 CST [1772] LOG:  disabling statistics collector for lack of working socket
2024-06-26 03:30:32.913 CST [1773] LOG:  database system was shut down at 2024-06-26 03:30:32 CST
2024-06-26 03:30:33.026 CST [1772] LOG:  database system is ready to accept connections
2024-06-26 03:30:39.630 CST [1790] ERROR:  constraint "fk_external_acl_user_table" of relation "external_acl" does not exist
2024-06-26 03:30:39.630 CST [1790] STATEMENT:  ALTER TABLE "external_acl" DROP CONSTRAINT "fk_external_acl_user_table"
2024-06-26 03:30:42.336 CST [1772] LOG:  server process (PID 1790) was terminated by signal 11: Segmentation fault
2024-06-26 03:30:42.336 CST [1772] LOG:  terminating any other active server processes
2024-06-26 03:30:42.339 CST [1772] LOG:  all server processes terminated; reinitializing
2024-06-26 03:30:42.486 CST [1802] LOG:  PID 1790 in cancel request did not match any process
2024-06-26 03:30:42.487 CST [1801] LOG:  database system was interrupted; last known up at 2024-06-26 03:30:32 CST
2024-06-26 03:30:43.627 CST [1801] LOG:  database system was not properly shut down; automatic recovery in progress
2024-06-26 03:30:43.656 CST [1801] LOG:  redo starts at 0/130000A0
2024-06-26 03:30:43.690 CST [1801] LOG:  invalid record length at 0/1300EFA8: wanted 24, got 0
2024-06-26 03:30:43.691 CST [1801] LOG:  redo done at 0/1300EF68
2024-06-26 03:30:44.296 CST [1772] LOG:  database system is ready to accept connections
2024-06-26 03:31:03.385 CST [2064] ERROR:  constraint "fk_external_acl_user_table" of relation "external_acl" does not exist
2024-06-26 03:31:03.385 CST [2064] STATEMENT:  ALTER TABLE "external_acl" DROP CONSTRAINT "fk_external_acl_user_table"
2024-06-26 03:31:06.148 CST [1772] LOG:  server process (PID 2064) was terminated by signal 11: Segmentation fault
2024-06-26 03:31:06.148 CST [1772] LOG:  terminating any other active server processes
2024-06-26 03:31:06.151 CST [2066] LOG:  PID 2064 in cancel request did not match any process
2024-06-26 03:31:06.153 CST [2065] FATAL:  the database system is in recovery mode
2024-06-26 03:31:06.156 CST [1772] LOG:  all server processes terminated; reinitializing
2024-06-26 03:31:06.288 CST [2067] LOG:  database system was interrupted; last known up at 2024-06-26 03:30:44 CST
2024-06-26 03:31:06.288 CST [2068] FATAL:  the database system is in recovery mode
2024-06-26 03:31:06.291 CST [2069] FATAL:  the database system is in recovery mode
2024-06-26 03:31:06.295 CST [2070] FATAL:  the database system is in recovery mode
2024-06-26 03:31:06.299 CST [2071] FATAL:  the database system is in recovery mode
2024-06-26 03:31:06.329 CST [2072] FATAL:  the database system is in recovery mode
2024-06-26 03:31:06.431 CST [2081] FATAL:  the database system is in recovery mode
2024-06-26 03:31:06.436 CST [2082] FATAL:  the database system is in recovery mode
2024-06-26 03:31:06.441 CST [2083] FATAL:  the database system is in recovery mode
2024-06-26 03:31:06.445 CST [2084] FATAL:  the database system is in recovery mode
2024-06-26 03:31:07.997 CST [2067] LOG:  database system was not properly shut down; automatic recovery in progress
2024-06-26 03:31:08.086 CST [2067] LOG:  redo starts at 0/1300F020
2024-06-26 03:31:08.088 CST [2067] LOG:  invalid record length at 0/1301D898: wanted 24, got 0
2024-06-26 03:31:08.088 CST [2067] LOG:  redo done at 0/1301D858
2024-06-26 03:31:08.478 CST [1772] LOG:  database system is ready to accept connections
2024-06-26 03:31:10.148 CST [2091] ERROR:  duplicate key value violates unique constraint "acl_host_hash_key"
2024-06-26 03:31:10.148 CST [2091] DETAIL:  Key (hash)=(40481c2a9201d6f829edef672631611d) already exists.
2024-06-26 03:31:10.148 CST [2091] STATEMENT:  INSERT INTO "acl_host" ("host","folder_id","service","access","hash","extend") VALUES ($1,$2,$3,$4,$5,$6)
2024-06-26 03:31:10.153 CST [2091] ERROR:  duplicate key value violates unique constraint "acl_host_hash_key"
2024-06-26 03:31:10.153 CST [2091] DETAIL:  Key (hash)=(c0f55c57ae4828e2c31ebb20b13d04e2) already exists.
2024-06-26 03:31:10.153 CST [2091] STATEMENT:  INSERT INTO "acl_host" ("host","folder_id","service","access","hash","extend") VALUES ($1,$2,$3,$4,$5,$6)
2024-06-26 03:31:33.206 CST [2541] ERROR:  constraint "fk_external_acl_user_table" of relation "external_acl" does not exist
2024-06-26 03:31:33.206 CST [2541] STATEMENT:  ALTER TABLE "external_acl" DROP CONSTRAINT "fk_external_acl_user_table"
2024-06-26 03:31:36.021 CST [1772] LOG:  server process (PID 2541) was terminated by signal 11: Segmentation fault
2024-06-26 03:31:36.021 CST [1772] LOG:  terminating any other active server processes
2024-06-26 03:31:36.024 CST [2544] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.028 CST [2545] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.037 CST [2547] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.044 CST [2548] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.050 CST [2549] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.054 CST [2550] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.094 CST [1772] LOG:  all server processes terminated; reinitializing
2024-06-26 03:31:36.199 CST [2564] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.202 CST [2563] LOG:  database system was interrupted; last known up at 2024-06-26 03:31:08 CST
2024-06-26 03:31:36.205 CST [2565] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.209 CST [2566] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.213 CST [2567] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.405 CST [2571] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.408 CST [2572] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.413 CST [2573] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.417 CST [2574] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.451 CST [2578] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.455 CST [2579] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.463 CST [2580] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.468 CST [2581] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.472 CST [2582] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.476 CST [2583] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.482 CST [2584] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.485 CST [2585] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.490 CST [2586] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.494 CST [2587] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.498 CST [2588] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.504 CST [2589] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.507 CST [2590] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.512 CST [2591] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.516 CST [2592] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.619 CST [2600] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.624 CST [2601] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.629 CST [2602] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.634 CST [2603] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.656 CST [2563] LOG:  database system was not properly shut down; automatic recovery in progress
2024-06-26 03:31:36.724 CST [2563] LOG:  redo starts at 0/1301D910
2024-06-26 03:31:36.727 CST [2563] LOG:  redo done at 0/1303E160
2024-06-26 03:31:36.811 CST [2606] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.960 CST [2610] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.963 CST [2611] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.965 CST [2612] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.968 CST [2613] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.971 CST [2614] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.974 CST [2615] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.977 CST [2616] FATAL:  the database system is in recovery mode
2024-06-26 03:31:36.980 CST [2617] FATAL:  the database system is in recovery mode
2024-06-26 03:31:37.079 CST [2618] FATAL:  the database system is in recovery mode
2024-06-26 03:31:37.164 CST [2627] FATAL:  the database system is in recovery mode
2024-06-26 03:31:37.169 CST [2628] FATAL:  the database system is in recovery mode
2024-06-26 03:31:37.174 CST [2629] FATAL:  the database system is in recovery mode
2024-06-26 03:31:37.179 CST [2630] FATAL:  the database system is in recovery mode
2024-06-26 03:31:37.184 CST [2631] FATAL:  the database system is in recovery mode
2024-06-26 03:31:37.189 CST [2632] FATAL:  the database system is in recovery mode
2024-06-26 03:31:37.297 CST [1772] LOG:  database system is ready to accept connections
2024-06-26 03:33:06.710 CST [3132] ERROR:  constraint "fk_external_acl_user_table" of relation "external_acl" does not exist
2024-06-26 03:33:06.710 CST [3132] STATEMENT:  ALTER TABLE "external_acl" DROP CONSTRAINT "fk_external_acl_user_table"
2024-06-26 03:33:09.473 CST [1772] LOG:  server process (PID 3132) was terminated by signal 11: Segmentation fault
2024-06-26 03:33:09.473 CST [1772] LOG:  terminating any other active server processes
2024-06-26 03:33:09.478 CST [3140] LOG:  PID 3132 in cancel request did not match any process
2024-06-26 03:33:09.480 CST [1772] LOG:  all server processes terminated; reinitializing
2024-06-26 03:33:09.617 CST [3141] LOG:  database system was interrupted; last known up at 2024-06-26 03:31:37 CST
2024-06-26 03:33:09.617 CST [3142] FATAL:  the database system is in recovery mode
2024-06-26 03:33:09.622 CST [3143] FATAL:  the database system is in recovery mode
2024-06-26 03:33:10.001 CST [3141] LOG:  database system was not properly shut down; automatic recovery in progress
2024-06-26 03:33:10.065 CST [3141] LOG:  redo starts at 0/1303EFE0
2024-06-26 03:33:10.067 CST [3141] LOG:  redo done at 0/13056FE8
2024-06-26 03:33:10.458 CST [1772] LOG:  database system is ready to accept connections

[TMroy]

Two consecutive unexpected power outages may lead to the damage of some system files or databases. In this case, you can only reinstall the system.

[Nekle]

Ok ok, so there is no way to correct that with out reinstalling ?

And if i choose to reinstall, do it select "automatic" or "personalized" if i want to keep my data on my disks ?

[TMroy]

Reinstalling a new system will not affect the data on the data partition, because the system will be installed on the system partition of the disk, unless the file system of your data partition is also damaged due to unexpected power failure. If during the process of reinstalling the system, the page prompts you to recreate the storage pool, please stop immediately. In this case, you need to seek help from a professional data recovery agency to try to restore your data.