Please take this survey to help us learn more about how you use third party tools. Your input is greatly appreciated!

Install option failure-threshold not working

Hi,

 

I'm trying to install Vertica 8.0 on linux server (RHEL6), I've got one warning and one hint error and I want to omit this errors with this option --failure-threshold WARN but it doesn't work ...

 

My install command:

/opt/vertica/sbin/install_vertica --hosts auric --rpm /home/vertica/RPM/vertica-8.0.1-0.x86_64.RHEL6.rpm --dba-user vertica --dba-group dba --data-dir /usr3/vertica/data/ --failure-threshold WARN

 

My log:

Vertica Analytic Database 8.0.1-0 Installation Tool


>> Validating options...


Mapping hostnames in --hosts (-s) to addresses...
auric => 10.0.2.40

>> Starting installation tasks.
>> Getting system information for cluster (this may take a while)...

Default shell on nodes:
10.0.2.40 /bin/bash

>> Validating software versions (rpm or deb)...


>> Beginning new cluster creation...

successfully backed up admintools.conf on 10.0.2.40

>> Creating or validating DB Admin user/group...

Successful on hosts (1): 10.0.2.40
Provided DB Admin account details: user = vertica, group = dba, home = /home/vertica
Creating group... Group already exists
Validating group... Okay
Creating user... User already exists
Validating user... Okay


>> Validating node and cluster prerequisites...

Error: Command failed on '10.0.2.40':
VERT_DBA_USR=vertica VERT_DBA_DATA_DIR=/usr3/vertica/data/ VERT_DBA_HOME=/home/vertica VERT_DBA_GRP=dba /opt/vertica/oss/python/bin/python -m vertica.local_coerce
returncode = 1
System prerequisites failed. Threshold = WARN
Hint: Fix above failures or use --failure-threshold

Installation FAILED with errors.

****
AdminTools and your existing Vertica databases may be unavailable.
Investigate the above warnings/errors and re-run installation.
****

 

And the two errors founded in verify-latest.xml

<failure eid="S0141" help="https://my.vertica.com/docs/8.0.x/HTML/index.htm#cshid=S0141" message="CPUs have discouraged cpufreq scaling policies: cpu0, cpu1, cpu2, cpu3, cpu4, cpu5, cpu6, cpu7, cpu8, cpu9, cpu10, cpu11" severity="WARN" severitystr="WARN" type="VerticaAssertionError.vertica.platform.check.assertions">Traceback (most recent call last):
File &quot;/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/shared/classrunner.py&quot;, line 153, in _inner_run
out = method(*args, **kwargs)
File &quot;/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/platform/node/t/cpu.py&quot;, line 104, in check_cpufreq_governor_policy
&quot;, &quot;.join(ondemand), eid = &apos;S0141&apos;, sev = Severity.WARN)
File &quot;/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/platform/check/assertions.py&quot;, line 91, in vassert
raise VerticaAssertionError(msg, **kwargs)
VerticaAssertionError: WARN(eS0141): CPUs have discouraged cpufreq scaling policies: cpu0, cpu1, cpu2, cpu3, cpu4, cpu5, cpu6, cpu7, cpu8, cpu9, cpu10, cpu11
</failure>

...

<failure eid="S0151" help="https://my.vertica.com/docs/8.0.x/HTML/index.htm#cshid=S0151" message="These disks do not have known IO schedulers: &apos;/dev/mapper/BAIE08-PUR-AURIC-01L&apos; (&apos;&apos;) = &apos;&apos;" severity="HINT" severitystr="HINT" type="VerticaAssertionError.vertica.platform.check.assertions">Traceback (most recent call last):
File &quot;/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/shared/classrunner.py&quot;, line 153, in _inner_run
out = method(*args, **kwargs)
File &quot;/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/platform/node/t/disk.py&quot;, line 289, in check_io_scheduler_none
% &quot;, &quot;.join(unknowns), eid = &quot;S0151&quot;, sev = Severity.HINT)
File &quot;/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/platform/check/assertions.py&quot;, line 91, in vassert
raise VerticaAssertionError(msg, **kwargs)
VerticaAssertionError: HINT(eS0151): These disks do not have known IO schedulers: &apos;/dev/mapper/BAIE08-PUR-AURIC-01L&apos; (&apos;&apos;) = &apos;&apos;
</failure>

...

 

And incomprehensible error found in the log file install.log:

 

...

