[et-mgmt-tools] Traceback on system add and distro import

Michael DeHaan mdehaan at redhat.com
Wed Oct 24 19:33:05 UTC 2007


Eric Raymond wrote:
> What occurred is that I was using the WebUI to add a system, as well as running an import media 
> command from the command line..apparently I ran out of memory, hence the "memory corruption error" during import, so it 
>
> probably couldnt allocate anymore resource to finish writing the yaml file and broke it.
>
> I will need to slow down my efforts in the future.
>   

As an added measure, I can make the non-read-only Cobbler WebUI  
commands observe cobbler's command line lock.   This seems like it would 
solve the dual-usage problem.
The RAM problem seems unrelated though -- rsync gone haywire, perhaps?



> Eric
>
> Michael DeHaan wrote:
>   
>
>     Eric Raymond wrote:
>         
>
>         Hello All,
>
>               
>
>         I am not sure what exactly happened, but it definitely seems
>         like threading issue went wrong. I was importing a distro and
>         during that time, I also added a system, but the newly added
>         system was not using the currently importing distro or
>         profile. The import bombed out with memory corruption error.
>         Then I tried to recover but found that I kept getting
>         traceback errors whenever i ran any cobbler command. I have
>         rebooted, and still cobbler is not able to run now. Before I
>         blow away my installation and try again any suggestions? 
>
>     Hmmm .... Cobbler isn't threaded. Were you using the WebUI and
>     command line at the same time? Ordinarily that should be ok,
>     though if one were to crash (still not sure why it actually
>     crashed?) while it had not yet finished writing the configuration
>     file, that would be a problem. Do you have a copy of the error
>     (traceback) you could post? 
>
> Apparently I'm blind.
>
>   
> I see the traceback and that is most certaintly coming from the parser 
> when it's trying to re-read the file, though I'm curious as to what 
> you meant by "memory corruption error".
> ------------------------------------------------------------------------
>
> _______________________________________________
> et-mgmt-tools mailing list
> et-mgmt-tools at redhat.com
> https://www.redhat.com/mailman/listinfo/et-mgmt-tools




More information about the et-mgmt-tools mailing list