Project

General

Profile

Bug #26405

11.1Beta1 Regular console view error: could not open & could not find cache sequence file in /var/db/system/update

Added by Allen Polikoff almost 3 years ago. Updated almost 3 years ago.

Status:
Closed: Cannot reproduce
Priority:
No priority
Assignee:
Sean Fagan
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:

Supermicro x11 SSL-F
Intel Xeon e3 1245 v6
32 gig of ram (pc-2133) over 2 single channel dimms by Micron
16gb supermicro SATADOM (system boot drive)
3x 3TB WD RE drives (however two of them are sata II for some reason)
Oracle F20 hard drive accelerator for the SLOG

ChangeLog Required:
No

Description

The console view on my FreeNAS 11.1 beta 1 system is displaying the following error on a fairly regular basis (more than a few times a day i believe):

Could not open SEQUENCE file in cache directory /var/db/system/update followed by no such file or directory /var/db/system/update/SEQUENCE.
Then directory /var/db/system/update does not have a sequence file.

In addition during one of the first few days running the beta I received a security output email from the system stating:

env: python: No such file or directory

I’m running the beta on a system with the following hardware & the pool was originally created by/in FreeNAS Corral then exported into the 11 OS:

Supermicro x11 SSL-F
Intel Xeon e3 1245 v6
32 gig of ram (pc-2133) over 2 single channel dimms by Micron
16gb supermicro SATADOM (system boot drive)
3x 3TB WD RE drives (however two of them are sata II for some reason)
Oracle F20 hard drive accelerator for the SLOG

No VMs currently running, few jails & a startup script to control fanspeed (which may be written in python, don’t recall).

History

#1 Updated by Dru Lavigne almost 3 years ago

  • Category changed from 129 to 1
  • Assignee changed from Release Council to Sean Fagan

#2 Updated by Sean Fagan almost 3 years ago

  • Status changed from Unscreened to 15

In and of itself, this doesn't mean anything other than, for some reason, attempts to download an available update failed (since there was a MANIFEST file, and it was able to get a lock on the MANIFEST file, but the expected SEQUENCE file did not exist).

Would need the debug logs; alternately, you can try running, from the shell, "freenas-update -v check" and see if it completes.

#3 Updated by Allen Polikoff almost 3 years ago

Sean Fagan wrote:

In and of itself, this doesn't mean anything other than, for some reason, attempts to download an available update failed (since there was a MANIFEST file, and it was able to get a lock on the MANIFEST file, but the expected SEQUENCE file did not exist).

Would need the debug logs; alternately, you can try running, from the shell, "freenas-update -v check" and see if it completes.

I tried running freenas-update -v check, but the result was “freenas-update: command not found”. I went to the system folder and it seems like there are two different log files - is there a specific file needed/way to send you the debug log?

#4 Updated by Sean Fagan almost 3 years ago

If you logged into the console, or in the terminal in the web ui, or as root over ssh, and it says "freenas-update: command not found", then your system is not installed properly, and there's not a lot I can do to help there.

I think. Hm. Try "ls -l /usr/local/bin/python"; if that doesn't exist, that could explain some things.

#5 Updated by Allen Polikoff almost 3 years ago

The result of that command was:
lrwxr-xr-x 1 root wheel 7 Oct 25 00:34 /usr/local/bin/python -> python3

However if I reboot the machine (after upgrading to the beta) it seems like the morning after the security run output email isn't blank and says:
Env: python: no such file or directory (from the kernel log message) as noted in the bug report.
So I wouldn't be surprised if the update to the beta wasn't fully successful maybe?

#6 Updated by Dru Lavigne almost 3 years ago

  • Status changed from 15 to Unscreened
  • Target version set to 11.1

#7 Updated by Sean Fagan almost 3 years ago

  • Status changed from Unscreened to 15

Yeah, that's what it sounds like. Can you get to a previous BE? If so, do that, and try running "freenas-update -v check ; freenas-update -v --reboot update".

#8 Updated by Allen Polikoff almost 3 years ago

Yes, I have boots of 11.0 u4 saved. Would that work?
Also - I’ve updated to 11.1 rc1 and it seems like those errors have been squashed (and wouldn’t the update command update the system to the rc1 anyhow?). With that said should I still do as you ask? Maybe you guys have already fixed it...anyway I have 11.0 u4, 11.1 beta1 and 11.1 rc1 environments.

Btw - the only issue I’ve experienced in 11.1 rc1 is a check demon showing a warning during re-slivering while I was having a disk replaced with a different drive. After the re-silver was done the error stopped & the old drive came off the pool.

Best benefit of 11.1 has been the smb changes btw. Previously my printer or apps on my iPhone couldn’t connect to my smb shares. Kudos!

#9 Updated by Dru Lavigne almost 3 years ago

  • Status changed from 15 to Closed: Cannot reproduce
  • Target version changed from 11.1 to N/A

Thanks for the update, Allen. I'll close this ticket out.

Also available in: Atom PDF