Skip to Content.
Sympa Menu

perfsonar-user - RE: [perfsonar-user] Upgrade from pS 3.4.1

Subject: perfSONAR User Q&A and Other Discussion

List archive

RE: [perfsonar-user] Upgrade from pS 3.4.1


Chronological Thread 
  • From: "Garnizov, Ivan (RRZE)" <>
  • To: Andrew Lake <>
  • Cc: perfsonar-user <>
  • Subject: RE: [perfsonar-user] Upgrade from pS 3.4.1
  • Date: Wed, 16 Mar 2016 14:00:20 +0000
  • Accept-language: en-GB, de-DE, en-US

Thanks Andy,

 

I had been hinted by a colleague, that in fact all these differences, that I see are because of runtime compilation updates to files. This applies to all of them, except for one, which has the secret key.

About the output from the commands you gave as instructions, I have it already posted yesterday (applied it here as an attachment as well).

 

I have played these instructions today as well and the result + output is the same as in the attached file.

 

With regards to “Did you get any errors during the yum update process?

I did not get any error or warning messages even during the reinstallation (see previous email from me), but I see there are many operational/status messages from running these commands manually. Could it be that this output is suppressed during installation time, hence no info during install?

 

Best regards,

Ivan

 

From: Andrew Lake [mailto:]
Sent: Mittwoch, 16. März 2016 14:21
To: Garnizov, Ivan (RRZE)
Cc: perfsonar-user
Subject: RE: [perfsonar-user] Upgrade from pS 3.4.1

 

Hi Ivan,

 

I have no idea what’s going on with your system. Perhaps you have one system pointing at staging and one pointing at the production repo hence the binary differences? In terms of the actual problem what errors are you getting now?

 

Thanks,

Andy

 

 

 

On March 16, 2016 at 7:53:58 AM, Garnizov, Ivan (RRZE) () wrote:

Hi Andy,

 

I have made an additional check. Having 2 systems running latest CentOS one correctly and another broken, I made simple binary comparison for the files related to the esmond package (same version both ends)

esmond.x86_64                       2.0.2-1.el6                       @Internet2

 

The files for the Esmond package on the two servers differ. I have applied the md5 sum file and the results.

My guess is that this should not be the case and the broken server lacks the correct version of files, but then I ran a reinstall of the esmond package.

The reinstallation went without any complaint (applied is the output), yet the system is not working. What can I do about it?

 

 

Best regards,

Ivan

 

 

From: [] On Behalf Of Garnizov, Ivan (RRZE)
Sent: Dienstag, 15. März 2016 16:58
To: Andrew Lake
Cc: perfsonar-user
Subject: RE: [perfsonar-user] Upgrade from pS 3.4.1

 

Hi Andy,

 

I have applied the output in a text file.

 

Thanks for looking into this!

 

Best regards,

Ivan

 

 

 

From: Andrew Lake []
Sent: Montag, 14. März 2016 16:26
To: Garnizov, Ivan (RRZE)
Cc: Antoine Delvaux; perfsonar-user
Subject: Re: [perfsonar-user] Upgrade from pS 3.4.1

 

Hi Ivan,

 

Did you get any errors during the yum update process? These get run by the esmond RPM on update but you can try running them manually to see if that fixes the issue:

 

cd /usr/lib/esmond

source /opt/rh/python27/enable

/opt/rh/python27/root/usr/bin/virtualenv --prompt="(esmond)" .

. bin/activate

python esmond/manage.py migrate --fake-initial

python util/migrate_tastypie_keys.py

 

Thanks,

Andy

 

 

 

On Mon, Mar 14, 2016 at 6:38 AM, Garnizov, Ivan (RRZE) <> wrote:

Hi Antoine,

 

I am upgrading to pS 3.5.1.

 

Installed Packages

esmond.x86_64                       2.0.1-1.el6                       @Internet2

perfsonar-common.noarch                           3.5.1-1             @Internet2

perfsonar-core.noarch                             3.5.1-1             @Internet2

perfsonar-graphs.noarch                           3.5.1-1             @Internet2

perfsonar-lscachedaemon.noarch                    3.5.1-1             @Internet2

perfsonar-lsregistrationdaemon.noarch             3.5.1-1             @Internet2

perfsonar-meshconfig-agent.noarch                 3.5.1-1             @Internet2

perfsonar-meshconfig-jsonbuilder.noarch           3.5.1-1             @Internet2

perfsonar-meshconfig-shared.noarch                3.5.1-1             @Internet2

perfsonar-oppd-bwctl.noarch                       3.5.1-1             @Internet2

perfsonar-oppd-owamp.noarch                       3.5.1-1             @Internet2

perfsonar-oppd-server.noarch                      3.5.1-1             @Internet2

perfsonar-oppd-shared.noarch                      3.5.1-1             @Internet2

perfsonar-regulartesting.noarch                   3.5.1.1-1           @Internet2

