ReactiveMongo with Cluster DocumentDB throw internal server error after warning timeout connection - reactivemongo

We are using Playframework 2.7.x, Scala 2.13.x, ReactiveMongo 0.19.2 and a Cluster DocumentDB, when We put in the connection string pointing to cluster
mongodb://user:pwd#clusterhost:27017/db-name?replicaSet=rs0
We had this error
Dec 5 22:50:23 i-00f33fa3398767595 xxxxx INFO [warn] r.a.MongoConnection - [Supervisor-1/Connection-1] Timeout after 8200 milliseconds while probing the connection monitor: IsPrimaryAvailable#560128359?
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO [error] application -
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO ! #7e4b6iijd - Internal server error, for (GET) [/api/user-sessions/user/session] ->
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO play.api.UnexpectedException: Unexpected exception[MongoException: unexpected failed when read info to userId : 12345]
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at play.api.http.HttpErrorHandlerExceptions$.throwableToUsefulException(HttpErrorHandler.scala:347)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at play.api.http.DefaultHttpErrorHandler.onServerError(HttpErrorHandler.scala:267)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at play.core.server.AkkaHttpServer$$anonfun$1.applyOrElse(AkkaHttpServer.scala:448)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at play.core.server.AkkaHttpServer$$anonfun$1.applyOrElse(AkkaHttpServer.scala:446)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at scala.concurrent.impl.Promise$Transformation.run(Promise.scala:453)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:55)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:92)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.scala:18)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:94)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at akka.dispatch.BatchingExecutor$BlockableBatch.run(BatchingExecutor.scala:92)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO Caused by: com.rappi.infrastructure.repositories.mongo.exceptions.MongoException: unexpected failed when read info to userId : 12345
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at com.rappi.infrastructure.repositories.mongo.UserRepositoryMongo$$anonfun$loadUser$4.applyOrElse(UserRepositoryMongo.scala:40)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at com.rappi.infrastructure.repositories.mongo.UserRepositoryMongo$$anonfun$loadUser$4.applyOrElse(UserRepositoryMongo.scala:36)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at scala.concurrent.impl.Promise$Transformation.run(Promise.scala:453)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:55)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:92)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.scala:18)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:94)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at akka.dispatch.BatchingExecutor$BlockableBatch.run(BatchingExecutor.scala:92)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:41)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(ForkJoinExecutorConfigurator.scala:49)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO Caused by: reactivemongo.core.actors.Exceptions$PrimaryUnavailableException: MongoError['No primary node is available! (Supervisor-1/Connection-1)']
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at play.modules.reactivemongo.DefaultReactiveMongoApi.database(DefaultReactiveMongoApi.scala:54)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at reactivemongo.api.MongoConnection.database(MongoConnection.scala:96)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO Caused by: reactivemongo.core.actors.Exceptions$InternalState:
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at reactivemongo.ChannelDisconnected(fa5db447, {{NodeSet Some(rs0) Node[documentdb-dev.cluster-cn18vvzkqual.us-east-1.docdb.amazonaws.com:27017: Unknown (20/20/20 available connections), latency=7517999ns, authenticated={user-sessions#user-sessions}] }})(<time:16609211522842>)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at reactivemongo.ChannelDisconnected(229a0250, {{NodeSet Some(rs0) Node[documentdb-dev.cluster-cn18vvzkqual.us-east-1.docdb.amazonaws.com:27017: Primary (20/20/20 available connections), latency=7517999ns, authenticated={user-sessions#user-sessions}] }})(<time:16609164193108>)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at reactivemongo.SetUnavailable({{NodeSet Some(rs0) Node[documentdb-dev.cluster-cn18vvzkqual.us-east-1.docdb.amazonaws.com:27017: Unknown (20/20/20 available connections), latency=7517999ns, authenticated={user-sessions#user-sessions}] }})(<time:16609164187318>)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at reactivemongo.ConnectAll({{NodeSet Some(rs0) Node[documentdb-dev.cluster-cn18vvzkqual.us-east-1.docdb.amazonaws.com:27017: Primary (20/20/20 available connections), latency=7517999ns, authenticated={user-sessions#user-sessions}] }})(<time:16608976741545>)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at reactivemongo.ConnectAll$IsMaster(53, {{NodeSet Some(rs0) Node[documentdb-dev.cluster-cn18vvzkqual.us-east-1.docdb.amazonaws.com:27017: Primary (20/20/20 available connections), latency=7517999ns, authenticated={user-sessions#user-sessions}] }})(<time:16608974830690>)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at reactivemongo.IsMaster(true, 53, {{NodeSet Some(rs0) Node[documentdb-dev.cluster-cn18vvzkqual.us-east-1.docdb.amazonaws.com:27017: Primary (20/20/20 available connections), latency=16608966983407ns, authenticated={user-sessions#user-sessions}] }})(<time:16608974658158>)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at reactivemongo.RefreshAll({{NodeSet Some(rs0) Node[documentdb-dev.cluster-cn18vvzkqual.us-east-1.docdb.amazonaws.com:27017: Primary (20/20/20 available connections), latency=4699542ns, authenticated={user-sessions#user-sessions}] }})(<time:16608967488204>)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at reactivemongo.ConnectAll({{NodeSet Some(rs0) Node[documentdb-dev.cluster-cn18vvzkqual.us-east-1.docdb.amazonaws.com:27017: Primary (20/20/20 available connections), latency=4699542ns, authenticated={user-sessions#user-sessions}] }})(<time:16598976125426>)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at reactivemongo.ConnectAll$IsMaster(52, {{NodeSet Some(rs0) Node[documentdb-dev.cluster-cn18vvzkqual.us-east-1.docdb.amazonaws.com:27017: Primary (20/20/20 available connections), latency=4699542ns, authenticated={user-sessions#user-sessions}] }})(<time:16598972081992>)
Dec 5 22:50:23 i-00f33fa3398767595 user-sessions-dev INFO at reactivemongo.IsMaster(true, 52, {{NodeSet Some(rs0) Node[documentdb-dev.cluster-cn18vvzkqual.us-east-1.docdb.amazonaws.com:27017: Primary (20/20/20 available connections), latency=16598966982725ns, authenticated={user-sessions#user-sessions}] }})(<time:16598971885250>)
Dec 5 22:51:54 i-00f33fa3398767595 user-sessions-dev INFO [warn] r.c.a.MongoDBSystem - [Supervisor-1/Connection-1] The entire node set is unreachable, is there a network problem?
Dec 5 22:53:34 i-00f33fa3398767595 user-sessions-dev INFO [warn] r.c.a.MongoDBSystem - [Supervisor-1/Connection-1] The entire node set is unreachable, is there a network problem?
Dec 5 22:55:14 i-00f33fa3398767595 user-sessions-dev INFO [warn] r.c.a.MongoDBSystem - [Supervisor-1/Connection-1] The entire node set is unreachable, is there a network problem?
We try to change our string connection to pointing directly to primary node (writer) like this:
mongodb://user:pwd#primarynode:27017/db-name?replicaSet=rs0
This work properly, but, the url of primary node could change constantly, and that solution doesn't work for us.

Related

cassandra.service: main process exited, code=killed, status=11/SEGV

cassandra.service: main process exited, code=killed, status=11/SEGV
env:
apache-cassandra-4.0.0
jdk-11.0.12
ZGC
jvm:
-Xms31G
-Xmx31G
host:
16core 128G
/var/log/message:
Jul 4 13:57:10 iZ2zec1q29sosy4bdv893qZ systemd-logind: Removed session 277.
Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [CompactionExecutor:4] 2022-07-04 13:57:12,074 CompactionTask.java:245 - Compacted (24af5250-fb5e-11ec-aa2a-6b96728ba428)
4 sstables to [/data/cassandra/data/data/spaceport/xm_coupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6494-big,] to level=0. 27.414MiB to 27.412MiB (~99% of original) i
n 1,812ms. Read Throughput = 15.127MiB/s, Write Throughput = 15.126MiB/s, Row Throughput = ~123,625/s. 32,718 total partitions merged to 32,689. Partition merge counts were {1:
32663, 2:23, 3:3, }
Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [NonPeriodicTasks:1] 2022-07-04 13:57:12,083 SSTable.java:111 - Deleting sstable: /data/cassandra/data/data/spaceport/xm_c
oupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6490-big
Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [NonPeriodicTasks:1] 2022-07-04 13:57:12,084 SSTable.java:111 - Deleting sstable: /data/cassandra/data/data/spaceport/xm_c
oupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6493-big
Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [NonPeriodicTasks:1] 2022-07-04 13:57:12,085 SSTable.java:111 - Deleting sstable: /data/cassandra/data/data/spaceport/xm_c
oupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6491-big
Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [NonPeriodicTasks:1] 2022-07-04 13:57:12,085 SSTable.java:111 - Deleting sstable: /data/cassandra/data/data/spaceport/xm_c
oupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6492-big
Jul 4 14:00:01 iZ2zec1q29sosy4bdv893qZ systemd: Started Session 293 of user root.
Jul 4 14:01:01 iZ2zec1q29sosy4bdv893qZ systemd: Started Session 294 of user root.
Jul 4 14:01:59 iZ2zec1q29sosy4bdv893qZ systemd: cassandra.service: main process exited, code=killed, status=11/SEGV
Jul 4 14:02:00 iZ2zec1q29sosy4bdv893qZ systemd: Unit cassandra.service entered failed state.
Jul 4 14:02:00 iZ2zec1q29sosy4bdv893qZ systemd: cassandra.service failed.
Jul 4 14:02:05 iZ2zec1q29sosy4bdv893qZ systemd: cassandra.service holdoff time over, scheduling restart.
Jul 4 14:02:05 iZ2zec1q29sosy4bdv893qZ systemd: Stopped Cassandra Server Service.
Jul 4 14:02:05 iZ2zec1q29sosy4bdv893qZ systemd: Started Cassandra Server Service.
Jul 4 14:02:55 iZ2zec1q29sosy4bdv893qZ cassandra: CompileCommand: dontinline org/apache/cassandra/db/Columns$Serializer.deserializeLargeSubset(Lorg/apache/cassandra/io/util/DataI
nputPlus;Lorg/apache/cassandra/db/Columns;I)Lorg/apache/cassandra/db/Columns;
The log entries you posted on their own don't explain what the problem is. You will need to review the Cassandra system.log for clues.
A friendly reminder that Stack Overflow is for getting help with coding, algorithm, or programming language problems. For future reference, you should post DB admin/ops questions on dba.stackexchange.com. If you post it there, I'd be happy to help. Cheers!

Postgres not responding after reboot - needs /usr/lib/postgresql/12/bin/pg_ctl restart -D /var/lib/postgresql/12/main

I'm having problems with PostgreSQL on Ubuntu 20.04. After server is rebooted, the database doesn't work and I need to switch the user to postgres and call /usr/lib/postgresql/12/bin/pg_ctl restart -D /var/lib/postgresql/12/main to restart it.
EDIT
So it looks like that the night this started, these upgrades have been automatically installed:
tart-Date: 2021-11-12 06:35:51
Commandline: /usr/bin/unattended-upgrade
Upgrade: libtdb1:amd64 (1.4.2-3build1, 1.4.3-0ubuntu0.20.04.1)
End-Date: 2021-11-12 06:35:51
Start-Date: 2021-11-12 06:35:59
Commandline: /usr/bin/unattended-upgrade
Upgrade: libpq5:amd64 (12.8-0ubuntu0.20.04.1, 12.9-0ubuntu0.20.04.1), libpq-dev:amd64 (12.8-0ubuntu0.20.04.1, 12.9-0ubuntu0.20.04.1)
End-Date: 2021-11-12 06:35:59
Start-Date: 2021-11-12 06:36:07
Commandline: /usr/bin/unattended-upgrade
Upgrade: postgresql-client-12:amd64 (12.8-0ubuntu0.20.04.1, 12.9-0ubuntu0.20.04.1)
End-Date: 2021-11-12 06:36:08
Start-Date: 2021-11-12 06:36:16
Commandline: /usr/bin/unattended-upgrade
Upgrade: postgresql-12:amd64 (12.8-0ubuntu0.20.04.1, 12.9-0ubuntu0.20.04.1)
End-Date: 2021-11-12 06:36:19
----------------------------------------------------------------------------------------------------------
I absolutely don't know where the problem is, can you take a look at it? These are steps:
(Step 4 - postgresql not working, step 8 - it works)
*1 REBOOT
*2
master#myproject-ubuntu:~$ sudo service postgresql status
● postgresql.service - PostgreSQL RDBMS
Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor preset: enabled)
Active: active (exited) since Tue 2021-11-16 15:16:22 CST; 29s ago
Process: 713 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 713 (code=exited, status=0/SUCCESS)
Nov 16 15:16:22 myproject-ubuntu systemd[1]: Starting PostgreSQL RDBMS...
Nov 16 15:16:22 myproject-ubuntu systemd[1]: Finished PostgreSQL RDBMS.
*3
sudo grep "postgres" /var/log/syslog
Nov 16 15:16:22 myproject-ubuntu kernel: [ 3.939501] systemd[1]: Created slice system-postgresql.slice.
Nov 16 15:16:22 myproject-ubuntu postgresql#12-main[712]: Error: Could not open logfile /var/log/postgresql/postgresql-12-main.log
Nov 16 15:16:22 myproject-ubuntu postgresql#12-main[638]: Error: /usr/lib/postgresql/12/bin/pg_ctl /usr/lib/postgresql/12/bin/pg_ctl start -D /var/lib/postgresql/12/main -l /var/log/postgresql/postgresql-12-main.log -s -o -c config_file="/etc/postgresql/12/main/postgresql.conf" exited with status 1:
Nov 16 15:16:22 myproject-ubuntu systemd[1]: postgresql#12-main.service: Can't open PID file /run/postgresql/12-main.pid (yet?) after start: Operation not permitted
Nov 16 15:16:22 myproject-ubuntu systemd[1]: postgresql#12-main.service: Failed with result 'protocol'.
Nov 16 15:16:49 myproject-ubuntu gunicorn[984]: File "/home/master/.virtualenvs/arcounty_django/lib/python3.8/site-packages/django/db/backends/postgresql/base.py", line 187, in get_new_connection
*4
pg_lsclusters
Ver Cluster Port Status Owner Data directory Log file
12 main 5432 down <unknown> /var/lib/postgresql/12/main /var/log/postgresql/postgresql-12-main.log
*5
CMD: sudo service postgresql restart
CMD: pg_lsclusters
Ver Cluster Port Status Owner Data directory Log file
12 main 5432 down <unknown> /var/lib/postgresql/12/main /var/log/postgresql/postgresql-12-main.log
*6
CMD: sudo su - postgres
CMD: /usr/lib/postgresql/12/bin/pg_ctl restart -D /var/lib/postgresql/12/main
pg_ctl: PID file "/var/lib/postgresql/12/main/postmaster.pid" does not exist
Is server running?
trying to start server anyway
waiting for server to start....2021-11-16 21:21:55.805 UTC [1158] LOG: starting PostgreSQL 12.9 (Ubuntu 12.9-0ubuntu0.20.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, 64-bit
2021-11-16 21:21:55.806 UTC [1158] LOG: listening on IPv4 address "127.0.0.1", port 5432
2021-11-16 21:21:55.808 UTC [1158] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2021-11-16 21:21:55.847 UTC [1163] LOG: database system was shut down at 2021-11-16 21:13:45 UTC
2021-11-16 21:21:55.865 UTC [1158] LOG: database system is ready to accept connections
done
server started
*7 exit
*8 (as normal user)
`CMD:pg_lsclusters`
Ver Cluster Port Status Owner Data directory Log file 12 main 5432 online <unknown> /var/lib/postgresql/12/main /var/log/postgresql/postgresql-12-main.log
EDIT:
permissions & ownerships after reboot (when it's not working)
sudo ls -la /var/lib/postgresql/12/main/
master#myproject-ubuntu:~$ sudo ls -la /var/lib/postgresql/12/main/
[sudo] password for master:
total 88
drwx------ 19 postgres postgres 4096 Nov 16 15:39 .
drwx------ 3 postgres postgres 4096 Oct 6 2020 ..
-rwx------ 1 postgres postgres 3 Oct 6 2020 PG_VERSION
drwx------ 7 postgres postgres 4096 Jan 12 2021 base
drwx------ 2 postgres postgres 4096 Nov 16 15:22 global
drwx------ 2 postgres postgres 4096 Oct 6 2020 pg_commit_ts
drwx------ 2 postgres postgres 4096 Oct 6 2020 pg_dynshmem
drwx------ 4 postgres postgres 4096 Nov 16 15:39 pg_logical
drwx------ 4 postgres postgres 4096 Oct 6 2020 pg_multixact
drwx------ 2 postgres postgres 4096 Nov 16 15:21 pg_notify
drwx------ 2 postgres postgres 4096 Oct 6 2020 pg_replslot
drwx------ 2 postgres postgres 4096 Oct 6 2020 pg_serial
drwx------ 2 postgres postgres 4096 Oct 6 2020 pg_snapshots
drwx------ 2 postgres postgres 4096 Nov 16 15:39 pg_stat
drwx------ 2 postgres postgres 4096 Oct 6 2020 pg_stat_tmp
drwx------ 2 postgres postgres 4096 Nov 1 14:55 pg_subtrans
drwx------ 2 postgres postgres 4096 Oct 6 2020 pg_tblspc
drwx------ 2 postgres postgres 4096 Oct 6 2020 pg_twophase
drwx------ 3 postgres postgres 4096 Nov 11 22:20 pg_wal
drwx------ 2 postgres postgres 4096 Oct 27 09:13 pg_xact
-rwx------ 1 postgres postgres 88 Oct 6 2020 postgresql.auto.conf
-rwx------ 1 postgres postgres 130 Nov 16 15:21 postmaster.opts
sudo ls -la /var/lib/postgresql/12/
master#myproject-ubuntu:~$ sudo ls -la /var/lib/postgresql/12/
total 12
drwx------ 3 postgres postgres 4096 Oct 6 2020 .
drwxr-xr-x 3 postgres postgres 4096 Dec 22 2020 ..
drwx------ 19 postgres postgres 4096 Nov 16 15:39 main
sudo cat etc/postgresql/12/main/start.conf
# Automatic startup configuration
# auto: automatically start the cluster
# manual: manual startup with pg_ctlcluster/postgresql#.service only
# disabled: refuse to start cluster
# See pg_createcluster(1) for details. When running from systemd,
# invoke 'systemctl daemon-reload' after editing this file.
auto
cat /var/log/apt/history.log
Start-Date: 2021-11-09 06:34:56
Commandline: apt-get -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confold -qq install -y --only-upgrade do-agent
Upgrade: do-agent:amd64 (3.11.0, 3.12.0)
End-Date: 2021-11-09 06:34:57
Start-Date: 2021-11-10 06:49:20
Commandline: /usr/bin/unattended-upgrade
Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic)
Upgrade: linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-virtual:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-headers-virtual:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-virtual:amd64 (5.4.0.89.93, 5.4.0.90.94)
End-Date: 2021-11-10 06:49:40
Start-Date: 2021-11-10 06:49:48
Commandline: /usr/bin/unattended-upgrade
Upgrade: linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101)
End-Date: 2021-11-10 06:49:49
Start-Date: 2021-11-11 06:44:31
Commandline: /usr/bin/unattended-upgrade
Remove: linux-headers-5.4.0-88-generic:amd64 (5.4.0-88.99), linux-headers-5.4.0-88:amd64 (5.4.0-88.99)
End-Date: 2021-11-11 06:44:34
Start-Date: 2021-11-11 06:44:41
Commandline: /usr/bin/unattended-upgrade
Remove: linux-image-5.4.0-88-generic:amd64 (5.4.0-88.99)
End-Date: 2021-11-11 06:44:43
Start-Date: 2021-11-11 06:44:50
Commandline: /usr/bin/unattended-upgrade
Remove: linux-modules-5.4.0-88-generic:amd64 (5.4.0-88.99)
End-Date: 2021-11-11 06:44:50
Start-Date: 2021-11-12 06:35:51
Commandline: /usr/bin/unattended-upgrade
Upgrade: libtdb1:amd64 (1.4.2-3build1, 1.4.3-0ubuntu0.20.04.1)
End-Date: 2021-11-12 06:35:51
Start-Date: 2021-11-12 06:35:59
Commandline: /usr/bin/unattended-upgrade
Upgrade: libpq5:amd64 (12.8-0ubuntu0.20.04.1, 12.9-0ubuntu0.20.04.1), libpq-dev:amd64 (12.8-0ubuntu0.20.04.1, 12.9-0ubuntu0.20.04.1)
End-Date: 2021-11-12 06:35:59
Start-Date: 2021-11-12 06:36:07
Commandline: /usr/bin/unattended-upgrade
Upgrade: postgresql-client-12:amd64 (12.8-0ubuntu0.20.04.1, 12.9-0ubuntu0.20.04.1)
End-Date: 2021-11-12 06:36:08
Start-Date: 2021-11-12 06:36:16
Commandline: /usr/bin/unattended-upgrade
Upgrade: postgresql-12:amd64 (12.8-0ubuntu0.20.04.1, 12.9-0ubuntu0.20.04.1)
End-Date: 2021-11-12 06:36:19
Start-Date: 2021-11-16 06:29:53
Commandline: /usr/bin/unattended-upgrade
Upgrade: xxd:amd64 (2:8.1.2269-1ubuntu5.3, 2:8.1.2269-1ubuntu5.4)
End-Date: 2021-11-16 06:29:54
Start-Date: 2021-11-16 06:30:01
Commandline: /usr/bin/unattended-upgrade
Upgrade: vim-common:amd64 (2:8.1.2269-1ubuntu5.3, 2:8.1.2269-1ubuntu5.4), vim-runtime:amd64 (2:8.1.2269-1ubuntu5.3, 2:8.1.2269-1ubuntu5.4), vim:amd64 (2:8.1.2269-1ubuntu5.3, 2:8.1.2269-1ubuntu5.4), vim-tiny:amd64 (2:8.1.2269-1ubuntu5.3, 2:8.1.2269-1ubuntu5.4)
End-Date: 2021-11-16 06:30:05
Start-Date: 2021-11-17 06:57:29
Commandline: /usr/bin/unattended-upgrade
Upgrade: accountsservice:amd64 (0.6.55-0ubuntu12~20.04.4, 0.6.55-0ubuntu12~20.04.5), libaccountsservice0:amd64 (0.6.55-0ubuntu12~20.04.4, 0.6.55-0ubuntu12~20.04.5)
End-Date: 2021-11-17 06:57:30
Start-Date: 2021-11-17 07:07:27
Commandline: apt-get purge --auto-remove redis-server
Requested-By: master (1000)
Purge: lua-bitop:amd64 (1.0.2-5), libhiredis0.14:amd64 (0.14.0-6), lua-cjson:amd64 (2.1.0+dfsg-2.1), redis:amd64 (5:5.0.7-2), redis-tools:amd64 (5:5.0.7-2), liblua5.1-0:amd64 (5.1.5-8.1build4), libjemalloc2:amd64 (5.2.1-1ubuntu1), redis-server:amd64 (5:5.0.7-2)
End-Date: 2021-11-17 07:07:30
Start-Date: 2021-11-17 07:07:49
Commandline: apt-get install redis-server
Requested-By: master (1000)
Install: lua-bitop:amd64 (1.0.2-5, automatic), libhiredis0.14:amd64 (0.14.0-6, automatic), lua-cjson:amd64 (2.1.0+dfsg-2.1, automatic), redis-tools:amd64 (5:5.0.7-2, automatic), liblua5.1-0:amd64 (5.1.5-8.1build4, automatic), libjemalloc2:amd64 (5.2.1-1ubuntu1, automatic), redis-server:amd64 (5:5.0.7-2)
End-Date: 2021-11-17 07:07:52

Apache2 is not starting,I am using Ubuntu 16.04

Unable to start Apache2 server after I modifed dir.conf file, even after changing it back to normal
I modified /etc/apache2/mods-enabled/dir.conf and changed the order and wrote index.php in
the first place before index.html, so the file contents have been modified from
"DirectoryIndex index.php index.html index.cgi index.pl index.xhtml index.htm" to now
"DirectoryIndex index.php index.html index.cgi index.pl index.xhtml index.htm". But still
changing that back to original order, also does not start apache2 server, it gives the same
error. I tried restarting and stop and start, but none seem to work.
** Here are the details of systemctl status apache2.service **
● apache2.service - LSB: Apache2 web server
Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: failed (Result: exit-code) since Tue 2020-11-24 12:28:31 IST; 5min ago
Docs: man:systemd-sysv-generator(8)
Process: 20300 ExecStop=/etc/init.d/apache2 stop (code=exited, status=0/SUCCESS)
Process: 25755 ExecStart=/etc/init.d/apache2 start (code=exited, status=1/FAILURE)
Nov 24 12:28:31 localhost apache2[25755]: *
Nov 24 12:28:31 localhost apache2[25755]: * The apache2 configtest failed.
Nov 24 12:28:31 localhost apache2[25755]: Output of config test was:
Nov 24 12:28:31 localhost apache2[25755]: AH00534: apache2: Configuration error: More than one MPM loaded.
Nov 24 12:28:31 localhost apache2[25755]: Action 'configtest' failed.
Nov 24 12:28:31 localhost apache2[25755]: The Apache error log may have more information.
Nov 24 12:28:31 localhost systemd[1]: apache2.service: Control process exited, code=exited status=1
Nov 24 12:28:31 localhost systemd[1]: Failed to start LSB: Apache2 web server.
Nov 24 12:28:31 localhost systemd[1]: apache2.service: Unit entered failed state.
Nov 24 12:28:31 localhost systemd[1]: apache2.service: Failed with result 'exit-code'.
**Here is the details of journalctl -xe**
Nov 24 12:44:42 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:75]
Nov 24 12:44:42 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:77]
Nov 24 12:44:43 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:75]
Nov 24 12:44:43 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:77]
Nov 24 12:44:44 localhost systemd[1]: Failed to start MySQL Community Server.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has failed.
--
-- The result is failed.
Nov 24 12:44:44 localhost systemd[1]: mysql.service: Unit entered failed state.
Nov 24 12:44:44 localhost systemd[1]: mysql.service: Failed with result 'exit-code'.
Nov 24 12:44:44 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:75]
Nov 24 12:44:44 localhost systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Nov 24 12:44:44 localhost systemd[1]: Stopped MySQL Community Server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has finished shutting down.
Nov 24 12:44:44 localhost systemd[1]: Starting MySQL Community Server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has begun starting up.
Nov 24 12:44:44 localhost mysqld[5387]: 2020-11-24T07:14:44.545855Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
Nov 24 12:44:44 localhost mysqld[5387]: 2020-11-24T07:14:44.545908Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
Nov 24 12:44:44 localhost mysqld[5387]: 2020-11-24T07:14:44.705792Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --expl
Nov 24 12:44:44 localhost mysqld[5387]: 2020-11-24T07:14:44.707018Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.32-0ubuntu0.16.04.1) starting as process 538
Nov 24 12:44:44 localhost mysqld[5387]: 2020-11-24T07:14:44.709650Z 0 [ERROR] Could not open file '/var/log/mysql/error.log' for error logging: No suc
Nov 24 12:44:44 localhost mysqld[5387]: 2020-11-24T07:14:44.709678Z 0 [ERROR] Aborting
Nov 24 12:44:44 localhost mysqld[5387]: 2020-11-24T07:14:44.709703Z 0 [Note] Binlog end
Nov 24 12:44:44 localhost mysqld[5387]: 2020-11-24T07:14:44.709770Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
Nov 24 12:44:44 localhost systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
Nov 24 12:44:44 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:77]
Nov 24 12:44:44 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:75]
Nov 24 12:44:45 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:77]
Nov 24 12:44:45 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:75]
Nov 24 12:44:45 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:77]

