vertica installation on ubuntu 14.04 server

Hi

Did you manage to re-run the installer as you said after fixing this?If yes can you kindly provide admintoools-dbadmin.log & admintools-root.log (path: /opt/vertica/log) from the same server where you ran this install_vertica script.

Regards
Rahul

Also if you are performing this installation on a test/dev environment you can use --failure-threshold NONE (not supported or recommended in production environment) switch with install_vertica command which can help you bypass this & let your installation complete.

I can not find where to attach a file. (
adminTools-root.log

Dec 19 12:02:26  [11668] NEW LOG: '/opt/vertica/share/eggs/vertica/install/__main__.py' --hosts localhost --deb '/tmp/vertica_7.1.1-0_amd64.deb' --dba-user dbadmin Dec 19 12:02:26  [11668] [adminExec.__init__] Unique Ports: False 
Dec 19 12:02:26  [11668] Saved Configurator(clusterSize=0, dbs=()) -> /opt/vertica/config/admintools.conf 
Dec 19 12:02:26  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: <command hidden> 
Dec 19 12:02:26  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['[ -f /etc/fedora-release ]'] 
Dec 19 12:02:26  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=1) [] 
Dec 19 12:02:26  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['[ -f /etc/redhat-release ]'] 
Dec 19 12:02:26  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=1) [] 
Dec 19 12:02:26  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['[ -f /etc/SuSE-release ]'] 
Dec 19 12:02:26  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=1) [] 
Dec 19 12:02:26  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['[ -f /etc/debian_version ]'] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=0) [] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['grep "^4." /etc/debian_version'] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=1) [] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['grep "^5." /etc/debian_version'] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=1) [] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['grep "^6." /etc/debian_version'] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=1) [] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['grep "^7." /etc/debian_version'] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=1) [] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['grep "wheezy" /etc/debian_version'] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=1) [] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['grep "jessie" /etc/debian_version'] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=0) ['jessie/sid'] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['LANG=C /sbin/ip -oneline -family inet addr'] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=0) ['1: lo    inet 127.0.0.1/8 scope host lo\\       valid_lft forever preferred_lft forever', '2: eth0    inet 172.31.33.177/21 brd 172.31.39.255 scope global eth0\\       valid_lft forever preferred_lft forever', '3: virbr0    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0\\       valid_lft forever preferred_lft forever'] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ["dpkg -s vertica 2>&1 | grep Status | awk '{print $2}'"] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=0) ['install'] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ["dpkg -l vertica 2>/dev/null | tail -1 | awk '{print $3}'"] 
Dec 19 12:02:27  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=0) ['7.1.1-0'] 
Dec 19 12:02:27  [11668] [Profile.VerticaRelease] query results '7.1.1-0' 
Dec 19 12:02:27  [11668] Hosts to add: ['127.0.0.1'] 
Dec 19 12:02:27  [11668] Hosts to remove: [] 
Dec 19 12:02:27  [11668] Hosts to update: [] 
Dec 19 12:02:27  [11668] Resulting cluster: ['127.0.0.1'] 
Dec 19 12:02:28  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: <command hidden> 
Dec 19 12:02:28  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: <command hidden> 
Dec 19 12:02:28  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: <command hidden> 
Dec 19 12:02:28  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['echo 'if [ -e "/opt/vertica" ]; then cd /tmp; find /opt/vertica -perm -755 -type d | grep "/opt/vertica\\$"; else echo /opt/vertica; fi''] 
Dec 19 12:02:28  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=0) ['/opt/vertica'] 
Dec 19 12:02:28  [11668] RPM Check,  The same version is already installed 
Dec 19 12:02:28  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: <command hidden> 
Dec 19 12:02:28  [11668] backing up admintools.conf on 127.0.0.1  
Dec 19 12:02:28  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['id dbadmin'] 
Dec 19 12:02:28  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=0) ['uid=1001(dbadmin) gid=1002(verticadba) groups=1002(verticadba),0(root)'] 
Dec 19 12:02:28  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: <command hidden> 
Dec 19 12:02:29  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['VERT_DBA_USR=dbadmin VERT_DBA_HOME=/home/dbadmin VERT_DBA_GRP=verticadba /opt/vertica/oss/python/bin/python -m vertica.local_coerce'] 
Dec 19 12:02:36  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=0) [] 
Dec 19 12:02:36  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['install --owner avdeevfi --mode 700 -d /tmp/vstage-064be69f-7575-4712-81e3-f40e9b8bf875'] 
Dec 19 12:02:36  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=0) [] 
Dec 19 12:02:36  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['cp -T /opt/vertica/log/verify-latest.xml /tmp/vstage-064be69f-7575-4712-81e3-f40e9b8bf875/file'] 
Dec 19 12:02:36  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=0) [] 
Dec 19 12:02:36  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['chown avdeevfi /tmp/vstage-064be69f-7575-4712-81e3-f40e9b8bf875/file'] 
Dec 19 12:02:36  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=0) [] 
Dec 19 12:02:36  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: ['rm -rf /tmp/vstage-064be69f-7575-4712-81e3-f40e9b8bf875'] 
Dec 19 12:02:37  [11668] <BashAdapter: avdeevfi@127.0.0.1 sudo>: (rc=0) [] 

