I am running a bitnami instance of mongodb for our pre-production. The default port for mongo is 27017. But for security reasons i want to change it but it is not possible. I have tried these things: changes the port in mongodb.conf and restarted the server. It shows the below error: **connecting to: mongodb:///opt/bitnami/mongodb/tmp/mongodb-27017.sock/ 2018-04-20T12:55:04.373+0530 W NETWORK [thread1] Failed to connect to /opt/bitnami/mongodb/tmp/mongodb-27017.sock:0, in(connect), reason: Connection refused 2018-04-20T12:55:04.373+0530 E QUERY [thread1] Error: couldn't connect to server /opt/bitnami/mongodb/tmp/mongodb-27017.sock:27017, connection attempt failed : connect@src/mongo/shell/mongo.js:237:13 @(connect):1:6 exception: connect failed** I restarted mongod with different port. Still i am not able to do it. when i switch back to 27017. It comes back to normal. Any suggestions on how to do it the right way?

sudo cat /opt/bitnami/mysql/logs/mysqld.log 2024-10-27T07:54:59.478600Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user . Shutting down mysqld (Version: 8.0.35). 2024-10-27T07:55:01.598187Z 0 [Warning] [MY-010909] [Server] /opt/bitnami/mysql/bin/mysqld: Forcing close of thread 19496 user: 'bn_mattermost'. 2024-10-27T07:55:01.598399Z 0 [Warning] [MY-010909] [Server] /opt/bitnami/mysql/bin/mysqld: Forcing close of thread 19624 user: 'bn_mattermost'. 2024-10-27T07:55:01.598490Z 0 [Warning] [MY-010909] [Server] /opt/bitnami/mysql/bin/mysqld: Forcing close of thread 19618 user: 'bn_mattermost'. 2024-10-27T07:55:01.598610Z 0 [Warning] [MY-010909] [Server] /opt/bitnami/mysql/bin/mysqld: Forcing close of thread 19005 user: 'bn_mattermost'. 2024-10-27T07:55:01.598711Z 0 [Warning] [MY-010909] [Server] /opt/bitnami/mysql/bin/mysqld: Forcing close of thread 19454 user: 'bn_mattermost'. 2024-10-27T07:55:01.598818Z 0 [Warning] [MY-010909] [Server] /opt/bitnami/mysql/bin/mysqld: Forcing close of thread 19623 user: 'bn_mattermost'. 2024-10-27T07:55:04.172354Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld: Shutdown complete (mysqld 8.0.35) Source distribution. %%%%%%%%%%%%%%%%2024-10-28T04:53:41.719203Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld (mysqld 8.0.35) starting as process 2410934 2024-10-28T04:53:41.959977Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2024-10-28T04:53:43.575311Z 1 [ERROR] [MY-013882] [InnoDB] Missing redo log file ./#innodb_redo/#ib_redo1292 (with start_lsn = 4230987776). 2024-10-28T04:53:43.575375Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error. 2024-10-28T04:53:43.674441Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine 2024-10-28T04:53:43.674754Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. 2024-10-28T04:53:43.674796Z 0 [ERROR] [MY-010119] [Server] Aborting 2024-10-28T04:53:43.689846Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld: Shutdown complete (mysqld 8.0.35) Source distribution. 2024-10-28T04:56:39.833310Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld (mysqld 8.0.35) starting as process 2411144 2024-10-28T04:56:39.850289Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2024-10-28T04:56:41.063343Z 1 [ERROR] [MY-013882] [InnoDB] Missing redo log file ./#innodb_redo/#ib_redo1292 (with start_lsn = 4230987776). 2024-10-28T04:56:41.063395Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error. 2024-10-28T04:56:41.416893Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine 2024-10-28T04:56:41.417157Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. 2024-10-28T04:56:41.417200Z 0 [ERROR] [MY-010119] [Server] Aborting 2024-10-28T04:56:41.417837Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld: Shutdown complete (mysqld 8.0.35) Source distribution. 2024-10-28T04:58:39.211474Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld (mysqld 8.0.35) starting as process 2411267 2024-10-28T04:58:39.221770Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2024-10-28T04:58:40.078596Z 1 [ERROR] [MY-013882] [InnoDB] Missing redo log file ./#innodb_redo/#ib_redo1292 (with start_lsn = 4230987776). 2024-10-28T04:58:40.078647Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error. 2024-10-28T04:58:40.496715Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine 2024-10-28T04:58:40.496998Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. 2024-10-28T04:58:40.497041Z 0 [ERROR] [MY-010119] [Server] Aborting 2024-10-28T04:58:40.497739Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld: Shutdown complete (mysqld 8.0.35) Source distribution. 2024-10-28T04:59:58.332324Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld (mysqld 8.0.35) starting as process 2411447 2024-10-28T04:59:58.345141Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2024-10-28T04:59:59.454446Z 1 [ERROR] [MY-013882] [InnoDB] Missing redo log file ./#innodb_redo/#ib_redo1292 (with start_lsn = 4230987776). 2024-10-28T04:59:59.454502Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error. 2024-10-28T04:59:59.829494Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine 2024-10-28T04:59:59.829793Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. 2024-10-28T04:59:59.829837Z 0 [ERROR] [MY-010119] [Server] Aborting 2024-10-28T04:59:59.830457Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld: Shutdown complete (mysqld 8.0.35) Source distribution. 2024-10-28T05:04:30.093217Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld (mysqld 8.0.35) starting as process 2411689 2024-10-28T05:04:30.104180Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2024-10-28T05:04:31.153706Z 1 [ERROR] [MY-013882] [InnoDB] Missing redo log file ./#innodb_redo/#ib_redo1292 (with start_lsn = 4230987776). 2024-10-28T05:04:31.153915Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error. 2024-10-28T05:04:31.563530Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine 2024-10-28T05:04:31.563787Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. 2024-10-28T05:04:31.563853Z 0 [ERROR] [MY-010119] [Server] Aborting 2024-10-28T05:04:31.564498Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld: Shutdown complete (mysqld 8.0.35) Source distribution. 2024-10-28T06:16:42.688464Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld (mysqld 8.0.35) starting as process 2412572 2024-10-28T06:16:42.849064Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2024-10-28T06:16:44.206632Z 1 [ERROR] [MY-013882] [InnoDB] Missing redo log file ./#innodb_redo/#ib_redo1292 (with start_lsn = 4230987776). 2024-10-28T06:16:44.206696Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error. 2024-10-28T06:16:44.356909Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine 2024-10-28T06:16:44.357168Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. 2024-10-28T06:16:44.357210Z 0 [ERROR] [MY-010119] [Server] Aborting 2024-10-28T06:16:44.365658Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld: Shutdown complete (mysqld 8.0.35) Source distribution.