Tor bundle error circuit_remove_handled_ports(): Port 443 is not handled

When I start Tor bundle on Ubuntu 18.04 I get an error:
Jul 11 11:25:05.000 [debug] command_process_destroy_cell(): Received for circID 3910604357.
Jul 11 11:25:05.000 [info] circuit_mark_for_close_(): Circuit 0 (id: 37) marked for close at ../src/core/or/command.c:654 (orig reason: 517, new reason: 0)
Jul 11 11:25:05.000 [debug] connection_or_process_cells_from_inbuf(): 13: starting, inbuf_datalen 0 (0 pending in tls object).
Jul 11 11:25:05.000 [debug] circuit_increment_failure_count(): n_circuit_failures now 6.
Jul 11 11:25:05.000 [info] circuit_free_(): Circuit 0 (id: 37) has been freed.
Jul 11 11:25:05.000 [debug] circuit_remove_handled_ports(): Port 443 is not handled.
Jul 11 11:25:05.000 [info] circuit_predict_and_launch_new(): Have 0 clean circs (0 internal), need another exit circ.
Jul 11 11:25:06.000 [debug] circuit_remove_handled_ports(): Port 443 is not handled.
Jul 11 11:25:06.000 [info] circuit_predict_and_launch_new(): Have 0 clean circs (0 internal), need another exit circ.
Jul 11 11:25:07.000 [debug] circuit_remove_handled_ports(): Port 443 is not handled.
Jul 11 11:25:07.000 [info] circuit_predict_and_launch_new(): Have 0 clean circs (0 internal), need another exit circ.
Jul 11 11:25:08.000 [debug] circuit_remove_handled_ports(): Port 443 is not handled.
Jul 11 11:25:08.000 [info] circuit_predict_and_launch_new(): Have 0 clean circs (0 internal), need another exit circ.
I've installed Tor bundle from official Tor repo. What have I to do to prevent this error?

