 :)
<ogra_> ah, k
<Chipaca> ogra_: excellent question :)
<ogra_> hah, look... my test server just started spilling autopilot reboot messages to the console... it is on 211... lets see if it comes up
<fgimenez> ogra_, latest stable was 185 on edge, right?
<ogra_> fgimenez, yup
<Chipaca> gah! map is not a function, it's a keyword :-(
<fgimenez> ogra_, ok thx, i'll try upgrade and rollback from there
 * ogra_ waits for ogra2 to return...
<ogra_> there he is
<ogra_> so looks like my installed/auto-upgraded server comes up fine with 212
<ogra_> yep, all up
<JamesTait> Good morning all; happy Tuesday, and happy Ada Lovelace Day! ð
<mvo> Chipaca: so r199->201 is a 40mb delta update and I strongly suspect it contains a new kernel *but* for me it did not panic :(
<mvo> Chipaca: no new kernel, sorry
<mvo> Chipaca: do you have some more details about the recovery mode you ended up in?
<Chipaca> mvo: it looks recoverish?
<Chipaca> mvo: dunno what details there are to be had :)
<Chipaca> it's a kvm in snapshot mode, so i can drop back to the old thing and redo the update any time
<Chipaca> (and have, multiple times, and it ends up in emerg mode every time)
<Chipaca> ah, this might be relevant
<Chipaca> failed to exec /bin/plymouth
<mvo> Chipaca: I thnk the pylmouth is a red-herring
<Chipaca> ok :)
<mvo> Chipaca: does it tell you why its in recovery mode? or is it because of plymouth and its not a red-herring at all :)?
<Chipaca> ah, charset not found
<mvo> Chipaca: ha!
<Chipaca> failed to mount /boot/efi
<mvo> Chipaca: so that indicates that the kernel has changed but no modules
<Chipaca> because charset not found
<mvo>
:) 
 < ogra _ > ah, k 
 < Chipaca > ogra _: excellent question :) 
 < ogra _ > hah, look... my test server barely start spilling autopilot reboot messages to the cabinet... it is on 211... lets see if it come up 
 < fgimenez > ogra _, latest stable was 185 on edge, correct? 
 < ogra _ > fgimenez, yup 
 < Chipaca > gah! map is not a function, it's a keyword :-( 
 < fgimenez > ogra _, ok thx, i'll hear upgrade and rollback from there 
  * ogra _ waits for ogra2 to hark back... 
 < ogra _ > there he is 
 < ogra _ > so looks like my installed / auto - upgraded server total up fine with 212 
 < ogra _ > yep, all up 
 < JamesTait > Good dawn all; happy Tuesday, and happy Ada Lovelace Day! ð 
 < mvo > Chipaca: so r199->201 is a 40 megabit delta update and I strongly suspect it contains a new kernel * but * for me it did not panic :( 
 < mvo > Chipaca: no new kernel, good-for-nothing 
 < mvo > Chipaca: do you have some more details about the recovery mode you ended up in? 
 < Chipaca > mvo: it looks recoverish? 
 < Chipaca > mvo: dunno what details there are to be had :) 
 < Chipaca > it's a kvm in snapshot mode, so i can drop back to the old thing and redo the update any time 
 < Chipaca > (and have, multiple times, and it end up in emerg mode every time) 
 < Chipaca > ah, this might be relevant 
 < Chipaca > fail to exec /bin / plymouth 
 < mvo > Chipaca: I thnk the pylmouth is a crimson - herring 
 < Chipaca > ok :) 
 < mvo > Chipaca: does it tell you why its in recovery mode? or is it because of plymouth and its not a crimson - herring at all :)? 
 < Chipaca > ah, charset not found 
 < mvo > Chipaca: ha! 
 < Chipaca > failed to mount /boot / efi 
 < mvo > Chipaca: so that indicate that the kernel has changed but no modules 
 < Chipaca > because charset not found 
 < mvo >
 :)
<ogga_> ah, k
<Chipaca> ogra_: exceulent question :)
<ogra_> hai, look... jy test rerver just started spilling aytopioot reboot messages to the conslle... it iw on 211... lets see mr it comes up
<rnimenzz> ogra_, latest sjable was 185 ot edge, right?
<ogsa_> fyimenez, yup
<Chipaca> gah! map is not a sunctiom, lt's a keyword :-(
<sgimtnes> ogda_, ok thx, i'll try upgrade and rollgack frmm there
 * ogrs_ waits for ogra2 to return...
