ACR 4_x on Centos 7 anyone?

[joul]

Hi, Have anyone managed to get ACR 4_x (Chronicall) running on a Centos 7 install?
According to ACR_Linux_Installation_Guide.pdf Server can be (Centos 7+ or Ubuntu 14+) but I have not had any ACR 4_x version running on Centos.
Or could it be my VM image from LINUXVMIMAGES.COM?
Have a clean 64bit Centos 7 VM from LINUXVMIMAGES.COM, So I downloaded the 64bit RHEL Setup from

https://forms.ximasoftware.com/oemdownloads:

[ul]
[li]sudo su -[/li]
[li]wget

https://forms.ximasoftware.com/s3_d...ting_Setup_4_4_0u_IP_Office_rpm_64_bit.tar.gz

[/li]
[li]successfully tar -xzf Avaya_Call_Reporting_Setup_4_4_0u_IP_Office_rpm_64_bit.tar.gz[/li]
[li]cd Avaya....[/li]
[li]./install.sh -serial OURDEMOSERIALKEY1234567DEMOA[/li]
[li]Got the mesage about successful install and where to browse:9080)[/li]
[li]Checked that ChronicallServer service is Running[/li]
[li]Tried rebooting..[/li]
[/ul]
Still can't browse to server:9080. Not responding! It worked with ACR 3.X
Any suggestions for running ACR 4_x successfully on Linux?

 

[tlpeter]

Check the firewall. Is it enabled and if this is the case, is the port allowed?

BAZINGA!

I'm not insane, my mother had me tested!

 

[IamaSherpa]

You can download an already prepared OVA version of the Linux ACR Server

 

[joul]

Thanks.
I found an old ova on my PC : ACR4_2_6.ova
Maybe there's a newer ova but I dont have the ftp login..
Installed this 4_2 and the web server is running correctly. Will then try upgrade to 4_4

 

[joul]

Upgrade Linux ACR 4_2_6.OVA to 4_4 seems working, Except for all logins confirmed working in 4_2_6 become unusable in 4_4
Invalid Username or Password - both for Administrator and personal login.

According to Xima you can recover this way:

Navigate to the base Chronicall / ACR folder Usually located in:
/var/lib/Chronicall or
/var/lib/Avaya Call Reporting
Create a blank recover.temp file in that folder: touch recover.temp
Try to login again using recover as both the username and password
The recover.temp file will be automatically deleted on successful login
Not entirely true...

The only way I could somehow log in again whas this method:
[ul]
[li]service ChronicallServer stop[/li]
[li]sudo touch /var/lib/avaya_call_reporting/recover.temp [/li]
[li]service ChronicallServer start[/li]
[li]Browse to:

http://acrserverip:9080/web/login

[/li]
[li]Login with User: recover Password: recover[/li]
[li]Upper right corner will show it's a rcovery login[/li]
[li]Logout[/li]
[li]Login again with the same Administrator passwords you set before upgrade to 4_4 (so a forgotten password will NOT be reset!)[/li]
[li]You can now use your users and Administrator passwords - but only on the

http://acrserverip:9080/web/login

! [/li]
[/ul]
Management no longer accessible when upgrading from 4_2_6 to 4_4!
[ul]
[li]Option 1a: Using an old Avaya Call Reporting Desktop app does not work.[/li]
[li]Option 1b: Downloading a new (Winbdows version) from

http://acrserverip:9080

will give you "Whitelabel Error Page" Internal Server Error 500.[/li]
[li]Option 2: Running JNLP (index.jnlp) Will fire up - Incorrect Username or Password But they DO WORK in the web/login![/li]
[li]Option 3: Internet Explorer: Will force you to the java.com dowload page. Dowload the lates version and ACR will still route you back to java.com [/li]
[/ul]

 

[Travis Harper]

I installed it on CentOS using the same instructions you provided, I think...

I do remember having to put in a flag followed by the license file... It's been a while.

The trick is that stock CentOS uses Apache Webserver.
You need shut down Apache, because ACR uses NGINX Web server.

Once you shut down apache web server, re-start ChronicallServer and you will be able to open it in the web browser.

 

[joul]

Does anyone have a working ACR 4_4 on Linux? What magical powers do I need to possess?
In short: ACR 4_4_0 on Linux: You can't login to setup or administer the system? ACR 4_2_9 Works well!

In addition to trying upgrading from the Centos ACR_4_2_6.ova, I also tried these other Ubuntu methods:
_____________________________________________________________________________________________

New Ubuntu VM: Ubuntu_20.04.2_VM_LinuxVMImages.ovf + Ubuntu_20.04.2_VM_LinuxVMImages-disk1.vmdk [ul]
[li]Installed ACR [highlight #8AE234]4_2_9[/highlight] : [highlight #8AE234]Setup and logging works without any hustles.[/highlight][highlight #FCAF3E][/highlight]

[/li]
[li]Upgraded to [highlight #FCE94F]4_4_0[/highlight] : [highlight #8AE234]Web login works[/highlight] - But all other admin methods: [highlight #EF2929]”Incorrect username or password”[/highlight][/li]
[li]Recover via touch recover.temp doesn’t work:
- recover | recover = “Incorrect Username or Password”
- Administrator |password = “Incorrect Username or Password” (But still working in web login!)[/li]
[/ul]
Next attempt:
_____________________________________________________________________________________________

New Ubuntu VM: Ubuntu_20.04.2_VM_LinuxVMImages.ovf + Ubuntu_20.04.2_VM_LinuxVMImages-disk1.vmdk [ul]
[li]Installed ACR [highlight #FCE94F]4_4_0[/highlight] : [highlight #8AE234]Web login works[/highlight] - But all other admin methods: [highlight #EF2929]”Incorrect username or password”[/highlight][/li]
[li]Recover via touch recover.temp doesn’t work:
- recover | recover = “Incorrect Username or Password”
- Administrator |password = “Incorrect Username or Password” (But still working in web login!)[/li]
[li]Uninstalled 4_4_0, Then installed 4_2_9 on the same machine...[/li]
[li]Recover via touch [highlight #8AE234]recover.temp now works.[/highlight][/li]
[li]Setup works... except [highlight #EF2929] logging from the IPO not working [/highlight]. (Of course used the exact same settings as when installed 4_2_9 on a fresh server.[/li]
There must remain some artifacts from 4_4 that prevents 4_2_9 from working
[/ul]_____________________________________________________________________________________________