Deploy kubernetes cluster on Azure

I tried to create kubernetes cluster(v1.2.3) on azure with coreos cluster. I followed the documentation (http://kubernetes.io/docs/getting-started-guides/coreos/azure/)
Then I cloned the repo( git clone https://github.com/kubernetes/kubernetes). And I did a minor change in file( docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-main-nodes-template.yml) changed the kube version from v1.1.2 to v1.2.3.
And then I created the cluster by running the file(./create-kubernetes-cluster.js), cluster is successfully created for me. But in master node API server didn't get started..
I checked the log it was showing - Cloud provider could not be initialized: unknown cloud provider "vagrant".. I could not catch why this issue was coming..
This is my Log of -> kube-apiserver.service
-- Logs begin at Sat 2016-07-23 12:41:36 UTC, end at Sat 2016-07-23 12:44:19 UTC. --
Jul 23 12:43:06 anudemon-master-00 systemd[1]: Started Kubernetes API Server.
Jul 23 12:43:06 anudemon-master-00 kube-apiserver[1964]: I0723 12:43:06.299966 1964 server.go:188] Will report 172.16.0.4 as public IP address.
Jul 23 12:43:06 anudemon-master-00 kube-apiserver[1964]: F0723 12:43:06.300057 1964 server.go:211] Cloud provider could not be initialized: unknown cloud provider "vagrant"
Jul 23 12:43:06 anudemon-master-00 systemd[1]: kube-apiserver.service: Main process exited, code=exited, status=255/n/a
Jul 23 12:43:06 anudemon-master-00 systemd[1]: kube-apiserver.service: Unit entered failed state.
Jul 23 12:43:06 anudemon-master-00 systemd[1]: kube-apiserver.service: Failed with result 'exit-code'.
Jul 23 12:43:16 anudemon-master-00 systemd[1]: kube-apiserver.service: Service hold-off time over, scheduling restart.
Jul 23 12:43:16 anudemon-master-00 systemd[1]: Stopped Kubernetes API Server.
Jul 23 12:43:16 anudemon-master-00 kube-apiserver[2015]: I0723 12:43:16.428476 2015 server.go:188] Will report 172.16.0.4 as public IP address.
Jul 23 12:43:16 anudemon-master-00 kube-apiserver[2015]: F0723 12:43:16.428534 2015 server.go:211] Cloud provider could not be initialized: unknown cloud provider "vagrant"
Jul 23 12:43:16 anudemon-master-00 systemd[1]: Started Kubernetes API Server.
Jul 23 12:43:16 anudemon-master-00 systemd[1]: kube-apiserver.service: Main process exited, code=exited, status=255/n/a
Jul 23 12:43:16 anudemon-master-00 systemd[1]: kube-apiserver.service: Unit entered failed state.
Jul 23 12:43:16 anudemon-master-00 systemd[1]: kube-apiserver.service: Failed with result 'exit-code'.
Jul 23 12:43:26 anudemon-master-00 systemd[1]: kube-apiserver.service: Service hold-off time over, scheduling restart.
Jul 23 12:43:26 anudemon-master-00 systemd[1]: Stopped Kubernetes API Server.
Jul 23 12:43:26 anudemon-master-00 systemd[1]: Started Kubernetes API Server.
Jul 23 12:43:26 anudemon-master-00 kube-apiserver[2024]: I0723 12:43:26.756551 2024 server.go:188] Will report 172.16.0.4 as public IP address.
Jul 23 12:43:26 anudemon-master-00 kube-apiserver[2024]: F0723 12:43:26.756654 2024 server.go:211] Cloud provider could not be initialized: unknown cloud provider "vagrant"
Jul 23 12:43:26 anudemon-master-00 systemd[1]: kube-apiserver.service: Main process exited, code=exited, status=255/n/a
Jul 23 12:43:26 anudemon-master-00 systemd[1]: kube-apiserver.service: Unit entered failed state.
Jul 23 12:43:26 anudemon-master-00 systemd[1]: kube-apiserver.service: Failed with result 'exit-code'.
Jul 23 12:43:36 anudemon-master-00 systemd[1]: kube-apiserver.service: Service hold-off time over, scheduling restart.
Jul 23 12:43:36 anudemon-master-00 systemd[1]: Stopped Kubernetes API Server.
Jul 23 12:43:36 anudemon-master-00 systemd[1]: Started Kubernetes API Server.
Jul 23 12:43:36 anudemon-master-00 kube-apiserver[2039]: I0723 12:43:36.872849 2039 server.go:188] Will report 172.16.0.4 as public IP address.
Have you had a look at kuberenetes-anywhere (https://github.com/kubernetes/kubernetes-anywhere)? Much work has been done there and now probably has all the right bits to deploy out your cluster with Azure specific cloud provider integrations.

Resources