Forum

Unified Communications System


Getting an error up...
 

Getting an error updating from 2.1.1-1 to 2.3.0.-2  

Page 1 / 2
  RSS

DannyLarsen
(@dannylarsen)
Estimable Member
Joined: 1 year ago
Posts: 101
14/03/2019 9:35 am  

When updating from the gui from 2.1.1-1 to 2.3.0-2

After clicking for the update, I get a red error

"Cannot update to the latest version"

Thanks


Quote
mrivera
(@ing-joserivera26)
Developer Admin
Joined: 1 year ago
Posts: 998
14/03/2019 9:38 am  

We are checking that issue. For now, you may update from the Linux console:

yum clean all

yum update vitalpbx

ReplyQuote
DannyLarsen
(@dannylarsen)
Estimable Member
Joined: 1 year ago
Posts: 101
14/03/2019 10:44 am  

After updating via yum the CDR no longer shows in CDR reports

I have done a module reload cdr_adaptive_obdc.so   and a reboot but CDR reports have no calls.

Thank you

 


ReplyQuote
mrivera
(@ing-joserivera26)
Developer Admin
Joined: 1 year ago
Posts: 998
14/03/2019 10:50 am  

We made some test in our production server and is working as expected.

Please check the asterisk and MariaDB services


ReplyQuote
DannyLarsen
(@dannylarsen)
Estimable Member
Joined: 1 year ago
Posts: 101
14/03/2019 11:04 am  

mariadb seems to be running correctly


ReplyQuote
DannyLarsen
(@dannylarsen)
Estimable Member
Joined: 1 year ago
Posts: 101
14/03/2019 11:06 am  

asterisk is running calls are processing normally as far as I can see so far


ReplyQuote
mrivera
(@ing-joserivera26)
Developer Admin
Joined: 1 year ago
Posts: 998
14/03/2019 11:19 am  

Check the cdr table status:

mysql -uroot asterisk -e'check table cdr';

 


ReplyQuote
DannyLarsen
(@dannylarsen)
Estimable Member
Joined: 1 year ago
Posts: 101
14/03/2019 11:29 am  

Returns a table entry 

 

asterisk.cdr  check  status  OK


ReplyQuote
mrivera
(@ing-joserivera26)
Developer Admin
Joined: 1 year ago
Posts: 998
14/03/2019 11:31 am  

Looks like everything is ok.


ReplyQuote
DannyLarsen
(@dannylarsen)
Estimable Member
Joined: 1 year ago
Posts: 101
14/03/2019 11:43 am  

just no calls in the CDR report


ReplyQuote
mrivera
(@ing-joserivera26)
Developer Admin
Joined: 1 year ago
Posts: 998
14/03/2019 11:52 am  

Well, we cannot reproduce the issue. I also tried on a clean installation and all is working.


ReplyQuote
DannyLarsen
(@dannylarsen)
Estimable Member
Joined: 1 year ago
Posts: 101
14/03/2019 12:40 pm  

Strange thing, I have the demo Sonata Billing email me and it shows some calls  there

But not on the CDR report


ReplyQuote
tonywhelan
(@tonywhelan)
Trusted Member
Joined: 12 months ago
Posts: 65
14/03/2019 2:48 pm  

Getting the same "cannot update" error trying to update from 2.3.0-1 to 2.3.0-2

When I run "yum update vitalpbx" I get this:

One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable <repoid>
or
subscription-manager repos --disable=<repoid>

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again


ReplyQuote
mrivera
(@ing-joserivera26)
Developer Admin
Joined: 1 year ago
Posts: 998
14/03/2019 3:11 pm  

@tonywhelan first clean the yum cache, the try to update again.

yum clean all

yum update vitalpbx

ReplyQuote
tonywhelan
(@tonywhelan)
Trusted Member
Joined: 12 months ago
Posts: 65
14/03/2019 3:42 pm  

Yes, I had done that.

But "rm -rf /var/cache/yum" actually fixed the problem and I was then able to run "yum update vitalpbx" successfully.

 


ReplyQuote
Page 1 / 2
Share:
  
Working

Please Login or Register