robakabobbo
Technical User
Greetings,
We had to rollback our IPOCC 10.1 back to the 9.1.9, as the upgrade on the IPO 9.1.9 to 10.1 failed. IPO is working fine after we rollack back to its previous state in the VM before the upgrade, and we rolled back to the snap shot of the IPOCC with 9.1.9. Since then we have a monitoring program that keeps kicking out an error to us:
***** Overseer Icinga *****
Notification Type: PROBLEM
Service: IPOCC PostgreSQL 9.3
Host: ipocc.is
Address: xxx.xx.xx.xxx
State: CRITICAL
Date/Time: Tue Jan 16 08:47:59 EST 2018
Additional Info
ostgreSQL 9.3: Stopped. I found a thread that said to rename the postmaster file it it was empty, which it is not empty. There is a file string of C:/ProgramData/Avaya/PostgreSQL/9.3 1516048993 5432 *.
WE have a separate Chat server for the IPOCC. Our chat is working right now.
We had to rollback our IPOCC 10.1 back to the 9.1.9, as the upgrade on the IPO 9.1.9 to 10.1 failed. IPO is working fine after we rollack back to its previous state in the VM before the upgrade, and we rolled back to the snap shot of the IPOCC with 9.1.9. Since then we have a monitoring program that keeps kicking out an error to us:
***** Overseer Icinga *****
Notification Type: PROBLEM
Service: IPOCC PostgreSQL 9.3
Host: ipocc.is
Address: xxx.xx.xx.xxx
State: CRITICAL
Date/Time: Tue Jan 16 08:47:59 EST 2018
Additional Info
ostgreSQL 9.3: Stopped. I found a thread that said to rename the postmaster file it it was empty, which it is not empty. There is a file string of C:/ProgramData/Avaya/PostgreSQL/9.3 1516048993 5432 *.WE have a separate Chat server for the IPOCC. Our chat is working right now.