FTP Error in FOG 1.0.1



  • I have a strange error I cannot resolve. This error occurs when downloading a kernel and it throws this error.

    FOGFTP: Failed to rename file. Remote Path: /var/www/fog/service/ipxe/backup/bzImage3.8.820140513_230733, Local Path: /var/www/fog/service/ipxe/bzImage3.8.8, Error: ftp_rename(): RNFR command failed.

    Downloading kernel 3.8.8 trying to rename to bzImage3.8.8.



  • Kernel updates are now working for me on CentOS 6.5 after installing subversion 17?? On Friday.

    These instructions were helpful:

    [url]http://fogproject.org/wiki/index.php/SVN[/url]



  • Thanks for your answer Tom.
    Now I have tried the bzImage that comes by default (3.14.3) and it works without errors.
    Thanks anyway.

    Regards.

    Frank


  • Senior Developer

    [quote=“Frank, post: 28190, member: 691”]Hi again,
    now I realized that the downloaded kernel goes to /tmp, so I can move from there to ipxe.
    Anyway my client don’t start bzImage giving a “Kernel panic - not syncing; No init found.”.
    Aaarggg!!
    Any ideas Tom? Please!

    Thanks in advance![/quote]

    What kernel are you downloading? It does go to /tmp first on your webserver, but if you’re trying to download an x86 kernel and it’s trying to boot a 64 bit init, it will cause a kernel panic because the kernel doesn’t know how to interpret the init.



  • Hi again,
    now I realized that the downloaded kernel goes to /tmp, so I can move from there to ipxe.
    Anyway my client don’t start bzImage giving a “Kernel panic - not syncing; No init found.”.
    Aaarggg!!
    Any ideas Tom? Please!

    Thanks in advance!



  • Hi Tom,
    I have ubuntu too. Where have I to put de “sudo” in?
    In case using wget to get the kernel as you suggent in the FAQ, what filename must I use to get de 39.1 kernel? I can not list them to know it. What are the rules to name them?
    Thanks in advance.

    Frank



  • FYI - currently getting a similar message under CentOS 6.5 after a message flashed briefly that the download was complete.

    FOGFTP: Failed to rename file. Remote Path: /var/www/html/fog/service/ipxe/backup/3142TEX6420140521_172900, Local Path: /var/www/html/fog/service/ipxe/3142TEX64, Error: ftp_rename(): RNFR command failed.

    -FOG Version 1.0.1
    -OS Version CentOS 6.5 (minimal install + base and a few others)
    -Apache error logs show nothing useful on this
    -Not finding applicable content on forums
    -Fresh test build on CentOS 6.5 in hopes of using GUI for Kernel updates. It is strictly a convenience. I will happily use wiki’s manual method linked in Tom’s signature if it means imaging stays working!

    Thanks for all your hard work Tom and others!!


  • Senior Developer

    That’s because, you’re choice, you’re using Ubuntu. I’m aware of the issue, but have not been able to to come up with a very elegant solution yet.

    Use the last link in my signature if you need to update your kernel.

    If I “fix” the issue so Ubuntu works, imaging becomes broken. Seeing as this software is more designed to image, I think I need to make sure that part operates before Web GUI kernel updates.



  • Ok so I have updated to Ubuntu 14.04 LTS same issues with kernel updates through the web gui.



  • I think i am going to go down the same road and install centOS



  • [quote=“Tom Elliott, post: 27263, member: 7271”]I’m not saying you should or shouldn’t. But I know it works on Centos 6.5. That said, I don’t think GUI Kernel Updating is the highest on the priority list.

    Not saying I want to keep it in a broken state, just saying there’s alternate means to update your kernel.

    For example, the last line in my signature will do it.[/quote]

    Ya I think I will just dump ubuntu and go with CentOS I am using it for Zenoss Server and working beautifully although some of the commands are diifferent than I’m use to. Thanks.


  • Senior Developer

    I’m not saying you should or shouldn’t. But I know it works on Centos 6.5. That said, I don’t think GUI Kernel Updating is the highest on the priority list.

    Not saying I want to keep it in a broken state, just saying there’s alternate means to update your kernel.

    For example, the last line in my signature will do it.



  • [quote=“Tom Elliott, post: 27090, member: 7271”]It’s because you’re running Ubuntu.[/quote]
    Should I just dump Ubuntu Server and run CentoOS?



  • [quote=“Tom Elliott, post: 27090, member: 7271”]It’s because you’re running Ubuntu.[/quote]
    I’m running ubuntu 12.04, fog 1.0.1, error logs are pointing to an error in /var/fog/management/index.php line 72 this is directly related to the kernel update through the gui.



  • [quote=“Wolfbane8653, post: 27106, member: 3362”]Seeeeeee TOOOOOMMMMMMM""""SSSSSSS [I][U][B]signature[/B][/U][/I] and update your kernals this way on Ubuntu machines!

    you may need to add [B]sudo[/B] infront of these commands[/quote]

    I tried that from the Webpage. Under FOG Configuration -> Kernel Update, there you can choose a kernel and then it asks you for the bzImage name. I think this should not work now, but later in a future update of FOG?


  • Developer

    Seeeeeee TOOOOOMMMMMMM""""SSSSSSS [I][U][B]signature[/B][/U][/I] and update your kernals this way on Ubuntu machines!

    you may need to add [B]sudo[/B] infront of these commands

    [QUOTE][SIZE=12px]Have you searched the forums for your issue yet?[/SIZE]
    [SIZE=12px]Have you checked the [/SIZE][URL=‘http://fogproject.org/wiki’][SIZE=12px]wiki[/SIZE][/URL][SIZE=12px] yet?[/SIZE]
    [SIZE=12px]Kernel Issues: [/SIZE][URL=‘http://fogproject.org/wiki/index.php/FAQ’][SIZE=12px]http://fogproject.org/wiki/index.php/FAQ[/SIZE][/URL][/QUOTE]



  • [quote=“Tom Elliott, post: 27090, member: 7271”]It’s because you’re running Ubuntu.[/quote]

    Do you mean some problem with permissions?


  • Senior Developer

    It’s because you’re running Ubuntu.



  • I can confirm this error on my side too. Tried latest revision 1687.


Log in to reply
 

364
Online

38982
Users

10712
Topics

101678
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.