[SOLVED?]Illegal instructions?

Support
,
1

Hardware: VPS bought online ( Contabo )
YunoHost version: 11.0.9.14 (stable)
I have access to my server : Through SSH and browser
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

overnight, i received 50 emails from the root (diagnosis?) all stating:

/bin/bash: line 1: 206859 Illegal instruction     yunohost dyndns update >> /dev/null

the number after line 1 changes in every email.

what does it mean? should i do something?

2

also, just try to access my yunohost from browser and got this message:

YunoHost API is not responding

Really sorry about that.

Error: "502"

Action: "PUT" /yunohost/api/diagnosis/run?except_if_never_ran_yet

Error message:

The YunoHost API is not responding. Maybe ‘yunohost-api’ is down or got restarted?

3

Hello,

Let’s start a dignosis : sudo yunohost diagnosis run

Please post the output or the log.

4

the issue mentioned in the post seemed to have stopped in the morning at some point btw. however, the diagnosis showed a long-term issue no one has been able to help me with so far.

admin@xxx:~$ sudo yunohost diagnosis run
Success! Everything looks OK for Base system!
Success! Everything looks OK for Internet connectivity!
Success! Everything looks OK for DNS records!
Success! Everything looks OK for Ports exposure!
Success! Everything looks OK for Web!
Success! Everything looks OK for Email!
Error: Found 1 significant issue(s) related to Services status check!
Success! Everything looks OK for System resources!
Success! Everything looks OK for System configurations! (+ 1 ignored issue(s))
Success! Everything looks OK for Applications!
Warning: To see the issues found, you can go to the Diagnosis section of the webadmin, or run 'yunohost diagnosis show --issues --human-readable' from the command-line.
admin@xxx:~$ sudo yunohost diagnosis show --issues --human-readable
=================================
Services status check (services)
=================================

