These are chat archives for fossasia/open-event-server

26th
Jul 2018
Mayank Vaidya
@mayank8318
Jul 26 2018 03:27 UTC
@maxlorenz This is the stacktrace -
Traceback (most recent call last):
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/flask/app.py", line 2309, in __call__
    return self.wsgi_app(environ, start_response)
  File "/home/mayank/OpenSource/open-event-server/app/__init__.py", line 67, in __call__
    return self.app(environ, start_response)
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/flask/app.py", line 2295, in wsgi_app
    response = self.handle_exception(e)
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/flask_cors/extension.py", line 161, in wrapped_function
    return cors_after_request(app.make_response(f(*args, **kwargs)))
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/flask_cors/extension.py", line 161, in wrapped_function
    return cors_after_request(app.make_response(f(*args, **kwargs)))
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/flask/app.py", line 1741, in handle_exception
    reraise(exc_type, exc_value, tb)
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/flask/_compat.py", line 35, in reraise
    raise value
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/flask/app.py", line 2292, in wsgi_app
    response = self.full_dispatch_request()
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/flask/app.py", line 1815, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/flask_cors/extension.py", line 161, in wrapped_function
    return cors_after_request(app.make_response(f(*args, **kwargs)))
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/flask_cors/extension.py", line 161, in wrapped_function
    return cors_after_request(app.make_response(f(*args, **kwargs)))
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/flask/app.py", line 1718, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/flask/_compat.py", line 35, in reraise
    raise value
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/flask/app.py", line 1813, in full_dispatch_request
    rv = self.dispatch_request()
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/flask/app.py", line 1799, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/flask/views.py", line 88, in view
    return self.dispatch_request(*args, **kwargs)
  File "/home/mayank/OpenSource/open-event-server/src/flask-rest-jsonapi/flask_rest_jsonapi/resource.py", line 68, in dispatch_request
    response = method(*args, **kwargs)
  File "/home/mayank/OpenSource/open-event-server/app/api/full_text_search/events.py", line 60, in get
    return self.search(args)
  File "/home/mayank/OpenSource/open-event-server/app/api/full_text_search/events.py", line 55, in search
    return [to_dict(r) for r in search.execute()]
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/elasticsearch_dsl/search.py", line 679, in execute
    **self._params
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/elasticsearch/client/utils.py", line 76, in _wrapped
    return func(*args, params=params, **kwargs)
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/elasticsearch/client/__init__.py", line 655, in search
    doc_type, '_search'), params=params, body=body)
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/elasticsearch/transport.py", line 318, in perform_request
    status, headers_response, data = connection.perform_request(method, url, params, body, headers=headers, ignore=ignore, timeout=timeout)
  File "/home/mayank/anaconda3/envs/openevent3/lib/python3.6/site-packages/elasticsearch/connection/http_urllib3.py", line