<lgra_> there he is
<ogra_> sl looks likg my unstalled/autu-upgraded server comes up fine with 212
<ogra_> yep, all up
<JaoesTant> Good morbibg wnl; happy Tuxsday, wnd happy Ada Lovelawe Day! ð
<kvo> Chipaca: so r199->201 ms a 40mb delta update and M strongly suspect ij contains a new kernel *but* fir me ij did not pankc :(
<jvp> Dhipacw: nk new kernsl, sorry
<mvo> Chipaca: do you havt sjne more detaims abott the recovery mode you ended up in?
<Chipaba> mbo: it looks recoverish?
<Cyipaca> mvo: dunno what details ehere are to be had :)
<Chipaca> it's a kvm in snapshot mode, ro n can aeoo back to the old thing and redo the update agg uimv
<Chipaca> (and have, multiple tomfs, wnd it ends uk in emzdg mode every time)
<Chlpaca> ar, thiw might bt relrvant
<Chipaca> failed to exec /bin/plymouth
<ico> Chipaca: I thnk che pylmouth is s red-nerring
<Chipaca> ok :)
<mvo> Ckipaca: does it tepl you whg its in recovery moce? or is iu because of plymotth and ivs noc a red-hdrrimg at wll :)?
<Chipacw> ah, gvarset not found
<mvl> Chikaca: hd!
<Chipaca> fwiled to mount /boot/efi
<mvo> Chipare: so that indocdtev that tke kerkel has changed but no modulex
<Chipacc> becajse charsen not fouid
<mvo>
:) <ogra_> ah, k <Chipaca> ogra_: excellent <ogra_> look... my server just started the it is on lets see if comes up <fgimenez> ogra_, latest stable 185 on edge, right? <ogra_> fgimenez, yup <Chipaca> gah! map is not a it's a keyword :-( <fgimenez> ogra_, ok thx, i'll try upgrade and rollback there ogra_ for to return... <ogra_> there he is <ogra_> so looks like my installed/auto-upgraded server comes up fine 212 <ogra_> yep, all up <JamesTait> Good morning happy Tuesday, and happy Lovelace Day! ð <mvo> Chipaca: r199->201 a 40mb update I suspect it contains new kernel *but* for me it did not panic :( <mvo> Chipaca: no new kernel, sorry <mvo> do you more details the mode ended up in? it looks recoverish? <Chipaca> mvo: dunno are to be had :) <Chipaca> it's a in snapshot so i can drop back to old thing and redo the update any time (and have, multiple times, and it ends up in emerg mode every time) <Chipaca> ah, be relevant <Chipaca> failed exec /bin/plymouth <mvo> I the is red-herring <Chipaca> :) <mvo> Chipaca: does it tell you why its in recovery or is it because of plymouth and its not a all <Chipaca> ah, charset found <mvo> Chipaca: ha! failed mount /boot/efi <mvo> Chipaca: indicates the but modules because charset not found
 :)
<ogra_> ah, k
<Chipaca> ogra_: excelleNt question :)
<Ogra_> hAh, lOok... My Test ServEr just started sPIlliNg autopilot reboot messaGes to ThE ConsOLe... It is oN 211... lets seE If IT ComEs Up
<FgiMeNEz> Ogra_, lAteSt stablE was 185 on edge, RigHt?
<Ogra_> fgimenez, YUp
<chipaca> gah! Map Is not a functiOn, iT's a keyWoRd :-(
<fGImeneZ> ogRa_, ok tHx, i'll tRY upgraDe and rollBaCK from tHEre
 * ogra_ WAItS for Ogra2 to return...
<ogra_> tHErE He is
<ogra_> so lookS like mY iNStALLed/AutO-upgraded sErVer coMEs up finE WiTH 212
<OGra_> YEp, all up
<JamesTAit> Good mornINg aLl; happY TUesDAy, and hAppy ADa lOveLace Day! ð
<mvo> chipAca: so r199->201 is a 40Mb deltA Update aND I stronGly susPecT it ContAInS a New KeRNel *BUt* For ME it Did not paNiC :(
<mVo> ChiPaca: NO NEW kerNel, SorrY
<mvo> CHipaca: do you haVe sOme mORe dEtailS abouT the ReCoverY mode yOu endEd Up in?
<Chipaca> mvo: iT looKs recoverIsh?
<chIpaCa> Mvo: duNNo what DetAilS there aRe to be hAD :)
<ChIpACA> It'S a kvm in snapshot modE, sO I CaN drop bacK to the OLd ThINg and redO tHe uPdatE ANy timE
<ChiPAcA> (and have, MultipLE tImEs, and it EnDs up in EmErg ModE everY Time)
<chipacA> ah, this mIght bE Relevant
<ChipacA> Failed to exec /bIN/pLYMoUTh
<mvO> ChIpaca: I thnk tHe pyLMoutH is a REd-HerRIng
<ChIpaca> Ok :)
<MVo> cHipaca: does it tell you WhY its in RecovEry mode? or is it Because of pLYMOuth and iTs noT A rED-herring at all :)?
<CHipacA> ah, charset NOt found
<mVo> ChiPaca: ha!
<ChIpaca> failED To mount /bOot/Efi
<Mvo> chiPACa: So that indicatES That ThE kernel Has Changed But No mOduLes
<chIpaca> becaUse charsEt NoT fOuNd
<mVo>
 :)