I have to migrate from **MongoDB packaged with Bitnami** (sharded helm chart with 0 shard) to **MongoDB Atlas** (replicaset or sharded cluster) Do you know if there is a way to do that ? Does that mean downtime application ? Is there a way to take advantage of the Live Migration functionality offered by Atlas ?

I'm having a similar issue as to what is described in this post which never received an answer. Essentially, I'm running bitnami and my server space is filling up over time on what is a very simple static website. I narrowed the cluprit down to the /opt/bitnami/mysql/data folder which seems to be increasing in size at a rate of about 158KB per minute (aka 230MB per day). Some potentially relevant (or irrelevant) info I noticed: Running sudo du -b yields the following > 10553149373 ./data but running ls -l yields the following > drwxr-x--- 7 mysql root 12288 Dec 25 06:25 data The size of the data folder is stationary in the case of the ls command as each time I run that I get the same output. But the du command shows that the size is growing. And note the size difference between the two (I understand that du shows allocated space and ls shows actual usage. Why would one be so much bigger than the other - and why does du show it growing while ls does not).

how are you? I have been trying to solve this for a long time and I have not been able to, the case is like this. I have an instance in amazon lightsail it was 1 GB RAM, 1 vCPU, 40 GB SSD but due to space issues, upgrade to 2 GB RAM, 1 vCPU, 60 GB SSD Yesterday it had only 20 GB occupied in the main storage:  Today it is already occupying 40 GB:  I ran the following commands:

sudo du -shx /\* | sort -h

until you get to this path

sudo du -shx /opt/bitnami/mysql/\* | sort -h

and discover that

/opt/bitnami/mysql/data

...weighs in at around 37GB:  Does anyone know how I can see why it is doing that? I still don't know how to stop it from filling up the storage

Previously when I using the Bitnami Helm chart by way of Terraform to deploy PostgreSQL, I would have a database created. Now I no longer have a database created. I'm using * same connect string * same usernname * same password But I am getting this error in my Kubernetes logs, > psql: error: FATAL: database "foo" does not exist Why is it that I no longer have an initial database?

Since there are issues with collations in the default alpine-based timescaledb images, I tried to use the bitnami-image . But I get an error on startup. docker run ^ -p 5432:5432 ^ -v tsdb-bitnami:/bitnami/postgresql ^ --env POSTGRES_USER=tsdbu ^ --env POSTGRES_DB=tsdbu ^ --env POSTGRES_PASSWORD=tsdbu ^ --name timeseriesdb ^ timescale/timescaledb:1.5.0-pg11-bitnami This fails with: ERROR: permission denied to create extension "timescaledb" HINT: Must be superuser to create this extension. Is there some other parameter that we must pass? i.e. I've tried POSTGRESQL_POSTGRES_PASSWORD (ref= bitnami postgres docs ), but this did also not work. Versions: * Windows 10 64-bit * Docker version 19.03.4, build 9013bf5 * Timescale container: timescale/timescaledb:1.5.0-pg11-bitnami Full Output: postgresql 12:31:34.41 postgresql 12:31:34.41 Welcome to the Bitnami postgresql container postgresql 12:31:34.41 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-postgresql postgresql 12:31:34.41 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-postgresql/issues postgresql 12:31:34.42 Send us your feedback at containers@bitnami.com postgresql 12:31:34.42 postgresql 12:31:34.42 INFO ==> ** Starting PostgreSQL setup ** postgresql 12:31:34.45 INFO ==> Validating settings in POSTGRESQL_* env vars.. postgresql 12:31:34.46 INFO ==> Initializing PostgreSQL database... postgresql 12:31:34.46 INFO ==> postgresql.conf file not detected. Generating it... postgresql 12:31:34.47 INFO ==> pg_hba.conf file not detected. Generating it... postgresql 12:31:35.67 INFO ==> Starting PostgreSQL in background... postgresql 12:31:36.14 INFO ==> Creating user tsdbu postgresql 12:31:36.15 INFO ==> Grating access to "tsdbu" to the database "tsdbu" postgresql 12:31:36.16 INFO ==> Configuring replication parameters postgresql 12:31:36.18 INFO ==> Configuring fsync postgresql 12:31:36.18 INFO ==> Loading custom scripts... postgresql 12:31:36.19 INFO ==> Loading user's custom files from /docker-entrypoint-initdb.d ... postgresql 12:31:36.19 INFO ==> Starting PostgreSQL in background... ERROR: permission denied to create extension "timescaledb" HINT: Must be superuser to create this extension. postgresql 12:31:36.20 INFO ==> Stopping PostgreSQL...