perfsonar-testpoint.noarch                        3.5.1-1             @Internet2

perfsonar-toolkit.noarch                          3.5.1-1             @Internet2

perfsonar-toolkit-install.noarch                  3.5.1-1             @Internet2

perfsonar-toolkit-library.noarch                  3.5.1-1             @Internet2

perfsonar-toolkit-ntp.noarch                      3.5.1-1             @Internet2

perfsonar-toolkit-security.noarch                 3.5.1-1             @Internet2

perfsonar-toolkit-servicewatcher.noarch           3.5.1-1             @Internet2

perfsonar-toolkit-sysctl.noarch                   3.5.1-1             @Internet2

perfsonar-toolkit-systemenv.noarch                3.5.1-1             @Internet2

perfsonar-tools.noarch                            3.5.1-1             @Internet2

perfsonar-traceroute-viewer.noarch                3.5.1-1             @Internet2

Available Packages

 

Does that help?

 

Best regards,

Ivan

 

 

 

From: Antoine Delvaux [mailto:]
Sent: Montag, 14. März 2016 10:32
To: Garnizov, Ivan (RRZE)
Cc: perfsonar-user
Subject: Re: [perfsonar-user] Upgrade from pS 3.4.1

 

Hello Ivan,

 

To which version are you upgrading to?  Do you have the exact esmond version numbers of the upgrade?

 

Cheers,

 

Antoine.

 

Le 11 mars 2016 à 17:42, Garnizov, Ivan (RRZE) <> a écrit :

 

Hi guys,

 

Here is the result from my first attempt to run an upgrade from a 3.4.1 instance.

Please provide hints and instructions on how to deal with these errors from Esmond:

 

2016-03-11 18:37:45,413 [ERROR] /usr/lib/esmond/lib/python2.7/site-packages/django/core/handlers/base.py: Internal Server Error: /esmond/perfsonar/archive/

Traceback (most recent call last):

  File "/usr/lib/esmond/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response

    response = wrapped_callback(request, *callback_args, **callback_kwargs)

  File "/usr/lib/esmond/lib/python2.7/site-packages/django/views/decorators/csrf.py", line 58, in wrapped_view

    return view_func(*args, **kwargs)

  File "/usr/lib/esmond/lib/python2.7/site-packages/rest_framework/viewsets.py", line 85, in view

    return self.dispatch(request, *args, **kwargs)

  File "/usr/lib/esmond/lib/python2.7/site-packages/rest_framework/views.py", line 456, in dispatch

    response = self.handle_exception(exc)

  File "/usr/lib/esmond/lib/python2.7/site-packages/rest_framework/views.py", line 444, in dispatch

    self.initial(request, *args, **kwargs)

  File "/usr/lib/esmond/lib/python2.7/site-packages/rest_framework/views.py", line 358, in initial

    self.perform_authentication(request)

  File "/usr/lib/esmond/lib/python2.7/site-packages/rest_framework/views.py", line 296, in perform_authentication

    request.user

  File "/usr/lib/esmond/lib/python2.7/site-packages/rest_framework/request.py", line 489, in __getattribute__

    return super(Request, self).__getattribute__(attr)

  File "/usr/lib/esmond/lib/python2.7/site-packages/rest_framework/request.py", line 264, in user

    self._authenticate()

  File "/usr/lib/esmond/lib/python2.7/site-packages/rest_framework/request.py", line 452, in _authenticate

    user_auth_tuple = authenticator.authenticate(self)

  File "/usr/lib/esmond/lib/python2.7/site-packages/rest_framework/authentication.py", line 173, in authenticate

    return self.authenticate_credentials(auth[1])

  File "/usr/lib/esmond/lib/python2.7/site-packages/rest_framework/authentication.py", line 177, in authenticate_credentials

    token = self.model.objects.select_related('user').get(key=key)

  File "/usr/lib/esmond/lib/python2.7/site-packages/django/db/models/query.py", line 328, in get

    num = len(clone)

  File "/usr/lib/esmond/lib/python2.7/site-packages/django/db/models/query.py", line 144, in __len__

    self._fetch_all()

  File "/usr/lib/esmond/lib/python2.7/site-packages/django/db/models/query.py", line 965, in _fetch_all

    self._result_cache = list(self.iterator())

  File "/usr/lib/esmond/lib/python2.7/site-packages/django/db/models/query.py", line 238, in iterator

    results = compiler.execute_sql()

  File "/usr/lib/esmond/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 840, in execute_sql

    cursor.execute(sql, params)

  File "/usr/lib/esmond/lib/python2.7/site-packages/django/db/backends/utils.py", line 64, in execute

    return self.cursor.execute(sql, params)

  File "/usr/lib/esmond/lib/python2.7/site-packages/django/db/utils.py", line 97, in __exit__

    six.reraise(dj_exc_type, dj_exc_value, traceback)

  File "/usr/lib/esmond/lib/python2.7/site-packages/django/db/backends/utils.py", line 64, in execute

    return self.cursor.execute(sql, params)

