[Spacewalk-list] Can't delete system from spacewalk UI

[Milan Zazrivec]

On Tuesday 31 January 2012 09:38:03 Željko Dokman wrote:
> Regards,
> I have a problem deleting systems from spacewalk UI, when I try to delete a
> system a gat this message in UI...
> 
>  "System profile xxxxxxxxxxx could not be deleted.
>  Internal Server Error
> The server experienced a problem which prevented your request from being
> filled out. It may not be possible to execute this action at this time.
> Please help us correct this problem by contacting us with details of how
> you received this message. "
> 
> Checked logs /var/log/tomcat5/catalina.out  and 
> /var/log/cobbler/cobbler.log Log entries are attached ..
> 
> A think the problem appeared after upgrade to spacewalk 1.6, I upgraded 2
> weeks ago everything seemed to work correctly, on v1.5 a was able to
> delete systems from UI .
> 
> Task Engine Status in UI - Admin tub:
> 	Cobbler Sync:	FAILED
> 	Kickstart Sync:  	FAILED
> 
> Based on log entries thread to fix the problem by doing...
> 
> run:    cobbler-setup  ## didn't  help
> 
> run:    cobbler sync
> output........
> 
> 	task started: 2012-01-30_092822_sync
> 	task started (id=Sync, time=Mon Jan 30 09:28:22 2012)
> 	running pre-sync triggers
> 	cleaning trees
> 	removing: /tftpboot/pxelinux.cfg/default
> 	removing: /tftpboot/grub/efidefault
> 	removing: /tftpboot/grub/images
> 	removing: /tftpboot/s390x/profile_list
> 	copying bootloaders
> 	copying distros
> 	copying images
> 	generating PXE configuration files
> 	cleaning link caches
> 	generating PXE menu structure
> 	running post-sync triggers
> 	running python triggers from /var/lib/cobbler/triggers/sync/post/*
> 	running python trigger cobbler.modules.sync_post_restart_services
> 	running shell triggers from /var/lib/cobbler/triggers/sync/post/*
> 	running python triggers from /var/lib/cobbler/triggers/change/*
> 	running python trigger cobbler.modules.scm_track
> 	running shell triggers from /var/lib/cobbler/triggers/change/*
> 	*** TASK COMPLETE ***
> 
> run:    cobbler check
> output......
> 
> 	1 : some network boot-loaders are missing from /var/lib/cobbler/loaders,
> you may run 'cobbler get-loaders' to download them, or, if you only want
> to handle x86/x86_64 	netbooting, you may ensure that you have installed a
> *recent* version of the syslinux package installed and can ignore this
> message entirely.  Files in this directory, 	should you want to support
> all architectures, should include pxelinux.0, menu.c32, elilo.efi, and
> yaboot. The 'cobbler get-loaders' command is the easiest way to resolve
> 	these requirements.  ###not using netbooting 2 : change 'disable' to 'no'
> in /etc/xinetd.d/tftp  ### corrected didn't help 3 : change 'disable' to
> 'no' in /etc/xinetd.d/rsync  ### corrected didn't help 4 : since iptables
> may be running, ensure 69, 80, and 25151 are unblocked  ### flushing
> iptables didn't help 5 : debmirror package is not installed, it will be
> required to manage debian deployments and repositories ##no debian systems
> 6 : The default password used by the sample templates for newly installed
> machines (default_password_crypted in /etc/cobbler/settings) is still set
> to 'cobbler' and 	should be changed, try: "openssl passwd -1 -salt
> 'random-phrase-here' 'your-password-here'" to generate new one  ##don't
> think this is the problem 7 : fencing tools were not found, and are
> required to use the (optional) power management features. install cman or
> fence-agents to use them  ###no need for  power 	management features
> 
> Please help, ran out of ideas
> 
> System info:
> Spacewalk server 1.6 and Oracle XE
> On Centos 5.7 x84
> 
> Best Regards

Please try to run

    # cobbler-setup

as root on your Spacewalk system.

-MZ