Page 1 of 3 123 LastLast
Results 1 to 10 of 24

Thread: Kernel Panic during upgrade - some insights

Hybrid View

  1. 04-13-2012, 07:41 AM #1
    nunovi
    nunovi is offline
    Member nunovi's Avatar
    Join Date
    Sep 2011
    Location
    London
    Posts
    84

    Kernel Panic during upgrade - some insights

    Hi,

    After getting yet another kernel panic after upgrading my VB, I've decided to further dig into the problem. On my testing it seems the problem might be related to the VB Web GUI. If I install a fresh copy of VB 2.0 from around 1 month ago and perform the upgrade directly via the command line with a simple yum upgrade, the upgrade goes smoothly and the system works fine. If I upgrade via the Vortexbox Web GUI, then I get the POSTTRANS error and respective kernel panic. Now given the package generating the error is httpd, it could be that whilst on the webgui the httpd daemon is active and, as such, somehow hampers the upgrade of the package and corrupts the kernel installation.
    I have no idea how this could be solved but right now I've found the only way to reliably upgrade is via the command line.
    Worth taking a look as I've seen already people moving away from Vortexbox after their systems get bricked everytime they do an upgrade. I will also look further into this and check back if I find a solution.
    Reply With Quote Reply With Quote
  2. 04-13-2012, 08:17 AM #2
    Ron Olsen
    Ron Olsen is offline
    Administrator Ron Olsen's Avatar
    Join Date
    Dec 2009
    Location
    Boulder CO USA
    Posts
    4,953
    Brilliant insight! I believe you are correct in your analysis. This explains why I did not see the problem — I always upgrade from the command line. Also why I could find little info about this via Google — this is a VB GUI problem, not a Fedora problem.

    Perhaps the VB GUI code can be modified to exclude httpd from updates, or not update httpd and the kernel at the same time. More investigation is needed to find a fix, but at least now we know where to look.

    Thanks for figuring this out!
    Reply With Quote Reply With Quote
  3. 04-13-2012, 08:36 AM #3
    nunovi
    nunovi is offline
    Member nunovi's Avatar
    Join Date
    Sep 2011
    Location
    London
    Posts
    84
    Quote Originally Posted by Ron Olsen View Post
    Brilliant insight! I believe you are correct in your analysis. This explains why I did not see the problem — I always upgrade from the command line. Also why I could find little info about this via Google — this is a VB GUI problem, not a Fedora problem.

    Perhaps the VB GUI code can be modified to exclude httpd from updates, or not update httpd and the kernel at the same time. More investigation is needed to find a fix, but at least now we know where to look.

    Thanks for figuring this out!
    As a first approach, why not stop the httpd service, start the upgrade and then start the httpd again or reboot. This would at least avoid further bricking until a more elegant solution is found. A message would be needed to warn the webgui would be down for the upgrade.
    Reply With Quote Reply With Quote
  4. 04-13-2012, 08:41 AM #4
    garym
    garym is offline
    Senior Member
    Join Date
    Mar 2010
    Location
    United States
    Posts
    632
    So for now is the upgrade as simple as:

    Connect to vb with cryptoterm
    at command line enter
    yum upgrade

    (or is that not the exact command)
    How do I reboot from command line after above command runs.
    Location 1: VB Appliance 6TB (2.2) > LMS 7.7.2 > Transporter, Touch, Boom, Radio w/Battery (all ethernet)
    Location 2: VBA 3TB (2.2) > LMS 7.7.2 > Touch > Benchmark DAC I, Boom, Radio w/Battery (all ethernet except Radio)
    Office: Win7(64) > LMS 7.7.2 > SqueezePlay
    Spares:     VBA 4TB, SB3, Touch (3), Radio (2), CONTROLLER
    Controllers:     iPhone (iPeng), iPad (iPengHD & SqueezePad), CONTROLLER, or SqueezePlay 7.7 on Win7(64) laptop
    Files:     Ripping (FLAC) - dbpoweramp, Tagging - mp3tag, Spotify
    Reply With Quote Reply With Quote
  5. 04-13-2012, 08:48 AM #5
    nunovi
    nunovi is offline
    Member nunovi's Avatar
    Join Date
    Sep 2011
    Location
    London
    Posts
    84
    Quote Originally Posted by garym View Post
    So for now is the upgrade as simple as:

    Connect to vb with cryptoterm
    at command line enter
    yum upgrade

    (or is that not the exact command)
    How do I reboot from command line after above command runs.
    Just type reboot
    Reply With Quote Reply With Quote
  6. 04-13-2012, 08:52 AM #6
    Ron Olsen
    Ron Olsen is offline
    Administrator Ron Olsen's Avatar
    Join Date
    Dec 2009
    Location
    Boulder CO USA
    Posts
    4,953
    Quote Originally Posted by garym
    So for now is the upgrade as simple as:

    Connect to vb with cryptoterm
    at command line enter
    yum upgrade

    (or is that not the exact command)
    How do I reboot from command line after above command runs.
    The way to upgrade from the command line is
    Code:
    yum clean all; yum update
    A reboot is only needed if the update installed a new kernel – look for an install of the kernel-PAE package.

    To reboot, enter
    Code:
    reboot
    If you're doing this from a remote login, "reboot" will close the session. You'll have to wait for the VB to complete the reboot before you can login remotely again.
    Reply With Quote Reply With Quote
  7. 04-13-2012, 07:13 PM #7
    rgro
    rgro is offline
    Senior Member
    Join Date
    Nov 2010
    Posts
    175
    May I humbly suggest that, until there is a permanent fix for this issue, this be made a sticky??

    rgro


    Quote Originally Posted by Ron Olsen View Post
    The way to upgrade from the command line is
    Code:
    yum clean all; yum update
    A reboot is only needed if the update installed a new kernel – look for an install of the kernel-PAE package.

    To reboot, enter
    Code:
    reboot
    If you're doing this from a remote login, "reboot" will close the session. You'll have to wait for the VB to complete the reboot before you can login remotely again.
    Reply With Quote Reply With Quote
  8. 04-13-2012, 09:08 PM #8
    Ron Olsen
    Ron Olsen is offline
    Administrator Ron Olsen's Avatar
    Join Date
    Dec 2009
    Location
    Boulder CO USA
    Posts
    4,953
    Quote Originally Posted by Ron Olsen View Post
    The way to upgrade from the command line is
    Code:
    yum clean all; yum update
    A reboot is only needed if the update installed a new kernel – look for an install of the kernel-PAE package.

    To reboot, enter
    Code:
    reboot
    If you're doing this from a remote login, "reboot" will close the session. You'll have to wait for the VB to complete the reboot before you can login remotely again.
    Quote Originally Posted by rgro View Post
    May I humbly suggest that, until there is a permanent fix for this issue, this be made a sticky??

    rgro
    Good idea; see http://vortexbox.org/threads/3691-Ho...e-Command-Line
    Reply With Quote Reply With Quote
  9. 04-13-2012, 08:46 AM #9
    Ron Olsen
    Ron Olsen is offline
    Administrator Ron Olsen's Avatar
    Join Date
    Dec 2009
    Location
    Boulder CO USA
    Posts
    4,953
    Quote Originally Posted by nunovi
    As a first approach, why not stop the httpd service, start the upgrade and then start the httpd again or reboot. This would at least avoid further bricking until a more elegant solution is found. A message would be needed to warn the webgui would be down for the upgrade.
    If you want to experiment, the code to modify is in /opt/vortexbox/doaction.sh, in the Upgrade section.
    Reply With Quote Reply With Quote
  10. 04-13-2012, 02:45 PM #10
    radish112
    radish112 is offline
    Member
    Join Date
    Nov 2010
    Posts
    86
    nunovi,

    Brilliant! After having experienced many kernel (and personal) panics over the last couple of upgrades via the VBA GUI, I just did a painless upgrade using the command line option, and all's right with the world (well...the audio part anyway).

    Many thanks for the clear thinking and excellent tip.

    Rad
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules