Error logging into test.

62 views
Skip to first unread message

Anton Angelo

unread,
Jan 2, 2018, 7:11:34 PM1/2/18
to Jason Gush, nz-orcid-hub

Kia ora all, and a happy new year!

 

Logging into test, I get a password error, and the following stack:

 

Anton.

 

Traceback (most recent call last):

  File "/var/www/orcidhub/orcid_hub/failover.py", line 37, in _connect

    return super()._connect(database, encoding=encoding, **kwargs)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 4164, in _connect

    conn = psycopg2.connect(database=database, **kwargs)

  File "/usr/lib64/python3.6/site-packages/psycopg2/__init__.py", line 130, in connect

    conn = _connect(dsn, connection_factory=connection_factory, **kwasync)

psycopg2.OperationalError: could not translate host name "db" to address: Name or service not known

 

 

During handling of the above exception, another exception occurred:

 

Traceback (most recent call last):

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3768, in _create_connection

    return self._connect(self.database, **self.connect_kwargs)

  File "/var/www/orcidhub/orcid_hub/failover.py", line 43, in _connect

   conn = super()._connect(database, encoding=encoding, **kwargs)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 4164, in _connect

    conn = psycopg2.connect(database=database, **kwargs)

  File "/usr/lib64/python3.6/site-packages/psycopg2/__init__.py", line 130, in connect

    conn = _connect(dsn, connection_factory=connection_factory, **kwasync)

psycopg2.OperationalError: FATAL:  password authentication failed for user "orcidhub"

 

 

During handling of the above exception, another exception occurred:

 

Traceback (most recent call last):

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3828, in execute_sql

    cursor = self.get_cursor()

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3774, in get_cursor

    return self.get_conn().cursor()

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3763, in get_conn

    self.connect()

  File "/var/www/orcidhub/orcid_hub/failover.py", line 28, in connect

    super().connect()

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3738, in connect

    self._local.conn = self._create_connection()

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3768, in _create_connection

    return self._connect(self.database, **self.connect_kwargs)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3656, in __exit__

    reraise(new_type, new_type(*exc_args), traceback)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 135, in reraise

    raise value.with_traceback(tb)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3768, in _create_connection

    return self._connect(self.database, **self.connect_kwargs)

  File "/var/www/orcidhub/orcid_hub/failover.py", line 43, in _connect

    conn = super()._connect(database, encoding=encoding, **kwargs)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 4164, in _connect

    conn = psycopg2.connect(database=database, **kwargs)

  File "/usr/lib64/python3.6/site-packages/psycopg2/__init__.py", line 130, in connect

    conn = _connect(dsn, connection_factory=connection_factory, **kwasync)

peewee.OperationalError: FATAL:  password authentication failed for user "orcidhub"

 

 

During handling of the above exception, another exception occurred:

 

Traceback (most recent call last):

  File "/var/www/orcidhub/orcid_hub/failover.py", line 55, in execute_sql

    return super().execute_sql(sql, params=params, require_commit=require_commit)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3837, in execute_sql

    self.commit()

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3656, in __exit__

    reraise(new_type, new_type(*exc_args), traceback)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 135, in reraise

    raise value.with_traceback(tb)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3828, in execute_sql

    cursor = self.get_cursor()

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3774, in get_cursor

    return self.get_conn().cursor()

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3763, in get_conn

    self.connect()

  File "/var/www/orcidhub/orcid_hub/failover.py", line 28, in connect

    super().connect()

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3738, in connect

    self._local.conn = self._create_connection()

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3768, in _create_connection

    return self._connect(self.database, **self.connect_kwargs)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3656, in __exit__

    reraise(new_type, new_type(*exc_args), traceback)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 135, in reraise

    raise value.with_traceback(tb)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3768, in _create_connection

    return self._connect(self.database, **self.connect_kwargs)

  File "/var/www/orcidhub/orcid_hub/failover.py", line 43, in _connect

    conn = super()._connect(database, encoding=encoding, **kwargs)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 4164, in _connect

    conn = psycopg2.connect(database=database, **kwargs)

  File "/usr/lib64/python3.6/site-packages/psycopg2/__init__.py", line 130, in connect

    conn = _connect(dsn, connection_factory=connection_factory, **kwasync)

peewee.OperationalError: FATAL:  password authentication failed for user "orcidhub"

 

 

During handling of the above exception, another exception occurred:

 

Traceback (most recent call last):

  File "/var/www/orcidhub/orcid_hub/failover.py", line 37, in _connect

    return super()._connect(database, encoding=encoding, **kwargs)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 4164, in _connect

    conn = psycopg2.connect(database=database, **kwargs)

  File "/usr/lib64/python3.6/site-packages/psycopg2/__init__.py", line 130, in connect

    conn = _connect(dsn, connection_factory=connection_factory, **kwasync)

psycopg2.OperationalError: could not translate host name "db" to address: Name or service not known

 

 

During handling of the above exception, another exception occurred:

 

Traceback (most recent call last):

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3768, in _create_connection

    return self._connect(self.database, **self.connect_kwargs)

  File "/var/www/orcidhub/orcid_hub/failover.py", line 43, in _connect

    conn = super()._connect(database, encoding=encoding, **kwargs)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 4164, in _connect

    conn = psycopg2.connect(database=database, **kwargs)

  File "/usr/lib64/python3.6/site-packages/psycopg2/__init__.py", line 130, in connect

    conn = _connect(dsn, connection_factory=connection_factory, **kwasync)

psycopg2.OperationalError: FATAL:  password authentication failed for user "orcidhub"

 

 

During handling of the above exception, another exception occurred:

 

Traceback (most recent call last):

  File "/usr/lib/python3.6/site-packages/flask/app.py", line 1982, in wsgi_app

    response = self.full_dispatch_request()

  File "/usr/lib/python3.6/site-packages/flask/app.py", line 1614, in full_dispatch_request

    rv = self.handle_user_exception(e)

  File "/usr/lib/python3.6/site-packages/flask/app.py", line 1517, in handle_user_exception

    reraise(exc_type, exc_value, tb)

  File "/usr/lib/python3.6/site-packages/flask/_compat.py", line 33, in reraise

    raise value

  File "/usr/lib/python3.6/site-packages/flask/app.py", line 1612, in full_dispatch_request

    rv = self.dispatch_request()

  File "/usr/lib/python3.6/site-packages/flask/app.py", line 1598, in dispatch_request

    return self.view_functions[rule.endpoint](**req.view_args)

  File "/var/www/orcidhub/orcid_hub/authcontroller.py", line 196, in handle_login

    | (Organisation.name == shib_org_name))

  File "/usr/lib/python3.6/site-packages/peewee.py", line 4988, in get

    return sq.get()

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3220, in get

    return next(clone.execute())

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3274, in execute

    self._qr = ResultWrapper(model_class, self._execute(), query_meta)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 2939, in _execute

    return self.database.execute_sql(sql, params, self.require_commit)

  File "/var/www/orcidhub/orcid_hub/failover.py", line 57, in execute_sql

    self.connect()

  File "/var/www/orcidhub/orcid_hub/failover.py", line 28, in connect

    super().connect()

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3738, in connect

    self._local.conn = self._create_connection()

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3768, in _create_connection

    return self._connect(self.database, **self.connect_kwargs)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3656, in __exit__

    reraise(new_type, new_type(*exc_args), traceback)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 135, in reraise

    raise value.with_traceback(tb)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 3768, in _create_connection

    return self._connect(self.database, **self.connect_kwargs)

  File "/var/www/orcidhub/orcid_hub/failover.py", line 43, in _connect

    conn = super()._connect(database, encoding=encoding, **kwargs)

  File "/usr/lib/python3.6/site-packages/peewee.py", line 4164, in _connect

    conn = psycopg2.connect(database=database, **kwargs)

  File "/usr/lib64/python3.6/site-packages/psycopg2/__init__.py", line 130, in connect

    conn = _connect(dsn, connection_factory=connection_factory, **kwasync)

peewee.OperationalError: FATAL:  password authentication failed for user "orcidhub"

 

 

From: nz-orci...@aucklanduni.ac.nz [mailto:nz-orci...@aucklanduni.ac.nz] On Behalf Of Jason Gush
Sent: Sunday, 31 December 2017 3:34 p.m.
To: nz-orcid-hub <nz-orci...@aucklanduni.ac.nz>
Subject: Closing out 2017 with V3 on both test and production - custom templates and writing funding

 

Hello all and sincere thanks for those who've stuck with us throughout the year,

 

If you've recently been by either the test or production Hubs you'll have seen that two new features are live: customising the Hub's email messages; and the ability to upload funding tasks.

 

Although these features are available now, proper documentation and guidance will be following in the new year.

 

However, if you'd like to try them out on test, to customise the mail you'll find a small set of changes in the menu bar.  

 

Customising your email messages

 

"Your organisation" has been replaced with "Settings", and underneath the new "Settings" dropdown you can now find:

 

  • "Your organisation"
  • "Logo", and
  • "Email template"

 