Mario Behling
@mariobehling
Jul 26 2018 07:56 UTC
Hi, we need help to get the Google Cloud server working again. Yesterday Google limited the usable versions of Nodejs and this resulted in our server failing. The node version has been updated but the server does not work yet. Anyone who could help? @bhaveshAn Do you have experience?
Atharva Padhye
@starlord1311
Jul 26 2018 08:22 UTC
can someone check fossasia/open-event-server#5174 and tell me where i went wrong?
Screenshot from 2018-07-26 13-54-32.png
this is how my setup is @srv-twry is it right?
Saurav Tiwary
@srv-twry
Jul 26 2018 08:31 UTC
Yeah, looks fine.
Atharva Padhye
@starlord1311
Jul 26 2018 08:33 UTC
Screenshot from 2018-07-26 14-02-58.png
@srv-twry what to do now. postman ends up showing error 404
Saurav Tiwary
@srv-twry
Jul 26 2018 08:35 UTC
What do you want to do ?
Atharva Padhye
@starlord1311
Jul 26 2018 08:37 UTC
try the endpoint using postman @srv-twry
what @mayank8318 said in fossasia/open-event-server#5152
can you help?
Saurav Tiwary
@srv-twry
Jul 26 2018 08:50 UTC
Enter the right endpoint in the URL then. That's not the right endpoint.
Atharva Padhye
@starlord1311
Jul 26 2018 10:33 UTC
how to put endpoint url ? @srv-twry
Saurav Tiwary
@srv-twry
Jul 26 2018 10:37 UTC
Umm, search for the endpoint url in the api docs and add it in the Postman URL.
Bhavesh Anand
@bhaveshAn
Jul 26 2018 11:28 UTC
@mariobehling No I don't have a working experience in it. But since its not from scratch so I think I can still look into that !
Mario Behling
@mariobehling
Jul 26 2018 11:45 UTC
@bhaveshAn Would be great. Please have a look at the cloud console
Bhavesh Anand
@bhaveshAn
Jul 26 2018 11:45 UTC
Okay !
Mario Behling
@mariobehling
Jul 26 2018 12:22 UTC
@Kreijstal @bhaveshAn @maxlorenz @srv-twry What are your ideas to bring the standard event server up and running?
Kreijstal
@Kreijstal
Jul 26 2018 16:36 UTC
the thing is the pod database is down
Kreijstal
@Kreijstal
Jul 26 2018 18:11 UTC
@niranjan94 Thanks for fixing the eventyay.
Niranjan Rajendran
@niranjan94
Jul 26 2018 18:11 UTC
Hi ... Just got eventyay.com back up. Seems someone might have accidentally deleted the postgres pod.
Bringing it back up is pretty straightforward. Take the config from https://github.com/fossasia/open-event-legacy/blob/development/kubernetes/yamls/postgres/postgres-pod.yml .. (be sure to change the image to postgres:9.6 as the existing data is compatible with that version)
Then you use kubectl apply -f <path-to-file>
Kreijstal
@Kreijstal
Jul 26 2018 18:11 UTC
How did you do it? I did not know how to do it and did a lot of research, but I am not very familiar.
Niranjan Rajendran
@niranjan94
Jul 26 2018 18:12 UTC
(Of course, you'll have to setup and configure gcloud cli and kubectl. docs are available in the google cloud docs and kubernetes docs)
Kreijstal
@Kreijstal
Jul 26 2018 18:12 UTC
what do you mean setup and configure
Niranjan Rajendran
@niranjan94
Jul 26 2018 18:12 UTC
If you want to access the kubernetes dashboard, you can run kubectl proxy and navigate to https://127.0.0.1:8001/ui

what do you mean setup and configure

You'll have to download and install the CLI client on your machine. And also, give it your credentials ...

Mario Behling
@mariobehling
Jul 26 2018 18:13 UTC
@niranjan94 Thanks a lot!
No problem @mariobehling
Kreijstal
@Kreijstal
Jul 26 2018 18:17 UTC
oh I have gcloud and kubectl that was not the problem
the problem is that I wanted to find the location of the database, where was the data stored on the databases
and I wanted to know if this was somehow stored on the gcloud server
Niranjan Rajendran
@niranjan94
Jul 26 2018 18:19 UTC
well ... kubectl get all would give you all the resources running. You compare them with the config files at https://github.com/fossasia/open-event-legacy/tree/development/kubernetes/yamls to ensure all are running ...
You can also view the yams and stuff on the dashboard
And if you notice https://github.com/fossasia/open-event-legacy/blob/development/kubernetes/yamls/postgres/postgres-pod.yml#L30, you can see that we are using GCE persistent disk to store the PG data. So, for that you can check the google cloud console to ensure that disk is present. (It'll be under compute section if I'm right)
Kreijstal
@Kreijstal
Jul 26 2018 18:20 UTC
the postgres pod is not managed by a controller, right
that means when it's updated it won't be restarted
take a look
Niranjan Rajendran
@niranjan94
Jul 26 2018 18:23 UTC
Ah okay. i didn't know someone updated the node.
Yes. it shoudl be managed by a controller. should have been a deployment instead of a pod. Like https://github.com/fossasia/open-event-server/blob/development/kubernetes/yamls/postgres/deployment.yml
But the legacy setup wasn't really according to the best practices.
Kreijstal
@Kreijstal
Jul 26 2018 18:25 UTC
Is it possible for you to update the version?
or wrap it inside a controller
Niranjan Rajendran
@niranjan94
Jul 26 2018 18:26 UTC
Node version ? I'd rather we don't update for the vintage cluster. It wasn't exactly configured in a very reliable manner. (I take the blame for that :sweat_smile: )

or wrap it inside a controller

That, I can

Will do.
Kreijstal
@Kreijstal
Jul 26 2018 18:27 UTC
thankss