What error message does the install now give, after disabling iptables ?

The error remains the same "WARN (N0010) Linux iptables (firewall)"
before and after disabling iptables 

if getting the same iptables message, can you check the output of -
sudo ufw status

Hi!

Post please output for next commands:

iptables --list --table filter
iptables --list --table mangle

PS
OMG! Does Vertica can't recognize that iptables is disabled and do not validate iptables rules? Awful development.

Here is a pseudo code how it should be implemented:

001: iptables -> is active?
002: if not active:
003:     so continue installation wihout iptables rules validation
004: else:
005:     raise an exception on iptables rules

Not so hard and not require a PHD for this.

Try flushing the whole -

  iptables -t mangle -F

Hi!

Option -F will delete all rules and still it will not solve your problem: error occurs on mangle and on filter and Raul command will remove rules from mangle only.

$ sudo iptables -t mangle -F
$ sudo iptables -t filter -F

And Im still pretty sure that even after you will clear all rules you will get same error, because of this lines:

            accept_re = re.compile(r'\bACCEPT\b')
            header_re= re.compile(r'^\s*target\b')

Even if you have no rules, regexp will return response that rules exists. Why? Awful developers - do not do usage in their brain. Looks like HP with their developers tries to proof "Infinite monkey theorem"


I will show why I think like this:

daniel@synapse:~$ sudo ufw status
[sudo] password for daniel: 
Status: inactive

daniel@synapse:~$ sudo iptables -t mangle -F   # clear rules
daniel@synapse:~$ sudo iptables -t filter -F   # clear rules

daniel@synapse:~$ sudo iptables -t filter --list    # show rules for filter
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         

daniel@synapse:~$ sudo iptables -t mangle --list    # show rules for mangler
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination         

Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination         
 

As you can see I removed all rules, but what regexp validates? That word ACCEPT and/or target are exists. Yes, these words are exists, but no rules, iptables is disabled. Dismiss these developers - this is not a developers, it is a headache of Vertica clients.

I've tried it, does not help

Hi!

Actually I pointed that its will not help.

And Im still pretty sure that even after you will clear all rules you will get same error

Yes I have seen. I tried before writing the entire post. I just confirmed

Thanks. I'll look into the source code....

Hi!

I'll look into the source code....

Are you python developer?

problem occurs here: /opt/vertica/share/eggs/vertica/platform/node/t/network.py
functions names:

• check_iptables_disabled(self)
  
• examine_table(t)

**********

    def check_iptables_disabled(self):
        """Validerates that iptables is all ACCEPT (or non-present)"""

And something interesting - function actually do not do what it should do. By name of function and doc string, script should validate if iptables is disabled or all rules are - ACCEPT. Script do not validates if iptables is disabled, because if it disabled so no reason to check rules, but script in any case validated iptables rules.


Awful design. Development Team Leader should be fired.

Hi Skvid, 
I am sorry that you are having this issue. We don't have too many installations in Ubuntu and perhaps that issue skip our qa testing. Thanks so much for raising it and I will notify our engineer team so they can take a look. At the contrary of what id10t said, we care about ALL our customers and community. 

@id10t,  Sorry that you had such a strong and negative feelings about Vertica support and engineer team. I am happy to said that you are an exception and would like to change that experience. if you can give us more details of the issues that you had experienced I will personally look at them. If you are a customer  (synapse? - I don't see that you are a customer ) I will look at your support tickets. 

Eugenia

corrected file /opt/vertica/share/eggs/vertica/platform/node/t/network.py 
Now everything is set up and running

Thanks.

Hi!

Its just my personal opinion based on almost 3 years of experience with support.
Its a community, Im a part of community and so can give my FeedBack. If you don't like - ban me.

we care about ALL our customers and community.

Nice joke

If you are a customer

No, Im not, just an enthusiast, troll and idiot, but helpful troll. "synapse" - its my laptop with DEV environment.

Hi!

Of cause they will take a look... now... when it solved by community members ))
A classical example of support.

Hi Skvid!


Can you post patch/diff? Can you help to Vertica engineers? Otherwise they will fail to fix it:)