Project

General

Profile

Bug #15832

Can't access services tab

Added by Anonymous over 4 years ago. Updated about 3 years ago.

Status:
Closed: Not To Be Fixed
Priority:
Important
Assignee:
William Grzybowski
Category:
OS
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

When I try to access my "Services" tab, this is the error I get. I think it is because I had my UPS configured, then I updated, and now a path doesn't match or a column name changed. See attached images. I don't know the command to stop the UPS service unfortunately. I feel like that might help. Please assist, thanks in advance! :)

2016-06-07_20h37_03.png (18.8 KB) 2016-06-07_20h37_03.png Anonymous, 06/07/2016 05:42 PM
2016-06-07_20h47_10.png (11.1 KB) 2016-06-07_20h47_10.png Anonymous, 06/07/2016 05:47 PM
2016-06-08_11h59_19.png (12.1 KB) 2016-06-08_11h59_19.png Anonymous, 06/08/2016 09:01 AM
2016-06-08_13h14_50.png (6.49 KB) 2016-06-08_13h14_50.png Anonymous, 06/08/2016 10:55 AM
6232
6233
6242
6246

Associated revisions

Revision 41235dc9 (diff)
Added by William Grzybowski over 4 years ago

Remove delete ghost migrations option I dont know whose idea was to use delete ghost migrations but it was a terrible one. We never simply delete migrations in our development and removing them means a downgrade happened which will cause even more trouble when we try to reapply them (because they are not there in the first place anymore) Ticket: #15774 Ticket: #15832

Revision 2e721324 (diff)
Added by William Grzybowski over 4 years ago

Remove delete ghost migrations option I dont know whose idea was to use delete ghost migrations but it was a terrible one. We never simply delete migrations in our development and removing them means a downgrade happened which will cause even more trouble when we try to reapply them (because they are not there in the first place anymore) Ticket: #15774 Ticket: #15832

Revision 18eef119 (diff)
Added by William Grzybowski over 4 years ago

Remove delete ghost migrations option I dont know whose idea was to use delete ghost migrations but it was a terrible one. We never simply delete migrations in our development and removing them means a downgrade happened which will cause even more trouble when we try to reapply them (because they are not there in the first place anymore) Ticket: #15774 Ticket: #15832 (cherry picked from commit 2e72132454d4d1d59d28c20ed9c1864d74ac1ca7)

Revision 6ab4c1ec (diff)
Added by William Grzybowski over 4 years ago

Remove delete ghost migrations option I dont know whose idea was to use delete ghost migrations but it was a terrible one. We never simply delete migrations in our development and removing them means a downgrade happened which will cause even more trouble when we try to reapply them (because they are not there in the first place anymore) Ticket: #15774 Ticket: #15832 (cherry picked from commit 2e72132454d4d1d59d28c20ed9c1864d74ac1ca7)

History

#1 Updated by Anonymous over 4 years ago

  • File debug-FIONA-SERVER-20160607204156.txz added

#2 Updated by Anonymous over 4 years ago

  • File 2016-06-07_20h37_30.png added

#3 Updated by Anonymous over 4 years ago

6232

#4 Updated by Anonymous over 4 years ago

  • File deleted (2016-06-07_20h37_30.png)

#5 Updated by Anonymous over 4 years ago

6233

#6 Updated by Alexander Motin over 4 years ago

  • Assignee changed from Alexander Motin to William Grzybowski

William, could you take a look? It looks like some database schema problem.

#7 Updated by William Grzybowski over 4 years ago

  • Status changed from Unscreened to 15
  • Priority changed from No priority to Important

When did this started happening?

Do you have a /data/update.failed? Have you ever switched between STABLE and Nightlies?

#8 Updated by Anonymous over 4 years ago

6242

I haven't checked this tab in a few weeks so it is hard to say but I did get this critical error sometime between now and then. See attached. Maybe it has something to do with it. I can try and get you the update.failed file after work. I have never tried the switch to Nightlies. Thanks again for all the help guys.

#9 Updated by Anonymous over 4 years ago

Also forgot to add, the update see in attached picture I am running now. Maybe that fixed the problem. I will keep you posted.

#10 Updated by William Grzybowski over 4 years ago

Please attach /data/update.failed

#11 Updated by Anonymous over 4 years ago

  • File 2016-06-08_11h59_19.png added
  • File update.failed added

Oops, not good. My http & https interfaces don't work anymore after that last update. Attached is what my interface looks like now as well as my update.failed file.

#12 Updated by Anonymous over 4 years ago

  • File deleted (2016-06-08_11h59_19.png)

#13 Updated by Anonymous over 4 years ago

6246

#14 Updated by William Grzybowski over 4 years ago

I need your database prior to 9.10 upgrade, care to grab it for me?

mkdir /tmp/root
mount -t zfs freenas-boot/ROOT/9.3.1-STABLE /tmp/root

It will be in /tmp/root/data/freenas-v1.db

#15 Updated by Anonymous over 4 years ago

  • File freenas-v1.db added

#16 Updated by William Grzybowski over 4 years ago

  • Status changed from 15 to Investigation

Thanks, I'll do some investigation, might take a day or two and then get back to you.

#17 Updated by Anonymous over 4 years ago

Thank you sir! Much appreciated.

#18 Updated by William Grzybowski over 4 years ago

  • Status changed from Investigation to 15

Are you sure you have me the right database file? Did you mount that dataset properly? It sounds like you have given me the most recent one.

If that is the case, sounds like you have installed a 9.3 freenas version and then uploaded a more recent database to it, is that it?

#19 Updated by William Grzybowski over 4 years ago

Oh, nevermind, I think I see the issue.

#20 Updated by William Grzybowski over 4 years ago

Err, no. I stand correct. Your database from the version 9.3 does not have field it should have, it means a downgrade happened at some point.

#21 Updated by Anonymous over 4 years ago

Well I had a failed flash drive at one point (after updating to 9.10) but the only config file I had was a 9.3 config. I used that. That is probably leading to this error. Is there any fixing to this other than starting fresh?

#22 Updated by William Grzybowski over 4 years ago

  • Status changed from 15 to Closed: Not To Be Fixed

You can try this, but I make no promises:

cd /usr/local/www/freenasUI
python manage.py migrate services 0192 --fake --merge
python manage.py migrate --merge

#23 Updated by Anonymous over 4 years ago

Yeah that didn't work. I'm going to install 9.3 and use my 9.3 config file and then upgrade to 9.10. That's the correct way to do this right?

#24 Updated by William Grzybowski over 4 years ago

Brandon Jakas wrote:

Yeah that didn't work. I'm going to install 9.3 and use my 9.3 config file and then upgrade to 9.10. That's the correct way to do this right?

I am not sure that will work given that we dont know when db got mangled.

#25 Updated by Anonymous over 4 years ago

Haha, you are right. It didn't work... I am going to rebuild.

#26 Avatar?id=14398&size=24x24 Updated by Kris Moore about 4 years ago

  • Seen in changed from Unspecified to N/A

#27 Updated by Dru Lavigne about 3 years ago

  • File deleted (debug-FIONA-SERVER-20160607204156.txz)

#28 Updated by Dru Lavigne about 3 years ago

  • File deleted (update.failed)

#29 Updated by Dru Lavigne about 3 years ago

  • File deleted (freenas-v1.db)

#30 Updated by Dru Lavigne about 3 years ago

  • Target version set to N/A
  • Private changed from Yes to No

Also available in: Atom PDF