Zypper UP AMD issues

[frequency]

Hi,

We're using the latest 8.1.2 vicibox with 3050 SVN. We updated the server to the latest version via Zypper. We have a reason to believe that new zypper is breaking up with AMD. We witnessed that there was a huge drop in filtering process in the latest zypper update. We're using 8369 routing extension. We managed to move the DB to 7.0.1 and also 8.0.1 versions for vici without updating their OS and the problem was resolved succesfully. We are using 3050 on multiple server's without any issues although the newer version is 3053 as per today.

We updated the server today, and we are still facing the same issue on our ex-server that is being used for testing purposes only now after AMD broke. We have copied configuration files again, amd.conf and 8369 under extensions.conf and it seems to be just fine or as they should be. We first believe it was the carrier but it wasn't as things are working just fine on old versions for vicibox.

E3-1246v3, 32GB Ram, 256x2 SSD, AIO VICI installation with 3050 SVN, VERSION: 2.14-693a
BUILD: 181003-1619, Load average: 1.50, no disk wait time, no mysql bottlenecks. Vicibox 8.1.2. No any additional HW.

[williamconley]

1) Missing: Vicidial version with build. Good job posting your Vicibox installer version, and even your SVN revision level. But the Vicidial Version with Build is a requirement.

2) Stop using zypper up if you have no specific need. If you have your server whitelist locked down (which you should!), then your only security risk is people you've specifically allowed into your system. If one of them is a hacker, honestly, zypper up is not going to stop them. Even daily. Zypper up does not affect Vicidial operation at all, it's just for the OS anyway.

[frequency]

1) Missing: Vicidial version with build. Good job posting your Vicibox installer version, and even your SVN revision level. But the Vicidial Version with Build is a requirement.

2) Stop using zypper up if you have no specific need. If you have your server whitelist locked down (which you should!), then your only security risk is people you've specifically allowed into your system. If one of them is a hacker, honestly, zypper up is not going to stop them. Even daily. Zypper up does not affect Vicidial operation at all, it's just for the OS anyway.

We're not upgrading on a daily basis or weekly basis. Its a routine installing a newer server, we upgrade the server via zypper. SOP's. Setting up 5-10 server's on a daily basis including clusters, we come across a lot of problems and what we have witnessed in current release of zypper upgrades is that the AMD is breaking up. We thought this should have been conveyed.

[williamconley]

... installing a newer server, we upgrade the server via zypper ...

If your system fails during a fresh install, try again without zypper up. If the install does not fail, then stop using zypper up during your fresh installs (until the situation clears).

When the .iso image is built, Kumba has tested with all the versions of all the software installed by the .iso. But OpenSuSE is a live operating system. Changes happen daily. Some of those changes collide with the Vicidial core systems and have to be fixed. Until they are fixed, Zypper may break the system.

It's my understanding that this is the reason Vicibox is on OpenSuSE rather than Ubuntu. Ubuntu was MUCH worse in this regard. Zypper *usually* works fine. But ...

[frequency]

... installing a newer server, we upgrade the server via zypper ...

If your system fails during a fresh install, try again without zypper up. If the install does not fail, then stop using zypper up during your fresh installs (until the situation clears).

When the .iso image is built, Kumba has tested with all the versions of all the software installed by the .iso. But OpenSuSE is a live operating system. Changes happen daily. Some of those changes collide with the Vicidial core systems and have to be fixed. Until they are fixed, Zypper may break the system.

It's my understanding that this is the reason Vicibox is on OpenSuSE rather than Ubuntu. Ubuntu was MUCH worse in this regard. Zypper *usually* works fine. But ...

You have a valid point. But issues such as dial with customer and leave 3-way issues during higher dial level situations seems to have been resolved by updating asterisk and its related packages on the server. Hence we update.

[williamconley]

It seems more likely that your upgrade also matched the "version" information with the "code" properly this time. Which is a fairly common problem. Vicidial doesn't gain or lose features based on the version of the underlying operating system and packages. BUT if you have a mismatch anywhere in the system configuration and fix it during an upgrade, you may get the impression that the upgrade fixed something.

Of course, it's also possible that there was a bug introduced during one Zypper Up and that bug was fixed (oddly enough, that does happen) and the next time you Zypper Up'd it was resolved.

We only recommend upgrading the OS during installation, and even then if the install fails the next install will not have zypper up to see if that fixes the problem since Kumba doesn't release an OS .iso without testing it at least once (and by X.X.4 is pretty much fully debugged).

[Kumba]

What is the asterisk version that 'works'?

[frequency]

What is the asterisk version that 'works'?

For us, 11.25.3 is working fine or a early asterisk 13 on the 8.1.2 release ones. Not aware of the exact version. will have to dig deep on this.

We monitored most of the servers with updated asterisk 13, most of them installed last week, we witnessed that those servers has higher ACD's and lower SDP/SDC so the voip charges are more too. To rectify the issue, we updated the OS, which included some asterisk 13 updates as well. The server's completely stopped the AMD, like running 8368. we have left those higher ALOC servers as is as they might break too.

We can confirm this happened to two of our server's hence we moved those server's back to 8.0.1 which was super stable.

[dspaan]

Stop using zypper up if you have no specific need. If you have your server whitelist locked down (which you should!), then your only security risk is people you've specifically allowed into your system. If one of them is a hacker, honestly, zypper up is not going to stop them. Even daily. Zypper up does not affect Vicidial operation at all, it's just for the OS anyway.

I never do zypper up because indeed it breaks stuff. I don't understand why it's in the Vicibox install manual.

[williamconley]

Because it's a best practice. If it works, it's "good to do", but IMHO if the server already works it doesn't need Zypper Up. This isn't a windows workstation upon which someone will be surfing porn and need to have the latest security updates, nor is it a publicly accessible web server in need of the latest brute force protections, nor is it a Windows server of any sort with virtually unlimited security vulnerabilities that are patched one at a time while opening others.

[dspaan]

It's best practice for a regular linux install guide but not in this case.

[thephaseusa]

Latest security updates for porn surfers)))) good one Bill))

[williamconley]

Latest security updates for porn surfers)))) good one Bill))

Work in corporate IT for a while. It's a given, along with wiping every workstation's HD after a firing. (And making sure janitorial staff cleans the desk ... thoroughly. Including undersides and sidewalls.)

[dspaan]

lol!

[rameez.amjad4]

8.0.1 works better than this one 8.1.2 for amd please update if yes we will move back to 8.0.1?


For us, 11.25.3 is working fine or a early asterisk 13 on the 8.1.2 release ones. Not aware of the exact version. will have to dig deep on this.

We monitored most of the servers with updated asterisk 13, most of them installed last week, we witnessed that those servers has higher ACD's and lower SDP/SDC so the voip charges are more too. To rectify the issue, we updated the OS, which included some asterisk 13 updates as well. The server's completely stopped the AMD, like running 8368. we have left those higher ALOC servers as is as they might break too.

We can confirm this happened to two of our server's hence we moved those server's back to 8.0.1 which was super stable.[/quote]

[frequency]

8.0.1 works better than this one 8.1.2 for amd please update if yes we will move back to 8.0.1?


For us, 11.25.3 is working fine or a early asterisk 13 on the 8.1.2 release ones. Not aware of the exact version. will have to dig deep on this.

We monitored most of the servers with updated asterisk 13, most of them installed last week, we witnessed that those servers has higher ACD's and lower SDP/SDC so the voip charges are more too. To rectify the issue, we updated the OS, which included some asterisk 13 updates as well. The server's completely stopped the AMD, like running 8368. we have left those higher ALOC servers as is as they might break too.

We can confirm this happened to two of our server's hence we moved those server's back to 8.0.1 which was super stable.

[/quote]


we moved back to 3050 svn with Vicibox 8.0.1 updated. works perfectly fine.