[ERROR] Service postgresql is dead :(
  - You can try to restart the service, and if it doesn't work, have a look at the service logs in the webadmin (from the command line, you can do this with 'yunohost service restart postgresql' and 'yunohost service log postgresql').

and yes, i’ve already tried to do what’s suggested in the diagnosis, but it didn’t solve it.

5

Well, let’s see why postgresql is dead : yunohost service log postgresql

6

here we are!

~$ sudo yunohost service log postgresql
/var/log/postgresql/postgresql-13-main.log: 
  - 2022-09-21 01:16:12.428 CEST [33952] LOG:  starting PostgreSQL 13.8 (Debian 13.8-0+deb11u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
  - 2022-09-21 01:16:12.429 CEST [33952] LOG:  listening on IPv6 address "::1", port 5432
  - 2022-09-21 01:16:12.429 CEST [33952] LOG:  listening on IPv4 address "127.0.0.1", port 5432
  - 2022-09-21 01:16:12.430 CEST [33952] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
  - 2022-09-21 01:16:12.524 CEST [33953] LOG:  database system was shut down at 2022-09-21 01:16:12 CEST
  - 2022-09-21 01:16:12.558 CEST [33952] LOG:  database system is ready to accept connections
  - 2022-09-23 13:17:58.917 CEST [33952] LOG:  received fast shutdown request
  - 2022-09-23 13:17:58.995 CEST [33952] LOG:  aborting any active transactions
  - 2022-09-23 13:17:58.998 CEST [33952] LOG:  background worker "logical replication launcher" (PID 33959) exited with exit code 1
  - 2022-09-23 13:17:59.018 CEST [54073] gotosocial@gotosocial FATAL:  terminating connection due to administrator command
  - 2022-09-23 13:17:59.018 CEST [34395] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-23 13:17:59.021 CEST [33974] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-23 13:17:59.021 CEST [34021] gotosocial@gotosocial FATAL:  terminating connection due to administrator command
  - 2022-09-23 13:17:59.022 CEST [34004] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-23 13:17:59.025 CEST [33975] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-23 13:17:59.025 CEST [33972] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-23 13:17:59.025 CEST [33973] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-23 13:17:59.028 CEST [34392] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-23 13:17:59.029 CEST [54072] gotosocial@gotosocial FATAL:  terminating connection due to administrator command
  - 2022-09-23 13:17:59.029 CEST [33989] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-23 13:17:59.196 CEST [33954] LOG:  shutting down
  - 2022-09-23 13:17:59.314 CEST [33952] LOG:  database system is shut down
  - 2022-09-23 13:17:59.815 CEST [99557] LOG:  starting PostgreSQL 13.8 (Debian 13.8-0+deb11u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
  - 2022-09-23 13:17:59.815 CEST [99557] LOG:  listening on IPv6 address "::1", port 5432
  - 2022-09-23 13:17:59.815 CEST [99557] LOG:  listening on IPv4 address "127.0.0.1", port 5432
  - 2022-09-23 13:17:59.834 CEST [99557] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
  - 2022-09-23 13:17:59.972 CEST [99558] LOG:  database system was shut down at 2022-09-23 13:17:59 CEST
  - 2022-09-23 13:18:00.081 CEST [99557] LOG:  database system is ready to accept connections
  - 2022-09-26 16:41:57.772 CEST [99576] matrix_synapse@matrix_synapse ERROR:  could not serialize access due to concurrent delete
  - 2022-09-26 16:41:57.772 CEST [99576] matrix_synapse@matrix_synapse STATEMENT:  DELETE FROM presence_stream WHERE stream_id < 495634 AND user_id = ANY(ARRAY['@tcit:matrix.tcit.fr'])
  - 2022-09-27 01:56:35.145 CEST [99585] matrix_synapse@matrix_synapse LOG:  could not receive data from client: Connection reset by peer
  - 2022-09-27 01:56:35.145 CEST [99584] matrix_synapse@matrix_synapse LOG:  could not receive data from client: Connection reset by peer
  - 2022-09-27 01:56:35.145 CEST [99578] matrix_synapse@matrix_synapse LOG:  could not receive data from client: Connection reset by peer
  - 2022-09-27 01:56:35.145 CEST [99586] matrix_synapse@matrix_synapse LOG:  could not receive data from client: Connection reset by peer
  - 2022-09-27 01:56:35.145 CEST [99576] matrix_synapse@matrix_synapse LOG:  could not receive data from client: Connection reset by peer
  - 2022-09-27 01:56:35.145 CEST [99582] matrix_synapse@matrix_synapse LOG:  could not receive data from client: Connection reset by peer
  - 2022-09-27 01:56:35.145 CEST [99580] matrix_synapse@matrix_synapse LOG:  could not receive data from client: Connection reset by peer
  - 2022-09-27 01:56:35.145 CEST [139048] matrix_synapse@matrix_synapse LOG:  could not receive data from client: Connection reset by peer
  - 2022-09-27 01:56:35.145 CEST [99579] matrix_synapse@matrix_synapse LOG:  could not receive data from client: Connection reset by peer
  - 2022-09-27 10:03:48.828 CEST [994] LOG:  starting PostgreSQL 13.8 (Debian 13.8-0+deb11u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
  - 2022-09-27 10:03:48.965 CEST [994] LOG:  listening on IPv6 address "::1", port 5432
  - 2022-09-27 10:03:48.965 CEST [994] LOG:  listening on IPv4 address "127.0.0.1", port 5432
  - 2022-09-27 10:03:49.049 CEST [994] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
  - 2022-09-27 10:03:50.035 CEST [1099] LOG:  database system was interrupted; last known up at 2022-09-27 01:59:41 CEST
  - 2022-09-27 10:03:55.331 CEST [1099] LOG:  database system was not properly shut down; automatic recovery in progress
  - 2022-09-27 10:03:55.482 CEST [1099] LOG:  redo starts at 3/44126BD0
  - 2022-09-27 10:03:55.482 CEST [1099] LOG:  invalid record length at 3/44126CB8: wanted 24, got 0
  - 2022-09-27 10:03:55.482 CEST [1099] LOG:  redo done at 3/44126C80
  - 2022-09-27 10:03:55.750 CEST [994] LOG:  database system is ready to accept connections
  - 2022-09-27 10:04:23.711 CEST [1755] matrix_synapse@matrix_synapse WARNING:  there is already a transaction in progress
journalctl: 
  - -- Journal begins at Thu 2022-09-15 00:26:29 CEST, ends at Tue 2022-09-27 21:47:37 CEST. --
  - Sep 18 18:56:59 systemd[1]: Stopping PostgreSQL Cluster 11-main...
  - Sep 18 18:57:02 systemd[1]: postgresql@11-main.service: Succeeded.
  - Sep 18 18:57:02 systemd[1]: Stopped PostgreSQL Cluster 11-main.
  - Sep 18 18:57:02 systemd[1]: Starting PostgreSQL Cluster 11-main...
  - Sep 18 18:57:10 systemd[1]: Started PostgreSQL Cluster 11-main.
  - Sep 18 19:06:13 systemd[1]: Stopping PostgreSQL Cluster 11-main...
  - Sep 18 19:06:13 systemd[1]: postgresql@11-main.service: Succeeded.
  - Sep 18 19:06:13 systemd[1]: Stopped PostgreSQL Cluster 11-main.
  - Sep 18 19:06:13 systemd[1]: Starting PostgreSQL Cluster 11-main...
  - Sep 18 19:06:16 systemd[1]: Started PostgreSQL Cluster 11-main.
  - Sep 18 19:37:10 systemd[1]: Stopping PostgreSQL Cluster 11-main...
  - Sep 18 19:37:11 systemd[1]: postgresql@11-main.service: Succeeded.
  - Sep 18 19:37:11 systemd[1]: Stopped PostgreSQL Cluster 11-main.
  - Sep 18 19:37:11 systemd[1]: Starting PostgreSQL Cluster 11-main...
  - Sep 18 19:37:15 systemd[1]: Started PostgreSQL Cluster 11-main.
  - Sep 18 19:51:41 systemd[1]: Reloading PostgreSQL Cluster 11-main.
  - Sep 18 19:51:41 systemd[1]: Reloaded PostgreSQL Cluster 11-main.
  - -- Boot 09c6bc504c524e05bdc65fd6bd7462e3 --
  - Sep 19 18:19:12 systemd[1]: Starting PostgreSQL Cluster 11-main...
  - Sep 19 18:19:14 postgresql@11-main[686]: Removed stale pid file.
  - Sep 19 18:19:26 systemd[1]: Started PostgreSQL Cluster 11-main.
  - Sep 19 18:31:26 systemd[1]: Stopping PostgreSQL Cluster 11-main...
  - Sep 19 18:31:26 systemd[1]: postgresql@11-main.service: Succeeded.
  - Sep 19 18:31:26 systemd[1]: Stopped PostgreSQL Cluster 11-main.
  - Sep 19 18:31:26 systemd[1]: postgresql@11-main.service: Consumed 1.937s CPU time.
  - -- Boot ee0e86dc619042259065dc271e150806 --
  - Sep 19 18:32:11 systemd[1]: Starting PostgreSQL Cluster 11-main...
  - Sep 19 18:32:20 systemd[1]: Started PostgreSQL Cluster 11-main.
  - Sep 19 18:41:56 systemd[1]: Stopping PostgreSQL Cluster 11-main...
  - Sep 19 18:41:57 systemd[1]: postgresql@11-main.service: Succeeded.
  - Sep 19 18:41:57 systemd[1]: Stopped PostgreSQL Cluster 11-main.
  - Sep 19 18:41:57 systemd[1]: postgresql@11-main.service: Consumed 1.559s CPU time.
7

Maybe you can rename the thread “Postgresql error”.

Sorry, can’t help more, seems a database is corrupted or something and mess with Synapse & Gotosocial.

8

no worries and thanks :slight_smile:

i already have an open one here so no need to rename this. i hope.

9

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.