2017-01-24 08:31:09.463 installer/107739:0x7f224beef700 [FixContext._init_set_stage_dir] <INFO> Creating backup, new, and temporary directories
2017-01-24 08:31:09.487 installer/107314:0x7fe24fd4c700 [BashAdapter.execute] <INFO> <BashAdapter: [email protected]>: (rc=1) ['Traceback (most recent call last):', ' File "/opt/vertica/oss/python/lib/python2.7/runpy.py", line 162, in _run_module_as_main', ' "__main__", fname, loader, pkg_name)', ' File "/opt/vertica/oss/python/lib/python2.7/runpy.py", line 72, in _run_code', ' exec code in run_globals', ' File "/opt/vertica/share/eggs/vertica/local_coerce.py", line 215, in <module>', ' _lcMain()', ' File "/opt/vertica/share/eggs/vertica/local_coerce.py", line 212, in _lcMain', ' coerce.run()', ' File "/opt/vertica/share/eggs/vertica/local_coerce.py", line 88, in run', ' halted = self._run_to_halt()', ' File "/opt/vertica/share/eggs/vertica/local_coerce.py", line 93, in _run_to_halt', ' if self._iterate(x):', ' File "/opt/vertica/share/eggs/vertica/local_coerce.py", line 127, in _iterate', ' configure.load()', ' File "/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/platform/fix/runner.py", line 51, in load', ' self._report.load_results(self._infile)', ' File "/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/platform/check/report.py", line 62, in load_results', ' tree = xml.etree.ElementTree.parse(xmlfile)', ' File "/opt/vertica/oss/python/lib/python2.7/xml/etree/ElementTree.py", line 1182, in parse', ' tree.parse(source, parser)', ' File "/opt/vertica/oss/python/lib/python2.7/xml/etree/ElementTree.py", line 656, in parse', ' parser.feed(data)', ' File "/opt/vertica/oss/python/lib/python2.7/xml/etree/ElementTree.py", line 1642, in feed', ' self._raiseerror(v)', ' File "/opt/vertica/oss/python/lib/python2.7/xml/etree/ElementTree.py", line 1506, in _raiseerror', ' raise err', 'xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 116, column 36']

...

 

Thanks for your help

Philippe

 

Comments

  •  

     

       Actually the WARN threadshold is the default one. If a WARN or greater issue is encountered the installation will stop.

     

      You need to run a default install first and list your errors or warning, try to fix errors and then run install with 

    --failure-threshold NONE

     

      In your errors case you need to create those direcotries and grant verticadba & dbadmin user full access before you run the install cmd.

      BTW you can create the user and groups before the install, Vertica will just validate the existance of them.

     

    Hope this helps 

  • @Adrian_Oprea_1

     

    What directory are you talking about ?

     

    About io scheduler which must be permanent or noop, I don't why I've got this error, see below:

     

    [[email protected] ~]$ ls -alrt /dev/mapper
    total 0
    crw-rw----  1 root root 10, 58 Jan 23 15:02 control
    lrwxrwxrwx  1 root root      7 Jan 23 15:02 vg_auric-lv_swap -> ../dm-1
    drwxr-xr-x  2 root root    180 Jan 23 15:02 .
    lrwxrwxrwx  1 root root      7 Jan 23 15:02 vg_auric-lv_root -> ../dm-0
    lrwxrwxrwx  1 root root      7 Jan 23 15:02 vg_auric-lv_home -> ../dm-5
    lrwxrwxrwx  1 root root      7 Jan 23 15:02 vg_auric-lv_work -> ../dm-4
    lrwxrwxrwx  1 root root      7 Jan 23 15:02 BAIE08-PUR-AURIC-02L -> ../dm-2
    lrwxrwxrwx  1 root root      7 Jan 23 15:02 BAIE08-PUR-AURIC-01L -> ../dm-3
    drwxr-xr-x 19 root root   4120 Jan 23 15:03 ..
    [[email protected] ~]$ cat /sys/block/dm-3/queue/scheduler
    [noop] anticipatory deadline cfq
    [[email protected] ~]$ id
    uid=2863(vertica) gid=101(dba) groups=101(dba)

  •  

     

    Hi,

    Your scheduler should be deadline to change that add this to your /etc/rc.local file 

    echo deadline > /sys/block/<volume name eg: xvdb>/queue/scheduler

    See this link for more info https://my.vertica.com/docs/8.0.x/HTML/index.htm#Authoring/InstallationGuide/BeforeYouInstall/IOScheduling.htm

     

      As for the folders , i was reffering to folders where you want Vertica to be installed and have its catalog + data file in.

     

     

    Also you can skipp CPU frequnecy if you run in AWS or virtual machines, you wont  be able to change it anyway to just use failure NONE

     

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file

Can't find what you're looking for? Search the Vertica Documentation, Knowledge Base, or Blog for more information.