ProgrammingError: relation "authtoken_token" does not exist

LINE 1: ...user"."is_active", "auth_user"."date_joined" FROM "authtoken...

 

 

Best regards,

Ivan

 

 


[root@62-40-106-249
~]# cd /usr/lib/esmond
[root@62-40-106-249
esmond]# source /opt/rh/python27/enable
[root@62-40-106-249
esmond]# /opt/rh/python27/root/usr/bin/virtualenv --prompt="(esmond)" .
New python executable in ./bin/python
Installing
Setuptools.............................................................................................done.
Installing
Pip....................................................................................................................................done.
[root@62-40-106-249
esmond]# . bin/activate
(esmond)[root@62-40-106-249
esmond]# python esmond/manage.py migrate --fake-initial
System check identified some issues:

WARNINGS:
api.IfRef.ipAddr: (fields.W900) IPAddressField has been deprecated. Support
for it (except in historical migrations) will be removed in Django 1.9.
HINT: Use GenericIPAddressField instead.
api.LSPOpStatus.dstAddr: (fields.W900) IPAddressField has been deprecated.
Support for it (except in historical migrations) will be removed in Django
1.9.
HINT: Use GenericIPAddressField instead.
api.LSPOpStatus.srcAddr: (fields.W900) IPAddressField has been deprecated.
Support for it (except in historical migrations) will be removed in Django
1.9.
HINT: Use GenericIPAddressField instead.
Operations to perform:
Synchronize unmigrated apps: staticfiles, rest_framework, esmond_admin,
netfields
Apply all migrations: authtoken, sessions, admin, auth, contenttypes, api
Synchronizing apps without migrations:
Creating tables...
Running deferred SQL...
Installing custom SQL...
Running migrations:
Rendering model states... DONE
Applying api.0001_initial...Traceback (most recent call last):
File "esmond/manage.py", line 14, in <module>
execute_from_command_line(sys.argv)
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/core/management/__init__.py",
line 351, in execute_from_command_line
utility.execute()
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/core/management/__init__.py",
line 343, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/core/management/base.py",
line 394, in run_from_argv
self.execute(*args, **cmd_options)
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/core/management/base.py",
line 445, in execute
output = self.handle(*args, **options)
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/core/management/commands/migrate.py",
line 222, in handle
executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial)
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/db/migrations/executor.py",
line 110, in migrate
self.apply_migration(states[migration], migration, fake=fake,
fake_initial=fake_initial)
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/db/migrations/executor.py",
line 148, in apply_migration
state = migration.apply(state, schema_editor)
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/db/migrations/migration.py",
line 115, in apply
operation.database_forwards(self.app_label, schema_editor, old_state,
project_state)
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/db/migrations/operations/models.py",
line 59, in database_forwards
schema_editor.create_model(model)
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/db/backends/base/schema.py",
line 286, in create_model
self.execute(sql, params or None)
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/db/backends/base/schema.py",
line 111, in execute
cursor.execute(sql, params)
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/db/backends/utils.py",
line 64, in execute
return self.cursor.execute(sql, params)
File "/usr/lib/esmond/lib/python2.7/site-packages/django/db/utils.py", line
97, in __exit__
six.reraise(dj_exc_type, dj_exc_value, traceback)
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/db/backends/utils.py",
line 62, in execute
return self.cursor.execute(sql)
django.db.utils.ProgrammingError: relation "alusapref" already exists

(esmond)[root@62-40-106-249
esmond]# python util/migrate_tastypie_keys.py
Traceback (most recent call last):
File "util/migrate_tastypie_keys.py", line 18, in <module>
token = Token.objects.get(user=tp_user)
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/db/models/manager.py",
line 127, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/db/models/query.py", line
328, in get
num = len(clone)
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/db/models/query.py", line
144, in __len__
self._fetch_all()
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/db/models/query.py", line
965, in _fetch_all
self._result_cache = list(self.iterator())
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/db/models/query.py", line
238, in iterator
results = compiler.execute_sql()
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/db/models/sql/compiler.py",
line 840, in execute_sql
cursor.execute(sql, params)
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/db/backends/utils.py",
line 64, in execute
return self.cursor.execute(sql, params)
File "/usr/lib/esmond/lib/python2.7/site-packages/django/db/utils.py", line
97, in __exit__
six.reraise(dj_exc_type, dj_exc_value, traceback)
File
"/usr/lib/esmond/lib/python2.7/site-packages/django/db/backends/utils.py",
line 64, in execute
return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: relation "authtoken_token" does not exist
LINE 1: ...oken"."user_id", "authtoken_token"."created" FROM "authtoken...
^



Archive powered by MHonArc 2.6.16.

Top of Page