Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

First attempt at new install #27

Merged
merged 7 commits into from
Mar 27, 2016
Merged

Conversation

micke2k
Copy link
Contributor

@micke2k micke2k commented Mar 24, 2016

  1. Added check for RRD 1.5
  2. Backported dependencies check
  3. Backported template installer
  4. Added theme selection

Tested and working with a new installation on Linux. Backported a template for testing as well -> Disk IO.

I will test Upgrade and Windows installation, as well as clean it up and add some extras.

1. Added check for RRD 1.5
2. Backported dependencies check
3. Backported template installer
4. Added theme selection

Tested and working with new installation on Linux. Backported a template for testing as well -> Disk IO.

I will test the Upgrade and Windows installation as well as clean it up and add some extras.
Tables were not created because primary key was: KEY PRIMARY 'id' Instead of PRIMARY KEY 'id

Saw some weird behaviour when switching between 0.8.8g and 1.0, this was solved when browser was closed between upgrades.

Removed top and bottom header

Issues:
1. the new way of creating tables with db_create_table doesnt give any log output, if it fails it fails silently.
2. after upgrade user are sent to login page but cant login with admin/admin, realm problem?
This fixed the login issue.

Now upgraded database and new installed database is exactly equal, no difference.

Still need to fix/test:
1. output for array sql log
2. test windows
3. cleanup, import more features, make it look better

Works:
Linux New install
Upgrade from 0.8.8g
@@ -365,8 +364,8 @@ function upgrade_to_1_0_0() {
// Add secpass fields
db_install_add_column ('1.0', 'user_auth', array('name' => 'lastchange', 'type' => 'int(12)', 'NULL' => false, 'default' => '-1'));
db_install_add_column ('1.0', 'user_auth', array('name' => 'lastlogin', 'type' => 'int(12)', 'NULL' => false, 'default' => '-1'));
db_install_add_column ('1.0', 'user_auth', array('name' => 'password_history', 'type' => 'varchar(4096)', 'NULL' => false, 'default' => ''));
db_install_add_column ('1.0', 'user_auth', array('name' => 'locked', 'type' => 'varchar(3)', 'NULL' => false, 'default' => ''));
db_install_add_column ('1.0', 'user_auth', array('name' => 'password_history', 'type' => 'INT(12)', 'NULL' => false, 'default' => '-1'));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mistake here. should remain varchar(4096). avoid use of 'text' fields at all cost.

@cigamit
Copy link
Member

cigamit commented Mar 26, 2016

I've made some comments. If you can update, that would be good.

@micke2k
Copy link
Contributor Author

micke2k commented Mar 26, 2016

Ill fix it. The values comes from cacti.sql, ill fix that one too. Thanks for the comments!

Edit: i might have made som mistakes, anyway ill look into it.

Change cacti.sql datetime to timestamp, good idea?
@cigamit
Copy link
Member

cigamit commented Mar 26, 2016

before merging, let's do those other two changes.

@micke2k
Copy link
Contributor Author

micke2k commented Mar 26, 2016

yup agreed

ill fix them

Edit: Saw you comment on the closed pull now, im on it

Added back index parent. Although i don't think it should be used since it is not in cacti.sql, see attached screenshot. cacti2 is the upgraded, and cacti is new installation.
@micke2k
Copy link
Contributor Author

micke2k commented Mar 27, 2016

sqlcompare

@cigamit
Copy link
Member

cigamit commented Mar 27, 2016

yea, the index should also be on the cacti.sql file. I'll merge this. add the parent index to the cacti.sql in a separate pull.

@cigamit cigamit merged commit df7407e into Cacti:develop Mar 27, 2016
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants