Re: [Users] bug with ovirt nightlies and engine-setup-2 script
----- Original Message -----
From: "Hetz Ben Hamo" <hetz(a)hetz.biz>
To: "Alon Bar-Lev" <alonbl(a)redhat.com>
Cc: "users(a)oVirt.org" <users(a)ovirt.org>, "Sandro Bonazzola"
<sbonazzo(a)redhat.com>
Sent: Wednesday, July 17, 2013 11:56:48 PM
Subject: Re: bug with ovirt nightlies and engine-setup-2 script
Thanks for the patch.
I just found another problem, my desktop probably gets heat too much and it
was stuck. I'm trying the no firewall approach (engine-cleanup-2,
engine-setup-2) but now it fails with the message that it failed to clear
zombie tasks. How can I clear it manually?
Is it clean installation?
If it does, try to clean database first using engine-cleanup-2.
תודה,
*חץ בן חמו*
"*חץ ביז <http://www.hetz.biz>*"- שרותי פרילאנס לניהול ותחזוקת שרתי
Linux
ופתרונות וירטואליזציה.
טלפון: 054-5297156
אתם מוזמנים לבקר אותנו בבלוג היעוץ שלנו <http://vps-consulting.info>
[image: גם אתר זה מתארח ב-חץ ביז שרתי VPS]
*
*
2013/7/17 Alon Bar-Lev <alonbl(a)redhat.com>
>
>
> ----- Original Message -----
> > From: "Hetz Ben Hamo" <hetz(a)hetz.biz>
> > To: "users(a)oVirt.org" <users(a)ovirt.org>
> > Cc: "Sandro Bonazzola" <sbonazzo(a)redhat.com>,
alonbl(a)redhat.com
> > Sent: Wednesday, July 17, 2013 4:05:46 PM
> > Subject: bug with ovirt nightlies and engine-setup-2 script
> >
> > *
> > *
> > Hi,
> >
> > I installed the all in one plugin and run the engine-setup-2 script. it
> > detects the plugin, and I'm using the iptables option. problem is that it
> > writes the wrong lines in iptables:
> >
> > -A INPUT -p tcp -m state --state NEW -m tcp --dport 5634-6166 -j ACCEPT
> > -A INPUT -p tcp -m state --state NEW -m tcp --dport 49152-49216 -j ACCEPT
> >
> > iptables does not accept the minus sign when mentioning port range, so
> > 5634-6166 should be 5634:6166 (I wish it would accept the minus sign,
> it's
> > a stupid thing that it doesn't).
>
> Confirmed, thanks!
> Patch is available[1].
>
> > So the script failes to start iptables due to these wrong lines, and I'm
> > stuck with oVirt that doesn't work.
>
> You can select no firewall to workaround this.
>
> >
> > Log file - enclosed.
> >
> > Hetz
> >
>
> [1] http://gerrit.ovirt.org/17036
>