!MNkZeDktHEshWITStt:matrix.org

OpenLMIS-Help

67 Members
23 Servers

Load older messages


SenderMessageTime
26 Dec 2020
@harry:ggc-project.de@harry:ggc-project.de left the room.20:56:52
27 Dec 2020
@kamilla:fairydust.space@kamilla:fairydust.space 17:32:38
@kamilla:fairydust.space@kamilla:fairydust.space left the room.17:56:25
28 Dec 2020
@dave:halogen.city@dave:halogen.city 11:31:50
@ringo:matrixim.cc@ringo:matrixim.cc left the room.12:54:42
@dave:halogen.city@dave:halogen.city left the room.14:40:51
@richard:perthchat.org@richard:perthchat.org left the room.18:03:30
4 Jan 2021
@_slack_openlmis_U01JMUKSZ88:matrix.orgJack Bolles joined the room.12:14:21
@_slack_openlmis_U01JMUKSZ88:matrix.orgJack Bolles changed their display name from _slack_openlmis_U01JMUKSZ88 to Jack Bolles.12:34:58
@_slack_openlmis_U01JMUKSZ88:matrix.orgJack Bolles set a profile picture.12:34:59
7 Jan 2021
@jeremy:nitro.chatjeremy 00:13:18
12 Jan 2021
@jair:hope.net@jair:hope.net left the room.17:56:06
13 Jan 2021
@_slack_openlmis_U01EHHKQD8Q:matrix.orgelly makubaScreenshot from 2021-01-13 09-33-30.png
Download Screenshot from 2021-01-13 09-33-30.png
06:43:08
@_slack_openlmis_U01EHHKQD8Q:matrix.orgelly makuba @room has anybody experienced the error logs attached when starting up an openlmis-distro? how did you fix it? 06:43:08
@_slack_openlmis_U01EHHKQD8Q:matrix.orgelly makuba (edited) ... logs attached? how ... => ... logs attached when starting up an openlmis-distro? how ... 06:44:08
@_slack_openlmis_UKPHYGSR0:matrix.orgjjakubowski changed their profile picture.08:54:57
@_slack_openlmis_UKPHYGSR0:matrix.orgjjakubowski
In reply to@_slack_openlmis_U01EHHKQD8Q:matrix.org
@room has anybody experienced the error logs attached when starting up an openlmis-distro? how did you fix it?
Hi, it's an issue with PostgreSQL, increasing max_connections value should fix that issue. You can find it on database container on path
/var/lib/docker/volumes/postgresql.conf
Try to add at the bottom of this file those variables:
max_connections = 200
shared_buffers = 512MB
08:55:01
@_slack_openlmis_U01EHHKQD8Q:matrix.orgelly makuba
In reply to@_slack_openlmis_UKPHYGSR0:matrix.org
Hi, it's an issue with PostgreSQL, increasing max_connections value should fix that issue. You can find it on database container on path
/var/lib/docker/volumes/postgresql.conf
Try to add at the bottom of this file those variables:
max_connections = 200
shared_buffers = 512MB
Hi jjakubowski I cannot find postgresql.conf in path /var/lib/docker/volumes - there is one in the postgresql container in /var/lib/postgresql/data/postgresql.conf but is being overriden when i stop and start the distro.
10:08:30
@_slack_openlmis_UKPHYGSR0:matrix.orgjjakubowski
In reply to@_slack_openlmis_U01EHHKQD8Q:matrix.org
Hi jjakubowski I cannot find postgresql.conf in path /var/lib/docker/volumes - there is one in the postgresql container in /var/lib/postgresql/data/postgresql.conf but is being overriden when i stop and start the distro.
Yes, I meant that file. If you are using docker-compose down -v to stop the distro you are deleting all of the docker volumes. If you want to keep it, just use docker-compose down without -v . In this case this file should be kept.
10:14:32
@_slack_openlmis_U01EHHKQD8Q:matrix.orgelly makuba
In reply to@_slack_openlmis_UKPHYGSR0:matrix.org
Yes, I meant that file. If you are using docker-compose down -v to stop the distro you are deleting all of the docker volumes. If you want to keep it, just use docker-compose down without -v . In this case this file should be kept.
Same problem with "docker-compose down" command, it's still being overriden.
10:54:21
@_slack_openlmis_UKPHYGSR0:matrix.orgjjakubowski
In reply to@_slack_openlmis_U01EHHKQD8Q:matrix.org
Same problem with "docker-compose down" command, it's still being overriden.
Hmm, that's weird. How is your settings.env file looks like? Try with profiler set like this:
############################################################################################################
# Profile:  use one of the desired deployment profiles below by uncommenting one (and only one) line below
############################################################################################################
## Production - doesn't wipe the database - WARNING unless this profile is active, your database is wiped
## every time the application starts
spring_profiles_active=production
## Demo data - the default, loads a basic set of demo data on startup
## Refresh DB - refreshes some necessary DB tables as services start, outside of Hibernate management
## (notably referencedata.right_assignments).
# spring_profiles_active=demo-data,refresh-db
# spring_profiles_active = refresh-db
## Performance testing - optionally load more junk data on top of the demo data for performance testing purposes
# spring_profiles_active=demo-data,performance-data,refresh-db
############################################################################################################
11:02:32
@_slack_openlmis_U01EHHKQD8Q:matrix.orgelly makuba
In reply to@_slack_openlmis_UKPHYGSR0:matrix.org
Hmm, that's weird. How is your settings.env file looks like? Try with profiler set like this:
############################################################################################################
# Profile:  use one of the desired deployment profiles below by uncommenting one (and only one) line below
############################################################################################################
## Production - doesn't wipe the database - WARNING unless this profile is active, your database is wiped
## every time the application starts
spring_profiles_active=production
## Demo data - the default, loads a basic set of demo data on startup
## Refresh DB - refreshes some necessary DB tables as services start, outside of Hibernate management
## (notably referencedata.right_assignments).
# spring_profiles_active=demo-data,refresh-db
# spring_profiles_active = refresh-db
## Performance testing - optionally load more junk data on top of the demo data for performance testing purposes
# spring_profiles_active=demo-data,performance-data,refresh-db
############################################################################################################
Still being overridden with this profiler settings.
11:21:22
@_slack_openlmis_UKPHYGSR0:matrix.orgjjakubowski
In reply to@_slack_openlmis_U01EHHKQD8Q:matrix.org
Still being overridden with this profiler settings.
Okay, so it seems that you'll have to override this file every startup. The best way to do it is firstly start only DataBase with command docker-compose up -d db then override this postgresql.conf file, after that use docker-compose up -d as usual.
11:29:39
@_slack_openlmis_U01EHHKQD8Q:matrix.orgelly makuba
In reply to@_slack_openlmis_UKPHYGSR0:matrix.org
Okay, so it seems that you'll have to override this file every startup. The best way to do it is firstly start only DataBase with command docker-compose up -d db then override this postgresql.conf file, after that use docker-compose up -d as usual.
okay
11:38:04
@_slack_openlmis_U03QATSPZ:matrix.orgjoshzamor
In reply to@_slack_openlmis_U01EHHKQD8Q:matrix.org
okay
jjakubowski: you shouldn't need to do this though right? If you use the bundled postgres, it has a connection limit increased doesn't it?
18:46:00
@_slack_openlmis_UKPHYGSR0:matrix.orgjjakubowski
In reply to@_slack_openlmis_U03QATSPZ:matrix.org
jjakubowski: you shouldn't need to do this though right? If you use the bundled postgres, it has a connection limit increased doesn't it?
joshzamor I'm not sure how it's done in Core, but I had a similar issue in selv-distro and those steps were the fastest workaround to start selv-distro locally. In case removed docker PostgreSQL volume, in SELV there is an instruction to increase this value manually: https://github.com/villagereach/selv-v3-deployment#volume-initialization
19:22:34
@_slack_openlmis_U03QATSPZ:matrix.orgjoshzamor
In reply to@_slack_openlmis_UKPHYGSR0:matrix.org
joshzamor I'm not sure how it's done in Core, but I had a similar issue in selv-distro and those steps were the fastest workaround to start selv-distro locally. In case removed docker PostgreSQL volume, in SELV there is an instruction to increase this value manually: https://github.com/villagereach/selv-v3-deployment#volume-initialization
Something must be missing there, /var/lib/docker/volumes doesn't specify which volume (and it's a better practice to use docker cp for this). Moreover though, for a non-production deployment, you should just be able to use the bundled postgres. That's odd and it works here.
19:39:04
@_slack_openlmis_U03QATSPZ:matrix.orgjoshzamor
In reply to@_slack_openlmis_U03QATSPZ:matrix.org
Something must be missing there, /var/lib/docker/volumes doesn't specify which volume (and it's a better practice to use docker cp for this). Moreover though, for a non-production deployment, you should just be able to use the bundled postgres. That's odd and it works here.
elly makuba could you post the full log (not a screenshot)? And also the results of docker system info . That'll give us more information.
19:40:01
20 Jan 2021
@_slack_openlmis_U03QATSPZ:matrix.orgjoshzamor Does anyone know what "uat-test-env-elb" is for? It has no associated instances. Should it have been deleted? 22:36:17
21 Jan 2021
@_slack_openlmis_U03QATSPZ:matrix.orgjoshzamor Also, is uat2.openlmis.org being used? I don't see how as the DNS entry doesn't point to the ELB. 00:04:28

There are no newer messages yet.


Back to Room List