BUG PIAF3 with Centos 6.7

[Jlobee]

I've installed PIAF3 Green on top of Centos 6.7 64bit using the Nerd vittles instructions. After running the PIAF installer I got the following prompt (notice how it detects the install as 6.4 and not 6.7):

CentOS release 6.4 (Custom) on x86_64
In order to continue your
PIAF/SIAF/CIAF/XIAF/FIAF/VIAF Installation
Please log in as root to continue
******************************************

install-green - 3.1.6 released on 033015
**********************************************************************
* We have detected the following Operating System and Version *
**********************************************************************
Operating System = CentOS
Version = 6.4

After the installer starts it correctly detects it as 6.7.

The issue I'm having is that after everything is installed and ready to go, I keep getting the following message on the console (I am able to login to the machine and use it):

CentOS release 6.4 (Custom) on x86_64
In order to continue your
PIAF/SIAF/CIAF/XIAF/FIAF/VIAF Installation
Please log in as root to continue
******************************************
Your IP Address is:

192.168.1.60
*****************************************

localhost login:

 

[darmock]

That is hard coded into the .bashrc as well as the motd file somewhere. Off the top of my head you will have to modify both of these files.... sorry not near the source.


Tom

 

[Jlobee]

Should this be coming up after the install is done or is it a bug?

 

[darmock]

PIAF3 was only designed to work with centos 6.4. Thus it is not a bug rather a feature..... seriously tinker with the .bashrc in /root and look at the motd and issue files in /etc

I also suspect you aren't using the current installer or some earlier variant.

Tom

 

[Jlobee]

I'll try that, thank you.

I'm using the most current version of the installer available as of yesterday (2014-12-03). Back when CentOS was only at 6.5 I didn't see this feature. I tried installing using CentOS 6.5, but after you run "yum -y upgrade" as one of the prerequisites, you're up to 6.7.

Should I be running the following for 6.7 (instructions are old so I didn't know if it applied or not):

# for CentOS/Scientific Linux 6.5/6.6 only, perform these additional steps:
wget http://pbxinaflash.com/update-kernel-devel
chmod +x update-kernel-devel
./update-kernel-devel
reboot

 

[darmock]

Yah sorry I did not write those! Personally we don't support Centos anymore since they screwed the pooch with their licensing

I will have a look the the old code when I get home and see if I can find an easier way.

The current installer for incredible uses the Scientific Linux 6.7 ISO we built and when PIAF 4 comes it it will also be using that or SL 6.7


Tom

 

[hecatae]

@Jlobee I consider it a feature of PIAF3.0.6.7

The issue did not appear with 3.0.6.5 or 3.0.6.6

 

[darmock]

I suspect there is more too this as I set up a new box with 6.7 and had no difficulty. Not sure beyond this.

 

[Jlobee]

That's strange, I installed it on two different boxes and got the same result using these instructions: http://liquidtelecom.dl.sourceforge.net/project/pbxinaflash/PIAF-3.6.5-Installer/readme.txt

 

[Jlobee]

The location of this banner is in /etc/issue
I went ahead and modified the file, but after a reboot it goes back to same as above, so some process is doing a check during bootup and overwriting the /etc/issue file.

 

[darmock]

look around in /usr/local/sbin seems I remember something in there is run


Tom

 

[darmock]

or make the issue file immutable after you change it.

chattr +i issue

 

[dicko]

The point is that /etc/issue should not be mutable by a startup script, it should be written ONLY by a process that actually does that, no?

 

[darmock]

Temp fix don't do it if you don't like.


Tom