Re: how to deploy rocket-chat in openshift 3.11

2020-05-29 Thread Ben Holmes 
I've always used these templates to deploy RocketChat with a proper MongoDB
replicaset as a statefulset.

https://github.com/redhat-cop/pbl-rocketchat

The template itself is fairly old, so double check what images it pulls for
RocketChat and MongoDB. But it should get you up and running.

Ben



On Tue, 26 May 2020 at 15:10, Marcello Lorenzi  wrote:

> Hi Aida,
> if you installed rocketchat with a standalone mongodb instance, you have
> to migrate it to a replicaset with one node configured. On our
> environment we fixed this issue in this way.
>
> Marcello
>
> On Tue, May 26, 2020 at 4:06 PM SUBASHI Aida  wrote:
>
>> Dear all,
>>
>> we are trying to deploy rocketchat in openshift 3.11
>>
>>
>> https://github.com/RocketChat/Rocket.Chat/blob/develop/.openshift/rocket-chat-ephemeral.json
>> https://github.com/RocketChat/Rocket.Chat/blob/develop/.openshift/rocket-chat-ephemeral.json
>>
>> rocketchat version is  3.2 and mongodb is  3.6.3
>>
>>
>> we are facing below error internally rocketchat pod.
>> Please can someone provide a hit or suggestion how to resolve this issue ?
>>
>> LOGS of rocketchat pod:
>>
>> Setting default file store to GridFS
>> {"line":"120","file":"migrations.js","message":"Migrations: Not
>> migrating, already at version
>> 188","time":{"$date":1590498456786},"level":"info"}
>> ufs: temp directory created at "/tmp/ufs"
>> Loaded the Apps Framework and loaded a total of 0 Apps!
>> Updating process.env.MAIL_URL
>> Using GridFS for custom sounds storage
>> Using GridFS for custom emoji storage
>> Browserslist: caniuse-lite is outdated. Please run next command `npm
>> update`
>> ➔ server.js:204 System ➔ error
>> ➔
>> +---+
>> ➔ |SERVER
>> ERROR   |
>> ➔
>> +---+
>> ➔
>> |
>> |
>> ➔ |  Rocket.Chat Version:
>> 3.2.0-rc.2  |
>> ➔ |   NodeJS Version: 12.16.1 -
>> x64   |
>> ➔ |  MongoDB Version:
>> 3.6.3   |
>> ➔ |   MongoDB Engine:
>> unknown |
>> ➔ | Platform:
>> linux   |
>> ➔ | Process Port:
>> 3000|
>> ➔ | Site URL: http://localhost:3000
>> |
>> ➔ | ReplicaSet OpLog:
>> Disabled|
>> ➔ |  Commit Hash:
>> 0520a3d480  |
>> ➔ |Commit Branch:
>> HEAD|
>> ➔
>> |
>> |
>> ➔ |  OPLOG / REPLICASET IS REQUIRED TO RUN ROCKET.CHAT, MORE INFORMATION
>> AT:  |
>> ➔ |  https://go.rocket.chat/i/oplog-required
>> |
>> ➔
>> |
>> |
>> ➔
>> +---+
>>
>>
>> Thanks and BR
>> Aida
>>
>>
>> ___
>> Aida SUBASHI | DevOps Specialist | Scientific Games International GmbH
>>  | Klitschgasse 2-4, A-1130 Vienna | FN 157284
>> a, HG Wien | (O) +43 1 80100 - 0
>>
>> May be privileged. May be confidential. Please delete if not the
>> addressee.
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>


-- 

BENJAMIN HOLMES

SENIOR Solution ARCHITECT

Red Hat UKI Presales 

bhol...@redhat.comM: 07876-885388


___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: clsut stopped working - certificate problems

2020-03-31 Thread Ben Holmes 
Hi Tim,

Can you verify that the host's clocks are being synced correctly as per
Simon's other suggestion?

Ben

On Tue, 31 Mar 2020 at 16:05, Tim Dudgeon  wrote:

> Hi Simon,
>
> we're run those playbooks and all certs are reported as still being valid.
>
> Tim
>
> On 31/03/2020 15:59, Simon Krenger wrote:
> > Hi Tim,
> >
> > Note that there are multiple sets of certificates, both external and
> > internal. So it would be worth checking the certificates again using
> > the Certificate Expiration Playbooks (see link below). The
> > documentation also has an overview of what can be done to renew
> > certain certificates:
> >
> > - [ Redeploying Certificates ]
> >https://docs.okd.io/3.11/install_config/redeploying_certificates.html
> >
> > Apart from checking all certificates, I'd certainly review the time
> > synchronisation for the whole cluster, as we see the message "x509:
> > certificate has expired or is not yet valid".
> >
> > I hope this helps.
> >
> > Kind regards
> > Simon
> >
> > On Tue, Mar 31, 2020 at 4:33 PM Tim Dudgeon 
> wrote:
> >> One of our OKD 3.11 clusters has suddenly stopped working without any
> >> obvious reason.
> >>
> >> The origin-node service on the nodes does not start (times out).
> >> The master-api pod is running on the master.
> >> The nodes can access the master-api endpoints.
> >>
> >> The logs of the master-api pod look mostly OK other than a huge number
> >> of warnings about certificates that don't really make sense as the
> >> certificates are valid (we use named certificates from let's Encryt and
> >> they were renewed about 2 weeks ago and all appear to be correct.
> >>
> >> Examples of errors from the master-api pod are:
> >>
> >> I0331 12:46:57.065147   1 establishing_controller.go:73] Starting
> >> EstablishingController
> >> I0331 12:46:57.065561   1 logs.go:49] http: TLS handshake error from
> >> 192.168.160.17:58024: EOF
> >> I0331 12:46:57.071932   1 logs.go:49] http: TLS handshake error from
> >> 192.168.160.19:48102: EOF
> >> I0331 12:46:57.072036   1 logs.go:49] http: TLS handshake error from
> >> 192.168.160.19:37178: EOF
> >> I0331 12:46:57.072141   1 logs.go:49] http: TLS handshake error from
> >> 192.168.160.17:58022: EOF
> >>
> >> E0331 12:47:37.855023   1 memcache.go:147] couldn't get resource
> >> list for metrics.k8s.io/v1beta1: the server is currently unable to
> >> handle the request
> >> E0331 12:47:37.856569   1 memcache.go:147] couldn't get resource
> >> list for servicecatalog.k8s.io/v1beta1: the server is currently unable
> >> to handle the request
> >> E0331 12:47:44.115290   1 authentication.go:62] Unable to
> >> authenticate the request due to an error: [x509: certificate has expired
> >> or is not yet valid, x509: certificate
> >>has expired or is not yet valid]
> >> E0331 12:47:44.118976   1 authentication.go:62] Unable to
> >> authenticate the request due to an error: [x509: certificate has expired
> >> or is not yet valid, x509: certificate
> >>has expired or is not yet valid]
> >> E0331 12:47:44.122276   1 authentication.go:62] Unable to
> >> authenticate the request due to an error: [x509: certificate has expired
> >> or is not yet valid, x509: certificate
> >>has expired or is not yet valid]
> >>
> >> Huge number of this second sort.
> >>
> >> Any ideas what is wrong?
> >>
> >>
> >>
> >> ___
> >> users mailing list
> >> users@lists.openshift.redhat.com
> >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
> >
> >
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>

-- 

BENJAMIN HOLMES

SENIOR Solution ARCHITECT

Red Hat UKI Presales 

bhol...@redhat.comM: 07876-885388


___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users