Был поддержан, теперь не поддерживается ... wtf?
Форум
  1. Forums
  2. KernelCare
  3. KernelCare General Discussion
  1. Darren Wright
  2. Sunday, 12 March 2017
  3.  Subscribe via email
Hello Guys & Gals,

I am a new user to kernelcare and enabled several of our servers late last night.

Every machine was tested to make sure that they were supported by using..


wget -qq -O - https://raw.githubusercontent.com/iseletsk/kernelchecker/master/py/kc-compat.py | python


.. and we found the following..

Debain 8 - stock kernel (supported)
Debain 7 running OpenVZ deb kernel (unsupported)
CentOS 6 running OpenVZ kernel (supported)

.. anyway we installed the main supported machines which was our core stock Debian 8 machines and found this afternoon that we started getting mails saying that its now UNSUPPORTED.

We throughly tested last night that they were supported and it was clearly SUPPORTED less then a day ago and now even if we run the python test script its now changed to unsupported.

There has been no kernel updates over the past 24 hours which have been manually applied.

We have also ran..


kcarectl --check
Unknown kernel (debian 3.16.0-4-amd64), no patches available



kcare-uname -a
Linux oxygen.zonebroadband.co.uk 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 3.16.0-4-amd64 x86_64 GNU/Linux



kcarectl --info
Unknown kernel (debian 3.16.0-4-amd64), no patches available



uname -r
3.16.0-4-amd64


Last night the outputs were different mostly the "kcare-uname -a" giving a higher version (forgot what right now) so it was definitely working, however less then 24 hours later it seems its broken.

Nothing has changed our side.

Going by the other posts on your forum, seems to show that others seems to be having issues. I thought you kept these up to date very quickly.

Right now we are overly not impressed and considering we were playing to cover all 50+ servers with you, we are glad we found this out now while running the trial still.

This issue is present on all machines we randomly tested.

Deeply disappointed,

Darren
Rate this post:
  1. 13.03.2017 11:03:00
  2. # 1
Konstantin Olshanov Accepted Answer
Posts: 0
Joined: 17.11.2019
0
Votes
Undo
Hello Darren, it sounds like a bug into kc-compat, could you please describe the environment in which it was executed? Is access to patches.kernelcare.com(69.175.3.11) filtered by your firewall? Is it a virtual machine, if yes which hypervisor is used and which network card is emulated? Also please show an output of `cat /proc/version` from a server which shown as supported earlier.

We are working on support for 3.16.39-1+deb8u2, it would be added in 24 hours.
  • Page :
  • 1


There are no replies made for this post yet.
Be one of the first to reply to this post!
гость
Submit Your Response
Upload files or images for this discussion by clicking on the upload button below. Supports gif,jpg,png,zip,rar,pdf
• Insert • Remove Upload Files (Maximum File Size: 2 MB)
Captcha
To protect the site from bots and unauthorized scripts, we require that you enter the captcha codes below before posting your question.