Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-65

FIWARE.Request.Lab.Spain.Re: RV: Another different issue.

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: Sprint 4.1.1
    • Component/s: FIWARE-LAB-HELP
    • Labels:
      None

      Description

      Hi Raul,

      Thanks for writing us, but I'd like to recommend you to keep the list in
      CC when you report problems.

      As you told us, you did a "do-release-upgrade" which may look like a
      good idea, but it may cause some problems. Specially if the update isn't
      well done. –

      When booting your VM, we can see that there is a kernel panic booting
      the Image. So I mounted the image and I saw that the Ramdisk image for
      your new kernel has NOT been generated by the update. - This means that
      a new image for the new kernel must be generated.

      I booted your VM with a previous kernel, and as you are the root user,
      you must finish the upgrade of your Ubuntu. I can think of serveral
      options, buy

      (a) – Removing and reinstalling the latest kernel package:
      linux-image-3.13.0-24-generic (or whatever your kernel is). I don't
      know if this will work.
      (b) – Generating your a new image and updating the grub with some
      commands like (this example works in my laptop):
      sudo update-initramfs -c -k 3.13.0-24-generic
      sudo update-grub

      Hope this helps. - And don't forget to CC the list.

      Best regards,
      José Ignacio.

      El 27/05/14 15:34, HENAR MUÑOZ FRUTOS escribió:
      >
      > ----Mensaje original----
      > De: Raul Tavares - Full IT rtavares@fullit.pt
      > Enviado el: martes, 27 de mayo de 2014 15:25
      > Para: HENAR MUÑOZ FRUTOS
      > Asunto: Another different issue
      >
      > Hello again Henar.
      >
      > Sorry disturbing you again, but I've got another issue - different one, that time.
      >
      > In my account rtavares@gmail.com - project "ID00...003171" - I have an instance Ubuntu with ip's 10.0.1.138 / 130.206.83.33.
      >
      > I've updated the machine - by system recommendation - to version 14.04, with command "do-release-upgrade".
      >
      > Now I cannot access the machine, by ssh -i nor it's web pages - http://130.206.83.33.
      >
      > I've already rebooted the machine several times, accessing Cloud through Mac OS X Safari.
      >
      > Any advice?
      >
      > Tks
      >
      > Bst Rgds
      > Raul
      >
      >

      ________________________________

      Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
      This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
      http://www.tid.es/ES/PAGINAS/disclaimer.aspx
      _______________________________________________
      Fiware-lab-help mailing list
      Fiware-lab-help@lists.fi-ware.org
      https://lists.fi-ware.org/listinfo/fiware-lab-help

        Activity

        Hide
        FIWARE-LAB-HELP FIWARE-LAB-HELP added a comment -

        Hi José.

        Thank you for your quick answer.

        And yes, it looked a good idea!....

        I'm going to check your suggestions.

        And yes, I will take the care of addressing the list in my issues.

        Tks

        Bst Rgds

        R Tavares

        2014-05-27 15:52 GMT+01:00 José Ignacio Carretero Guarde <jicg@tid.es>:

        > Hi Raul,
        >
        > Thanks for writing us, but I'd like to recommend you to keep the list in
        > CC when you report problems.
        >
        > As you told us, you did a "do-release-upgrade" which may look like a
        > good idea, but it may cause some problems. Specially if the update isn't
        > well done. –
        >
        > When booting your VM, we can see that there is a kernel panic booting
        > the Image. So I mounted the image and I saw that the Ramdisk image for
        > your new kernel has NOT been generated by the update. - This means that
        > a new image for the new kernel must be generated.
        >
        > I booted your VM with a previous kernel, and as you are the root user,
        > you must finish the upgrade of your Ubuntu. I can think of serveral
        > options, buy
        >
        > (a) – Removing and reinstalling the latest kernel package:
        > linux-image-3.13.0-24-generic (or whatever your kernel is). I don't
        > know if this will work.
        > (b) – Generating your a new image and updating the grub with some
        > commands like (this example works in my laptop):
        > sudo update-initramfs -c -k 3.13.0-24-generic
        > sudo update-grub
        >
        > Hope this helps. - And don't forget to CC the list.
        >
        > Best regards,
        > José Ignacio.
        >
        >
        > El 27/05/14 15:34, HENAR MUÑOZ FRUTOS escribió:
        >
        >>
        >> ----Mensaje original----
        >> De: Raul Tavares - Full IT rtavares@fullit.pt
        >> Enviado el: martes, 27 de mayo de 2014 15:25
        >> Para: HENAR MUÑOZ FRUTOS
        >> Asunto: Another different issue
        >>
        >> Hello again Henar.
        >>
        >> Sorry disturbing you again, but I've got another issue - different one,
        >> that time.
        >>
        >> In my account rtavares@gmail.com - project "ID00...003171" - I have an
        >> instance Ubuntu with ip's 10.0.1.138 / 130.206.83.33.
        >>
        >> I've updated the machine - by system recommendation - to version 14.04,
        >> with command "do-release-upgrade".
        >>
        >> Now I cannot access the machine, by ssh -i nor it's web pages -
        >> http://130.206.83.33.
        >>
        >> I've already rebooted the machine several times, accessing Cloud through
        >> Mac OS X Safari.
        >>
        >> Any advice?
        >>
        >> Tks
        >>
        >> Bst Rgds
        >> Raul
        >>
        >>
        >>
        >
        > ________________________________
        >
        > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
        > nuestra política de envío y recepción de correo electrónico en el enlace
        > situado más abajo.
        > This message is intended exclusively for its addressee. We only send and
        > receive email on the basis of the terms set out at:
        > http://www.tid.es/ES/PAGINAS/disclaimer.aspx
        >


        Muito grato pela atenção.

        Com os melhores cumprimentos,

        Raul Tavares

        Contactos: Telemóvel: 913 652 668
        e-mail: rtavares@gmail.com

        Skype: rfdtavares

        _______________________________________________
        Fiware-lab-help mailing list
        Fiware-lab-help@lists.fi-ware.org
        https://lists.fi-ware.org/listinfo/fiware-lab-help

        Show
        FIWARE-LAB-HELP FIWARE-LAB-HELP added a comment - Hi José. Thank you for your quick answer. And yes, it looked a good idea!.... I'm going to check your suggestions. And yes, I will take the care of addressing the list in my issues. Tks Bst Rgds R Tavares 2014-05-27 15:52 GMT+01:00 José Ignacio Carretero Guarde <jicg@tid.es>: > Hi Raul, > > Thanks for writing us, but I'd like to recommend you to keep the list in > CC when you report problems. > > As you told us, you did a "do-release-upgrade" which may look like a > good idea, but it may cause some problems. Specially if the update isn't > well done. – > > When booting your VM, we can see that there is a kernel panic booting > the Image. So I mounted the image and I saw that the Ramdisk image for > your new kernel has NOT been generated by the update. - This means that > a new image for the new kernel must be generated. > > I booted your VM with a previous kernel, and as you are the root user, > you must finish the upgrade of your Ubuntu. I can think of serveral > options, buy > > (a) – Removing and reinstalling the latest kernel package: > linux-image-3.13.0-24-generic (or whatever your kernel is). I don't > know if this will work. > (b) – Generating your a new image and updating the grub with some > commands like (this example works in my laptop): > sudo update-initramfs -c -k 3.13.0-24-generic > sudo update-grub > > Hope this helps. - And don't forget to CC the list. > > Best regards, > José Ignacio. > > > El 27/05/14 15:34, HENAR MUÑOZ FRUTOS escribió: > >> >> ---- Mensaje original ---- >> De: Raul Tavares - Full IT rtavares@fullit.pt >> Enviado el: martes, 27 de mayo de 2014 15:25 >> Para: HENAR MUÑOZ FRUTOS >> Asunto: Another different issue >> >> Hello again Henar. >> >> Sorry disturbing you again, but I've got another issue - different one, >> that time. >> >> In my account rtavares@gmail.com - project "ID00...003171" - I have an >> instance Ubuntu with ip's 10.0.1.138 / 130.206.83.33. >> >> I've updated the machine - by system recommendation - to version 14.04, >> with command "do-release-upgrade". >> >> Now I cannot access the machine, by ssh -i nor it's web pages - >> http://130.206.83.33 . >> >> I've already rebooted the machine several times, accessing Cloud through >> Mac OS X Safari. >> >> Any advice? >> >> Tks >> >> Bst Rgds >> Raul >> >> >> > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra política de envío y recepción de correo electrónico en el enlace > situado más abajo. > This message is intended exclusively for its addressee. We only send and > receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > – Muito grato pela atenção. Com os melhores cumprimentos, Raul Tavares Contactos: Telemóvel: 913 652 668 e-mail: rtavares@gmail.com Skype: rfdtavares _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help

          People

          • Assignee:
            jicg José Ignacio Carretero Guarde
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: