possibly my fault, but after the new 5.2 auto update, i decided to yum -y update and after a reboot, ruby refused to start.
a simple "gem install -v=2.3.4 rails" brought it back. just a heads up for anybody.
f12_x64
5.2 update issue? ruby on rails
Re: 5.2 update issue? ruby on rails
Thanks, I did a yum update because the mount information in phpsysinfo did not show.
after the update, still not working. After a reboot I got the ruby error.
your solution "gem install -v=2.3.4 rails" helped me and guess what? mount information in phpsysinfo is also showing again
after the update, still not working. After a reboot I got the ruby error.
your solution "gem install -v=2.3.4 rails" helped me and guess what? mount information in phpsysinfo is also showing again
Re: 5.2 update issue? ruby on rails
yes, this was an upstream update issue. only occurs to systems that get updated.
and the 5.2 platform update ought to have fixed this, but it's not too reliable: a fraction of users who updated still had this issue. we need to work to make amahi more resilient to this.
and the 5.2 platform update ought to have fixed this, but it's not too reliable: a fraction of users who updated still had this issue. we need to work to make amahi more resilient to this.
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 8GB RAM, 1TBx2+3TBx1
Who is online
Users browsing this forum: No registered users and 93 guests