 |
 |
Hi, The "Kernel Panic" issue is non-blocking right-now for John due to machine automated reboot, but we have to solve it to target a stable production system. With Yvan, we're converging on next update for the cluster: - on my side I update Qserv metadata on ccqserv100 w.r.t. new Qserv metadata format, and then I test Docker+Qserv on ccqserv100->ccqserv124, - then CC-IN2P3 team launches a upgrade of the kernel to kernel-ml ( "*m*ain*l*ine stable" branch of The Linux Kernel Archives <http://kernel.org>) on ccqserv100->ccqserv124, this could be done in January, - I control Qserv behaviour is still the same than before, - then Qserv developpers can use this cluster to see if "Kernel Panic' issue is solved. If it work we'll update to kernel-ml on ccqserv125->ccqserv149, if it doesn't, cc-in2p3 and Qserv developpers will have to find an other solution. Regards, Fabrice ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the QSERV-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1