Created attachment 446772 [details] related lines of the tomcat log Description of problem: I have tried to enable the Enable Monitoring Scout checkbox but I got an Internal Server error message Version-Release number of selected component (if applicable): 1.1 How reproducible: Just try to update ANY tab in the Spacewalk configuration menu. Related tomcat logs attached
From the logs, it looks like your sudo is not setup correctly. It should contain the following: ## RHN specifics ## Cmnd_Alias CONFIG_RHN = /usr/sbin/rhn-sat-restart-silent,\ /usr/bin/rhn-config-satellite.pl,\ /usr/bin/rhn-satellite-activate,\ /usr/bin/rhn-bootstrap,\ /usr/bin/rhn-load-ssl-cert.pl,\ /usr/bin/rhn-ssl-tool,\ /etc/rc.d/np.d/step Monitoring install,\ /etc/rc.d/np.d/step MonitoringScout install,\ /etc/rc.d/np.d/step Monitoring uninstall,\ /etc/rc.d/np.d/step MonitoringScout uninstall,\ /sbin/service Monitoring restart,\ /sbin/service MonitoringScout restart,\ /sbin/service taskomatic restart # The CONFIG_RHN commands are required for reconfiguration of a # running RHN Satellite. They should be enabled for proper operation # of the RHN Satellite. apache ALL=(root) NOPASSWD: CONFIG_RHN tomcat ALL=(root) NOPASSWD: CONFIG_RHN Does this work for you?
Hi, You are right! Sorry about the BUG report. I overwrote the sudoers file of the spacewalk server with a common linux configuration channel. Thanks for the help, Balazs
Mass-aligning under space12, so that we don't lose track of this bugzilla. This however does not mean that we plan (will be able to) address this bug in Spacewalk 1.2.
Mass-moving to space13.
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.
Aligning under space16.