yeah but i wont change anything if it’s causing problem my client need there email so i will wait till @CyberPanel fix the thingy!
the error with migrate.py is
[root@chamanweb CyberCP]# /usr/local/CyberCP/bin/python manage.py migrate System check identified some issues:
WARNINGS:
?: (mysql.W002) MySQL Strict Mode is not set for database connection ‘default’
HINT: MySQL’s Strict Mode fixes many data integrity problems in MySQL, s uch as data truncation upon insertion, by escalating warnings into errors. It is strongly recommended you activate it. See: https://docs.djangoproject.com/en/1. 11/ref/databases/#mysql-sql-mode
?: (mysql.W002) MySQL Strict Mode is not set for database connection ‘rootdb’
HINT: MySQL’s Strict Mode fixes many data integrity problems in MySQL, s uch as data truncation upon insertion, by escalating warnings into errors. It is strongly recommended you activate it. See: https://docs.djangoproject.com/en/1. 11/ref/databases/#mysql-sql-mode
Operations to perform:
Apply all migrations: CLManager, admin, auth, backup, baseTemplate, containeri zation, contenttypes, databases, dns, dockerManager, emailMarketing, emailPremiu m, firewall, ftp, loginSystem, mailServer, managePHP, manageServices, packages, s3Backups, sessions, websiteFunctions
Running migrations:
Applying CLManager.0001_initial…Traceback (most recent call last):
File “manage.py”, line 22, in
execute_from_command_line(sys.argv)
File “/usr/local/CyberCP/lib/python2.7/site-packages/django/core/management/__ init__.py”, line 363, in execute_from_command_line
utility.execute()
File “/usr/local/CyberCP/lib/python2.7/site-packages/django/core/management/__ init__.py”, line 355, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File “/usr/local/CyberCP/lib/python2.7/site-packages/django/core/management/ba se.py”, line 283, in run_from_argv
self.execute(*args, **cmd_options)
File “/usr/local/CyberCP/lib/python2.7/site-packages/django/core/management/ba se.py”, line 330, in execute
output = self.handle(*args, **options)
File “/usr/local/CyberCP/lib/python2.7/site-packages/django/core/management/co mmands/migrate.py”, line 204, in handle
fake_initial=fake_initial,
File “/usr/local/CyberCP/lib/python2.7/site-packages/django/db/migrations/exec utor.py”, line 115, in migrate
state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_i nitial=fake_initial)
File “/usr/local/CyberCP/lib/python2.7/site-packages/django/db/migrations/exec utor.py”, line 145, in migrate_all_forwards
state = self.apply_migration(state, migration, fake=fake, fake_initial=fake initial)
File “/usr/local/CyberCP/lib/python2.7/site-packages/django/db/migrations/exec utor.py”, line 244, in apply_migration
state = migration.apply(state, schema_editor)
File “/usr/local/CyberCP/lib/python2.7/site-packages/django/db/migrations/migr ation.py”, line 129, in apply
operation.database_forwards(self.app_label, schema_editor, old_state, projec t_state)
File “/usr/local/CyberCP/lib/python2.7/site-packages/django/db/migrations/oper ations/models.py”, line 97, in database_forwards
schema_editor.create_model(model)
File “/usr/local/CyberCP/lib/python2.7/site-packages/django/db/backends/base/s chema.py”, line 302, in create_model
self.execute(sql, params or None)
File “/usr/local/CyberCP/lib/python2.7/site-packages/django/db/backends/base/s chema.py”, line 119, in execute
cursor.execute(sql, params)
File “/usr/local/CyberCP/lib/python2.7/site-packages/django/db/backends/utils. py”, line 65, in execute
return self.cursor.execute(sql, params)
File “/usr/local/CyberCP/lib/python2.7/site-packages/django/db/utils.py”, line 94, in exit
six.reraise(dj_exc_type, dj_exc_value, traceback)
File “/usr/local/CyberCP/lib/python2.7/site-packages/django/db/backends/utils. py”, line 63, in execute
return self.cursor.execute(sql)
File “/usr/local/CyberCP/lib/python2.7/site-packages/django/db/backends/mysql/ base.py”, line 101, in execute
return self.cursor.execute(query, args)
File “/usr/lib64/python2.7/site-packages/MySQLdb/cursors.py”, line 205, in exe cute
self.errorhandler(self, exc, value)
File “/usr/lib64/python2.7/site-packages/MySQLdb/connections.py”, line 36, in defaulterrorhandler
raise errorclass, errorvalue
django.db.utils.OperationalError: (1050, “Table ‘CLManager_clpackages’ already e xists”)
[root@chamanweb CyberCP]#
@mmarquette Is there any specific reason that you run migrate manually, we don’t recommend that anymore?
ok so i just need to do the update and that it?
and does that bug have been fixed Authentication failed?
no it just when i do the update after it done, i cannot log anymore in any email that i have create.
i got Authentication failed
I am facing the same:
Internal Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
error with services memcached/redis/postfix not working.
I have raised a ticket but not response yet.
It’s a nice CP but the fact it brakes after every single update is really worrying.