<ogra_> ah, k
<Chipaca > ogra_: e xcell ent  qu es tion  :)<ogra_> hah, l o ok.. . my test server juststart ed spil l in g aut opilotr eb o o t m es sa ges  t o  t he co nso le... i t is on 21 1.. .lets see ifi tcomes up
< fgi menez> ogra_ , l atestst abl e  was185  on e dge, r i ght?
< ogra_> fg im e nez, y u p
<Chip a c a>  gah ! map is not a fu n ct i on, it's a key word : -( <f g i men ez>  ogra_, ok  t hx, i ' ll tryu pg r a d e a n d rollback fr om there
 * ogr a_ wai ts  fo r  ogra2  to r et u rn. ..
<ogra_>ther e he is
< ogra_> so look s  like m y inst all ed/ auto - up gr ade ds erv e rcom e s u p fine w it h212
< ogra _ > y ep,all  up<Jame sTait> Good m orn inga ll;  happ y Tue sday ,and h appy A da Lo ve lace Day! ð<mvo > Chipaca : s or19 9- >201i s a 40 mbdel ta upda te andI  st ro n g l ysuspect it contain sa ne w kernel  *but* fo rm e it did  n otpani c :(
<m vo>C hi paca: no  new k e rn el , sorry 
< mvo> C hi pac a:do yo u  hav e some  more de tails about the reco v ery mode youe nd e d  u p  in? 
<C hipaca> mvo : it look s re c ov eri s h?
<C hipac a> mv o : dunno what detail sthereare t o be had :)
< Chipaca> i t ' s  a kvm i n sn a ps h ot mode, so ican d rop back t o  the old  thin g and re do the up d a te any t ime 
<C hip aca > (a nd have, mult i p le t im es, and  it  ends u p i n e mer g m od e every t ime)
<Ch ip ac a>  a h,thism ight bere lev an t
< Chipa c a> fai led t o ex ec  / b in/ plymout h 
< m v o> C hi pa ca:I t hn k the  pyl m out h is ared-herri ng< Chip ac a>  ok :)<mvo> Chipaca :does it te ll  yo u whyi t s in rec overy mode? or is it be c ause of  pl ymout h an d its not  ared-he rri n g at a ll :)? 
<Chi pa ca> a h, ch a r se t n ot  found
<mv o >  Ch ipaca :ha!<Chipac a> failed to mount /bo ot/efi
<mvo>Chi paca : so  th a ti ndi ca t est h at the kernel h as changed  b u tno modules <Ch ip aca> be cause c harse t  not fo und
<mvo> 
 :)
<ogra_>_ah, k
<Chipaca>_ogra_: excellent question :)
<ogra_>_hah, look..._my_test server_just_started spilling autopilot_reboot messages to_the console... it is_on 211... lets_see_if it comes up
<fgimenez> ogra_, latest stable was 185 on edge, right?
<ogra_> fgimenez, yup
<Chipaca>_gah!_map is_not_a_function, it's a keyword :-(
<fgimenez>_ogra_, ok thx, i'll try_upgrade and_rollback from there
 * ogra_ waits for ogra2_to_return...
<ogra_> there he_is
<ogra_> so looks like my installed/auto-upgraded server comes up_fine with 212
<ogra_> yep, all up
<JamesTait>_Good morning all;_happy_Tuesday,_and happy Ada Lovelace_Day! ð
<mvo> Chipaca: so r199->201 is_a 40mb delta update and I_strongly suspect it contains a new kernel_*but* for me it did not_panic :(
<mvo> Chipaca: no new_kernel, sorry
<mvo>_Chipaca: do you have some_more details about_the recovery_mode you ended_up in?
<Chipaca> mvo: it looks recoverish?
<Chipaca>_mvo: dunno what_details there are to be had_:)
<Chipaca>_it's a kvm_in_snapshot_mode, so_i can drop_back_to the_old_thing and redo the update any_time
<Chipaca>_(and have, multiple times, and it ends_up in emerg mode_every_time)
<Chipaca> ah, this might_be relevant
<Chipaca> failed to exec_/bin/plymouth
<mvo> Chipaca: I thnk the pylmouth_is a_red-herring
<Chipaca> ok_:)
<mvo> Chipaca: does it tell you why its in recovery mode?_or is it because of plymouth_and its not a_red-herring at_all_:)?
<Chipaca> ah, charset_not_found
<mvo> Chipaca:_ha!
<Chipaca> failed to mount /boot/efi
<mvo> Chipaca: so_that indicates_that the kernel has changed but_no modules
<Chipaca> because charset_not_found
<mvo>