Any jpg or png can be uploaded by selecting "Logo" and using the options on the resulting page.  If you're prepared to put some effort into altering your email template then the options are very open, but for the simplest substitution please start with a picture that's 127 pixels high as it'll will drop right into the space occupied by the default Society logo.

 

Next from the "Email template" page you are given the option of toggling the "Email template enabled" option.

 

Once enabled, a blank document is opened where you can enter the html for the mail that the Hub sends on your behalf.

 

As that might be a little daunting, to start with (and perhaps doing all that you require) press the "Pre-fill" button to copy the default html for the Hub's messages and edit from there.

 

There are three merged fields that may be of use:

  • {EMAIL} : Recipient email address
  • {LOGO} : Organisation logo
  • {MESSAGE} : Core message that will be sent to the recipient

The {MESSAGE} field is customised for each type of mail that the Hub sends, e.g., invitation, affiliation invite, funding invite, reminders and revoked permission repeat request.

If you don't include this in the template the Hub will send the same message in all instances.

 

When you think you've got something that works, pressing "Send" will email you a test message with the current template.  If that's what you want, press save and any subsequent messages will be style with your new template.

 

If you ever want to go back to the default Society-style, just toggle off "Email template enabled".

 

Writing funding items

 

Writing funding works very similarly to affiliations, i.e., a funding file containing the email or ORCID iD of researcher/contributors and funding data is uploaded to the Hub and the Hub either sends the researcher/contributor invitations or uses the access token it already has to write the information to their ORCID records.

 

The main difference is that while affiliation files can be either csv or tsv, for funding the file must be in either json or YAML formats.  The Hub accepts these files structured in the same way as the ORCID 2.0/2.1 schema, and the contributors block is where each individual to be invited/written is specified.

 

If that's confusing, don't worry we'll be going into this in detail early next year.

 

That's us for 2017, we hope you've found the Hub either useful or with the solid promise of being of use to you.

 

We know that we've got to do some work on the user interface for naiive Tuakiri-member visitors, and have work on the Hub's API and writing works sketched out.

 

Best wishes,

Jason, Jilll and the UOA dev team.

 

 

 

--
You received this message because you are subscribed to the Google Groups "nz-orcid-hub" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nz-orcid-hub-...@aucklanduni.ac.nz.
To post to this group, send email to nz-orci...@aucklanduni.ac.nz.
To view this discussion on the web, visit https://groups.google.com/a/aucklanduni.ac.nz/d/msgid/nz-orcid-hub-gg/6b6f1e0a-76e2-44fc-b35b-d542afd22377%40aucklanduni.ac.nz.

Radomirs Cirskis

unread,
Jan 3, 2018, 3:29:07 AM1/3/18
to Anton Angelo, Jason Gush, nz-orcid-hub
Hi Anton!
hank you for bringing this to our attention. Further inspection showed that the DB size exceeded the allotted storage space to the UAT server.
It is fixed now and we will make sure that extra storage gets assigned so that we won't run in this issue again.
Happy New Year!
Rad

To unsubscribe from this group and stop receiving emails from it, send an email to nz-orcid-hub-gg+unsubscribe@aucklanduni.ac.nz.
To post to this group, send email to nz-orcid-hub-gg@aucklanduni.ac.nz.

--
You received this message because you are subscribed to the Google Groups "nz-orcid-hub" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nz-orcid-hub-gg+unsubscribe@aucklanduni.ac.nz.
To post to this group, send email to nz-orcid-hub-gg@aucklanduni.ac.nz.
To view this discussion on the web, visit https://groups.google.com/a/aucklanduni.ac.nz/d/msgid/nz-orcid-hub-gg/8CFBD20EF3B10B4D972B129D5CB63963BDC2C8BA%40UCEXMBX01-D.canterbury.ac.nz.

Anton Angelo

unread,
Jan 3, 2018, 2:06:03 PM1/3/18
to Radomirs Cirskis, Jason Gush, nz-orcid-hub
As ever, totally on top of it! Thanks all, and happy new year.

Anton




To unsubscribe from this group and stop receiving emails from it, send an email to nz-orcid-hub-...@aucklanduni.ac.nz.
To post to this group, send email to nz-orci...@aucklanduni.ac.nz.
To view this discussion on the web, visit https://groups.google.com/a/aucklanduni.ac.nz/d/msgid/nz-orcid-hub-gg/CADmPgQN55%2BdTkaLtPzf0vzk4x7LcBHfgCh5MM1RTgRL4avs-0g%40mail.gmail.com.

This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.

Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.

Reply all
Reply to author
Forward
0 new messages